Command: /usr/local/sbin/syslog-digest.py Time : 7.4737s Status : exited 0 Output : Syslog digest — 2026-09-27 02:05 EDT Processed 119,333 lines, filtered 1,398 (1%). 117,935 unknown (171 distinct) from 15 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 27 02:02:22 b0b02.cs.umd.edu rustdesk[1538741]: cannot open display: == biggulp.cs.umd.edu (4 distinct, 5 total) == Sep 27 01:39:27 biggulp.cs.umd.edu sshd-session[353897]: error: send_error: write: Connection reset by peer Sep 27 01:52:20 biggulp.cs.umd.edu sshd-session[355808]: pam_access(sshd:auth): access denied for user `larry' from `71.191.93.172' [x2] Sep 27 01:52:21 biggulp.cs.umd.edu sshd-session[355808]: Error in Duo login for 'larry' from 71.191.93.172 Sep 27 01:52:21 biggulp.cs.umd.edu sshd-session[355806]: error: PAM: Authentication failure for larry from 71.191.93.172 == hazfs.cs.umd.edu (11 distinct, 66 total) == Sep 27 01:33:47 hazfs.cs.umd.edu snmpd[1431]: send response: Failure in sendto [x6] Sep 27 01:33:47 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userweb" [x6] Sep 27 01:33:47 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."zfslist" [x6] Sep 27 01:33:47 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userhome" [x6] Sep 27 01:33:47 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userweb" [x6] Sep 27 01:33:47 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."zfslist" [x6] Sep 27 01:33:47 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userhome" [x6] Sep 27 01:33:47 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userweb" [x6] Sep 27 01:33:47 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."zfslist" [x6] Sep 27 01:33:47 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userhome" [x6] Sep 27 01:33:47 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutNumLines."userweb" [x6] == idm00 (1 distinct, 1 total) == Sep 27 01:54:09 idm00 named[4166701]: client @0x7f119804e448 10.73.240.42#49232: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 27 01:39:28 idmp0 named[1598691]: client @0x7f2d2801dea8 10.73.240.43#60684: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 5 total) == Sep 27 01:37:56 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x5] == newhonors2 (1 distinct, 24 total) == Sep 27 01:13:03 newhonors2 dhcpcd[3209007]: dhcpcd is not running [x24] == ntop00 (84 distinct, 117721 total) == Sep 27 01:05:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x13] Sep 27 01:05:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x13] Sep 27 01:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 994) *** Sep 27 01:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 994, QN: 0/59, ET: 0) *** Sep 27 01:05:09 ntop00 rsyslogd[1208]: imjournal: open() failed for path: '/var/lib/rsyslog/imjournal.state.tmp': No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2433 ] [x7660] Sep 27 01:05:09 ntop00 rsyslogd[1208]: file '/var/log/messages'[13] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x56138] Sep 27 01:05:09 ntop00 rsyslogd[1208]: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x53326] Sep 27 01:05:09 ntop00 rsyslogd[1208]: file '/var/log/maillog'[15] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x235] Sep 27 01:05:09 ntop00 rsyslogd[1208]: action 'action-3-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x235] Sep 27 01:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 995) *** Sep 27 01:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 995, QN: 4982/4982, ET: 0) *** Sep 27 01:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 995) *** Sep 27 01:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 995, QN: 62/62, ET: 0) *** Sep 27 01:10:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x12] Sep 27 01:10:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x12] Sep 27 01:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 996) *** Sep 27 01:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 996, QN: 0/5332, ET: 0) *** Sep 27 01:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 996) *** Sep 27 01:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 996, QN: 0/57, ET: 0) *** Sep 27 01:14:01 ntop00 rsyslogd[1208]: action 'action-1-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x3] Sep 27 01:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 998) *** Sep 27 01:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 998, QN: 0/4550, ET: 0) *** Sep 27 01:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 998) *** Sep 27 01:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 998, QN: 0/44, ET: 0) *** Sep 27 01:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 999) *** Sep 27 01:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 999, QN: 4181/4181, ET: 0) *** Sep 27 01:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 999) *** Sep 27 01:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 999, QN: 59/59, ET: 0) *** Sep 27 01:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1000) *** Sep 27 01:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1000, QN: 0/4835, ET: 0) *** ... 54 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 27 01:09:09 outbound00.cs.umd.edu python3[88452]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 27 01:13:06 outbound01.cs.umd.edu python3[2350588]: ldapdb [x6] == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Sep 27 01:22:15 sentry-docker00.cs.umd.edu systemd-udevd[382295]: link_config: could not get ethtool features for vethcc2a3ca Sep 27 01:22:15 sentry-docker00.cs.umd.edu systemd-udevd[382295]: Could not set offload features of vethcc2a3ca: No such device Sep 27 01:22:15 sentry-docker00.cs.umd.edu systemd-udevd[382335]: Could not generate persistent MAC address for veth2565a2d: No such file or directory Sep 27 01:22:15 sentry-docker00.cs.umd.edu systemd-udevd[382336]: Could not generate persistent MAC address for veth7f3d35c: No such file or directory Sep 27 01:22:15 sentry-docker00.cs.umd.edu systemd-udevd[382339]: Could not generate persistent MAC address for vethaef78cf: No such file or directory Sep 27 01:22:15 sentry-docker00.cs.umd.edu systemd-udevd[382340]: Could not generate persistent MAC address for veth56ad423: No such file or directory Sep 27 01:22:15 sentry-docker00.cs.umd.edu systemd-udevd[382355]: Could not generate persistent MAC address for vethbcef809: No such file or directory Sep 27 01:22:15 sentry-docker00.cs.umd.edu systemd-udevd[382360]: Could not generate persistent MAC address for vethfe6192a: No such file or directory Sep 27 01:22:15 sentry-docker00.cs.umd.edu systemd-udevd[382365]: Could not generate persistent MAC address for veth1b3d073: No such file or directory Sep 27 01:22:15 sentry-docker00.cs.umd.edu systemd-udevd[382366]: Could not generate persistent MAC address for vethb7c6c03: No such file or directory Sep 27 01:22:15 sentry-docker00.cs.umd.edu systemd-udevd[382416]: Could not generate persistent MAC address for vethe01ccb9: No such file or directory Sep 27 01:22:15 sentry-docker00.cs.umd.edu systemd-udevd[382419]: Could not generate persistent MAC address for veth4da65f1: No such file or directory Sep 27 01:42:23 sentry-docker00.cs.umd.edu systemd-udevd[391963]: link_config: could not get ethtool features for veth1b3d073 Sep 27 01:42:23 sentry-docker00.cs.umd.edu systemd-udevd[391963]: Could not set offload features of veth1b3d073: No such device Sep 27 01:42:24 sentry-docker00.cs.umd.edu systemd-udevd[392035]: Could not generate persistent MAC address for vethe66ae91: No such file or directory Sep 27 01:42:24 sentry-docker00.cs.umd.edu systemd-udevd[392036]: Could not generate persistent MAC address for vethe7d5825: No such file or directory Sep 27 01:42:24 sentry-docker00.cs.umd.edu systemd-udevd[392039]: Could not generate persistent MAC address for vethb1d1906: No such file or directory Sep 27 01:42:24 sentry-docker00.cs.umd.edu systemd-udevd[392040]: Could not generate persistent MAC address for veth58502ce: No such file or directory Sep 27 01:42:24 sentry-docker00.cs.umd.edu systemd-udevd[392063]: Could not generate persistent MAC address for veth0ab8b6c: No such file or directory Sep 27 01:42:24 sentry-docker00.cs.umd.edu systemd-udevd[392064]: Could not generate persistent MAC address for veth88bc1af: No such file or directory Sep 27 01:42:24 sentry-docker00.cs.umd.edu systemd-udevd[392082]: Could not generate persistent MAC address for veth0a8d887: No such file or directory Sep 27 01:42:24 sentry-docker00.cs.umd.edu systemd-udevd[392073]: Could not generate persistent MAC address for vethfb794bb: No such file or directory Sep 27 01:42:24 sentry-docker00.cs.umd.edu systemd-udevd[392079]: Could not generate persistent MAC address for veth1e4876d: No such file or directory Sep 27 01:42:24 sentry-docker00.cs.umd.edu systemd-udevd[392069]: Could not generate persistent MAC address for vethcaa04a4: No such file or directory Sep 27 02:02:32 sentry-docker00.cs.umd.edu systemd-udevd[401421]: link_config: could not set ethtool features for veth0a8d887 Sep 27 02:02:32 sentry-docker00.cs.umd.edu systemd-udevd[401421]: Could not set offload features of veth0a8d887: Operation not permitted Sep 27 02:02:32 sentry-docker00.cs.umd.edu systemd-udevd[401446]: Could not generate persistent MAC address for veth262900a: No such file or directory Sep 27 02:02:32 sentry-docker00.cs.umd.edu systemd-udevd[401447]: Could not generate persistent MAC address for vethee7109a: No such file or directory Sep 27 02:02:32 sentry-docker00.cs.umd.edu systemd-udevd[401465]: Could not generate persistent MAC address for vethc206693: No such file or directory Sep 27 02:02:32 sentry-docker00.cs.umd.edu systemd-udevd[401450]: Could not generate persistent MAC address for veth874fa89: No such file or directory ... 6 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 27 01:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 27 01:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 27 01:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 27 01:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 27 01:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 27 01:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 27 01:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f2 (1 distinct, 1 total) == Sep 27 01:30:07 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-f3 (10 distinct, 10 total) == Sep 27 01:06:45 submit26-b9-f3 setroubleshoot[3649673]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l a653b772-cbcd-438b-bae5-23c3dc69b31b Sep 27 01:06:45 submit26-b9-f3 setroubleshoot[3649673]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 3e904634-6caa-4202-8c92-f139db798859 Sep 27 01:06:45 submit26-b9-f3 setroubleshoot[3649673]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 580b20e4-ec2c-433d-905c-5bd417fba033 Sep 27 01:06:45 submit26-b9-f3 setroubleshoot[3649673]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.oqoEim/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Sep 27 01:06:45 submit26-b9-f3 setroubleshoot[3649673]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l bff72452-d40a-430b-9060-dd0a48f5b6ba Sep 27 01:06:45 submit26-b9-f3 setroubleshoot[3649673]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.oqoEim. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Sep 27 01:06:45 submit26-b9-f3 setroubleshoot[3649673]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 6da64b94-7024-45a9-b8c2-3b9812517407 Sep 27 01:06:45 submit26-b9-f3 setroubleshoot[3649673]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 64cbe179-abf1-4d5a-bade-bb164897ee65 Sep 27 01:06:45 submit26-b9-f3 setroubleshoot[3649673]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l d2e35b1a-e27c-4f91-9217-2bb1204e1e68 Sep 27 01:08:20 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-f4 (11 distinct, 14 total) == Sep 27 01:24:49 submit26-b9-f4 setroubleshoot[2669749]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l ee160f23-b161-4f4a-9985-c4edfd3a5beb Sep 27 01:24:49 submit26-b9-f4 setroubleshoot[2669749]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 89a83821-4b24-4081-9973-0a79ca6ed5b4 Sep 27 01:24:49 submit26-b9-f4 setroubleshoot[2669749]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l f73955d6-1416-45f9-bab6-ff1f3ea07e9d [x2] Sep 27 01:24:49 submit26-b9-f4 setroubleshoot[2669749]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.4WQs5e/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Sep 27 01:24:49 submit26-b9-f4 setroubleshoot[2669749]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 20293136-86a3-40ba-a651-cff48d36059e [x2] Sep 27 01:24:49 submit26-b9-f4 setroubleshoot[2669749]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.4WQs5e. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Sep 27 01:24:49 submit26-b9-f4 setroubleshoot[2669749]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l eec250fb-073f-456d-93bc-f98776fd476d Sep 27 01:24:49 submit26-b9-f4 setroubleshoot[2669749]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l c9209e04-a349-43d5-8cb2-3e303e48df74 [x2] Sep 27 01:24:49 submit26-b9-f4 setroubleshoot[2669749]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 3178d5f5-80e9-404b-92b7-9bef397a8915 Sep 27 01:24:49 submit26-b9-f4 setroubleshoot[2669749]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.EPY0OG/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Sep 27 01:50:10 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL