leap_platform.git/puppet/modules/site_check_mk/files/agent, branch master

webapp: alert on 409 responses

2017-11-08T08:13:46+00:00

They might be meaningful response codes for some scenarios. But
so far we are not conciously sending them out. If they occur that
is because we handed them down from couch. So we might want to
fix the underlying issue. Couch 409s should be caught by the webapp
and handled there.

ignore noisy 401 errors from soledad log.

2016-08-20T13:37:18+00:00

Change-Id: Ia1764cb28e263353856523c11f351a39774bf3b4

Remove bigcouch (#8056)

2016-06-30T13:41:19+00:00

Change-Id: I0c6e27298c63bd37de1410985d054799818c22a4

[feat] catch abnormal proc termination in syslog

2016-05-12T11:59:13+00:00

Sometimes a floating point exception or segfault of
a process results in systemd restarting it, we want
to recognize this from the syslog
i.e.:

  systemd[1]: pixelated-server.service: main process exited,
  code=killed, status=8/FPE
  systemd[1]: Unit pixelated-server.service entered failed state.

- Related: https://github.com/pixelated/pixelated-user-agent/issues/683

check_mk: monitor webapp log for response code 500

2016-04-03T14:06:23+00:00

[bug] Fix couch_stats script

2016-03-31T19:30:03+00:00

It failed to calculate the sessions and tokens db names.

- Resolves: #7658

Switch from 'vmail' to leap-mx's user/group (#6936, #7639)

2015-12-01T15:12:47+00:00

This change will make sure that the user/group for leap-mx exist, and it
changes the mail location from /var/mail/vmail to the more helpful name
/var/mail/leap-mx.

This change requires:

https://github.com/leapcode/leap_mx/pull/78

and it would replace merge request:

https://github.com/leapcode/leap_mx/pull/65

and fix https://leap.se/code/issues/6936 and
https://leap.se/code/issues/7635

Change-Id: Idbe678dc999e394232c2eeef2b2018d39ab7cc3b

[bug] Add bigcouch syslog snippet for logwatch

2015-10-31T19:03:28+00:00

[feat] remove tapicero leftovers

2015-10-06T09:07:35+00:00

Soledad now creates user-dbs, which has been done by tapicero
in the past. we need to remove any leftovers from tapicero.

Ignore openvpn logwatch warnings (#6867)

2015-07-07T14:04:40+00:00

These are warnings that might have different origins, each of
them we don't want to alarm the admin:

- A bitmask client bug (user will poke the client devs if things
  break, and they will go after it)
- A simple network failure, packets might get cut of
- Malicious user tries to temper with TLS handshakes - this gets
  more interesting, but still (like ssh bruteforce attacs) an admin
  would not want to get annoyed by this by default, but they still
  have the option to use log analysers of their choice if they want
  to investigate this.

Change-Id: I23ca3b700e41f22f34ad3346ed4e647b86000bb2