Command: /usr/local/sbin/syslog-digest.py Time : 0.0513s Status : exited 0 Output : Syslog digest — 2026-10-01 10:05 EDT Processed 3,177 lines, filtered 2,843 (89%). 334 unknown (179 distinct) from 19 host(s). == atif01.cs.umd.edu (2 distinct, 3 total) == Oct 1 09:22:36 atif01.cs.umd.edu kernel: net_ratelimit: 20 callbacks suppressed Oct 1 09:22:36 atif01.cs.umd.edu kernel: nfsd: peername failed (err 107)! [x2] == b0b02.cs.umd.edu (1 distinct, 1 total) == Oct 1 09:08:23 b0b02.cs.umd.edu rustdesk[3183994]: cannot open display: == idm00 (1 distinct, 1 total) == Oct 1 09:54:35 idm00 named[4166701]: client @0x7f11a8046198 10.73.240.42#63920: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Oct 1 09:39:27 idmp0 named[1598691]: client @0x7f2d4802a308 10.73.240.43#60073: update '73.10.in-addr.arpa/IN' denied == inbound00.cs.umd.edu (1 distinct, 5 total) == Oct 1 10:03:24 inbound00.cs.umd.edu cockpit-ws[1771949]: /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] == inbound01.cs.umd.edu (1 distinct, 5 total) == Oct 1 10:03:19 inbound01.cs.umd.edu cockpit-ws[3982324]: /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] == itmon02 (1 distinct, 3 total) == Oct 1 09:08:03 itmon02 sshd[805675]: error: beginning MaxStartups throttling [x3] == munin (2 distinct, 4 total) == Oct 1 09:43:54 munin sudo[2292818]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x2] Oct 1 09:43:54 munin sudo[2292818]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x2] == newhonors2 (1 distinct, 24 total) == Oct 1 09:13:02 newhonors2 dhcpcd[3407208]: dhcpcd is not running [x24] == ntop00 (97 distinct, 97 total) == Oct 1 09:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1186, QN: 118/118, ET: 0) *** Oct 1 09:05:06 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1186, QN: 3630/3630, ET: 5) *** Oct 1 09:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 1187) *** Oct 1 09:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 1187, QN: 91/91, ET: 0) *** Oct 1 09:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 1187) *** Oct 1 09:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 1187, QN: 3567/3567, ET: 0) *** Oct 1 09:10:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1188) *** Oct 1 09:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1188) *** Oct 1 09:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1188, QN: 81/81, ET: 0) *** Oct 1 09:10:06 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1188, QN: 3689/3689, ET: 5) *** Oct 1 09:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 1189) *** Oct 1 09:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 1189, QN: 3869/3869, ET: 0) *** Oct 1 09:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 1189) *** Oct 1 09:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 1189, QN: 69/69, ET: 0) *** Oct 1 09:15:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1190) *** Oct 1 09:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1190) *** Oct 1 09:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1190, QN: 68/68, ET: 0) *** Oct 1 09:15:06 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1190, QN: 3779/3779, ET: 5) *** Oct 1 09:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 1191) *** Oct 1 09:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 1191, QN: 3617/3617, ET: 0) *** Oct 1 09:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 1191) *** Oct 1 09:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 1191, QN: 73/73, ET: 0) *** Oct 1 09:20:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1192) *** Oct 1 09:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1192) *** Oct 1 09:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1192, QN: 55/55, ET: 0) *** Oct 1 09:20:06 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1192, QN: 3600/3600, ET: 5) *** Oct 1 09:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 1193) *** Oct 1 09:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 1193, QN: 3717/3717, ET: 0) *** Oct 1 09:23:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 1193) *** Oct 1 09:23:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 1193, QN: 72/72, ET: 0) *** ... 67 more distinct messages not shown == outbound00.cs.umd.edu (2 distinct, 11 total) == Oct 1 09:09:09 outbound00.cs.umd.edu python3[1564965]: ldapdb [x6] Oct 1 09:59:09 outbound00.cs.umd.edu cockpit-ws[1576925]: /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, 7 total) == Oct 1 09:13:06 outbound01.cs.umd.edu python3[3857581]: ldapdb [x6] Oct 1 09:59:15 outbound01.cs.umd.edu cockpit-ws[3869283]: /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 == portal (1 distinct, 70 total) == Oct 1 09:05:15 portal setroubleshoot[4027988]: 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 [x70] == sebatinsky.cs.umd.edu (1 distinct, 1 total) == Oct 1 09:48:46 sebatinsky.cs.umd.edu kernel: hpet1: lost 1 rtc interrupts == sentry-docker00.cs.umd.edu (38 distinct, 38 total) == Oct 1 09:05:14 sentry-docker00.cs.umd.edu systemd-udevd[3316359]: link_config: could not get ethtool features for vethc608b99 Oct 1 09:05:14 sentry-docker00.cs.umd.edu systemd-udevd[3316359]: Could not set offload features of vethc608b99: No such device Oct 1 09:05:14 sentry-docker00.cs.umd.edu systemd-udevd[3316423]: Could not generate persistent MAC address for veth2f262c0: No such file or directory Oct 1 09:05:14 sentry-docker00.cs.umd.edu systemd-udevd[3316424]: Could not generate persistent MAC address for vethd5f2b54: No such file or directory Oct 1 09:05:14 sentry-docker00.cs.umd.edu systemd-udevd[3316442]: Could not generate persistent MAC address for vethd7c44a1: No such file or directory Oct 1 09:05:14 sentry-docker00.cs.umd.edu systemd-udevd[3316448]: Could not generate persistent MAC address for veth4d573fc: No such file or directory Oct 1 09:05:14 sentry-docker00.cs.umd.edu systemd-udevd[3316444]: Could not generate persistent MAC address for veth10538de: No such file or directory Oct 1 09:05:14 sentry-docker00.cs.umd.edu systemd-udevd[3316432]: Could not generate persistent MAC address for vethadd1df9: No such file or directory Oct 1 09:05:14 sentry-docker00.cs.umd.edu systemd-udevd[3316454]: Could not generate persistent MAC address for veth67c4534: No such file or directory Oct 1 09:05:14 sentry-docker00.cs.umd.edu systemd-udevd[3316453]: Could not generate persistent MAC address for veth195bfcf: No such file or directory Oct 1 09:05:14 sentry-docker00.cs.umd.edu systemd-udevd[3316498]: Could not generate persistent MAC address for vethd68c721: No such file or directory Oct 1 09:05:14 sentry-docker00.cs.umd.edu systemd-udevd[3316499]: Could not generate persistent MAC address for veth8edaef6: No such file or directory Oct 1 09:25:22 sentry-docker00.cs.umd.edu systemd-udevd[3326033]: link_config: could not get ethtool features for veth10538de Oct 1 09:25:22 sentry-docker00.cs.umd.edu systemd-udevd[3326033]: Could not set offload features of veth10538de: No such device Oct 1 09:25:23 sentry-docker00.cs.umd.edu systemd-udevd[3326062]: Could not generate persistent MAC address for veth273524c: No such file or directory Oct 1 09:25:23 sentry-docker00.cs.umd.edu systemd-udevd[3326063]: Could not generate persistent MAC address for veth6dffa57: No such file or directory Oct 1 09:25:23 sentry-docker00.cs.umd.edu systemd-udevd[3326070]: Could not generate persistent MAC address for veth4006f39: No such file or directory Oct 1 09:25:23 sentry-docker00.cs.umd.edu systemd-udevd[3326081]: Could not generate persistent MAC address for veth839b2b5: No such file or directory Oct 1 09:25:23 sentry-docker00.cs.umd.edu systemd-udevd[3326069]: Could not generate persistent MAC address for veth8b8f949: No such file or directory Oct 1 09:25:23 sentry-docker00.cs.umd.edu systemd-udevd[3326074]: Could not generate persistent MAC address for vethc2583cb: No such file or directory Oct 1 09:25:23 sentry-docker00.cs.umd.edu systemd-udevd[3326069]: Could not generate persistent MAC address for veth92f60a0: No such file or directory Oct 1 09:25:23 sentry-docker00.cs.umd.edu systemd-udevd[3326074]: Could not generate persistent MAC address for veth435064f: No such file or directory Oct 1 09:25:23 sentry-docker00.cs.umd.edu systemd-udevd[3326069]: Could not generate persistent MAC address for vethb251b1e: No such file or directory Oct 1 09:25:23 sentry-docker00.cs.umd.edu systemd-udevd[3326074]: Could not generate persistent MAC address for veth44794a8: No such file or directory Oct 1 09:45:31 sentry-docker00.cs.umd.edu systemd-udevd[3335440]: link_config: could not get ethtool features for vethc2583cb Oct 1 09:45:31 sentry-docker00.cs.umd.edu systemd-udevd[3335440]: Could not set offload features of vethc2583cb: No such device Oct 1 09:45:31 sentry-docker00.cs.umd.edu systemd-udevd[3335441]: link_config: could not get ethtool features for vethb251b1e Oct 1 09:45:31 sentry-docker00.cs.umd.edu systemd-udevd[3335441]: Could not set offload features of vethb251b1e: No such device Oct 1 09:45:31 sentry-docker00.cs.umd.edu systemd-udevd[3335472]: Could not generate persistent MAC address for veth999b002: No such file or directory Oct 1 09:45:31 sentry-docker00.cs.umd.edu systemd-udevd[3335473]: Could not generate persistent MAC address for veth35767ae: No such file or directory ... 8 more distinct messages not shown == strawberry (7 distinct, 38 total) == Oct 1 09:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Oct 1 09:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Oct 1 09:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Oct 1 09:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Oct 1 09:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Oct 1 09:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Oct 1 09:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f2 (1 distinct, 2 total) == Oct 1 09:33:07 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x2] == submit26-b9-f3 (10 distinct, 12 total) == Oct 1 09:06:47 submit26-b9-f3 setroubleshoot[412480]: 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 1 09:06:47 submit26-b9-f3 setroubleshoot[412480]: 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 1 09:06:47 submit26-b9-f3 setroubleshoot[412480]: 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 1 09:06:47 submit26-b9-f3 setroubleshoot[412480]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.MWkedE/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Oct 1 09:06:47 submit26-b9-f3 setroubleshoot[412480]: 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 1 09:06:47 submit26-b9-f3 setroubleshoot[412480]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.MWkedE. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Oct 1 09:06:47 submit26-b9-f3 setroubleshoot[412480]: 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 1 09:06:47 submit26-b9-f3 setroubleshoot[412480]: 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 1 09:06:47 submit26-b9-f3 setroubleshoot[412480]: 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 Oct 1 09:10:22 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-f4 (9 distinct, 11 total) == Oct 1 09:24:52 submit26-b9-f4 setroubleshoot[3333154]: 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 [x2] Oct 1 09:24:52 submit26-b9-f4 setroubleshoot[3333154]: 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 [x2] Oct 1 09:24:52 submit26-b9-f4 setroubleshoot[3333154]: 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 1 09:24:52 submit26-b9-f4 setroubleshoot[3333154]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.G0Kzdt/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Oct 1 09:24:52 submit26-b9-f4 setroubleshoot[3333154]: 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 1 09:24:52 submit26-b9-f4 setroubleshoot[3333154]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.G0Kzdt. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Oct 1 09:24:52 submit26-b9-f4 setroubleshoot[3333154]: 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 1 09:24:52 submit26-b9-f4 setroubleshoot[3333154]: 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 1 09:24:52 submit26-b9-f4 setroubleshoot[3333154]: 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