Command: /usr/local/sbin/syslog-digest.py Time : 0.0463s Status : exited 0 Output : Syslog digest — 2026-10-04 02:05 EDT Processed 1,642 lines, filtered 1,246 (75%). 396 unknown (189 distinct) from 21 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Oct 4 01:12:34 b0b02.cs.umd.edu rustdesk[4160077]: cannot open display: == cheezit.cs.umd.edu (4 distinct, 4 total) == Oct 4 01:32:42 cheezit.cs.umd.edu sshd-session[1816838]: pam_access(sshd:auth): access denied for user `admin' from `34.77.122.5' Oct 4 01:32:42 cheezit.cs.umd.edu krb5_child[1816840]: Client 'admin@UMD.EDU' not found in Kerberos database Oct 4 01:32:42 cheezit.cs.umd.edu sshd-session[1816836]: error: PAM: System error for admin from 34.77.122.5 Oct 4 01:34:54 cheezit.cs.umd.edu sshd-session[1816990]: error: Protocol major versions differ: 2 vs. 1 == galax (1 distinct, 1 total) == Oct 4 01:33:05 galax kernel: workqueue: dm_irq_work_func [amdgpu] hogged CPU for >10000us 65539 times, consider switching to WQ_UNBOUND == hazfs.cs.umd.edu (11 distinct, 66 total) == Oct 4 01:32:35 hazfs.cs.umd.edu snmpd[1431]: send response: Failure in sendto [x6] Oct 4 01:32:35 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userweb" [x6] Oct 4 01:32:35 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."zfslist" [x6] Oct 4 01:32:35 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userhome" [x6] Oct 4 01:32:35 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userweb" [x6] Oct 4 01:32:35 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."zfslist" [x6] Oct 4 01:32:35 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userhome" [x6] Oct 4 01:32:35 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userweb" [x6] Oct 4 01:32:35 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."zfslist" [x6] Oct 4 01:32:35 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userhome" [x6] Oct 4 01:32:35 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutNumLines."userweb" [x6] == idm00 (1 distinct, 1 total) == Oct 4 01:54:37 idm00 named[4166701]: client @0x7f11a4071638 10.73.240.42#65225: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Oct 4 01:39:23 idmp0 named[1598691]: client @0x7f2d3002f808 10.73.240.43#50660: update '73.10.in-addr.arpa/IN' denied == inbound01.cs.umd.edu (2 distinct, 2 total) == Oct 4 01:43:52 inbound01.cs.umd.edu krb5_child[691510]: Client 'admin@UMD.EDU' not found in Kerberos database Oct 4 01:44:08 inbound01.cs.umd.edu sshd-session[691544]: error: Protocol major versions differ: 2 vs. 1 == itmon02 (1 distinct, 2 total) == Oct 4 01:43:05 itmon02 sshd[805675]: error: beginning MaxStartups throttling [x2] == munin (2 distinct, 16 total) == Oct 4 01:23:02 munin sudo[3674680]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x8] Oct 4 01:23:02 munin sudo[3674680]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x8] == netman.cs.umd.edu (1 distinct, 1 total) == Oct 4 01:57:32 netman.cs.umd.edu sshd[36739]: fatal: userauth_pubkey: parse request failed: incomplete message [preauth] == newhonors2 (1 distinct, 24 total) == Oct 4 01:13:02 newhonors2 dhcpcd[3528148]: dhcpcd is not running [x24] == ntop00 (97 distinct, 97 total) == Oct 4 01:05:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2722) *** Oct 4 01:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2722) *** Oct 4 01:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2722, QN: 88/88, ET: 0) *** Oct 4 01:05:08 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2722, QN: 4399/4399, ET: 7) *** Oct 4 01:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 2723) *** Oct 4 01:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 2723, QN: 3708/3708, ET: 0) *** Oct 4 01:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 2723) *** Oct 4 01:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 2723, QN: 65/65, ET: 0) *** Oct 4 01:10:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2724) *** Oct 4 01:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2724) *** Oct 4 01:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2724, QN: 55/55, ET: 0) *** Oct 4 01:10:06 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2724, QN: 3166/3166, ET: 5) *** Oct 4 01:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 2725) *** Oct 4 01:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 2725, QN: 3283/3283, ET: 0) *** Oct 4 01:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 2725) *** Oct 4 01:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 2725, QN: 54/54, ET: 0) *** Oct 4 01:15:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2726) *** Oct 4 01:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2726) *** Oct 4 01:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2726, QN: 41/41, ET: 0) *** Oct 4 01:15:05 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2726, QN: 3384/3384, ET: 4) *** Oct 4 01:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 2727) *** Oct 4 01:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 2727, QN: 3314/3314, ET: 0) *** Oct 4 01:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 2727) *** Oct 4 01:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 2727, QN: 45/45, ET: 0) *** Oct 4 01:20:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2728) *** Oct 4 01:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2728) *** Oct 4 01:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2728, QN: 47/47, ET: 0) *** Oct 4 01:20:06 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2728, QN: 3434/3434, ET: 5) *** Oct 4 01:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 2729) *** Oct 4 01:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 2729, QN: 3671/3671, ET: 0) *** ... 67 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Oct 4 01:09:09 outbound00.cs.umd.edu python3[2494238]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Oct 4 01:13:06 outbound01.cs.umd.edu python3[567059]: ldapdb [x6] == portal (1 distinct, 73 total) == Oct 4 01:05:42 portal setroubleshoot[688330]: 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 [x73] == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Oct 4 01:11:51 sentry-docker00.cs.umd.edu systemd-udevd[930900]: link_config: could not get ethtool features for vethcdd8240 Oct 4 01:11:51 sentry-docker00.cs.umd.edu systemd-udevd[930900]: Could not set offload features of vethcdd8240: No such device Oct 4 01:11:52 sentry-docker00.cs.umd.edu systemd-udevd[930934]: Could not generate persistent MAC address for veth626ca8d: No such file or directory Oct 4 01:11:52 sentry-docker00.cs.umd.edu systemd-udevd[930933]: Could not generate persistent MAC address for veth27ac3d5: No such file or directory Oct 4 01:11:52 sentry-docker00.cs.umd.edu systemd-udevd[930937]: Could not generate persistent MAC address for veth54a657b: No such file or directory Oct 4 01:11:52 sentry-docker00.cs.umd.edu systemd-udevd[930948]: Could not generate persistent MAC address for vethe38db55: No such file or directory Oct 4 01:11:52 sentry-docker00.cs.umd.edu systemd-udevd[930940]: Could not generate persistent MAC address for veth5436a59: No such file or directory Oct 4 01:11:52 sentry-docker00.cs.umd.edu systemd-udevd[930941]: Could not generate persistent MAC address for vethdcd0865: No such file or directory Oct 4 01:11:52 sentry-docker00.cs.umd.edu systemd-udevd[930940]: Could not generate persistent MAC address for veth66e764c: No such file or directory Oct 4 01:11:52 sentry-docker00.cs.umd.edu systemd-udevd[930941]: Could not generate persistent MAC address for veth497599a: No such file or directory Oct 4 01:11:52 sentry-docker00.cs.umd.edu systemd-udevd[930965]: Could not generate persistent MAC address for vethe444a7a: No such file or directory Oct 4 01:11:52 sentry-docker00.cs.umd.edu systemd-udevd[930967]: Could not generate persistent MAC address for veth3fb0732: No such file or directory Oct 4 01:32:00 sentry-docker00.cs.umd.edu systemd-udevd[940462]: link_config: could not get ethtool features for vethe444a7a Oct 4 01:32:00 sentry-docker00.cs.umd.edu systemd-udevd[940462]: Could not set offload features of vethe444a7a: No such device Oct 4 01:32:00 sentry-docker00.cs.umd.edu systemd-udevd[940502]: Could not generate persistent MAC address for veth20d2214: No such file or directory Oct 4 01:32:00 sentry-docker00.cs.umd.edu systemd-udevd[940503]: Could not generate persistent MAC address for veth94c9d80: No such file or directory Oct 4 01:32:00 sentry-docker00.cs.umd.edu systemd-udevd[940506]: Could not generate persistent MAC address for veth0670799: No such file or directory Oct 4 01:32:00 sentry-docker00.cs.umd.edu systemd-udevd[940507]: Could not generate persistent MAC address for veth38ea95d: No such file or directory Oct 4 01:32:00 sentry-docker00.cs.umd.edu systemd-udevd[940507]: Could not generate persistent MAC address for vethf55884a: No such file or directory Oct 4 01:32:00 sentry-docker00.cs.umd.edu systemd-udevd[940519]: Could not generate persistent MAC address for vethe4b852e: No such file or directory Oct 4 01:32:00 sentry-docker00.cs.umd.edu systemd-udevd[940532]: Could not generate persistent MAC address for veth7fda288: No such file or directory Oct 4 01:32:00 sentry-docker00.cs.umd.edu systemd-udevd[940533]: Could not generate persistent MAC address for veth071935f: No such file or directory Oct 4 01:32:00 sentry-docker00.cs.umd.edu systemd-udevd[940566]: Could not generate persistent MAC address for vethdec7a0e: No such file or directory Oct 4 01:32:00 sentry-docker00.cs.umd.edu systemd-udevd[940541]: Could not generate persistent MAC address for vetha0d2770: No such file or directory Oct 4 01:52:08 sentry-docker00.cs.umd.edu systemd-udevd[949874]: link_config: could not get ethtool features for veth7fda288 Oct 4 01:52:08 sentry-docker00.cs.umd.edu systemd-udevd[949874]: Could not set offload features of veth7fda288: No such device Oct 4 01:52:08 sentry-docker00.cs.umd.edu systemd-udevd[949907]: Could not generate persistent MAC address for veth346d67d: No such file or directory Oct 4 01:52:08 sentry-docker00.cs.umd.edu systemd-udevd[949908]: Could not generate persistent MAC address for veth0aaaaf6: No such file or directory Oct 4 01:52:08 sentry-docker00.cs.umd.edu systemd-udevd[949933]: Could not generate persistent MAC address for veth360e7e4: No such file or directory Oct 4 01:52:08 sentry-docker00.cs.umd.edu systemd-udevd[949934]: Could not generate persistent MAC address for vethfce5015: No such file or directory ... 6 more distinct messages not shown == strawberry (7 distinct, 38 total) == Oct 4 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 4 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 4 01:07:04 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Oct 4 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 4 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 4 01:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Oct 4 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 4 01:28:08 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 4 01:05:41 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-f3 (9 distinct, 9 total) == Oct 4 01:06:47 submit26-b9-f3 setroubleshoot[858250]: 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 Oct 4 01:06:47 submit26-b9-f3 setroubleshoot[858250]: 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 Oct 4 01:06:47 submit26-b9-f3 setroubleshoot[858250]: 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 4 01:06:47 submit26-b9-f3 setroubleshoot[858250]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.9u6WIb/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Oct 4 01:06:47 submit26-b9-f3 setroubleshoot[858250]: 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 4 01:06:47 submit26-b9-f3 setroubleshoot[858250]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.9u6WIb. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Oct 4 01:06:47 submit26-b9-f3 setroubleshoot[858250]: 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 Oct 4 01:06:47 submit26-b9-f3 setroubleshoot[858250]: 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 4 01:06:47 submit26-b9-f3 setroubleshoot[858250]: 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 == submit26-b9-f4 (9 distinct, 9 total) == Oct 4 01:24:52 submit26-b9-f4 setroubleshoot[3677816]: 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 4 01:24:52 submit26-b9-f4 setroubleshoot[3677816]: 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 4 01:24:52 submit26-b9-f4 setroubleshoot[3677816]: 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 4 01:24:52 submit26-b9-f4 setroubleshoot[3677816]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.Ro8kRg/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Oct 4 01:24:52 submit26-b9-f4 setroubleshoot[3677816]: 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 4 01:24:52 submit26-b9-f4 setroubleshoot[3677816]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.Ro8kRg. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Oct 4 01:24:52 submit26-b9-f4 setroubleshoot[3677816]: 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 4 01:24:52 submit26-b9-f4 setroubleshoot[3677816]: 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 4 01:24:52 submit26-b9-f4 setroubleshoot[3677816]: 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