Command: /usr/local/sbin/syslog-digest.py Time : 0.0425s Status : exited 0 Output : Syslog digest — 2026-09-16 02:05 EDT Processed 1,806 lines, filtered 1,477 (81%). 329 unknown (82 distinct) from 14 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 16 01:45:43 b0b02.cs.umd.edu rustdesk[1618285]: cannot open display: == csfw00a (1 distinct, 123 total) == Sep 16 01:03:59 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x123] == hazfs.cs.umd.edu (11 distinct, 66 total) == Sep 16 01:05:14 hazfs.cs.umd.edu snmpd[1431]: send response: Failure in sendto [x6] Sep 16 01:05:14 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userweb" [x6] Sep 16 01:05:14 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."zfslist" [x6] Sep 16 01:05:14 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userhome" [x6] Sep 16 01:05:14 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userweb" [x6] Sep 16 01:05:14 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."zfslist" [x6] Sep 16 01:05:14 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userhome" [x6] Sep 16 01:05:14 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userweb" [x6] Sep 16 01:05:14 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."zfslist" [x6] Sep 16 01:05:14 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userhome" [x6] Sep 16 01:05:14 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutNumLines."userweb" [x6] == idm00 (1 distinct, 1 total) == Sep 16 01:53:55 idm00 named[4166701]: client @0x7f11a4046478 10.73.240.42#62509: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 16 01:37:41 idmp0 named[1598691]: client @0x7f2d14025948 10.73.240.43#52859: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 5 total) == Sep 16 01:08:12 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x5] == munin (2 distinct, 2 total) == Sep 16 02:03:14 munin sudo[2667430]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory Sep 16 02:03:14 munin sudo[2667430]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. == newhonors2 (1 distinct, 24 total) == Sep 16 01:13:03 newhonors2 dhcpcd[2700624]: dhcpcd is not running [x24] == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 16 01:09:09 outbound00.cs.umd.edu python3[514954]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 16 01:13:06 outbound01.cs.umd.edu python3[2774419]: ldapdb [x6] == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Sep 16 01:13:03 sentry-docker00.cs.umd.edu systemd-udevd[1278193]: link_config: could not get ethtool features for veth0b56008 Sep 16 01:13:03 sentry-docker00.cs.umd.edu systemd-udevd[1278193]: Could not set offload features of veth0b56008: No such device Sep 16 01:13:03 sentry-docker00.cs.umd.edu systemd-udevd[1278224]: Could not generate persistent MAC address for veth9f2567b: No such file or directory Sep 16 01:13:03 sentry-docker00.cs.umd.edu systemd-udevd[1278225]: Could not generate persistent MAC address for veth55451c4: No such file or directory Sep 16 01:13:03 sentry-docker00.cs.umd.edu systemd-udevd[1278228]: Could not generate persistent MAC address for veth337679b: No such file or directory Sep 16 01:13:03 sentry-docker00.cs.umd.edu systemd-udevd[1278229]: Could not generate persistent MAC address for vethcca96dc: No such file or directory Sep 16 01:13:03 sentry-docker00.cs.umd.edu systemd-udevd[1278237]: Could not generate persistent MAC address for veth4116946: No such file or directory Sep 16 01:13:03 sentry-docker00.cs.umd.edu systemd-udevd[1278238]: Could not generate persistent MAC address for veth84e29b6: No such file or directory Sep 16 01:13:03 sentry-docker00.cs.umd.edu systemd-udevd[1278249]: Could not generate persistent MAC address for veth03b8a29: No such file or directory Sep 16 01:13:03 sentry-docker00.cs.umd.edu systemd-udevd[1278244]: Could not generate persistent MAC address for vethe79ff1f: No such file or directory Sep 16 01:13:03 sentry-docker00.cs.umd.edu systemd-udevd[1278238]: Could not generate persistent MAC address for vethb302ac4: No such file or directory Sep 16 01:13:03 sentry-docker00.cs.umd.edu systemd-udevd[1278237]: Could not generate persistent MAC address for veth0362ddb: No such file or directory Sep 16 01:33:11 sentry-docker00.cs.umd.edu systemd-udevd[1287702]: link_config: could not get ethtool features for vethe79ff1f Sep 16 01:33:11 sentry-docker00.cs.umd.edu systemd-udevd[1287702]: Could not set offload features of vethe79ff1f: No such device Sep 16 01:33:12 sentry-docker00.cs.umd.edu systemd-udevd[1287788]: Could not generate persistent MAC address for veth6155997: No such file or directory Sep 16 01:33:12 sentry-docker00.cs.umd.edu systemd-udevd[1287789]: Could not generate persistent MAC address for vethb1b3822: No such file or directory Sep 16 01:33:12 sentry-docker00.cs.umd.edu systemd-udevd[1287792]: Could not generate persistent MAC address for veth4d7d298: No such file or directory Sep 16 01:33:12 sentry-docker00.cs.umd.edu systemd-udevd[1287794]: Could not generate persistent MAC address for veth68e7bc1: No such file or directory Sep 16 01:33:12 sentry-docker00.cs.umd.edu systemd-udevd[1287795]: Could not generate persistent MAC address for vethcefe575: No such file or directory Sep 16 01:33:12 sentry-docker00.cs.umd.edu systemd-udevd[1287792]: Could not generate persistent MAC address for vethac89c16: No such file or directory Sep 16 01:33:12 sentry-docker00.cs.umd.edu systemd-udevd[1287807]: Could not generate persistent MAC address for vetha7ccfe8: No such file or directory Sep 16 01:33:12 sentry-docker00.cs.umd.edu systemd-udevd[1287792]: Could not generate persistent MAC address for veth2dc18bc: No such file or directory Sep 16 01:33:12 sentry-docker00.cs.umd.edu systemd-udevd[1287847]: Could not generate persistent MAC address for veth4aa38f5: No such file or directory Sep 16 01:33:12 sentry-docker00.cs.umd.edu systemd-udevd[1287848]: Could not generate persistent MAC address for veth4fdc6b2: No such file or directory Sep 16 01:53:20 sentry-docker00.cs.umd.edu systemd-udevd[1297122]: link_config: could not get ethtool features for vetha7ccfe8 Sep 16 01:53:20 sentry-docker00.cs.umd.edu systemd-udevd[1297122]: Could not set offload features of vetha7ccfe8: No such device Sep 16 01:53:20 sentry-docker00.cs.umd.edu systemd-udevd[1297194]: Could not generate persistent MAC address for veth3562668: No such file or directory Sep 16 01:53:20 sentry-docker00.cs.umd.edu systemd-udevd[1297195]: Could not generate persistent MAC address for veth14cbb8f: No such file or directory Sep 16 01:53:20 sentry-docker00.cs.umd.edu systemd-udevd[1297198]: Could not generate persistent MAC address for vethc2fb667: No such file or directory Sep 16 01:53:20 sentry-docker00.cs.umd.edu systemd-udevd[1297218]: Could not generate persistent MAC address for veth3db0d1c: No such file or directory ... 6 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 16 01:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 16 01:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 16 01:07:04 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 16 01:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 16 01:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 16 01:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 16 01:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f3 (9 distinct, 11 total) == Sep 16 01:06:41 submit26-b9-f3 setroubleshoot[1249911]: 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] Sep 16 01:06:41 submit26-b9-f3 setroubleshoot[1249911]: 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] Sep 16 01:06:41 submit26-b9-f3 setroubleshoot[1249911]: 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 16 01:06:41 submit26-b9-f3 setroubleshoot[1249911]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.gtXR8n/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Sep 16 01:06:41 submit26-b9-f3 setroubleshoot[1249911]: 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 16 01:06:41 submit26-b9-f3 setroubleshoot[1249911]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.gtXR8n. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Sep 16 01:06:41 submit26-b9-f3 setroubleshoot[1249911]: 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 16 01:06:41 submit26-b9-f3 setroubleshoot[1249911]: 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 16 01:06:41 submit26-b9-f3 setroubleshoot[1249911]: 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) == Sep 16 01:24:44 submit26-b9-f4 setroubleshoot[940988]: 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 16 01:24:44 submit26-b9-f4 setroubleshoot[940988]: 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 16 01:24:44 submit26-b9-f4 setroubleshoot[940988]: 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 Sep 16 01:24:44 submit26-b9-f4 setroubleshoot[940988]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.XBPojU/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Sep 16 01:24:44 submit26-b9-f4 setroubleshoot[940988]: 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 Sep 16 01:24:44 submit26-b9-f4 setroubleshoot[940988]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.XBPojU. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Sep 16 01:24:44 submit26-b9-f4 setroubleshoot[940988]: 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 16 01:24:44 submit26-b9-f4 setroubleshoot[940988]: 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 Sep 16 01:24:44 submit26-b9-f4 setroubleshoot[940988]: 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