Command: /usr/local/sbin/syslog-digest.py Time : 0.0418s Status : exited 0 Output : Syslog digest — 2026-09-24 23:05 EDT Processed 1,706 lines, filtered 1,451 (85%). 255 unknown (175 distinct) from 17 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 24 22:59:14 b0b02.cs.umd.edu rustdesk[756289]: cannot open display: == idm00 (1 distinct, 1 total) == Sep 24 22:54:06 idm00 named[4166701]: client @0x7f11a40662f8 10.73.240.42#64761: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 24 22:39:51 idmp0 named[1598691]: client @0x7f2d50036288 10.73.240.43#56562: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 4 total) == Sep 24 22:18:22 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x4] == munin (2 distinct, 10 total) == Sep 24 22:33:40 munin sudo[3104690]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x5] Sep 24 22:33:40 munin sudo[3104690]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x5] == netman.cs.umd.edu (1 distinct, 2 total) == Sep 24 22:14:59 netman.cs.umd.edu krb5_child[358530]: Client 'admin@UMD.EDU' not found in Kerberos database [x2] == newhonors.cs.umd.edu (1 distinct, 1 total) == Sep 24 23:02:41 newhonors.cs.umd.edu systemd-tmpfiles: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. == newhonors2 (1 distinct, 24 total) == Sep 24 22:13:02 newhonors2 dhcpcd[3111902]: dhcpcd is not running [x24] == ntop00 (96 distinct, 96 total) == Sep 24 22:05:01 ntop00 nfacctd[182312]: INFO ( m1/mysql ): *** Purging cache - START (PID: 346) *** Sep 24 22:05:01 ntop00 nfacctd[182312]: INFO ( m1/mysql ): *** Purging cache - END (PID: 346, QN: 44/44, ET: 0) *** Sep 24 22:05:08 ntop00 sfacctd[182241]: INFO ( m1/mysql ): *** Purging cache - END (PID: 346, QN: 4345/4345, ET: 7) *** Sep 24 22:08:01 ntop00 sfacctd[182241]: INFO ( p1/print ): *** Purging cache - START (PID: 347) *** Sep 24 22:08:01 ntop00 sfacctd[182241]: INFO ( p1/print ): *** Purging cache - END (PID: 347, QN: 4739/4739, ET: 0) *** Sep 24 22:08:01 ntop00 nfacctd[182312]: INFO ( p1/print ): *** Purging cache - START (PID: 347) *** Sep 24 22:08:01 ntop00 nfacctd[182312]: INFO ( p1/print ): *** Purging cache - END (PID: 347, QN: 52/52, ET: 0) *** Sep 24 22:10:01 ntop00 sfacctd[182241]: INFO ( m1/mysql ): *** Purging cache - START (PID: 348) *** Sep 24 22:10:01 ntop00 nfacctd[182312]: INFO ( m1/mysql ): *** Purging cache - START (PID: 348) *** Sep 24 22:10:01 ntop00 nfacctd[182312]: INFO ( m1/mysql ): *** Purging cache - END (PID: 348, QN: 49/49, ET: 0) *** Sep 24 22:10:08 ntop00 sfacctd[182241]: INFO ( m1/mysql ): *** Purging cache - END (PID: 348, QN: 4692/4692, ET: 7) *** Sep 24 22:13:01 ntop00 sfacctd[182241]: INFO ( p1/print ): *** Purging cache - START (PID: 349) *** Sep 24 22:13:01 ntop00 sfacctd[182241]: INFO ( p1/print ): *** Purging cache - END (PID: 349, QN: 4467/4467, ET: 0) *** Sep 24 22:13:01 ntop00 nfacctd[182312]: INFO ( p1/print ): *** Purging cache - START (PID: 349) *** Sep 24 22:13:01 ntop00 nfacctd[182312]: INFO ( p1/print ): *** Purging cache - END (PID: 349, QN: 53/53, ET: 0) *** Sep 24 22:15:01 ntop00 sfacctd[182241]: INFO ( m1/mysql ): *** Purging cache - START (PID: 350) *** Sep 24 22:15:01 ntop00 nfacctd[182312]: INFO ( m1/mysql ): *** Purging cache - START (PID: 350) *** Sep 24 22:15:02 ntop00 nfacctd[182312]: INFO ( m1/mysql ): *** Purging cache - END (PID: 350, QN: 52/52, ET: 1) *** Sep 24 22:15:09 ntop00 sfacctd[182241]: INFO ( m1/mysql ): *** Purging cache - END (PID: 350, QN: 4932/4932, ET: 8) *** Sep 24 22:18:01 ntop00 sfacctd[182241]: INFO ( p1/print ): *** Purging cache - START (PID: 351) *** Sep 24 22:18:01 ntop00 sfacctd[182241]: INFO ( p1/print ): *** Purging cache - END (PID: 351, QN: 5389/5389, ET: 0) *** Sep 24 22:18:01 ntop00 nfacctd[182312]: INFO ( p1/print ): *** Purging cache - START (PID: 351) *** Sep 24 22:18:01 ntop00 nfacctd[182312]: INFO ( p1/print ): *** Purging cache - END (PID: 351, QN: 52/52, ET: 0) *** Sep 24 22:20:01 ntop00 nfacctd[182312]: INFO ( m1/mysql ): *** Purging cache - START (PID: 352) *** Sep 24 22:20:01 ntop00 nfacctd[182312]: INFO ( m1/mysql ): *** Purging cache - END (PID: 352, QN: 47/47, ET: 0) *** Sep 24 22:20:01 ntop00 sfacctd[182241]: INFO ( m1/mysql ): *** Purging cache - START (PID: 352) *** Sep 24 22:20:08 ntop00 sfacctd[182241]: INFO ( m1/mysql ): *** Purging cache - END (PID: 352, QN: 5003/5003, ET: 7) *** Sep 24 22:23:01 ntop00 sfacctd[182241]: INFO ( p1/print ): *** Purging cache - START (PID: 353) *** Sep 24 22:23:01 ntop00 sfacctd[182241]: INFO ( p1/print ): *** Purging cache - END (PID: 353, QN: 4694/4694, ET: 0) *** Sep 24 22:23:01 ntop00 nfacctd[182312]: INFO ( p1/print ): *** Purging cache - START (PID: 353) *** ... 66 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 24 22:09:08 outbound00.cs.umd.edu python3[3561056]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 24 22:13:06 outbound01.cs.umd.edu python3[1627922]: ldapdb [x6] == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Sep 24 22:21:10 sentry-docker00.cs.umd.edu systemd-udevd[3133366]: link_config: could not get ethtool features for vethf7a0797 Sep 24 22:21:10 sentry-docker00.cs.umd.edu systemd-udevd[3133366]: Could not set offload features of vethf7a0797: No such device Sep 24 22:21:11 sentry-docker00.cs.umd.edu systemd-udevd[3133399]: Could not generate persistent MAC address for veth7663d24: No such file or directory Sep 24 22:21:11 sentry-docker00.cs.umd.edu systemd-udevd[3133400]: Could not generate persistent MAC address for vethd1be5dc: No such file or directory Sep 24 22:21:11 sentry-docker00.cs.umd.edu systemd-udevd[3133403]: Could not generate persistent MAC address for vethebff772: No such file or directory Sep 24 22:21:11 sentry-docker00.cs.umd.edu systemd-udevd[3133403]: Could not generate persistent MAC address for veth9997770: No such file or directory Sep 24 22:21:11 sentry-docker00.cs.umd.edu systemd-udevd[3133413]: Could not generate persistent MAC address for vethe3be107: No such file or directory Sep 24 22:21:11 sentry-docker00.cs.umd.edu systemd-udevd[3133421]: Could not generate persistent MAC address for vethcd4ec56: No such file or directory Sep 24 22:21:11 sentry-docker00.cs.umd.edu systemd-udevd[3133429]: Could not generate persistent MAC address for veth27d1726: No such file or directory Sep 24 22:21:11 sentry-docker00.cs.umd.edu systemd-udevd[3133430]: Could not generate persistent MAC address for vethad06bea: No such file or directory Sep 24 22:21:11 sentry-docker00.cs.umd.edu systemd-udevd[3133465]: Could not generate persistent MAC address for vethd148ea7: No such file or directory Sep 24 22:21:11 sentry-docker00.cs.umd.edu systemd-udevd[3133430]: Could not generate persistent MAC address for veth4941865: No such file or directory Sep 24 22:41:19 sentry-docker00.cs.umd.edu systemd-udevd[3142740]: link_config: could not get ethtool features for veth27d1726 Sep 24 22:41:19 sentry-docker00.cs.umd.edu systemd-udevd[3142740]: Could not set offload features of veth27d1726: No such device Sep 24 22:41:19 sentry-docker00.cs.umd.edu systemd-udevd[3142805]: Could not generate persistent MAC address for veth26856fe: No such file or directory Sep 24 22:41:19 sentry-docker00.cs.umd.edu systemd-udevd[3142806]: Could not generate persistent MAC address for veth7685bc5: No such file or directory Sep 24 22:41:19 sentry-docker00.cs.umd.edu systemd-udevd[3142809]: Could not generate persistent MAC address for veth7775f24: No such file or directory Sep 24 22:41:19 sentry-docker00.cs.umd.edu systemd-udevd[3142810]: Could not generate persistent MAC address for veth599da29: No such file or directory Sep 24 22:41:19 sentry-docker00.cs.umd.edu systemd-udevd[3142813]: Could not generate persistent MAC address for vethf40c6d7: No such file or directory Sep 24 22:41:19 sentry-docker00.cs.umd.edu systemd-udevd[3142815]: Could not generate persistent MAC address for veth6a2cf73: No such file or directory Sep 24 22:41:19 sentry-docker00.cs.umd.edu systemd-udevd[3142835]: Could not generate persistent MAC address for veth8e02508: No such file or directory Sep 24 22:41:19 sentry-docker00.cs.umd.edu systemd-udevd[3142836]: Could not generate persistent MAC address for veth91a3bae: No such file or directory Sep 24 22:41:19 sentry-docker00.cs.umd.edu systemd-udevd[3142861]: Could not generate persistent MAC address for veth2c511f9: No such file or directory Sep 24 22:41:19 sentry-docker00.cs.umd.edu systemd-udevd[3142862]: Could not generate persistent MAC address for vethf2eab89: No such file or directory Sep 24 23:01:27 sentry-docker00.cs.umd.edu systemd-udevd[3152245]: link_config: could not get ethtool features for vethf40c6d7 Sep 24 23:01:27 sentry-docker00.cs.umd.edu systemd-udevd[3152245]: Could not set offload features of vethf40c6d7: No such device Sep 24 23:01:27 sentry-docker00.cs.umd.edu systemd-udevd[3152278]: Could not generate persistent MAC address for veth479a450: No such file or directory Sep 24 23:01:27 sentry-docker00.cs.umd.edu systemd-udevd[3152279]: Could not generate persistent MAC address for vetha4ded74: No such file or directory Sep 24 23:01:27 sentry-docker00.cs.umd.edu systemd-udevd[3152282]: Could not generate persistent MAC address for veth921e8f5: No such file or directory Sep 24 23:01:27 sentry-docker00.cs.umd.edu systemd-udevd[3152283]: Could not generate persistent MAC address for veth5078cc7: No such file or directory ... 6 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 24 22:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 24 22:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 24 22:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 24 22:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 24 22:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 24 22:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 24 22:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (10 distinct, 10 total) == Sep 24 22:25:56 submit26-b9-f1 setroubleshoot[3547980]: 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 24 22:25:56 submit26-b9-f1 setroubleshoot[3547980]: 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 24 22:25:56 submit26-b9-f1 setroubleshoot[3547980]: 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 24 22:25:56 submit26-b9-f1 setroubleshoot[3547980]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.WgM4AW/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d Sep 24 22:25:56 submit26-b9-f1 setroubleshoot[3547980]: 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 24 22:25:56 submit26-b9-f1 setroubleshoot[3547980]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.WgM4AW. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 Sep 24 22:25:56 submit26-b9-f1 setroubleshoot[3547980]: 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 24 22:25:56 submit26-b9-f1 setroubleshoot[3547980]: 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 24 22:25:56 submit26-b9-f1 setroubleshoot[3547980]: 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 Sep 24 22:43:37 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-f2 (10 distinct, 11 total) == Sep 24 22:06:51 submit26-b9-f2 setroubleshoot[2629604]: 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 24 22:06:51 submit26-b9-f2 setroubleshoot[2629604]: 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 24 22:06:51 submit26-b9-f2 setroubleshoot[2629604]: 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 24 22:06:51 submit26-b9-f2 setroubleshoot[2629604]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.CGs8YA/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 Sep 24 22:06:51 submit26-b9-f2 setroubleshoot[2629604]: 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 24 22:06:51 submit26-b9-f2 setroubleshoot[2629604]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.CGs8YA. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8 Sep 24 22:06:51 submit26-b9-f2 setroubleshoot[2629604]: 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 24 22:06:51 submit26-b9-f2 setroubleshoot[2629604]: 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 24 22:06:51 submit26-b9-f2 setroubleshoot[2629604]: 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 Sep 24 22:25:20 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x2] == submit26-b9-f4 (1 distinct, 4 total) == Sep 24 22:23:11 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x4] == vacuum.cs.umd.edu (4 distinct, 4 total) == Sep 24 22:11:58 vacuum.cs.umd.edu abrt-hook-ccpp[11619]: Process 7192 (driver) of user 33 killed by SIGABRT - dumping core Sep 24 22:11:58 vacuum.cs.umd.edu abrt-server[11621]: Package 'amanda-backup_server' isn't signed with proper key Sep 24 22:11:58 vacuum.cs.umd.edu abrt-server[11621]: 'post-create' on '/var/spool/abrt/ccpp-2026-09-24-22:11:58-7192' exited with 1 Sep 24 22:11:58 vacuum.cs.umd.edu abrt-server[11621]: Deleting problem directory '/var/spool/abrt/ccpp-2026-09-24-22:11:58-7192'