Command: /usr/local/sbin/syslog-digest.py Time : 0.0468s Status : exited 0 Output : Syslog digest — 2026-10-01 03:05 EDT Processed 1,819 lines, filtered 1,504 (82%). 315 unknown (173 distinct) from 16 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Oct 1 02:07:56 b0b02.cs.umd.edu rustdesk[3010674]: cannot open display: == idm00 (1 distinct, 1 total) == Oct 1 02:54:24 idm00 named[4166701]: client @0x7f11a00618f8 10.73.240.42#57586: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Oct 1 02:39:27 idmp0 named[1598691]: client @0x7f2d480190a8 10.73.240.43#51374: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 2 total) == Oct 1 02:28:02 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x2] == munin (2 distinct, 8 total) == Oct 1 02:13:20 munin sudo[2128178]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x4] Oct 1 02:13:20 munin sudo[2128178]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x4] == newhonors2 (1 distinct, 24 total) == Oct 1 02:13:02 newhonors2 dhcpcd[3393973]: dhcpcd is not running [x24] == ntop00 (96 distinct, 96 total) == Oct 1 02:05:02 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1018) *** Oct 1 02:05:02 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1018, QN: 49/49, ET: 0) *** Oct 1 02:05:07 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1018, QN: 3877/3877, ET: 6) *** Oct 1 02:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 1019) *** Oct 1 02:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 1019, QN: 3539/3539, ET: 0) *** Oct 1 02:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 1019) *** Oct 1 02:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 1019, QN: 49/49, ET: 0) *** Oct 1 02:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1020) *** Oct 1 02:10:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1020) *** Oct 1 02:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1020, QN: 51/51, ET: 0) *** Oct 1 02:10:05 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1020, QN: 3400/3400, ET: 4) *** Oct 1 02:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 1021) *** Oct 1 02:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 1021, QN: 54/54, ET: 0) *** Oct 1 02:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 1021) *** Oct 1 02:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 1021, QN: 3345/3345, ET: 0) *** Oct 1 02:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1022) *** Oct 1 02:15:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1022) *** Oct 1 02:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1022, QN: 47/47, ET: 0) *** Oct 1 02:15:05 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1022, QN: 3298/3298, ET: 4) *** Oct 1 02:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 1023) *** Oct 1 02:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 1023, QN: 3228/3228, ET: 0) *** Oct 1 02:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 1023) *** Oct 1 02:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 1023, QN: 48/48, ET: 0) *** Oct 1 02:20:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1024) *** Oct 1 02:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1024) *** Oct 1 02:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1024, QN: 53/53, ET: 0) *** Oct 1 02:20:05 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1024, QN: 3442/3442, ET: 4) *** Oct 1 02:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 1025) *** Oct 1 02:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 1025, QN: 3423/3423, ET: 0) *** Oct 1 02:23:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 1025) *** ... 66 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Oct 1 02:09:09 outbound00.cs.umd.edu python3[1464644]: ldapdb [x6] == outbound01.cs.umd.edu (2 distinct, 7 total) == Oct 1 02:13:06 outbound01.cs.umd.edu python3[3730305]: ldapdb [x6] Oct 1 02:27:07 outbound01.cs.umd.edu krb5_child[3733908]: Client 'admin@UMD.EDU' not found in Kerberos database == portal (1 distinct, 68 total) == Oct 1 02:05:20 portal setroubleshoot[3937184]: 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 [x68] == sentry-docker00.cs.umd.edu (38 distinct, 38 total) == Oct 1 02:22:28 sentry-docker00.cs.umd.edu systemd-udevd[3125473]: link_config: could not get ethtool features for vethbe13ece Oct 1 02:22:28 sentry-docker00.cs.umd.edu systemd-udevd[3125473]: Could not set offload features of vethbe13ece: No such device Oct 1 02:22:28 sentry-docker00.cs.umd.edu systemd-udevd[3125548]: Could not generate persistent MAC address for veth150b8df: No such file or directory Oct 1 02:22:28 sentry-docker00.cs.umd.edu systemd-udevd[3125549]: Could not generate persistent MAC address for veth05d28ea: No such file or directory Oct 1 02:22:28 sentry-docker00.cs.umd.edu systemd-udevd[3125552]: Could not generate persistent MAC address for vethe56cbee: No such file or directory Oct 1 02:22:28 sentry-docker00.cs.umd.edu systemd-udevd[3125553]: Could not generate persistent MAC address for vetha6fe10d: No such file or directory Oct 1 02:22:28 sentry-docker00.cs.umd.edu systemd-udevd[3125557]: Could not generate persistent MAC address for vetha7eedf4: No such file or directory Oct 1 02:22:28 sentry-docker00.cs.umd.edu systemd-udevd[3125553]: Could not generate persistent MAC address for vethf03d82e: No such file or directory Oct 1 02:22:28 sentry-docker00.cs.umd.edu systemd-udevd[3125565]: Could not generate persistent MAC address for vethac0dae6: No such file or directory Oct 1 02:22:28 sentry-docker00.cs.umd.edu systemd-udevd[3125555]: Could not generate persistent MAC address for vethe07d54e: No such file or directory Oct 1 02:22:28 sentry-docker00.cs.umd.edu systemd-udevd[3125584]: Could not generate persistent MAC address for vethd3f5795: No such file or directory Oct 1 02:22:28 sentry-docker00.cs.umd.edu systemd-udevd[3125585]: Could not generate persistent MAC address for veth62b3f0a: No such file or directory Oct 1 02:42:36 sentry-docker00.cs.umd.edu systemd-udevd[3135122]: link_config: could not get ethtool features for vetha7eedf4 Oct 1 02:42:36 sentry-docker00.cs.umd.edu systemd-udevd[3135122]: Could not set offload features of vetha7eedf4: No such device Oct 1 02:42:36 sentry-docker00.cs.umd.edu systemd-udevd[3135159]: link_config: could not get ethtool features for veth150b8df Oct 1 02:42:36 sentry-docker00.cs.umd.edu systemd-udevd[3135159]: Could not set offload features of veth150b8df: No such device Oct 1 02:42:36 sentry-docker00.cs.umd.edu systemd-udevd[3135245]: Could not generate persistent MAC address for vethfc5dae7: No such file or directory Oct 1 02:42:36 sentry-docker00.cs.umd.edu systemd-udevd[3135246]: Could not generate persistent MAC address for veth95d6292: No such file or directory Oct 1 02:42:36 sentry-docker00.cs.umd.edu systemd-udevd[3135249]: Could not generate persistent MAC address for veth99372b4: No such file or directory Oct 1 02:42:36 sentry-docker00.cs.umd.edu systemd-udevd[3135251]: Could not generate persistent MAC address for veth0aa32c8: No such file or directory Oct 1 02:42:36 sentry-docker00.cs.umd.edu systemd-udevd[3135264]: Could not generate persistent MAC address for veth70e9658: No such file or directory Oct 1 02:42:36 sentry-docker00.cs.umd.edu systemd-udevd[3135256]: Could not generate persistent MAC address for vethbffb806: No such file or directory Oct 1 02:42:36 sentry-docker00.cs.umd.edu systemd-udevd[3135253]: Could not generate persistent MAC address for veth127b0ac: No such file or directory Oct 1 02:42:36 sentry-docker00.cs.umd.edu systemd-udevd[3135254]: Could not generate persistent MAC address for vethd6d2448: No such file or directory Oct 1 02:42:36 sentry-docker00.cs.umd.edu systemd-udevd[3135256]: Could not generate persistent MAC address for veth610c87f: No such file or directory Oct 1 02:42:36 sentry-docker00.cs.umd.edu systemd-udevd[3135246]: Could not generate persistent MAC address for veth85f3489: No such file or directory Oct 1 03:02:44 sentry-docker00.cs.umd.edu systemd-udevd[3144812]: link_config: could not get ethtool features for veth610c87f Oct 1 03:02:44 sentry-docker00.cs.umd.edu systemd-udevd[3144812]: Could not set offload features of veth610c87f: No such device Oct 1 03:02:45 sentry-docker00.cs.umd.edu systemd-udevd[3144889]: Could not generate persistent MAC address for vethe5c8194: No such file or directory Oct 1 03:02:45 sentry-docker00.cs.umd.edu systemd-udevd[3144893]: Could not generate persistent MAC address for veth5b63bcb: No such file or directory ... 8 more distinct messages not shown == strawberry (7 distinct, 38 total) == Oct 1 02: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 02: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 02:07:04 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Oct 1 02: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 02: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 02:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Oct 1 02:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (10 distinct, 10 total) == Oct 1 02:25:59 submit26-b9-f1 setroubleshoot[397417]: 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 02:25:59 submit26-b9-f1 setroubleshoot[397417]: 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 02:25:59 submit26-b9-f1 setroubleshoot[397417]: 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 02:25:59 submit26-b9-f1 setroubleshoot[397417]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.CZGBTd/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d Oct 1 02:25:59 submit26-b9-f1 setroubleshoot[397417]: 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 02:25:59 submit26-b9-f1 setroubleshoot[397417]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.CZGBTd. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 Oct 1 02:25:59 submit26-b9-f1 setroubleshoot[397417]: 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 02:25:59 submit26-b9-f1 setroubleshoot[397417]: 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 02:25:59 submit26-b9-f1 setroubleshoot[397417]: 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 Oct 1 02:49:31 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-f2 (9 distinct, 12 total) == Oct 1 02:06:53 submit26-b9-f2 setroubleshoot[3703912]: 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 02:06:53 submit26-b9-f2 setroubleshoot[3703912]: 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 02:06:53 submit26-b9-f2 setroubleshoot[3703912]: 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 [x2] Oct 1 02:06:53 submit26-b9-f2 setroubleshoot[3703912]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.fFQyOr/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 [x2] Oct 1 02:06:53 submit26-b9-f2 setroubleshoot[3703912]: 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 [x2] Oct 1 02:06:53 submit26-b9-f2 setroubleshoot[3703912]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.fFQyOr. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8 Oct 1 02:06:53 submit26-b9-f2 setroubleshoot[3703912]: 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 02:06:53 submit26-b9-f2 setroubleshoot[3703912]: 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 02:06:53 submit26-b9-f2 setroubleshoot[3703912]: 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, 2 total) == Oct 1 02:58:41 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x2] == submit26-b9-f4 (1 distinct, 1 total) == Oct 1 02:50:13 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL