Command: /usr/local/sbin/syslog-digest.py Time : 0.0478s Status : exited 0 Output : Syslog digest — 2026-10-01 15:05 EDT Processed 1,812 lines, filtered 1,486 (82%). 326 unknown (172 distinct) from 20 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Oct 1 14:08:44 b0b02.cs.umd.edu rustdesk[3260222]: cannot open display: == biggulp.cs.umd.edu (1 distinct, 5 total) == Oct 1 14:34:54 biggulp.cs.umd.edu sshd-session[1595024]: error: send_error: write: Connection reset by peer [x5] == borogove.cs.umd.edu (1 distinct, 1 total) == Oct 1 14:57:36 borogove.cs.umd.edu sshd-session[2038514]: error: maximum authentication attempts exceeded for root from 10.227.96.13 port 33640 ssh2 [preauth] == idm00 (1 distinct, 1 total) == Oct 1 14:54:36 idm00 named[4166701]: client @0x7f11a8c67778 10.73.240.42#61199: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Oct 1 14:39:26 idmp0 named[1598691]: client @0x7f2d48026348 10.73.240.43#64331: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 2 total) == Oct 1 14:34:00 itmon02 sshd[805675]: error: beginning MaxStartups throttling [x2] == lifepix (1 distinct, 2 total) == Oct 1 14:38:04 lifepix setroubleshoot[1046179]: SELinux is preventing /usr/bin/podman from using the nnp_transition access on a process. For complete SELinux messages run: sealert -l db6b3d2c-fa5b-4b9b-8ef7-675cd3f54e86 [x2] == munin (2 distinct, 8 total) == Oct 1 14:44:05 munin sudo[2402798]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x4] Oct 1 14:44:05 munin sudo[2402798]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x4] == newhonors2 (1 distinct, 24 total) == Oct 1 14:13:03 newhonors2 dhcpcd[3416532]: dhcpcd is not running [x24] == ntop00 (96 distinct, 96 total) == Oct 1 14:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1306) *** Oct 1 14:05:02 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1306, QN: 63/63, ET: 1) *** Oct 1 14:05:12 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1306, QN: 8107/8107, ET: 11) *** Oct 1 14:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 1307) *** Oct 1 14:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 1307, QN: 8439/8439, ET: 0) *** Oct 1 14:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 1307) *** Oct 1 14:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 1307, QN: 62/62, ET: 0) *** Oct 1 14:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1308) *** Oct 1 14:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1308, QN: 43/43, ET: 0) *** Oct 1 14:10:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1308) *** Oct 1 14:10:13 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1308, QN: 8881/8881, ET: 12) *** Oct 1 14:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 1309) *** Oct 1 14:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 1309, QN: 55/55, ET: 0) *** Oct 1 14:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 1309) *** Oct 1 14:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 1309, QN: 8518/8518, ET: 0) *** Oct 1 14:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1310) *** Oct 1 14:15:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1310) *** Oct 1 14:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1310, QN: 67/67, ET: 0) *** Oct 1 14:15:12 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1310, QN: 8479/8479, ET: 11) *** Oct 1 14:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 1311) *** Oct 1 14:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 1311) *** Oct 1 14:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 1311, QN: 63/63, ET: 0) *** Oct 1 14:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 1311, QN: 9018/9018, ET: 0) *** Oct 1 14:20:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1312) *** Oct 1 14:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1312) *** Oct 1 14:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1312, QN: 56/56, ET: 0) *** Oct 1 14:20:16 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1312, QN: 9251/9251, ET: 15) *** Oct 1 14:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 1313) *** Oct 1 14:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 1313, QN: 9425/9425, ET: 0) *** Oct 1 14:23:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 1313) *** ... 66 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Oct 1 14:09:09 outbound00.cs.umd.edu python3[1636630]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Oct 1 14:13:06 outbound01.cs.umd.edu python3[3929052]: ldapdb [x6] == portal (1 distinct, 73 total) == Oct 1 14:05:12 portal setroubleshoot[4091591]: 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] == sebatinsky.cs.umd.edu (1 distinct, 1 total) == Oct 1 14:25:47 sebatinsky.cs.umd.edu kernel: hpet1: lost 5 rtc interrupts == sentry-docker00.cs.umd.edu (34 distinct, 34 total) == Oct 1 14:07:28 sentry-docker00.cs.umd.edu systemd-udevd[3458404]: Could not generate persistent MAC address for vethce588cc: No such file or directory Oct 1 14:07:28 sentry-docker00.cs.umd.edu systemd-udevd[3458405]: Could not generate persistent MAC address for veth85a3936: No such file or directory Oct 1 14:07:28 sentry-docker00.cs.umd.edu systemd-udevd[3458408]: Could not generate persistent MAC address for vethc016045: No such file or directory Oct 1 14:07:28 sentry-docker00.cs.umd.edu systemd-udevd[3458409]: Could not generate persistent MAC address for veth6d5fc99: No such file or directory Oct 1 14:07:28 sentry-docker00.cs.umd.edu systemd-udevd[3458405]: Could not generate persistent MAC address for veth9b3383f: No such file or directory Oct 1 14:07:28 sentry-docker00.cs.umd.edu systemd-udevd[3458404]: Could not generate persistent MAC address for vethdd8483e: No such file or directory Oct 1 14:07:28 sentry-docker00.cs.umd.edu systemd-udevd[3458405]: Could not generate persistent MAC address for veth565eb3a: No such file or directory Oct 1 14:07:28 sentry-docker00.cs.umd.edu systemd-udevd[3458422]: Could not generate persistent MAC address for vethc26a834: No such file or directory Oct 1 14:07:28 sentry-docker00.cs.umd.edu systemd-udevd[3458404]: Could not generate persistent MAC address for veth2283852: No such file or directory Oct 1 14:07:28 sentry-docker00.cs.umd.edu systemd-udevd[3458405]: Could not generate persistent MAC address for veth6d8e28c: No such file or directory Oct 1 14:27:35 sentry-docker00.cs.umd.edu systemd-udevd[3467729]: link_config: could not get ethtool features for vethdd8483e Oct 1 14:27:35 sentry-docker00.cs.umd.edu systemd-udevd[3467729]: Could not set offload features of vethdd8483e: No such device Oct 1 14:27:36 sentry-docker00.cs.umd.edu systemd-udevd[3467763]: Could not generate persistent MAC address for vethf7eaf21: No such file or directory Oct 1 14:27:36 sentry-docker00.cs.umd.edu systemd-udevd[3467764]: Could not generate persistent MAC address for vethc2f3ae3: No such file or directory Oct 1 14:27:36 sentry-docker00.cs.umd.edu systemd-udevd[3467767]: Could not generate persistent MAC address for veth08a93f6: No such file or directory Oct 1 14:27:36 sentry-docker00.cs.umd.edu systemd-udevd[3467768]: Could not generate persistent MAC address for vethafba83d: No such file or directory Oct 1 14:27:36 sentry-docker00.cs.umd.edu systemd-udevd[3467764]: Could not generate persistent MAC address for veth0c9dc85: No such file or directory Oct 1 14:27:36 sentry-docker00.cs.umd.edu systemd-udevd[3467771]: Could not generate persistent MAC address for vethd6b3da6: No such file or directory Oct 1 14:27:36 sentry-docker00.cs.umd.edu systemd-udevd[3467793]: Could not generate persistent MAC address for veth3187672: No such file or directory Oct 1 14:27:36 sentry-docker00.cs.umd.edu systemd-udevd[3467794]: Could not generate persistent MAC address for veth50daa65: No such file or directory Oct 1 14:27:36 sentry-docker00.cs.umd.edu systemd-udevd[3467816]: Could not generate persistent MAC address for veth53a1cb8: No such file or directory Oct 1 14:27:36 sentry-docker00.cs.umd.edu systemd-udevd[3467825]: Could not generate persistent MAC address for veth2f8716d: No such file or directory Oct 1 14:47:44 sentry-docker00.cs.umd.edu systemd-udevd[3477093]: link_config: could not get ethtool features for vethd6b3da6 Oct 1 14:47:44 sentry-docker00.cs.umd.edu systemd-udevd[3477093]: Could not set offload features of vethd6b3da6: No such device Oct 1 14:47:45 sentry-docker00.cs.umd.edu systemd-udevd[3477181]: Could not generate persistent MAC address for veth48282ca: No such file or directory Oct 1 14:47:45 sentry-docker00.cs.umd.edu systemd-udevd[3477182]: Could not generate persistent MAC address for veth3ea0dd6: No such file or directory Oct 1 14:47:45 sentry-docker00.cs.umd.edu systemd-udevd[3477185]: Could not generate persistent MAC address for veth034a784: No such file or directory Oct 1 14:47:45 sentry-docker00.cs.umd.edu systemd-udevd[3477186]: Could not generate persistent MAC address for veth1eb1866: No such file or directory Oct 1 14:47:45 sentry-docker00.cs.umd.edu systemd-udevd[3477182]: Could not generate persistent MAC address for veth6e0427c: No such file or directory Oct 1 14:47:45 sentry-docker00.cs.umd.edu systemd-udevd[3477203]: Could not generate persistent MAC address for veth6edeb9f: No such file or directory ... 4 more distinct messages not shown == strawberry (7 distinct, 38 total) == Oct 1 14:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Oct 1 14:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Oct 1 14:07:04 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Oct 1 14:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Oct 1 14:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Oct 1 14:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Oct 1 14:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (10 distinct, 11 total) == Oct 1 14:18:11 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x2] Oct 1 14:25:59 submit26-b9-f1 setroubleshoot[430272]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 3ef7d677-731f-46bf-9c34-c2c55fea665c Oct 1 14:25:59 submit26-b9-f1 setroubleshoot[430272]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l aa60e26f-72e1-45f1-bc12-aa8b3b669e36 Oct 1 14:25:59 submit26-b9-f1 setroubleshoot[430272]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l d088fb43-23ee-4ae8-ae6a-5d1c041ee2d6 Oct 1 14:25:59 submit26-b9-f1 setroubleshoot[430272]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.cEVzDf/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d Oct 1 14:25:59 submit26-b9-f1 setroubleshoot[430272]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 0fd3339f-3ef2-45f3-9e58-65a58b42f3ee Oct 1 14:25:59 submit26-b9-f1 setroubleshoot[430272]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.cEVzDf. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 Oct 1 14:25:59 submit26-b9-f1 setroubleshoot[430272]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 405a8556-cf9f-4ef4-8525-0dca18d4259d Oct 1 14:25:59 submit26-b9-f1 setroubleshoot[430272]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 3c38e23e-3631-4cb5-81c7-992675c836d9 Oct 1 14:25:59 submit26-b9-f1 setroubleshoot[430272]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l a070e9b5-2867-47d6-b2e3-3b7d99725848 == submit26-b9-f2 (9 distinct, 9 total) == Oct 1 14:06:53 submit26-b9-f2 setroubleshoot[3741659]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 0659d546-3107-4f75-b00f-008c85f41dc6 Oct 1 14:06:53 submit26-b9-f2 setroubleshoot[3741659]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 156d9270-3466-4356-b86f-1a128825961a Oct 1 14:06:53 submit26-b9-f2 setroubleshoot[3741659]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l c8a40bf5-2fc4-46b3-b813-8592b3523339 Oct 1 14:06:53 submit26-b9-f2 setroubleshoot[3741659]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.B1FAjH/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 Oct 1 14:06:53 submit26-b9-f2 setroubleshoot[3741659]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 988123da-b724-4e6a-900c-33a2723fdaf1 Oct 1 14:06:53 submit26-b9-f2 setroubleshoot[3741659]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.B1FAjH. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8 Oct 1 14:06:53 submit26-b9-f2 setroubleshoot[3741659]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 3a749560-1cec-40ca-a4dc-596841be3885 Oct 1 14:06:53 submit26-b9-f2 setroubleshoot[3741659]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 0aa52f08-94f8-474e-96d8-e818846941af Oct 1 14:06:53 submit26-b9-f2 setroubleshoot[3741659]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l de019dc4-408f-439c-902a-676d18dfe8e7 == submit26-b9-f3 (1 distinct, 4 total) == Oct 1 14:07:59 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x4] == submit26-b9-f4 (1 distinct, 3 total) == Oct 1 14:18:10 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x3]