Command: /usr/local/sbin/syslog-digest.py Time : 0.0403s Status : exited 0 Output : Syslog digest — 2026-09-25 03:05 EDT Processed 1,610 lines, filtered 1,363 (84%). 247 unknown (165 distinct) from 14 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 25 02:59:30 b0b02.cs.umd.edu rustdesk[818085]: cannot open display: == biggulp.cs.umd.edu (2 distinct, 2 total) == Sep 25 02:55:19 biggulp.cs.umd.edu sshd-session[4064251]: error: kex_protocol_error: type 20 seq 2 [preauth] Sep 25 02:55:19 biggulp.cs.umd.edu sshd-session[4064251]: error: kex_protocol_error: type 30 seq 3 [preauth] == idm00 (1 distinct, 1 total) == Sep 25 02:54:07 idm00 named[4166701]: client @0x7f11a4064588 10.73.240.42#52414: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 25 02:39:51 idmp0 named[1598691]: client @0x7f2d14025948 10.73.240.43#57687: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 9 total) == Sep 25 02:08:31 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x9] == munin (2 distinct, 12 total) == Sep 25 02:23:04 munin sudo[3187345]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x6] Sep 25 02:23:04 munin sudo[3187345]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x6] == newhonors2 (1 distinct, 24 total) == Sep 25 02:13:02 newhonors2 dhcpcd[3119658]: dhcpcd is not running [x24] == ntop00 (95 distinct, 95 total) == Sep 25 02:05:02 ntop00 nfacctd[182312]: INFO ( m1/mysql ): *** Purging cache - START (PID: 442) *** Sep 25 02:05:02 ntop00 nfacctd[182312]: INFO ( m1/mysql ): *** Purging cache - END (PID: 442, QN: 46/46, ET: 0) *** Sep 25 02:05:05 ntop00 sfacctd[182241]: INFO ( m1/mysql ): *** Purging cache - END (PID: 442, QN: 3212/3212, ET: 4) *** Sep 25 02:08:01 ntop00 sfacctd[182241]: INFO ( p1/print ): *** Purging cache - START (PID: 443) *** Sep 25 02:08:01 ntop00 sfacctd[182241]: INFO ( p1/print ): *** Purging cache - END (PID: 443, QN: 3292/3292, ET: 0) *** Sep 25 02:08:01 ntop00 nfacctd[182312]: INFO ( p1/print ): *** Purging cache - START (PID: 443) *** Sep 25 02:08:01 ntop00 nfacctd[182312]: INFO ( p1/print ): *** Purging cache - END (PID: 443, QN: 49/49, ET: 0) *** Sep 25 02:10:01 ntop00 sfacctd[182241]: INFO ( m1/mysql ): *** Purging cache - START (PID: 444) *** Sep 25 02:10:01 ntop00 nfacctd[182312]: INFO ( m1/mysql ): *** Purging cache - START (PID: 444) *** Sep 25 02:10:01 ntop00 nfacctd[182312]: INFO ( m1/mysql ): *** Purging cache - END (PID: 444, QN: 52/52, ET: 0) *** Sep 25 02:10:06 ntop00 sfacctd[182241]: INFO ( m1/mysql ): *** Purging cache - END (PID: 444, QN: 3374/3374, ET: 5) *** Sep 25 02:13:01 ntop00 sfacctd[182241]: INFO ( p1/print ): *** Purging cache - START (PID: 445) *** Sep 25 02:13:01 ntop00 sfacctd[182241]: INFO ( p1/print ): *** Purging cache - END (PID: 445, QN: 3127/3127, ET: 0) *** Sep 25 02:13:01 ntop00 nfacctd[182312]: INFO ( p1/print ): *** Purging cache - START (PID: 445) *** Sep 25 02:13:01 ntop00 nfacctd[182312]: INFO ( p1/print ): *** Purging cache - END (PID: 445, QN: 44/44, ET: 0) *** Sep 25 02:15:01 ntop00 sfacctd[182241]: INFO ( m1/mysql ): *** Purging cache - START (PID: 446) *** Sep 25 02:15:01 ntop00 nfacctd[182312]: INFO ( m1/mysql ): *** Purging cache - START (PID: 446) *** Sep 25 02:15:01 ntop00 nfacctd[182312]: INFO ( m1/mysql ): *** Purging cache - END (PID: 446, QN: 37/37, ET: 0) *** Sep 25 02:15:06 ntop00 sfacctd[182241]: INFO ( m1/mysql ): *** Purging cache - END (PID: 446, QN: 3442/3442, ET: 5) *** Sep 25 02:18:01 ntop00 sfacctd[182241]: INFO ( p1/print ): *** Purging cache - START (PID: 447) *** Sep 25 02:18:01 ntop00 sfacctd[182241]: INFO ( p1/print ): *** Purging cache - END (PID: 447, QN: 4453/4453, ET: 0) *** Sep 25 02:18:01 ntop00 nfacctd[182312]: INFO ( p1/print ): *** Purging cache - START (PID: 447) *** Sep 25 02:18:01 ntop00 nfacctd[182312]: INFO ( p1/print ): *** Purging cache - END (PID: 447, QN: 46/46, ET: 0) *** Sep 25 02:20:01 ntop00 sfacctd[182241]: INFO ( m1/mysql ): *** Purging cache - START (PID: 448) *** Sep 25 02:20:01 ntop00 nfacctd[182312]: INFO ( m1/mysql ): *** Purging cache - START (PID: 448) *** Sep 25 02:20:01 ntop00 nfacctd[182312]: INFO ( m1/mysql ): *** Purging cache - END (PID: 448, QN: 53/53, ET: 0) *** Sep 25 02:20:07 ntop00 sfacctd[182241]: INFO ( m1/mysql ): *** Purging cache - END (PID: 448, QN: 4789/4789, ET: 6) *** Sep 25 02:23:01 ntop00 sfacctd[182241]: INFO ( p1/print ): *** Purging cache - START (PID: 449) *** Sep 25 02:23:01 ntop00 sfacctd[182241]: INFO ( p1/print ): *** Purging cache - END (PID: 449, QN: 4512/4512, ET: 0) *** Sep 25 02:23:01 ntop00 nfacctd[182312]: INFO ( p1/print ): *** Purging cache - START (PID: 449) *** ... 65 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 25 02:09:09 outbound00.cs.umd.edu python3[3618845]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 25 02:13:06 outbound01.cs.umd.edu python3[1684912]: ldapdb [x6] == sentry-docker00.cs.umd.edu (34 distinct, 34 total) == Sep 25 02:22:50 sentry-docker00.cs.umd.edu systemd-udevd[3246759]: link_config: could not get ethtool features for veth48bcb79 Sep 25 02:22:50 sentry-docker00.cs.umd.edu systemd-udevd[3246759]: Could not set offload features of veth48bcb79: No such device Sep 25 02:22:50 sentry-docker00.cs.umd.edu systemd-udevd[3246788]: Could not generate persistent MAC address for vethfc65790: No such file or directory Sep 25 02:22:50 sentry-docker00.cs.umd.edu systemd-udevd[3246789]: Could not generate persistent MAC address for vethb843f53: No such file or directory Sep 25 02:22:50 sentry-docker00.cs.umd.edu systemd-udevd[3246789]: Could not generate persistent MAC address for veth73d4491: No such file or directory Sep 25 02:22:50 sentry-docker00.cs.umd.edu systemd-udevd[3246807]: Could not generate persistent MAC address for veth32ad857: No such file or directory Sep 25 02:22:50 sentry-docker00.cs.umd.edu systemd-udevd[3246840]: Could not generate persistent MAC address for vetheac0ccc: No such file or directory Sep 25 02:22:50 sentry-docker00.cs.umd.edu systemd-udevd[3246844]: Could not generate persistent MAC address for veth0c58b0c: No such file or directory Sep 25 02:22:50 sentry-docker00.cs.umd.edu systemd-udevd[3246875]: Could not generate persistent MAC address for vethf3267bd: No such file or directory Sep 25 02:22:50 sentry-docker00.cs.umd.edu systemd-udevd[3246863]: Could not generate persistent MAC address for veth1aa9cfb: No such file or directory Sep 25 02:22:50 sentry-docker00.cs.umd.edu systemd-udevd[3246859]: Could not generate persistent MAC address for vethcd3cbef: No such file or directory Sep 25 02:22:50 sentry-docker00.cs.umd.edu systemd-udevd[3246871]: Could not generate persistent MAC address for vethf391026: No such file or directory Sep 25 02:43:00 sentry-docker00.cs.umd.edu systemd-udevd[3256518]: Could not generate persistent MAC address for veth6d05b12: No such file or directory Sep 25 02:43:00 sentry-docker00.cs.umd.edu systemd-udevd[3256519]: Could not generate persistent MAC address for veth64cb8da: No such file or directory Sep 25 02:43:00 sentry-docker00.cs.umd.edu systemd-udevd[3256521]: Could not generate persistent MAC address for vetha151448: No such file or directory Sep 25 02:43:00 sentry-docker00.cs.umd.edu systemd-udevd[3256522]: Could not generate persistent MAC address for veth8fe6381: No such file or directory Sep 25 02:43:00 sentry-docker00.cs.umd.edu systemd-udevd[3256540]: Could not generate persistent MAC address for veth4b8c744: No such file or directory Sep 25 02:43:00 sentry-docker00.cs.umd.edu systemd-udevd[3256526]: Could not generate persistent MAC address for veth6f849fc: No such file or directory Sep 25 02:43:00 sentry-docker00.cs.umd.edu systemd-udevd[3256561]: Could not generate persistent MAC address for vethbff2ddd: No such file or directory Sep 25 02:43:00 sentry-docker00.cs.umd.edu systemd-udevd[3256559]: Could not generate persistent MAC address for vethe36071f: No such file or directory Sep 25 02:43:00 sentry-docker00.cs.umd.edu systemd-udevd[3256594]: Could not generate persistent MAC address for veth065cf81: No such file or directory Sep 25 02:43:00 sentry-docker00.cs.umd.edu systemd-udevd[3256576]: Could not generate persistent MAC address for veth7ae0f5f: No such file or directory Sep 25 03:03:07 sentry-docker00.cs.umd.edu systemd-udevd[3266010]: link_config: could not get ethtool features for veth6f849fc Sep 25 03:03:07 sentry-docker00.cs.umd.edu systemd-udevd[3266010]: Could not set offload features of veth6f849fc: No such device Sep 25 03:03:07 sentry-docker00.cs.umd.edu systemd-udevd[3266033]: Could not generate persistent MAC address for veth80c2863: No such file or directory Sep 25 03:03:07 sentry-docker00.cs.umd.edu systemd-udevd[3266034]: Could not generate persistent MAC address for veth040d536: No such file or directory Sep 25 03:03:07 sentry-docker00.cs.umd.edu systemd-udevd[3266059]: Could not generate persistent MAC address for vethdb5bdc8: No such file or directory Sep 25 03:03:07 sentry-docker00.cs.umd.edu systemd-udevd[3266060]: Could not generate persistent MAC address for veth2935eca: No such file or directory Sep 25 03:03:07 sentry-docker00.cs.umd.edu systemd-udevd[3266063]: Could not generate persistent MAC address for vethad7ea3b: No such file or directory Sep 25 03:03:07 sentry-docker00.cs.umd.edu systemd-udevd[3266064]: Could not generate persistent MAC address for vethe352411: No such file or directory ... 4 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 25 02:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 25 02:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 25 02:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 25 02:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 25 02:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 25 02:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 25 02:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (9 distinct, 9 total) == Sep 25 02:25:56 submit26-b9-f1 setroubleshoot[3600625]: 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 Sep 25 02:25:56 submit26-b9-f1 setroubleshoot[3600625]: 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 Sep 25 02:25:56 submit26-b9-f1 setroubleshoot[3600625]: 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 Sep 25 02:25:56 submit26-b9-f1 setroubleshoot[3600625]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.Vloh3l/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d Sep 25 02:25:56 submit26-b9-f1 setroubleshoot[3600625]: 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 Sep 25 02:25:56 submit26-b9-f1 setroubleshoot[3600625]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.Vloh3l. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 Sep 25 02:25:56 submit26-b9-f1 setroubleshoot[3600625]: 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 Sep 25 02:25:56 submit26-b9-f1 setroubleshoot[3600625]: 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 Sep 25 02:25:56 submit26-b9-f1 setroubleshoot[3600625]: 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) == Sep 25 02:06:51 submit26-b9-f2 setroubleshoot[2693227]: 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 Sep 25 02:06:51 submit26-b9-f2 setroubleshoot[2693227]: 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 Sep 25 02:06:51 submit26-b9-f2 setroubleshoot[2693227]: 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 Sep 25 02:06:51 submit26-b9-f2 setroubleshoot[2693227]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.P1TSfZ/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 Sep 25 02:06:51 submit26-b9-f2 setroubleshoot[2693227]: 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 Sep 25 02:06:51 submit26-b9-f2 setroubleshoot[2693227]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.P1TSfZ. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8 Sep 25 02:06:51 submit26-b9-f2 setroubleshoot[2693227]: 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 Sep 25 02:06:51 submit26-b9-f2 setroubleshoot[2693227]: 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 Sep 25 02:06:51 submit26-b9-f2 setroubleshoot[2693227]: 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