Command: /usr/local/sbin/syslog-digest.py Time : 0.0503s Status : exited 0 Output : Syslog digest — 2026-09-17 23:05 EDT Processed 2,603 lines, filtered 2,156 (82%). 447 unknown (185 distinct) from 20 host(s). == abadi-computer (2 distinct, 2 total) == Sep 17 22:18:33 abadi-computer systemd-tmpfiles[1019068]: Opening file "/tmp/code-61e9f49c-a2ac-4356-823a-010a7b8bc67a" failed, ignoring: No such device or address Sep 17 22:18:33 abadi-computer systemd-tmpfiles[1019068]: Opening file "/tmp/code-283361a3-25bb-405e-a353-1fa70f26fd43" failed, ignoring: No such device or address == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 17 22:48:40 b0b02.cs.umd.edu rustdesk[2308400]: cannot open display: == csfw00a (1 distinct, 119 total) == Sep 17 22:04:01 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x119] == idm00 (1 distinct, 1 total) == Sep 17 22:53:57 idm00 named[4166701]: client @0x7f11a4069dd8 10.73.240.42#62077: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 17 22:37:57 idmp0 named[1598691]: client @0x7f2d1c01f278 10.73.240.43#53106: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 6 total) == Sep 17 22:08:42 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x6] == matrix (2 distinct, 3 total) == Sep 17 22:22:38 matrix krb5_child[1034615]: Client 'admin@UMD.EDU' not found in Kerberos database [x2] Sep 17 22:22:40 matrix sshd[1034609]: error: PAM: Authentication failure for admin from 34.140.225.163 == munin (2 distinct, 28 total) == Sep 17 22:48:16 munin sudo[3641960]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x14] Sep 17 22:48:16 munin sudo[3641960]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x14] == newhonors.cs.umd.edu (1 distinct, 1 total) == Sep 17 22:57:21 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 17 22:13:03 newhonors2 dhcpcd[2786783]: dhcpcd is not running [x24] == ntop00 (101 distinct, 145 total) == Sep 17 22:05:01 ntop00 nfacctd[323381]: INFO ( m1/mysql ): *** Purging cache - START (PID: 34) *** Sep 17 22:05:09 ntop00 sfacctd[323304]: INFO ( m1/mysql ): *** Purging cache - END (PID: 34, QN: 5158/5158, ET: 8) *** Sep 17 22:05:09 ntop00 nfacctd[323381]: INFO ( m1/mysql ): *** Purging cache - END (PID: 34, QN: 76/76, ET: 8) *** Sep 17 22:06:01 ntop00 sfacctd[323304]: INFO ( p1/print ): *** Purging cache - START (PID: 35) *** Sep 17 22:06:01 ntop00 sfacctd[323304]: INFO ( p1/print ): *** Purging cache - END (PID: 35, QN: 5274/5274, ET: 0) *** Sep 17 22:06:01 ntop00 nfacctd[323381]: INFO ( p1/print ): *** Purging cache - START (PID: 35) *** Sep 17 22:06:01 ntop00 nfacctd[323381]: INFO ( p1/print ): *** Purging cache - END (PID: 35, QN: 80/80, ET: 0) *** Sep 17 22:06:02 ntop00 setroubleshoot[333805]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l 58e35a5d-c7c9-4337-868c-bb9d5ac2e29f [x12] Sep 17 22:06:02 ntop00 setroubleshoot[333805]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 369b1df3-2c9d-461b-8b1c-2fcd48dc737c [x12] Sep 17 22:06:02 ntop00 setroubleshoot[333805]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12] Sep 17 22:06:02 ntop00 setroubleshoot[333805]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l 481e7e24-3846-4790-b17b-9e44a5f5b5d6 [x12] Sep 17 22:10:01 ntop00 sfacctd[323304]: INFO ( m1/mysql ): *** Purging cache - START (PID: 36) *** Sep 17 22:10:01 ntop00 nfacctd[323381]: INFO ( m1/mysql ): *** Purging cache - START (PID: 36) *** Sep 17 22:10:09 ntop00 sfacctd[323304]: INFO ( m1/mysql ): *** Purging cache - END (PID: 36, QN: 5339/5339, ET: 8) *** Sep 17 22:10:09 ntop00 nfacctd[323381]: INFO ( m1/mysql ): *** Purging cache - END (PID: 36, QN: 66/66, ET: 8) *** Sep 17 22:11:01 ntop00 sfacctd[323304]: INFO ( p1/print ): *** Purging cache - START (PID: 37) *** Sep 17 22:11:01 ntop00 sfacctd[323304]: INFO ( p1/print ): *** Purging cache - END (PID: 37, QN: 5216/5216, ET: 0) *** Sep 17 22:11:01 ntop00 nfacctd[323381]: INFO ( p1/print ): *** Purging cache - START (PID: 37) *** Sep 17 22:11:01 ntop00 nfacctd[323381]: INFO ( p1/print ): *** Purging cache - END (PID: 37, QN: 62/62, ET: 0) *** Sep 17 22:15:01 ntop00 sfacctd[323304]: INFO ( m1/mysql ): *** Purging cache - START (PID: 38) *** Sep 17 22:15:01 ntop00 nfacctd[323381]: INFO ( m1/mysql ): *** Purging cache - START (PID: 38) *** Sep 17 22:15:09 ntop00 sfacctd[323304]: INFO ( m1/mysql ): *** Purging cache - END (PID: 38, QN: 5262/5262, ET: 8) *** Sep 17 22:15:09 ntop00 nfacctd[323381]: INFO ( m1/mysql ): *** Purging cache - END (PID: 38, QN: 67/67, ET: 8) *** Sep 17 22:16:01 ntop00 sfacctd[323304]: INFO ( p1/print ): *** Purging cache - START (PID: 39) *** Sep 17 22:16:01 ntop00 sfacctd[323304]: INFO ( p1/print ): *** Purging cache - END (PID: 39, QN: 5290/5290, ET: 0) *** Sep 17 22:16:01 ntop00 nfacctd[323381]: INFO ( p1/print ): *** Purging cache - START (PID: 39) *** Sep 17 22:16:01 ntop00 nfacctd[323381]: INFO ( p1/print ): *** Purging cache - END (PID: 39, QN: 59/59, ET: 0) *** Sep 17 22:20:01 ntop00 sfacctd[323304]: INFO ( m1/mysql ): *** Purging cache - START (PID: 40) *** Sep 17 22:20:01 ntop00 nfacctd[323381]: INFO ( m1/mysql ): *** Purging cache - START (PID: 40) *** Sep 17 22:20:09 ntop00 sfacctd[323304]: INFO ( m1/mysql ): *** Purging cache - END (PID: 40, QN: 5449/5449, ET: 8) *** ... 71 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 17 22:09:09 outbound00.cs.umd.edu python3[1153484]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 17 22:13:06 outbound01.cs.umd.edu python3[3413156]: ldapdb [x6] == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Sep 17 22:11:38 sentry-docker00.cs.umd.edu systemd-udevd[2551576]: link_config: could not get ethtool features for veth000f232 Sep 17 22:11:38 sentry-docker00.cs.umd.edu systemd-udevd[2551576]: Could not set offload features of veth000f232: No such device Sep 17 22:11:38 sentry-docker00.cs.umd.edu systemd-udevd[2551605]: Could not generate persistent MAC address for vethb4f824d: No such file or directory Sep 17 22:11:38 sentry-docker00.cs.umd.edu systemd-udevd[2551606]: Could not generate persistent MAC address for vethc39ee7a: No such file or directory Sep 17 22:11:38 sentry-docker00.cs.umd.edu systemd-udevd[2551624]: Could not generate persistent MAC address for veth750dd60: No such file or directory Sep 17 22:11:38 sentry-docker00.cs.umd.edu systemd-udevd[2551610]: Could not generate persistent MAC address for vethc59a6c9: No such file or directory Sep 17 22:11:38 sentry-docker00.cs.umd.edu systemd-udevd[2551633]: Could not generate persistent MAC address for veth055829d: No such file or directory Sep 17 22:11:38 sentry-docker00.cs.umd.edu systemd-udevd[2551634]: Could not generate persistent MAC address for veth24b4e90: No such file or directory Sep 17 22:11:38 sentry-docker00.cs.umd.edu systemd-udevd[2551652]: Could not generate persistent MAC address for veth16d66b2: No such file or directory Sep 17 22:11:38 sentry-docker00.cs.umd.edu systemd-udevd[2551646]: Could not generate persistent MAC address for veth5a7a7d6: No such file or directory Sep 17 22:11:38 sentry-docker00.cs.umd.edu systemd-udevd[2551661]: Could not generate persistent MAC address for vethfc3de2f: No such file or directory Sep 17 22:11:38 sentry-docker00.cs.umd.edu systemd-udevd[2551662]: Could not generate persistent MAC address for veth264599f: No such file or directory Sep 17 22:31:46 sentry-docker00.cs.umd.edu systemd-udevd[2561044]: link_config: could not get ethtool features for veth16d66b2 Sep 17 22:31:46 sentry-docker00.cs.umd.edu systemd-udevd[2561044]: Could not set offload features of veth16d66b2: No such device Sep 17 22:31:47 sentry-docker00.cs.umd.edu systemd-udevd[2561069]: Could not generate persistent MAC address for veth6f1682a: No such file or directory Sep 17 22:31:47 sentry-docker00.cs.umd.edu systemd-udevd[2561068]: Could not generate persistent MAC address for veth017f796: No such file or directory Sep 17 22:31:47 sentry-docker00.cs.umd.edu systemd-udevd[2561072]: Could not generate persistent MAC address for vethf46a5a3: No such file or directory Sep 17 22:31:47 sentry-docker00.cs.umd.edu systemd-udevd[2561084]: Could not generate persistent MAC address for veth681e127: No such file or directory Sep 17 22:31:47 sentry-docker00.cs.umd.edu systemd-udevd[2561079]: Could not generate persistent MAC address for vethb63f6a3: No such file or directory Sep 17 22:31:47 sentry-docker00.cs.umd.edu systemd-udevd[2561069]: Could not generate persistent MAC address for veth5e6397b: No such file or directory Sep 17 22:31:47 sentry-docker00.cs.umd.edu systemd-udevd[2561098]: Could not generate persistent MAC address for veth7dc8d3c: No such file or directory Sep 17 22:31:47 sentry-docker00.cs.umd.edu systemd-udevd[2561099]: Could not generate persistent MAC address for veth5e87b45: No such file or directory Sep 17 22:31:47 sentry-docker00.cs.umd.edu systemd-udevd[2561149]: Could not generate persistent MAC address for veth3dfdd80: No such file or directory Sep 17 22:31:47 sentry-docker00.cs.umd.edu systemd-udevd[2561150]: Could not generate persistent MAC address for veth724aafa: No such file or directory Sep 17 22:51:55 sentry-docker00.cs.umd.edu systemd-udevd[2570401]: link_config: could not set ethtool features for veth3dfdd80 Sep 17 22:51:55 sentry-docker00.cs.umd.edu systemd-udevd[2570401]: Could not set offload features of veth3dfdd80: Operation not permitted Sep 17 22:51:55 sentry-docker00.cs.umd.edu systemd-udevd[2570475]: Could not generate persistent MAC address for vethd19f062: No such file or directory Sep 17 22:51:55 sentry-docker00.cs.umd.edu systemd-udevd[2570476]: Could not generate persistent MAC address for veth093863e: No such file or directory Sep 17 22:51:55 sentry-docker00.cs.umd.edu systemd-udevd[2570494]: Could not generate persistent MAC address for veth2178070: No such file or directory Sep 17 22:51:55 sentry-docker00.cs.umd.edu systemd-udevd[2570493]: Could not generate persistent MAC address for vethec6b1ee: No such file or directory ... 6 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 17 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 17 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 17 22:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 17 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 17 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 17 22:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 17 22:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (10 distinct, 11 total) == Sep 17 22:25:05 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x2] Sep 17 22:25:53 submit26-b9-f1 setroubleshoot[2245450]: 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 17 22:25:53 submit26-b9-f1 setroubleshoot[2245450]: 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 17 22:25:53 submit26-b9-f1 setroubleshoot[2245450]: 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 17 22:25:53 submit26-b9-f1 setroubleshoot[2245450]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.Kdyimu/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d Sep 17 22:25:53 submit26-b9-f1 setroubleshoot[2245450]: 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 17 22:25:53 submit26-b9-f1 setroubleshoot[2245450]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.Kdyimu. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 Sep 17 22:25:53 submit26-b9-f1 setroubleshoot[2245450]: 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 17 22:25:53 submit26-b9-f1 setroubleshoot[2245450]: 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 17 22:25:53 submit26-b9-f1 setroubleshoot[2245450]: 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 (10 distinct, 13 total) == Sep 17 22:06:48 submit26-b9-f2 setroubleshoot[1379451]: 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 17 22:06:48 submit26-b9-f2 setroubleshoot[1379451]: 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 17 22:06:48 submit26-b9-f2 setroubleshoot[1379451]: 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] Sep 17 22:06:48 submit26-b9-f2 setroubleshoot[1379451]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.Qzfdwj/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 Sep 17 22:06:48 submit26-b9-f2 setroubleshoot[1379451]: 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] Sep 17 22:06:48 submit26-b9-f2 setroubleshoot[1379451]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.Qzfdwj. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8 Sep 17 22:06:48 submit26-b9-f2 setroubleshoot[1379451]: 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 17 22:06:48 submit26-b9-f2 setroubleshoot[1379451]: 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 [x2] Sep 17 22:06:48 submit26-b9-f2 setroubleshoot[1379451]: 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 17 22:06:48 submit26-b9-f2 setroubleshoot[1379451]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.jegBcf/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 == submit26-b9-f3 (1 distinct, 1 total) == Sep 17 22:53:34 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-f4 (1 distinct, 1 total) == Sep 17 22:45:47 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == vacuum.cs.umd.edu (4 distinct, 4 total) == Sep 17 22:11:58 vacuum.cs.umd.edu abrt-hook-ccpp[26413]: Process 21992 (driver) of user 33 killed by SIGABRT - dumping core Sep 17 22:11:58 vacuum.cs.umd.edu abrt-server[26415]: Package 'amanda-backup_server' isn't signed with proper key Sep 17 22:11:58 vacuum.cs.umd.edu abrt-server[26415]: 'post-create' on '/var/spool/abrt/ccpp-2026-09-17-22:11:58-21992' exited with 1 Sep 17 22:11:58 vacuum.cs.umd.edu abrt-server[26415]: Deleting problem directory '/var/spool/abrt/ccpp-2026-09-17-22:11:58-21992'