Command: /usr/local/sbin/syslog-digest.py Time : 0.0514s Status : exited 0 Output : Syslog digest — 2026-10-06 02:05 EDT Processed 2,547 lines, filtered 2,127 (83%). 420 unknown (195 distinct) from 23 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Oct 6 01:15:30 b0b02.cs.umd.edu rustdesk[697588]: cannot open display: == biggulp.cs.umd.edu (3 distinct, 3 total) == Oct 6 01:21:28 biggulp.cs.umd.edu sshd-session[2818782]: pam_access(sshd:auth): access denied for user `admin' from `207.175.247.91' Oct 6 01:21:28 biggulp.cs.umd.edu krb5_child[2818784]: Client 'admin@UMD.EDU' not found in Kerberos database Oct 6 01:21:28 biggulp.cs.umd.edu sshd-session[2818780]: error: PAM: System error for admin from 207.175.247.91 == cheezit.cs.umd.edu (3 distinct, 3 total) == Oct 6 02:04:16 cheezit.cs.umd.edu sshd-session[2497560]: pam_access(sshd:auth): access denied for user `admin' from `34.53.176.236' Oct 6 02:04:16 cheezit.cs.umd.edu krb5_child[2497566]: Client 'admin@UMD.EDU' not found in Kerberos database Oct 6 02:04:16 cheezit.cs.umd.edu sshd-session[2497558]: error: PAM: System error for admin from 34.53.176.236 == cmsc436-0101-redis (3 distinct, 3 total) == Oct 6 01:05:47 cmsc436-0101-redis krb5_child[4568]: Client 'admin@UMD.EDU' not found in Kerberos database Oct 6 01:05:48 cmsc436-0101-redis sshd-session[4564]: error: PAM: Authentication failure for admin from 34.62.218.88 Oct 6 01:05:51 cmsc436-0101-redis sshd-session[4570]: error: Protocol major versions differ: 2 vs. 1 == hazfs.cs.umd.edu (11 distinct, 66 total) == Oct 6 01:28:16 hazfs.cs.umd.edu snmpd[1431]: send response: Failure in sendto [x6] Oct 6 01:28:16 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userweb" [x6] Oct 6 01:28:16 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."zfslist" [x6] Oct 6 01:28:16 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userhome" [x6] Oct 6 01:28:16 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userweb" [x6] Oct 6 01:28:16 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."zfslist" [x6] Oct 6 01:28:16 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userhome" [x6] Oct 6 01:28:16 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userweb" [x6] Oct 6 01:28:16 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."zfslist" [x6] Oct 6 01:28:16 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userhome" [x6] Oct 6 01:28:16 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutNumLines."userweb" [x6] == idm00 (1 distinct, 1 total) == Oct 6 01:54:40 idm00 named[4166701]: client @0x7f11986d6658 10.73.240.42#50259: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Oct 6 01:39:24 idmp0 named[1598691]: client @0x7f2d3c06efd8 10.73.240.43#52011: update '73.10.in-addr.arpa/IN' denied == inbound00.cs.umd.edu (1 distinct, 6 total) == Oct 6 01:34:52 inbound00.cs.umd.edu cockpit-ws[3356914]: /usr/share/cockpit/static/login.js/favicon.ico: Failed to open file “/usr/share/cockpit/static/login.js/favicon.ico”: open() failed: Not a directory [x6] == inbound01.cs.umd.edu (2 distinct, 5 total) == Oct 6 01:30:46 inbound01.cs.umd.edu krb5_child[1371092]: Client 'admin@UMD.EDU' not found in Kerberos database Oct 6 01:34:50 inbound01.cs.umd.edu cockpit-ws[1371836]: /usr/share/cockpit/static/login.js/favicon.ico: Failed to open file “/usr/share/cockpit/static/login.js/favicon.ico”: open() failed: Not a directory [x4] == itmon02 (1 distinct, 3 total) == Oct 6 01:13:05 itmon02 sshd[805675]: error: beginning MaxStartups throttling [x3] == krispykreme.cs.umd.edu (1 distinct, 1 total) == Oct 6 01:33:12 krispykreme.cs.umd.edu sshd-session[2463151]: error: send_error: write: Connection reset by peer == munin (2 distinct, 16 total) == Oct 6 01:23:25 munin sudo[522529]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x8] Oct 6 01:23:25 munin sudo[522529]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x8] == newhonors2 (1 distinct, 24 total) == Oct 6 01:13:03 newhonors2 dhcpcd[3618787]: dhcpcd is not running [x24] == ntop00 (94 distinct, 94 total) == Oct 6 01:05:05 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3874, QN: 2932/2932, ET: 4) *** Oct 6 01:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 3875) *** Oct 6 01:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 3875, QN: 2885/2885, ET: 0) *** Oct 6 01:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 3875) *** Oct 6 01:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 3875, QN: 67/67, ET: 0) *** Oct 6 01:10:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3876) *** Oct 6 01:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3876) *** Oct 6 01:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3876, QN: 59/59, ET: 0) *** Oct 6 01:10:05 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3876, QN: 2920/2920, ET: 4) *** Oct 6 01:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 3877) *** Oct 6 01:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 3877, QN: 2815/2815, ET: 0) *** Oct 6 01:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 3877) *** Oct 6 01:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 3877, QN: 61/61, ET: 0) *** Oct 6 01:15:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3878) *** Oct 6 01:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3878) *** Oct 6 01:15:02 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3878, QN: 66/66, ET: 1) *** Oct 6 01:15:05 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3878, QN: 2733/2733, ET: 4) *** Oct 6 01:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 3879) *** Oct 6 01:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 3879, QN: 2699/2699, ET: 0) *** Oct 6 01:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 3879) *** Oct 6 01:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 3879, QN: 68/68, ET: 0) *** Oct 6 01:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3880) *** Oct 6 01:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3880, QN: 68/68, ET: 0) *** Oct 6 01:20:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3880) *** Oct 6 01:20:06 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3880, QN: 2811/2811, ET: 5) *** Oct 6 01:23:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 3881) *** Oct 6 01:23:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 3881, QN: 72/72, ET: 0) *** Oct 6 01:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 3881) *** Oct 6 01:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 3881, QN: 2959/2959, ET: 0) *** Oct 6 01:25:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3882) *** ... 64 more distinct messages not shown == outbound00.cs.umd.edu (2 distinct, 11 total) == Oct 6 01:09:08 outbound00.cs.umd.edu python3[3170132]: ldapdb [x6] Oct 6 01:31:39 outbound00.cs.umd.edu cockpit-ws[3175757]: /usr/share/cockpit/static/login.js/favicon.ico: Failed to open file “/usr/share/cockpit/static/login.js/favicon.ico”: open() failed: Not a directory [x5] == outbound01.cs.umd.edu (2 distinct, 10 total) == Oct 6 01:13:06 outbound01.cs.umd.edu python3[1244338]: ldapdb [x6] Oct 6 01:55:36 outbound01.cs.umd.edu cockpit-ws[1253921]: /usr/share/cockpit/static/login.js/favicon.ico: Failed to open file “/usr/share/cockpit/static/login.js/favicon.ico”: open() failed: Not a directory [x4] == portal (1 distinct, 69 total) == Oct 6 01:05:07 portal setroubleshoot[1331198]: SELinux is preventing /usr/local/bin/traefik from connectto access on the unix_stream_socket /run/podman/podman.sock. For complete SELinux messages run: sealert -l e0a307a3-2c22-4320-8f9d-6a166c45222d [x69] == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Oct 6 01:11:45 sentry-docker00.cs.umd.edu systemd-udevd[2281645]: link_config: could not set ethtool features for veth5b70c0c Oct 6 01:11:45 sentry-docker00.cs.umd.edu systemd-udevd[2281645]: Could not set offload features of veth5b70c0c: Operation not permitted Oct 6 01:11:46 sentry-docker00.cs.umd.edu systemd-udevd[2281678]: Could not generate persistent MAC address for veth2414c73: No such file or directory Oct 6 01:11:46 sentry-docker00.cs.umd.edu systemd-udevd[2281679]: Could not generate persistent MAC address for vethde22e0d: No such file or directory Oct 6 01:11:46 sentry-docker00.cs.umd.edu systemd-udevd[2281682]: Could not generate persistent MAC address for veth88f392e: No such file or directory Oct 6 01:11:46 sentry-docker00.cs.umd.edu systemd-udevd[2281683]: Could not generate persistent MAC address for vethedd13ae: No such file or directory Oct 6 01:11:46 sentry-docker00.cs.umd.edu systemd-udevd[2281699]: Could not generate persistent MAC address for veth7db88c1: No such file or directory Oct 6 01:11:46 sentry-docker00.cs.umd.edu systemd-udevd[2281694]: Could not generate persistent MAC address for vethefa3404: No such file or directory Oct 6 01:11:46 sentry-docker00.cs.umd.edu systemd-udevd[2281683]: Could not generate persistent MAC address for veth6b5082d: No such file or directory Oct 6 01:11:46 sentry-docker00.cs.umd.edu systemd-udevd[2281694]: Could not generate persistent MAC address for veth035bfe7: No such file or directory Oct 6 01:11:46 sentry-docker00.cs.umd.edu systemd-udevd[2281694]: Could not generate persistent MAC address for vethfb34b82: No such file or directory Oct 6 01:11:46 sentry-docker00.cs.umd.edu systemd-udevd[2281699]: Could not generate persistent MAC address for veth223dc93: No such file or directory Oct 6 01:31:54 sentry-docker00.cs.umd.edu systemd-udevd[2291265]: link_config: could not get ethtool features for veth88f392e Oct 6 01:31:54 sentry-docker00.cs.umd.edu systemd-udevd[2291265]: Could not set offload features of veth88f392e: No such device Oct 6 01:31:54 sentry-docker00.cs.umd.edu systemd-udevd[2291297]: Could not generate persistent MAC address for vethd8ab886: No such file or directory Oct 6 01:31:54 sentry-docker00.cs.umd.edu systemd-udevd[2291298]: Could not generate persistent MAC address for veth046b249: No such file or directory Oct 6 01:31:54 sentry-docker00.cs.umd.edu systemd-udevd[2291301]: Could not generate persistent MAC address for veth6b90280: No such file or directory Oct 6 01:31:54 sentry-docker00.cs.umd.edu systemd-udevd[2291302]: Could not generate persistent MAC address for veth8df7a5a: No such file or directory Oct 6 01:31:54 sentry-docker00.cs.umd.edu systemd-udevd[2291312]: Could not generate persistent MAC address for veth7990272: No such file or directory Oct 6 01:31:54 sentry-docker00.cs.umd.edu systemd-udevd[2291308]: Could not generate persistent MAC address for veth953e14d: No such file or directory Oct 6 01:31:54 sentry-docker00.cs.umd.edu systemd-udevd[2291327]: Could not generate persistent MAC address for vethc9c06e3: No such file or directory Oct 6 01:31:54 sentry-docker00.cs.umd.edu systemd-udevd[2291328]: Could not generate persistent MAC address for veth2bcdc5f: No such file or directory Oct 6 01:31:54 sentry-docker00.cs.umd.edu systemd-udevd[2291346]: Could not generate persistent MAC address for veth73f77b5: No such file or directory Oct 6 01:31:54 sentry-docker00.cs.umd.edu systemd-udevd[2291336]: Could not generate persistent MAC address for veth4efc2d2: No such file or directory Oct 6 01:52:02 sentry-docker00.cs.umd.edu systemd-udevd[2300668]: link_config: could not get ethtool features for veth6b90280 Oct 6 01:52:02 sentry-docker00.cs.umd.edu systemd-udevd[2300668]: Could not set offload features of veth6b90280: No such device Oct 6 01:52:02 sentry-docker00.cs.umd.edu systemd-udevd[2300689]: Could not generate persistent MAC address for vethc4765e1: No such file or directory Oct 6 01:52:02 sentry-docker00.cs.umd.edu systemd-udevd[2300690]: Could not generate persistent MAC address for vethd5d3f31: No such file or directory Oct 6 01:52:02 sentry-docker00.cs.umd.edu systemd-udevd[2300708]: Could not generate persistent MAC address for veth3f3132e: No such file or directory Oct 6 01:52:02 sentry-docker00.cs.umd.edu systemd-udevd[2300696]: Could not generate persistent MAC address for vethe5ee417: No such file or directory ... 6 more distinct messages not shown == strawberry (7 distinct, 38 total) == Oct 6 01:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Oct 6 01:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Oct 6 01:07:04 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Oct 6 01:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Oct 6 01:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Oct 6 01:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Oct 6 01:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (1 distinct, 2 total) == Oct 6 01:21:47 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x2] == submit26-b9-f2 (1 distinct, 1 total) == Oct 6 01:27:14 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-f3 (11 distinct, 17 total) == Oct 6 01:06:48 submit26-b9-f3 setroubleshoot[1397190]: 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 [x2] Oct 6 01:06:48 submit26-b9-f3 setroubleshoot[1397190]: 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 [x2] Oct 6 01:06:48 submit26-b9-f3 setroubleshoot[1397190]: 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 Oct 6 01:06:48 submit26-b9-f3 setroubleshoot[1397190]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.mDnSgk/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Oct 6 01:06:48 submit26-b9-f3 setroubleshoot[1397190]: 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 Oct 6 01:06:48 submit26-b9-f3 setroubleshoot[1397190]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.mDnSgk. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Oct 6 01:06:48 submit26-b9-f3 setroubleshoot[1397190]: 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 [x2] Oct 6 01:06:48 submit26-b9-f3 setroubleshoot[1397190]: 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 Oct 6 01:06:48 submit26-b9-f3 setroubleshoot[1397190]: 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 [x2] Oct 6 01:06:48 submit26-b9-f3 setroubleshoot[1397190]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.FQl3BD. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Oct 6 01:20:04 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x3] == submit26-b9-f4 (9 distinct, 9 total) == Oct 6 01:24:53 submit26-b9-f4 setroubleshoot[4062079]: 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 Oct 6 01:24:54 submit26-b9-f4 setroubleshoot[4062079]: 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 Oct 6 01:24:54 submit26-b9-f4 setroubleshoot[4062079]: 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 Oct 6 01:24:54 submit26-b9-f4 setroubleshoot[4062079]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.GgHwGN/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Oct 6 01:24:54 submit26-b9-f4 setroubleshoot[4062079]: 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 Oct 6 01:24:54 submit26-b9-f4 setroubleshoot[4062079]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.GgHwGN. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Oct 6 01:24:54 submit26-b9-f4 setroubleshoot[4062079]: 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 Oct 6 01:24:54 submit26-b9-f4 setroubleshoot[4062079]: 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 Oct 6 01:24:54 submit26-b9-f4 setroubleshoot[4062079]: 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