Command: /usr/local/sbin/syslog-digest.py Time : 0.0447s Status : exited 0 Output : Syslog digest — 2026-09-15 23:05 EDT Processed 2,089 lines, filtered 1,752 (83%). 337 unknown (116 distinct) from 20 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 15 22:45:34 b0b02.cs.umd.edu rustdesk[1571818]: cannot open display: == biggulp.cs.umd.edu (2 distinct, 2 total) == Sep 15 22:52:36 biggulp.cs.umd.edu sshd-session[1631786]: pam_access(sshd:auth): access denied for user `root' from `212.116.238.41' Sep 15 22:52:39 biggulp.cs.umd.edu sshd-session[1631784]: error: PAM: Authentication failure for root from 212.116.238.41 == csfw00a (1 distinct, 127 total) == Sep 15 22:04:27 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x127] == gle-dind02.cs.umd.edu (24 distinct, 26 total) == Sep 15 22:06:06 gle-dind02.cs.umd.edu systemd-udevd[307572]: Could not generate persistent MAC address for vethc0f4406: No such file or directory Sep 15 22:06:06 gle-dind02.cs.umd.edu systemd-udevd[307573]: Could not generate persistent MAC address for veth4826d56: No such file or directory Sep 15 22:06:06 gle-dind02.cs.umd.edu systemd-udevd[307670]: Could not generate persistent MAC address for veth96ccf4f: No such file or directory Sep 15 22:06:06 gle-dind02.cs.umd.edu systemd-udevd[307671]: Could not generate persistent MAC address for vetha93a802: No such file or directory Sep 15 22:06:07 gle-dind02.cs.umd.edu systemd-udevd[307768]: Could not generate persistent MAC address for veth36b273a: No such file or directory Sep 15 22:06:07 gle-dind02.cs.umd.edu systemd-udevd[307767]: Could not generate persistent MAC address for vethe0d3751: No such file or directory Sep 15 22:06:08 gle-dind02.cs.umd.edu systemd-udevd[307866]: Could not generate persistent MAC address for vethcbedb21: No such file or directory Sep 15 22:06:08 gle-dind02.cs.umd.edu systemd-udevd[307867]: Could not generate persistent MAC address for veth24efa6f: No such file or directory Sep 15 22:06:09 gle-dind02.cs.umd.edu systemd-udevd[307954]: Could not generate persistent MAC address for vetha1045ea: No such file or directory Sep 15 22:06:09 gle-dind02.cs.umd.edu systemd-udevd[307955]: Could not generate persistent MAC address for veth4cf5c3f: No such file or directory Sep 15 22:06:27 gle-dind02.cs.umd.edu systemd-udevd[308240]: Could not generate persistent MAC address for veth4fa09b2: No such file or directory Sep 15 22:06:27 gle-dind02.cs.umd.edu systemd-udevd[308241]: Could not generate persistent MAC address for veth68c838b: No such file or directory Sep 15 22:06:27 gle-dind02.cs.umd.edu systemd-udevd[308338]: Could not generate persistent MAC address for veth1766f45: No such file or directory Sep 15 22:06:27 gle-dind02.cs.umd.edu systemd-udevd[308339]: Could not generate persistent MAC address for veth99085bd: No such file or directory Sep 15 22:06:29 gle-dind02.cs.umd.edu systemd-udevd[308518]: Could not generate persistent MAC address for veth6d6eb6e: No such file or directory Sep 15 22:06:29 gle-dind02.cs.umd.edu systemd-udevd[308517]: Could not generate persistent MAC address for veth4808dfa: No such file or directory Sep 15 22:06:30 gle-dind02.cs.umd.edu systemd-udevd[308629]: Could not generate persistent MAC address for veth0a043c1: No such file or directory Sep 15 22:06:30 gle-dind02.cs.umd.edu systemd-udevd[308630]: Could not generate persistent MAC address for veth29a5f40: No such file or directory Sep 15 22:07:27 gle-dind02.cs.umd.edu kernel: overlayfs: upperdir is in-use as upperdir/workdir of another mount, accessing files from both mounts will result in undefined behavior. [x2] Sep 15 22:07:27 gle-dind02.cs.umd.edu kernel: overlayfs: workdir is in-use as upperdir/workdir of another mount, accessing files from both mounts will result in undefined behavior. [x2] Sep 15 22:10:14 gle-dind02.cs.umd.edu systemd-udevd[311446]: Could not generate persistent MAC address for veth3b5cfd6: No such file or directory Sep 15 22:10:14 gle-dind02.cs.umd.edu systemd-udevd[311447]: Could not generate persistent MAC address for veth6db4dbf: No such file or directory Sep 15 22:10:15 gle-dind02.cs.umd.edu systemd-udevd[311559]: Could not generate persistent MAC address for vethbdbf0df: No such file or directory Sep 15 22:10:15 gle-dind02.cs.umd.edu systemd-udevd[311558]: Could not generate persistent MAC address for vethfcb3f27: No such file or directory == hazfs.cs.umd.edu (2 distinct, 2 total) == Sep 15 22:25:02 hazfs.cs.umd.edu pcp[4077616]: pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily-K.log Sep 15 22:43:45 hazfs.cs.umd.edu pcp[4177705]: pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily.log == idm00 (1 distinct, 1 total) == Sep 15 22:53:55 idm00 named[4166701]: client @0x7f11a006f7c8 10.73.240.42#49448: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 15 22:37:40 idmp0 named[1598691]: client @0x7f2d500324e8 10.73.240.43#60047: update '73.10.in-addr.arpa/IN' denied == inbound00.cs.umd.edu (1 distinct, 6 total) == Sep 15 22:15:34 inbound00.cs.umd.edu krb5_child[592032]: Client 'admin@UMD.EDU' not found in Kerberos database [x6] == itmon02 (1 distinct, 1 total) == Sep 15 22:48:27 itmon02 sshd[1750555]: error: beginning MaxStartups throttling == munin (2 distinct, 12 total) == Sep 15 22:28:42 munin sudo[2588439]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x6] Sep 15 22:28:42 munin sudo[2588439]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x6] == newhonors2 (1 distinct, 24 total) == Sep 15 22:13:03 newhonors2 dhcpcd[2694888]: dhcpcd is not running [x24] == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 15 22:09:09 outbound00.cs.umd.edu python3[472252]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 15 22:13:06 outbound01.cs.umd.edu python3[2731810]: ldapdb [x6] == sentry-docker00.cs.umd.edu (42 distinct, 42 total) == Sep 15 22:11:48 sentry-docker00.cs.umd.edu systemd-udevd[1193193]: link_config: could not get ethtool features for vetha16b034 Sep 15 22:11:48 sentry-docker00.cs.umd.edu systemd-udevd[1193193]: Could not set offload features of vetha16b034: No such device Sep 15 22:11:48 sentry-docker00.cs.umd.edu systemd-udevd[1193196]: link_config: could not get ethtool features for vethffbb998 Sep 15 22:11:48 sentry-docker00.cs.umd.edu systemd-udevd[1193196]: Could not set offload features of vethffbb998: No such device Sep 15 22:11:48 sentry-docker00.cs.umd.edu systemd-udevd[1193224]: Could not generate persistent MAC address for veth1851862: No such file or directory Sep 15 22:11:48 sentry-docker00.cs.umd.edu systemd-udevd[1193225]: Could not generate persistent MAC address for vethba72da4: No such file or directory Sep 15 22:11:48 sentry-docker00.cs.umd.edu systemd-udevd[1193225]: Could not generate persistent MAC address for veth60fecd4: No such file or directory Sep 15 22:11:48 sentry-docker00.cs.umd.edu systemd-udevd[1193228]: Could not generate persistent MAC address for veth5b5d91f: No such file or directory Sep 15 22:11:48 sentry-docker00.cs.umd.edu systemd-udevd[1193224]: Could not generate persistent MAC address for veth035d416: No such file or directory Sep 15 22:11:48 sentry-docker00.cs.umd.edu systemd-udevd[1193237]: Could not generate persistent MAC address for vethd5efacd: No such file or directory Sep 15 22:11:48 sentry-docker00.cs.umd.edu systemd-udevd[1193300]: Could not generate persistent MAC address for veth5459a5f: No such file or directory Sep 15 22:11:48 sentry-docker00.cs.umd.edu systemd-udevd[1193301]: Could not generate persistent MAC address for veth66bed66: No such file or directory Sep 15 22:11:48 sentry-docker00.cs.umd.edu systemd-udevd[1193307]: Could not generate persistent MAC address for veth011e88c: No such file or directory Sep 15 22:11:48 sentry-docker00.cs.umd.edu systemd-udevd[1193308]: Could not generate persistent MAC address for veth9fd4a8f: No such file or directory Sep 15 22:31:57 sentry-docker00.cs.umd.edu systemd-udevd[1202615]: link_config: could not get ethtool features for veth5459a5f Sep 15 22:31:57 sentry-docker00.cs.umd.edu systemd-udevd[1202615]: Could not set offload features of veth5459a5f: No such device Sep 15 22:31:57 sentry-docker00.cs.umd.edu systemd-udevd[1202619]: link_config: could not set ethtool features for veth011e88c Sep 15 22:31:57 sentry-docker00.cs.umd.edu systemd-udevd[1202619]: Could not set offload features of veth011e88c: Operation not permitted Sep 15 22:31:57 sentry-docker00.cs.umd.edu systemd-udevd[1202650]: Could not generate persistent MAC address for vethbe7da1a: No such file or directory Sep 15 22:31:57 sentry-docker00.cs.umd.edu systemd-udevd[1202651]: Could not generate persistent MAC address for vetha2e0016: No such file or directory Sep 15 22:31:57 sentry-docker00.cs.umd.edu systemd-udevd[1202654]: Could not generate persistent MAC address for veth4165e48: No such file or directory Sep 15 22:31:57 sentry-docker00.cs.umd.edu systemd-udevd[1202655]: Could not generate persistent MAC address for veth8b9f2e3: No such file or directory Sep 15 22:31:57 sentry-docker00.cs.umd.edu systemd-udevd[1202678]: Could not generate persistent MAC address for vethd3d1bf4: No such file or directory Sep 15 22:31:57 sentry-docker00.cs.umd.edu systemd-udevd[1202679]: Could not generate persistent MAC address for vethb0c460a: No such file or directory Sep 15 22:31:57 sentry-docker00.cs.umd.edu systemd-udevd[1202697]: Could not generate persistent MAC address for veth648d475: No such file or directory Sep 15 22:31:57 sentry-docker00.cs.umd.edu systemd-udevd[1202679]: Could not generate persistent MAC address for vetha9df859: No such file or directory Sep 15 22:31:57 sentry-docker00.cs.umd.edu systemd-udevd[1202713]: Could not generate persistent MAC address for veth6597dde: No such file or directory Sep 15 22:31:57 sentry-docker00.cs.umd.edu systemd-udevd[1202716]: Could not generate persistent MAC address for vethf13ee29: No such file or directory Sep 15 22:52:05 sentry-docker00.cs.umd.edu systemd-udevd[1212114]: link_config: could not get ethtool features for vethbe7da1a Sep 15 22:52:05 sentry-docker00.cs.umd.edu systemd-udevd[1212114]: Could not set offload features of vethbe7da1a: No such device ... 12 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 15 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 15 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 15 22:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 15 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 15 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 15 22:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 15 22:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (11 distinct, 17 total) == Sep 15 22:11:18 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x4] Sep 15 22:25:52 submit26-b9-f1 setroubleshoot[1877976]: 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 15 22:25:52 submit26-b9-f1 setroubleshoot[1877976]: 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 15 22:25:52 submit26-b9-f1 setroubleshoot[1877976]: 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 [x2] Sep 15 22:25:52 submit26-b9-f1 setroubleshoot[1877976]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.a4oBzC/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d Sep 15 22:25:52 submit26-b9-f1 setroubleshoot[1877976]: 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 [x2] Sep 15 22:25:52 submit26-b9-f1 setroubleshoot[1877976]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.a4oBzC. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 Sep 15 22:25:52 submit26-b9-f1 setroubleshoot[1877976]: 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 15 22:25:52 submit26-b9-f1 setroubleshoot[1877976]: 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 [x2] Sep 15 22:25:52 submit26-b9-f1 setroubleshoot[1877976]: 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 15 22:25:52 submit26-b9-f1 setroubleshoot[1877976]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.Ji6Fwm/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d == submit26-b9-f2 (11 distinct, 15 total) == Sep 15 22:06:47 submit26-b9-f2 setroubleshoot[1008487]: 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 [x2] Sep 15 22:06:47 submit26-b9-f2 setroubleshoot[1008487]: 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 [x2] Sep 15 22:06:48 submit26-b9-f2 setroubleshoot[1008487]: 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 15 22:06:48 submit26-b9-f2 setroubleshoot[1008487]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.nJ8ZLB/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 Sep 15 22:06:48 submit26-b9-f2 setroubleshoot[1008487]: 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 15 22:06:48 submit26-b9-f2 setroubleshoot[1008487]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.nJ8ZLB. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8 Sep 15 22:06:48 submit26-b9-f2 setroubleshoot[1008487]: 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 [x2] Sep 15 22:06:48 submit26-b9-f2 setroubleshoot[1008487]: 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 15 22:06:48 submit26-b9-f2 setroubleshoot[1008487]: 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 [x2] Sep 15 22:06:48 submit26-b9-f2 setroubleshoot[1008487]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.TbrgLf. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8 Sep 15 22:53:31 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-f3 (1 distinct, 5 total) == Sep 15 22:23:06 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x5] == submit26-b9-f4 (1 distinct, 1 total) == Sep 15 22:59:04 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 15 22:11:58 vacuum.cs.umd.edu abrt-hook-ccpp[16492]: Process 12061 (driver) of user 33 killed by SIGABRT - dumping core Sep 15 22:11:58 vacuum.cs.umd.edu abrt-server[16494]: Package 'amanda-backup_server' isn't signed with proper key Sep 15 22:11:58 vacuum.cs.umd.edu abrt-server[16494]: 'post-create' on '/var/spool/abrt/ccpp-2026-09-15-22:11:58-12061' exited with 1 Sep 15 22:11:58 vacuum.cs.umd.edu abrt-server[16494]: Deleting problem directory '/var/spool/abrt/ccpp-2026-09-15-22:11:58-12061'