Command: /usr/local/sbin/syslog-digest.py Time : 0.0452s Status : exited 0 Output : Syslog digest — 2026-09-25 01:05 EDT Processed 1,789 lines, filtered 1,403 (78%). 386 unknown (210 distinct) from 31 host(s). == abuse (3 distinct, 4 total) == Sep 25 00:10:13 abuse systemd[1]: New main PID 20630 does not belong to service, and PID file is not owned by root. Refusing. [x2] Sep 25 00:10:32 abuse systemd[1]: Daemon never wrote its PID file. Failing. Sep 25 00:10:42 abuse systemd[1]: pmlogger.service: Supervising process 28025 which is not our child. We'll most likely not notice when it exits. == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 25 00:59:22 b0b02.cs.umd.edu rustdesk[787615]: cannot open display: == biggulp.cs.umd.edu (3 distinct, 4 total) == Sep 25 00:44:02 biggulp.cs.umd.edu sshd-session[4042427]: pam_access(sshd:auth): access denied for user `larry' from `71.191.93.172' [x2] Sep 25 00:44:03 biggulp.cs.umd.edu sshd-session[4042427]: Error in Duo login for 'larry' from 71.191.93.172 Sep 25 00:44:03 biggulp.cs.umd.edu sshd-session[4042425]: error: PAM: Authentication failure for larry from 71.191.93.172 == cheezit.cs.umd.edu (3 distinct, 4 total) == Sep 25 00:13:49 cheezit.cs.umd.edu sshd-session[2839594]: pam_access(sshd:auth): access denied for user `larry' from `71.191.93.172' [x2] Sep 25 00:13:49 cheezit.cs.umd.edu sshd-session[2839594]: Error in Duo login for 'larry' from 71.191.93.172 Sep 25 00:13:49 cheezit.cs.umd.edu sshd-session[2839588]: error: PAM: Authentication failure for larry from 71.191.93.172 == grades01.cs.umd.edu (3 distinct, 4 total) == Sep 25 00:10:13 grades01.cs.umd.edu systemd[1]: New main PID 4496 does not belong to service, and PID file is not owned by root. Refusing. [x2] Sep 25 00:10:33 grades01.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing. Sep 25 00:10:49 grades01.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 11708 which is not our child. We'll most likely not notice when it exits. == hazfs.cs.umd.edu (11 distinct, 66 total) == Sep 25 00:57:38 hazfs.cs.umd.edu snmpd[1431]: send response: Failure in sendto [x6] Sep 25 00:57:38 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userweb" [x6] Sep 25 00:57:38 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."zfslist" [x6] Sep 25 00:57:38 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userhome" [x6] Sep 25 00:57:38 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userweb" [x6] Sep 25 00:57:38 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."zfslist" [x6] Sep 25 00:57:38 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userhome" [x6] Sep 25 00:57:38 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userweb" [x6] Sep 25 00:57:38 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."zfslist" [x6] Sep 25 00:57:38 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userhome" [x6] Sep 25 00:57:38 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutNumLines."userweb" [x6] == idm00 (1 distinct, 1 total) == Sep 25 00:54:07 idm00 named[4166701]: client @0x7f11a406bb48 10.73.240.42#64941: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 25 00:39:51 idmp0 named[1598691]: client @0x7f2d4c000cc8 10.73.240.43#52386: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 3 total) == Sep 25 00:33:13 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x3] == jubjub.cs.umd.edu (3 distinct, 4 total) == Sep 25 00:10:13 jubjub.cs.umd.edu systemd[1]: New main PID 967352 does not belong to service, and PID file is not owned by root. Refusing. [x2] Sep 25 00:10:33 jubjub.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing. Sep 25 00:10:41 jubjub.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 974448 which is not our child. We'll most likely not notice when it exits. == mirrors.cs.umd.edu (4 distinct, 6 total) == Sep 25 00:10:34 mirrors.cs.umd.edu root[29910]: pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily-K.log Sep 25 00:10:34 mirrors.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing. [x2] Sep 25 00:10:37 mirrors.cs.umd.edu systemd[1]: New main PID 28839 does not belong to service, and PID file is not owned by root. Refusing. [x2] Sep 25 00:11:59 mirrors.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 13616 which is not our child. We'll most likely not notice when it exits. == misty.cs.umd.edu (3 distinct, 4 total) == Sep 25 00:10:15 misty.cs.umd.edu systemd[1]: New main PID 5399 does not belong to service, and PID file is not owned by root. Refusing. [x2] Sep 25 00:10:35 misty.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing. Sep 25 00:10:51 misty.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 13195 which is not our child. We'll most likely not notice when it exits. == munin (2 distinct, 36 total) == Sep 25 00:13:40 munin sudo[3140682]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x18] Sep 25 00:13:40 munin sudo[3140682]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x18] == newhonors2 (1 distinct, 24 total) == Sep 25 00:13:03 newhonors2 dhcpcd[3115958]: dhcpcd is not running [x24] == ntop00 (94 distinct, 94 total) == Sep 25 00:05:07 ntop00 sfacctd[182241]: INFO ( m1/mysql ): *** Purging cache - END (PID: 394, QN: 4417/4417, ET: 6) *** Sep 25 00:08:01 ntop00 sfacctd[182241]: INFO ( p1/print ): *** Purging cache - START (PID: 395) *** Sep 25 00:08:01 ntop00 sfacctd[182241]: INFO ( p1/print ): *** Purging cache - END (PID: 395, QN: 4118/4118, ET: 0) *** Sep 25 00:08:01 ntop00 nfacctd[182312]: INFO ( p1/print ): *** Purging cache - START (PID: 395) *** Sep 25 00:08:01 ntop00 nfacctd[182312]: INFO ( p1/print ): *** Purging cache - END (PID: 395, QN: 55/55, ET: 0) *** Sep 25 00:10:01 ntop00 sfacctd[182241]: INFO ( m1/mysql ): *** Purging cache - START (PID: 396) *** Sep 25 00:10:01 ntop00 nfacctd[182312]: INFO ( m1/mysql ): *** Purging cache - START (PID: 396) *** Sep 25 00:10:01 ntop00 nfacctd[182312]: INFO ( m1/mysql ): *** Purging cache - END (PID: 396, QN: 47/47, ET: 0) *** Sep 25 00:10:08 ntop00 sfacctd[182241]: INFO ( m1/mysql ): *** Purging cache - END (PID: 396, QN: 4058/4058, ET: 7) *** Sep 25 00:13:01 ntop00 sfacctd[182241]: INFO ( p1/print ): *** Purging cache - START (PID: 397) *** Sep 25 00:13:01 ntop00 sfacctd[182241]: INFO ( p1/print ): *** Purging cache - END (PID: 397, QN: 5884/5884, ET: 0) *** Sep 25 00:13:01 ntop00 nfacctd[182312]: INFO ( p1/print ): *** Purging cache - START (PID: 397) *** Sep 25 00:13:01 ntop00 nfacctd[182312]: INFO ( p1/print ): *** Purging cache - END (PID: 397, QN: 35/35, ET: 0) *** Sep 25 00:15:01 ntop00 sfacctd[182241]: INFO ( m1/mysql ): *** Purging cache - START (PID: 398) *** Sep 25 00:15:01 ntop00 nfacctd[182312]: INFO ( m1/mysql ): *** Purging cache - START (PID: 398) *** Sep 25 00:15:01 ntop00 nfacctd[182312]: INFO ( m1/mysql ): *** Purging cache - END (PID: 398, QN: 33/33, ET: 0) *** Sep 25 00:15:10 ntop00 sfacctd[182241]: INFO ( m1/mysql ): *** Purging cache - END (PID: 398, QN: 5626/5626, ET: 9) *** Sep 25 00:18:01 ntop00 sfacctd[182241]: INFO ( p1/print ): *** Purging cache - START (PID: 399) *** Sep 25 00:18:01 ntop00 sfacctd[182241]: INFO ( p1/print ): *** Purging cache - END (PID: 399, QN: 3728/3728, ET: 0) *** Sep 25 00:18:01 ntop00 nfacctd[182312]: INFO ( p1/print ): *** Purging cache - START (PID: 399) *** Sep 25 00:18:01 ntop00 nfacctd[182312]: INFO ( p1/print ): *** Purging cache - END (PID: 399, QN: 42/42, ET: 0) *** Sep 25 00:20:01 ntop00 sfacctd[182241]: INFO ( m1/mysql ): *** Purging cache - START (PID: 400) *** Sep 25 00:20:01 ntop00 nfacctd[182312]: INFO ( m1/mysql ): *** Purging cache - START (PID: 400) *** Sep 25 00:20:01 ntop00 nfacctd[182312]: INFO ( m1/mysql ): *** Purging cache - END (PID: 400, QN: 46/46, ET: 0) *** Sep 25 00:20:07 ntop00 sfacctd[182241]: INFO ( m1/mysql ): *** Purging cache - END (PID: 400, QN: 3673/3673, ET: 6) *** Sep 25 00:23:01 ntop00 sfacctd[182241]: INFO ( p1/print ): *** Purging cache - START (PID: 401) *** Sep 25 00:23:01 ntop00 sfacctd[182241]: INFO ( p1/print ): *** Purging cache - END (PID: 401, QN: 4142/4142, ET: 0) *** Sep 25 00:23:01 ntop00 nfacctd[182312]: INFO ( p1/print ): *** Purging cache - START (PID: 401) *** Sep 25 00:23:01 ntop00 nfacctd[182312]: INFO ( p1/print ): *** Purging cache - END (PID: 401, QN: 52/52, ET: 0) *** Sep 25 00:25:01 ntop00 sfacctd[182241]: INFO ( m1/mysql ): *** Purging cache - START (PID: 402) *** ... 64 more distinct messages not shown == openrepo (1 distinct, 1 total) == Sep 25 00:48:27 openrepo (nin-node)[3759472]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 25 00:09:09 outbound00.cs.umd.edu python3[3590293]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 25 00:13:06 outbound01.cs.umd.edu python3[1656703]: ldapdb [x6] == sebatinsky.cs.umd.edu (1 distinct, 1 total) == Sep 25 00:17:41 sebatinsky.cs.umd.edu kernel: hpet1: lost 2 rtc interrupts == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Sep 25 00:22:00 sentry-docker00.cs.umd.edu systemd-udevd[3189934]: link_config: could not get ethtool features for vethdbbfe03 Sep 25 00:22:00 sentry-docker00.cs.umd.edu systemd-udevd[3189934]: Could not set offload features of vethdbbfe03: No such device Sep 25 00:22:01 sentry-docker00.cs.umd.edu systemd-udevd[3189971]: Could not generate persistent MAC address for vethd953e47: No such file or directory Sep 25 00:22:01 sentry-docker00.cs.umd.edu systemd-udevd[3189972]: Could not generate persistent MAC address for veth9ebe3f8: No such file or directory Sep 25 00:22:01 sentry-docker00.cs.umd.edu systemd-udevd[3189976]: Could not generate persistent MAC address for vethf1ac559: No such file or directory Sep 25 00:22:01 sentry-docker00.cs.umd.edu systemd-udevd[3189975]: Could not generate persistent MAC address for veth0a86034: No such file or directory Sep 25 00:22:01 sentry-docker00.cs.umd.edu systemd-udevd[3189994]: Could not generate persistent MAC address for vethd87b62a: No such file or directory Sep 25 00:22:01 sentry-docker00.cs.umd.edu systemd-udevd[3189984]: Could not generate persistent MAC address for vethd22a9ab: No such file or directory Sep 25 00:22:01 sentry-docker00.cs.umd.edu systemd-udevd[3190001]: Could not generate persistent MAC address for vethed9cd57: No such file or directory Sep 25 00:22:01 sentry-docker00.cs.umd.edu systemd-udevd[3190002]: Could not generate persistent MAC address for vethc851cb6: No such file or directory Sep 25 00:22:01 sentry-docker00.cs.umd.edu systemd-udevd[3190020]: Could not generate persistent MAC address for veth32ce5a5: No such file or directory Sep 25 00:22:01 sentry-docker00.cs.umd.edu systemd-udevd[3190018]: Could not generate persistent MAC address for vethb68b7b1: No such file or directory Sep 25 00:42:09 sentry-docker00.cs.umd.edu systemd-udevd[3199400]: link_config: could not get ethtool features for veth32ce5a5 Sep 25 00:42:09 sentry-docker00.cs.umd.edu systemd-udevd[3199400]: Could not set offload features of veth32ce5a5: No such device Sep 25 00:42:09 sentry-docker00.cs.umd.edu systemd-udevd[3199425]: Could not generate persistent MAC address for veth5a78d0f: No such file or directory Sep 25 00:42:09 sentry-docker00.cs.umd.edu systemd-udevd[3199424]: Could not generate persistent MAC address for veth4aa658b: No such file or directory Sep 25 00:42:09 sentry-docker00.cs.umd.edu systemd-udevd[3199428]: Could not generate persistent MAC address for vethbfe0784: No such file or directory Sep 25 00:42:09 sentry-docker00.cs.umd.edu systemd-udevd[3199435]: Could not generate persistent MAC address for veth2d25645: No such file or directory Sep 25 00:42:09 sentry-docker00.cs.umd.edu systemd-udevd[3199439]: Could not generate persistent MAC address for vethf0602bc: No such file or directory Sep 25 00:42:09 sentry-docker00.cs.umd.edu systemd-udevd[3199425]: Could not generate persistent MAC address for veth2533d76: No such file or directory Sep 25 00:42:09 sentry-docker00.cs.umd.edu systemd-udevd[3199425]: Could not generate persistent MAC address for veth4c82bfb: No such file or directory Sep 25 00:42:09 sentry-docker00.cs.umd.edu systemd-udevd[3199439]: Could not generate persistent MAC address for vetha469647: No such file or directory Sep 25 00:42:09 sentry-docker00.cs.umd.edu systemd-udevd[3199456]: Could not generate persistent MAC address for veth5717667: No such file or directory Sep 25 00:42:09 sentry-docker00.cs.umd.edu systemd-udevd[3199457]: Could not generate persistent MAC address for veth3d8511e: No such file or directory Sep 25 01:02:17 sentry-docker00.cs.umd.edu systemd-udevd[3208774]: link_config: could not get ethtool features for vethbfe0784 Sep 25 01:02:17 sentry-docker00.cs.umd.edu systemd-udevd[3208774]: Could not set offload features of vethbfe0784: No such device Sep 25 01:02:17 sentry-docker00.cs.umd.edu systemd-udevd[3208812]: Could not generate persistent MAC address for veth885995d: No such file or directory Sep 25 01:02:17 sentry-docker00.cs.umd.edu systemd-udevd[3208813]: Could not generate persistent MAC address for veth6bb7188: No such file or directory Sep 25 01:02:17 sentry-docker00.cs.umd.edu systemd-udevd[3208816]: Could not generate persistent MAC address for vethdae5954: No such file or directory Sep 25 01:02:17 sentry-docker00.cs.umd.edu systemd-udevd[3208817]: Could not generate persistent MAC address for veth437253a: No such file or directory ... 6 more distinct messages not shown == strawberry (8 distinct, 39 total) == Sep 25 00:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 25 00:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 25 00:07:04 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 25 00:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 25 00:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 25 00:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 25 00:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] Sep 25 01:04:42 strawberry smartd[5314]: Device: /dev/sda [SAT], not capable of Offline or Self-Testing. == submit10-cln25 (3 distinct, 4 total) == Sep 25 00:10:11 submit10-cln25 systemd: New main PID 11466 does not belong to service, and PID file is not owned by root. Refusing. [x2] Sep 25 00:10:30 submit10-cln25 systemd: Daemon never wrote its PID file. Failing. Sep 25 00:10:35 submit10-cln25 systemd: pmlogger.service: Supervising process 18364 which is not our child. We'll most likely not notice when it exits. == submit26-b9-f1 (1 distinct, 3 total) == Sep 25 00:18:08 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x3] == submit26-b9-f2 (1 distinct, 3 total) == Sep 25 00:13:08 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x3] == submit26-b9-f3 (1 distinct, 3 total) == Sep 25 00:20:04 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x3] == submit26-b9-f4 (1 distinct, 3 total) == Sep 25 00:08:11 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x3] == submit26-b9-fclone (9 distinct, 9 total) == Sep 25 00:21:59 submit26-b9-fclone setroubleshoot[441081]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 9355d9d9-a311-48d2-bd37-6c0f6947dfff Sep 25 00:21:59 submit26-b9-fclone setroubleshoot[441081]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l cc4658d7-9db1-405d-9eee-de0ccee5857f Sep 25 00:21:59 submit26-b9-fclone setroubleshoot[441081]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 568a2429-0b1b-49df-af41-49b5cd298ae8 Sep 25 00:21:59 submit26-b9-fclone setroubleshoot[441081]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.Ng1ptG/repodata/repomd.xml. For complete SELinux messages run: sealert -l 03e2f521-0e7c-481f-8e92-0602c6adeedc Sep 25 00:21:59 submit26-b9-fclone setroubleshoot[441081]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 0d6b7b1f-ebe3-4beb-915a-b06b63bf2566 Sep 25 00:21:59 submit26-b9-fclone setroubleshoot[441081]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.Ng1ptG. For complete SELinux messages run: sealert -l 887adbf9-2bb9-4009-b800-36ddf9ba0db5 Sep 25 00:21:59 submit26-b9-fclone setroubleshoot[441081]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 092e0644-8373-4017-b77f-1afa6c6da4ac Sep 25 00:21:59 submit26-b9-fclone setroubleshoot[441081]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l ce429a92-56de-4de1-b859-cbfb69ae123c Sep 25 00:21:59 submit26-b9-fclone setroubleshoot[441081]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 99b886eb-497b-406d-8206-afe76a1086b4 == tma-0 (3 distinct, 4 total) == Sep 25 00:10:13 tma-0 systemd[1]: New main PID 16461 does not belong to service, and PID file is not owned by root. Refusing. [x2] Sep 25 00:10:30 tma-0 systemd[1]: Daemon never wrote its PID file. Failing. Sep 25 00:10:38 tma-0 systemd[1]: pmlogger.service: Supervising process 23411 which is not our child. We'll most likely not notice when it exits. == uffish.cs.umd.edu (3 distinct, 4 total) == Sep 25 00:10:13 uffish.cs.umd.edu systemd[1]: New main PID 3479806 does not belong to service, and PID file is not owned by root. Refusing. [x2] Sep 25 00:10:39 uffish.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing. Sep 25 00:10:56 uffish.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 3487478 which is not our child. We'll most likely not notice when it exits. == vacuum.cs.umd.edu (3 distinct, 4 total) == Sep 25 00:10:14 vacuum.cs.umd.edu systemd[1]: New main PID 9863 does not belong to service, and PID file is not owned by root. Refusing. [x2] Sep 25 00:10:33 vacuum.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing. Sep 25 00:10:44 vacuum.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 16994 which is not our child. We'll most likely not notice when it exits. == whiffle.cs.umd.edu (3 distinct, 4 total) == Sep 25 00:10:13 whiffle.cs.umd.edu systemd[1]: New main PID 3017646 does not belong to service, and PID file is not owned by root. Refusing. [x2] Sep 25 00:10:32 whiffle.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing. Sep 25 00:10:46 whiffle.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 3024798 which is not our child. We'll most likely not notice when it exits.
participants (1)
-
cron/syslog01.cs.umd.edu