Command: /usr/local/sbin/syslog-digest.py Time : 0.4836s Status : exited 0 Output : Syslog digest — 2026-07-28 22:05 EDT Processed 4,179 lines, filtered 3,536 (84%). 643 unknown (104 distinct) from 23 host(s). == abuse (1 distinct, 346 total) == Jul 28 21:05:06 abuse rsyslogd[21745]: imjournal: open() failed for path: '/var/lib/rsyslog/imjournal.state.tmp': Input/output error [v8.2404.0 try https://www.rsyslog.com/e/2433 ] [x346] == alec.cs.umd.edu (3 distinct, 60 total) == Jul 28 21:05:27 alec.cs.umd.edu setroubleshoot[4132466]: failed to retrieve rpm info for path '/run/netns/netns-9dfd0347-71eb-5698-085c-c769043aa5c3': [x12] Jul 28 21:05:27 alec.cs.umd.edu sedispatch[1526]: AVC Message regarding setroubleshoot, ignoring message [x24] Jul 28 21:05:27 alec.cs.umd.edu setroubleshoot[4132466]: SELinux is preventing /usr/bin/df from getattr access on the file /run/netns/netns-9dfd0347-71eb-5698-085c-c769043aa5c3. For complete SELinux messages run: sealert -l 23f93208-3063-4aac-b78a-bb0fcb40740c [x24] == b0b02.cs.umd.edu (1 distinct, 1 total) == Jul 28 21:35:31 b0b02.cs.umd.edu rustdesk[435970]: cannot open display: == bachata (1 distinct, 2 total) == Jul 28 21:49:43 bachata setroubleshoot[2079639]: SELinux is preventing /usr/sbin/smbd from name_bind access on the udp_socket port 766. For complete SELinux messages run: sealert -l 8f7247f1-69a5-4a62-a4f0-88a324bfd75c [x2] == contest (9 distinct, 43 total) == Jul 28 21:06:10 contest goferd[1007]: [ERROR][worker-0] gofer.messaging.adapter.connect:33 - connect: proton+amqps://satellite8.cs.umd.edu:5647, failed: Connection amqps://satellite8.cs.umd.edu:5647 disconnected: Condition('proton.pythonio', 'Connection refused to all addresses') [x33] Jul 28 21:48:14 contest setroubleshoot[250389]: SELinux is preventing /usr/libexec/platform-python3.6 from create access on the directory libdnf.HujYl5. For complete SELinux messages run: sealert -l cb6b25c6-4765-4cf2-88a0-9b3b508e94e9 Jul 28 21:48:14 contest setroubleshoot[250389]: SELinux is preventing /usr/bin/gpgconf from add_name access on the directory repodata. For complete SELinux messages run: sealert -l 41cf7b1b-0f34-4609-98f2-b66e7825fef7 [x2] Jul 28 21:48:14 contest setroubleshoot[250389]: SELinux is preventing /usr/libexec/platform-python3.6 from create access on the file mirrorlist. For complete SELinux messages run: sealert -l fc20ff92-ea83-4f38-a24b-ddfd737a3141 Jul 28 21:48:14 contest setroubleshoot[250389]: SELinux is preventing /usr/libexec/platform-python3.6 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l ac675631-fa35-4e93-adc9-b692b18e53e5 Jul 28 21:48:14 contest setroubleshoot[250389]: SELinux is preventing /usr/libexec/platform-python3.6 from read access on the directory libdnf.HujYl5. For complete SELinux messages run: sealert -l 45d103b6-0810-4890-a705-990118577ce8 Jul 28 21:48:14 contest setroubleshoot[250389]: SELinux is preventing /usr/libexec/platform-python3.6 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 7e499113-2fd7-4f67-bec6-3521efbe3637 [x2] Jul 28 21:48:14 contest setroubleshoot[250389]: SELinux is preventing /usr/libexec/platform-python3.6 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 3928930b-a1ed-448d-950b-0665ac2adef8 Jul 28 21:48:15 contest setroubleshoot[250389]: SELinux is preventing /usr/libexec/platform-python3.6 from create access on the directory libdnf.xiuszc. For complete SELinux messages run: sealert -l cb6b25c6-4765-4cf2-88a0-9b3b508e94e9 == csfw00a (1 distinct, 14 total) == Jul 28 21:06:28 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x14] == hackerman (7 distinct, 12 total) == Jul 28 21:19:01 hackerman gnome-software[2060381]: failed to commit changes to dconf: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dfile_2derror_2dquark.Code2: Failed to create file “/adminhomes/sajith/.config/dconf/user.5FK0S3”: Permission denied Jul 28 21:20:04 hackerman gnome-software[2060381]: can't reliably fixup error code 4 in domain g-io-error-quark: Not a directory [x4] Jul 28 21:20:12 hackerman gnome-software[2060381]: Only 0 apps for recent list, hiding Jul 28 21:20:29 hackerman gnome-software[2060381]: failed to commit changes to dconf: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dfile_2derror_2dquark.Code2: Failed to create file “/adminhomes/sajith/.config/dconf/user.S6C7S3”: Permission denied Jul 28 21:20:29 hackerman packagekitd[1614625]: Failed to get cache filename for libreoffice [x2] Jul 28 21:20:29 hackerman packagekitd[1614625]: Failed to get cache filename for kernel [x2] Jul 28 21:20:38 hackerman packagekitd[1614625]: failed to parse public key for /etc/pki/rpm-gpg/RPM-GPG-KEY-PQC-redhat-release == idm00 (1 distinct, 1 total) == Jul 28 21:51:09 idm00 named[1455]: client @0x7f3314afcec8 10.73.240.42#57162: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Jul 28 21:36:03 idmp0 named[5198]: client @0x7f992c025008 10.73.240.43#52626: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 39 total) == Jul 28 21:07:59 itmon02 sshd[1834]: error: beginning MaxStartups throttling [x39] == netman.cs.umd.edu (1 distinct, 2 total) == Jul 28 21:46:44 netman.cs.umd.edu krb5_child[2257301]: Client 'admin@UMD.EDU' not found in Kerberos database [x2] == newhonors.cs.umd.edu (2 distinct, 2 total) == Jul 28 21:25:43 newhonors.cs.umd.edu sshd[17161]: error: maximum authentication attempts exceeded for root from 221.144.183.98 port 59562 ssh2 [preauth] Jul 28 21:25:43 newhonors.cs.umd.edu sshd[17161]: PAM service(sshd) ignoring max retries; 6 > 3 == newhonors2 (1 distinct, 24 total) == Jul 28 21:13:03 newhonors2 dhcpcd[421347]: dhcpcd is not running [x24] == outbound00.cs.umd.edu (1 distinct, 6 total) == Jul 28 21:09:08 outbound00.cs.umd.edu python3[581635]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Jul 28 21:13:06 outbound01.cs.umd.edu python3[2806164]: ldapdb [x6] == sentry-docker00.cs.umd.edu (38 distinct, 38 total) == Jul 28 21:05:09 sentry-docker00.cs.umd.edu systemd-udevd[1413437]: link_config: could not get ethtool features for veth5beeba9 Jul 28 21:05:09 sentry-docker00.cs.umd.edu systemd-udevd[1413437]: Could not set offload features of veth5beeba9: No such device Jul 28 21:05:09 sentry-docker00.cs.umd.edu systemd-udevd[1413440]: link_config: could not get ethtool features for veth80677f2 Jul 28 21:05:09 sentry-docker00.cs.umd.edu systemd-udevd[1413440]: Could not set offload features of veth80677f2: No such device Jul 28 21:05:10 sentry-docker00.cs.umd.edu systemd-udevd[1413489]: Could not generate persistent MAC address for vethb2dfcd3: No such file or directory Jul 28 21:05:10 sentry-docker00.cs.umd.edu systemd-udevd[1413490]: Could not generate persistent MAC address for veth7037ed2: No such file or directory Jul 28 21:05:10 sentry-docker00.cs.umd.edu systemd-udevd[1413493]: Could not generate persistent MAC address for veth0496e44: No such file or directory Jul 28 21:05:10 sentry-docker00.cs.umd.edu systemd-udevd[1413494]: Could not generate persistent MAC address for veth12366f5: No such file or directory Jul 28 21:05:10 sentry-docker00.cs.umd.edu systemd-udevd[1413517]: Could not generate persistent MAC address for vethaa77fa1: No such file or directory Jul 28 21:05:10 sentry-docker00.cs.umd.edu systemd-udevd[1413518]: Could not generate persistent MAC address for vetha8a4133: No such file or directory Jul 28 21:05:10 sentry-docker00.cs.umd.edu systemd-udevd[1413522]: Could not generate persistent MAC address for veth8f6be99: No such file or directory Jul 28 21:05:10 sentry-docker00.cs.umd.edu systemd-udevd[1413523]: Could not generate persistent MAC address for vethf7e4f2a: No such file or directory Jul 28 21:12:00 sentry-docker00.cs.umd.edu systemd-udevd[1417156]: Could not generate persistent MAC address for vethc6b8e37: No such file or directory Jul 28 21:12:00 sentry-docker00.cs.umd.edu systemd-udevd[1417157]: Could not generate persistent MAC address for veth73f044c: No such file or directory Jul 28 21:25:18 sentry-docker00.cs.umd.edu systemd-udevd[1423155]: link_config: could not get ethtool features for veth0496e44 Jul 28 21:25:18 sentry-docker00.cs.umd.edu systemd-udevd[1423155]: Could not set offload features of veth0496e44: No such device Jul 28 21:25:19 sentry-docker00.cs.umd.edu systemd-udevd[1423198]: Could not generate persistent MAC address for vethdfd36ae: No such file or directory Jul 28 21:25:19 sentry-docker00.cs.umd.edu systemd-udevd[1423199]: Could not generate persistent MAC address for veth5ea8a8b: No such file or directory Jul 28 21:25:19 sentry-docker00.cs.umd.edu systemd-udevd[1423208]: Could not generate persistent MAC address for veth7a42bc6: No such file or directory Jul 28 21:25:19 sentry-docker00.cs.umd.edu systemd-udevd[1423209]: Could not generate persistent MAC address for veth94dbec6: No such file or directory Jul 28 21:25:19 sentry-docker00.cs.umd.edu systemd-udevd[1423226]: Could not generate persistent MAC address for veth73997b1: No such file or directory Jul 28 21:25:19 sentry-docker00.cs.umd.edu systemd-udevd[1423227]: Could not generate persistent MAC address for veth1f119c2: No such file or directory Jul 28 21:25:19 sentry-docker00.cs.umd.edu systemd-udevd[1423252]: Could not generate persistent MAC address for vethda34668: No such file or directory Jul 28 21:25:19 sentry-docker00.cs.umd.edu systemd-udevd[1423253]: Could not generate persistent MAC address for veth658a1cb: No such file or directory Jul 28 21:32:08 sentry-docker00.cs.umd.edu systemd-udevd[1426799]: Could not generate persistent MAC address for vethab5d93f: No such file or directory Jul 28 21:32:08 sentry-docker00.cs.umd.edu systemd-udevd[1426800]: Could not generate persistent MAC address for vethba77543: No such file or directory Jul 28 21:45:26 sentry-docker00.cs.umd.edu systemd-udevd[1432602]: link_config: could not get ethtool features for vethdfd36ae Jul 28 21:45:26 sentry-docker00.cs.umd.edu systemd-udevd[1432602]: Could not set offload features of vethdfd36ae: No such device Jul 28 21:45:27 sentry-docker00.cs.umd.edu systemd-udevd[1432626]: Could not generate persistent MAC address for veth184fa46: No such file or directory Jul 28 21:45:27 sentry-docker00.cs.umd.edu systemd-udevd[1432627]: Could not generate persistent MAC address for veth6eb5ab9: No such file or directory ... 8 more distinct messages not shown == strawberry (2 distinct, 8 total) == Jul 28 21:09:44 strawberry udisksd[1067]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/ST2000DM001_1CH164_W1E8J5KJ: Error updating SMART data: Error sending ATA command CHECK POWER MODE: Unexpected sense data returned:#0120000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................#0120010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................#012 (g-io-error-quark, 0) [x6] Jul 28 21:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-2 (9 distinct, 9 total) == Jul 28 21:12:50 submit26-b9-2 setroubleshoot[378270]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l d506243c-d61e-48f3-b42a-4592c913deb0 Jul 28 21:12:50 submit26-b9-2 setroubleshoot[378270]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 3b4752ac-1b9a-4af9-a05b-32e4c2eb13ab Jul 28 21:12:50 submit26-b9-2 setroubleshoot[378270]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 29e5adbd-4381-4467-b40d-a2219101e096 Jul 28 21:12:50 submit26-b9-2 setroubleshoot[378270]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.KyM92y/repodata/repomd.xml. For complete SELinux messages run: sealert -l 1b38f2ec-01ce-4343-8059-ba7494ecc5c4 Jul 28 21:12:50 submit26-b9-2 setroubleshoot[378270]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l e5f9af40-1f63-4924-b012-27ab2a7b2266 Jul 28 21:12:50 submit26-b9-2 setroubleshoot[378270]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.KyM92y. For complete SELinux messages run: sealert -l 5c54db87-54a3-4a7c-97b4-b5c48d6c3543 Jul 28 21:12:50 submit26-b9-2 setroubleshoot[378270]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 63cd60e1-1e61-4276-afea-dd8526ffe8b2 Jul 28 21:12:50 submit26-b9-2 setroubleshoot[378270]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 81c7e9ec-e023-4c6d-b1ad-c02a242e655e Jul 28 21:12:50 submit26-b9-2 setroubleshoot[378270]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 6ae9a597-e123-4d74-8eec-a8ebe0f5e4d0 == submit26-b9-3 (9 distinct, 9 total) == Jul 28 21:20:36 submit26-b9-3 setroubleshoot[666503]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 5b912a44-22fd-4560-b201-2a4e289b73f5 Jul 28 21:20:36 submit26-b9-3 setroubleshoot[666503]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 7f1df1e4-725e-4953-98eb-1079f908f543 Jul 28 21:20:36 submit26-b9-3 setroubleshoot[666503]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 40b8852a-f77b-44b4-affe-5f11fa33de43 Jul 28 21:20:36 submit26-b9-3 setroubleshoot[666503]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.5Y7EQn/repodata/repomd.xml. For complete SELinux messages run: sealert -l 45a8019e-f6b5-4baa-92c1-862594b40d46 Jul 28 21:20:36 submit26-b9-3 setroubleshoot[666503]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l e9f0bfff-7784-4126-baa4-2bb06da56591 Jul 28 21:20:36 submit26-b9-3 setroubleshoot[666503]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.5Y7EQn. For complete SELinux messages run: sealert -l 0b17cc3d-cdc6-4fe2-a11f-3892e7c41dc7 Jul 28 21:20:36 submit26-b9-3 setroubleshoot[666503]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 10e38c64-b65f-4cdd-901e-4375652d9a42 Jul 28 21:20:36 submit26-b9-3 setroubleshoot[666503]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 7fd9cf72-ef38-48e1-b6aa-b571b26a7b22 Jul 28 21:20:36 submit26-b9-3 setroubleshoot[666503]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l b9b11116-89bd-4a3c-980c-1d422c5dcee4 == submit26-b9-4 (1 distinct, 3 total) == Jul 28 21:06:37 submit26-b9-4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x3] == submit26-clnb9 (10 distinct, 14 total) == Jul 28 21:31:54 submit26-clnb9 setroubleshoot[1459460]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 6783ed2b-5ae4-42b5-975a-4bf50eec4658 [x2] Jul 28 21:31:54 submit26-clnb9 setroubleshoot[1459460]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 9e7fa955-cc30-4804-ac8c-e1779e85946c [x2] Jul 28 21:31:54 submit26-clnb9 setroubleshoot[1459460]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 69bfa6e3-089c-40ff-9563-fd30787d0774 Jul 28 21:31:54 submit26-clnb9 setroubleshoot[1459460]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.pFZKWB/repodata/repomd.xml. For complete SELinux messages run: sealert -l 001acdb5-31ef-4e52-b10b-90f467a89ddc Jul 28 21:31:54 submit26-clnb9 setroubleshoot[1459460]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l edacddcf-16ed-4dc3-8d82-7c597d5dee23 Jul 28 21:31:54 submit26-clnb9 setroubleshoot[1459460]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.pFZKWB. For complete SELinux messages run: sealert -l 62b3782e-4730-4488-8178-94dafe9b552c Jul 28 21:31:54 submit26-clnb9 setroubleshoot[1459460]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 81cb3698-78f8-440a-8e3c-e5d1041e6b78 [x2] Jul 28 21:31:54 submit26-clnb9 setroubleshoot[1459460]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 792b472a-115c-4799-9805-fc7436f916b9 Jul 28 21:31:54 submit26-clnb9 setroubleshoot[1459460]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 15c83a86-837b-41e2-b662-b39cd4e361cb [x2] Jul 28 21:31:54 submit26-clnb9 setroubleshoot[1459460]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.1z1tFW. For complete SELinux messages run: sealert -l 62b3782e-4730-4488-8178-94dafe9b552c == whiffle.cs.umd.edu (2 distinct, 2 total) == Jul 28 21:21:53 whiffle.cs.umd.edu kernel: libceph: wrong peer, want 10.73.235.200:6801/-1847179276, got 10.73.235.200:6801/-1947649014 Jul 28 21:21:53 whiffle.cs.umd.edu kernel: libceph: osd0 10.73.235.200:6801 wrong peer at address == wraith (1 distinct, 1 total) == Jul 28 21:38:23 wraith kernel: workqueue: output_poll_execute hogged CPU for >10000us 32771 times, consider switching to WQ_UNBOUND