- Syslog-critical - Mailman suite of Computer Science Department

syslog-critical alerts
by cron/syslog01.cs.umd.edu 12 Oct '26

12 Oct '26

Command: /usr/local/sbin/syslog-ntfy-alert.py Time : 0.0598s Status : exited 0 Output : {"id":"PDuHibdwOCoR","time":1791819002,"expires":1791862202,"event":"message","topic":"syslog-critical-8Ufx3eD1","title":"Service failed on abuse","message":"Oct 12 11:28:03 abuse systemd[1]: Unit pmie_check.service entered failed state.","priority":3,"tags":["warning"]} Service failed on abuse Oct 12 11:28:03 abuse systemd[1]: Unit pmie_check.service entered failed state.

1 0

syslog-critical alerts
by cron/syslog01.cs.umd.edu 12 Oct '26

12 Oct '26

Command: /usr/local/sbin/syslog-ntfy-alert.py Time : 0.0603s Status : exited 0 Output : {"id":"k2tBRnWIe36l","time":1791817201,"expires":1791860401,"event":"message","topic":"syslog-critical-8Ufx3eD1","title":"Service failed on idmh1","message":"Oct 12 10:59:24 idmh1 systemd[1]: check-named-alive.service: Failed with result 'exit-code'.","priority":3,"tags":["warning"]} Service failed on idmh1 Oct 12 10:59:24 idmh1 systemd[1]: check-named-alive.service: Failed with result 'exit-code'.

1 0

syslog-critical alerts
by cron/syslog01.cs.umd.edu 12 Oct '26

12 Oct '26

Command: /usr/local/sbin/syslog-ntfy-alert.py Time : 0.0598s Status : exited 0 Output : {"id":"gDWxWEYPrnu6","time":1791816961,"expires":1791860161,"event":"message","topic":"syslog-critical-8Ufx3eD1","title":"Service failed on abuse","message":"Oct 12 10:55:01 abuse systemd[1]: Unit pmlogger_check.service entered failed state.","priority":3,"tags":["warning"]} Service failed on abuse Oct 12 10:55:01 abuse systemd[1]: Unit pmlogger_check.service entered failed state.

1 0

syslog-critical alerts
by cron/syslog01.cs.umd.edu 12 Oct '26

12 Oct '26

Command: /usr/local/sbin/syslog-ntfy-alert.py Time : 0.0601s Status : exited 0 Output : {"id":"ipk6utfzoX7p","time":1791816722,"expires":1791859922,"event":"message","topic":"syslog-critical-8Ufx3eD1","title":"Service failed on submit26-b9-3","message":"Sep 14 19:27:02 submit26-b9-3 systemd[1]: user(a)1001.service: Failed with result 'signal'.","priority":3,"tags":["warning"]} Service failed on submit26-b9-3 Sep 14 19:27:02 submit26-b9-3 systemd[1]: user(a)1001.service: Failed with result 'signal'.

1 0

syslog-critical alerts
by cron/syslog01.cs.umd.edu 12 Oct '26

12 Oct '26

Command: /usr/local/sbin/syslog-ntfy-alert.py Time : 0.0602s Status : exited 0 Output : {"id":"OnuFZnCDXnbK","time":1791815641,"expires":1791858841,"event":"message","topic":"syslog-critical-8Ufx3eD1","title":"Service failed on idmp0","message":"Oct 12 10:32:43 idmp0 systemd[1]: NetworkManager-wait-online.service: Failed with result 'exit-code'.","priority":3,"tags":["warning"]} Service failed on idmp0 Oct 12 10:32:43 idmp0 systemd[1]: NetworkManager-wait-online.service: Failed with result 'exit-code'.

1 0

syslog-critical alerts
by cron/syslog01.cs.umd.edu 12 Oct '26

12 Oct '26

Command: /usr/local/sbin/syslog-ntfy-alert.py Time : 0.0601s Status : exited 0 Output : {"id":"DBmV2FSHdH5j","time":1791815522,"expires":1791858722,"event":"message","topic":"syslog-critical-8Ufx3eD1","title":"Service failed on abuse","message":"Oct 12 10:30:03 abuse systemd[1]: Unit pmlogger_daily-poll.service entered failed state.","priority":3,"tags":["warning"]} Service failed on abuse Oct 12 10:30:03 abuse systemd[1]: Unit pmlogger_daily-poll.service entered failed state.

1 0

syslog-critical alerts
by cron/syslog01.cs.umd.edu 12 Oct '26

12 Oct '26

Command: /usr/local/sbin/syslog-ntfy-alert.py Time : 0.0598s Status : exited 0 Output : {"id":"wrL9z771I20H","time":1791815401,"expires":1791858601,"event":"message","topic":"syslog-critical-8Ufx3eD1","title":"Service failed on abuse","message":"Oct 12 10:28:03 abuse systemd[1]: Unit pmie_check.service entered failed state.","priority":3,"tags":["warning"]} Service failed on abuse Oct 12 10:28:03 abuse systemd[1]: Unit pmie_check.service entered failed state.

1 0

syslog-critical alerts
by cron/syslog01.cs.umd.edu 12 Oct '26

12 Oct '26

Command: /usr/local/sbin/syslog-ntfy-alert.py Time : 0.0600s Status : exited 0 Output : {"id":"fWlDNvVoWODv","time":1791815161,"expires":1791858361,"event":"message","topic":"syslog-critical-8Ufx3eD1","title":"Service failed on submit26-b9-f4","message":"Oct 12 10:24:08 submit26-b9-f4 systemd[1]: user(a)1001.service: Failed with result 'signal'.","priority":3,"tags":["warning"]} Service failed on submit26-b9-f4 Oct 12 10:24:08 submit26-b9-f4 systemd[1]: user(a)1001.service: Failed with result 'signal'.

1 0

syslog-critical alerts
by cron/syslog01.cs.umd.edu 12 Oct '26

12 Oct '26

Command: /usr/local/sbin/syslog-ntfy-alert.py Time : 0.0601s Status : exited 0 Output : {"id":"sQ1LJE3x61hk","time":1791814682,"expires":1791857882,"event":"message","topic":"syslog-critical-8Ufx3eD1","title":"Service failed on hazfs.cs.umd.edu","message":"Oct 12 10:17:18 hazfs.cs.umd.edu systemd[1]: userQuota.service: Failed with result 'exit-code'.","priority":3,"tags":["warning"]} Service failed on hazfs.cs.umd.edu Oct 12 10:17:18 hazfs.cs.umd.edu systemd[1]: userQuota.service: Failed with result 'exit-code'.

1 0

syslog-critical alerts
by cron/syslog01.cs.umd.edu 12 Oct '26

12 Oct '26

Command: /usr/local/sbin/syslog-ntfy-alert.py Time : 0.0603s Status : exited 0 Output : {"id":"GznFDiQASIPk","time":1791814561,"expires":1791857761,"event":"message","topic":"syslog-critical-8Ufx3eD1","title":"Service failed on idmv0","message":"Oct 12 10:14:14 idmv0 systemd[1]: gssproxy.service: Failed with result 'core-dump'.","priority":3,"tags":["warning"]} Service failed on idmv0 Oct 12 10:14:14 idmv0 systemd[1]: gssproxy.service: Failed with result 'core-dump'.

1 0