From e35fca3d367a6294123a0d9a2c077f4db7dfe809 Mon Sep 17 00:00:00 2001 From: varac Date: Thu, 12 May 2016 13:59:13 +0200 Subject: [feat] catch abnormal proc termination in syslog 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 --- puppet/modules/site_check_mk/files/agent/logwatch/syslog_tail.cfg | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'puppet/modules/site_check_mk') diff --git a/puppet/modules/site_check_mk/files/agent/logwatch/syslog_tail.cfg b/puppet/modules/site_check_mk/files/agent/logwatch/syslog_tail.cfg index 71395c50..7daf0cac 100644 --- a/puppet/modules/site_check_mk/files/agent/logwatch/syslog_tail.cfg +++ b/puppet/modules/site_check_mk/files/agent/logwatch/syslog_tail.cfg @@ -15,3 +15,7 @@ # 401 Unauthorized error logged by webapp and possible other # applications C Unauthorized +# catch abnormal termination of processes (due to segfault/fpe +# signals etc). +# see https://github.com/pixelated/pixelated-user-agent/issues/683 + C systemd.*: main process exited, code=killed, status= -- cgit v1.2.3