Command: /usr/local/sbin/syslog-digest.py Time : 0.5119s Status : exited 0 Output : Syslog digest — 2026-07-26 22:05 EDT Processed 4,481 lines, filtered 3,676 (82%). 805 unknown (97 distinct) from 20 host(s). == abuse (1 distinct, 347 total) == Jul 26 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 ] [x347] == alec.cs.umd.edu (3 distinct, 61 total) == Jul 26 21:05:19 alec.cs.umd.edu setroubleshoot[3415177]: failed to retrieve rpm info for path '/run/netns/netns-9dfd0347-71eb-5698-085c-c769043aa5c3': [x12] Jul 26 21:05:20 alec.cs.umd.edu sedispatch[1526]: AVC Message regarding setroubleshoot, ignoring message [x25] Jul 26 21:05:20 alec.cs.umd.edu setroubleshoot[3415177]: 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 26 21:56:10 b0b02.cs.umd.edu rustdesk[917837]: cannot open display: == contest (9 distinct, 41 total) == Jul 26 21:06:34 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 26 21:48:13 contest setroubleshoot[139900]: SELinux is preventing /usr/libexec/platform-python3.6 from create access on the directory libdnf.vGPeQH. For complete SELinux messages run: sealert -l cb6b25c6-4765-4cf2-88a0-9b3b508e94e9 Jul 26 21:48:13 contest setroubleshoot[139900]: 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 Jul 26 21:48:13 contest setroubleshoot[139900]: 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 26 21:48:13 contest setroubleshoot[139900]: 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 26 21:48:13 contest setroubleshoot[139900]: SELinux is preventing /usr/libexec/platform-python3.6 from read access on the directory libdnf.vGPeQH. For complete SELinux messages run: sealert -l 45d103b6-0810-4890-a705-990118577ce8 Jul 26 21:48:18 contest setroubleshoot[139900]: 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 Jul 26 21:48:21 contest setroubleshoot[139900]: SELinux is preventing rhsmcertd-worke from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 22835727-7fef-4cfb-b3b5-881f66888317 Jul 26 21:48:34 contest setroubleshoot[139950]: 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 == csfw00a (1 distinct, 200 total) == Jul 26 21:05:09 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x200] == hackerman (7 distinct, 12 total) == Jul 26 21:19:00 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.C7MCT3”: Permission denied Jul 26 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 26 21:20:12 hackerman gnome-software[2060381]: Only 0 apps for recent list, hiding Jul 26 21:20:28 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.7KTBT3”: Permission denied Jul 26 21:20:29 hackerman packagekitd[947945]: Failed to get cache filename for libreoffice [x2] Jul 26 21:20:29 hackerman packagekitd[947945]: Failed to get cache filename for kernel [x2] Jul 26 21:20:38 hackerman packagekitd[947945]: failed to parse public key for /etc/pki/rpm-gpg/RPM-GPG-KEY-PQC-redhat-release == idm00 (1 distinct, 1 total) == Jul 26 21:51:07 idm00 named[1455]: client @0x7f33103591b8 10.73.240.42#59235: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Jul 26 21:34:56 idmp0 named[5198]: client @0x7f99280434c8 10.73.240.43#55885: update '73.10.in-addr.arpa/IN' denied == inbound00.cs.umd.edu (1 distinct, 1 total) == Jul 26 21:50:52 inbound00.cs.umd.edu krb5_child[4131266]: Client 'admin@UMD.EDU' not found in Kerberos database == itmon02 (1 distinct, 28 total) == Jul 26 21:07:48 itmon02 sshd[1834]: error: beginning MaxStartups throttling [x28] == newhonors2 (1 distinct, 24 total) == Jul 26 21:13:02 newhonors2 dhcpcd[328315]: dhcpcd is not running [x24] == outbound00.cs.umd.edu (1 distinct, 6 total) == Jul 26 21:09:09 outbound00.cs.umd.edu python3[4099337]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Jul 26 21:13:06 outbound01.cs.umd.edu python3[2129494]: ldapdb [x6] == sebatinsky.cs.umd.edu (2 distinct, 4 total) == Jul 26 21:50:23 sebatinsky.cs.umd.edu setroubleshoot[3777768]: failed to retrieve rpm info for /var/lib/rpm/.dbenv.lock [x2] Jul 26 21:50:27 sebatinsky.cs.umd.edu setroubleshoot[3777768]: SELinux is preventing /usr/libexec/platform-python3.6 from add_name access on the directory /var/lib/rpm/.dbenv.lock. For complete SELinux messages run: sealert -l 26d5bc02-bfff-4827-a9f2-b991fef962b5 [x2] == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Jul 26 21:05:20 sentry-docker00.cs.umd.edu systemd-udevd[52303]: Could not generate persistent MAC address for vethbf0b8de: No such file or directory Jul 26 21:05:20 sentry-docker00.cs.umd.edu systemd-udevd[52304]: Could not generate persistent MAC address for vethe28a76a: No such file or directory Jul 26 21:05:20 sentry-docker00.cs.umd.edu systemd-udevd[52307]: Could not generate persistent MAC address for veth4e8cdc4: No such file or directory Jul 26 21:05:20 sentry-docker00.cs.umd.edu systemd-udevd[52318]: Could not generate persistent MAC address for veth8dbc360: No such file or directory Jul 26 21:05:20 sentry-docker00.cs.umd.edu systemd-udevd[52332]: Could not generate persistent MAC address for veth711a704: No such file or directory Jul 26 21:05:20 sentry-docker00.cs.umd.edu systemd-udevd[52336]: Could not generate persistent MAC address for veth9c7aade: No such file or directory Jul 26 21:05:20 sentry-docker00.cs.umd.edu systemd-udevd[52375]: Could not generate persistent MAC address for veth8e91926: No such file or directory Jul 26 21:05:20 sentry-docker00.cs.umd.edu systemd-udevd[52373]: Could not generate persistent MAC address for vethf7915bb: No such file or directory Jul 26 21:15:01 sentry-docker00.cs.umd.edu systemd-udevd[56987]: link_config: could not get ethtool features for vethf50afe2 Jul 26 21:15:01 sentry-docker00.cs.umd.edu systemd-udevd[56987]: Could not set offload features of vethf50afe2: No such device Jul 26 21:15:02 sentry-docker00.cs.umd.edu systemd-udevd[57015]: Could not generate persistent MAC address for veth1ca2d51: No such file or directory Jul 26 21:15:02 sentry-docker00.cs.umd.edu systemd-udevd[57016]: Could not generate persistent MAC address for vethe57f49e: No such file or directory Jul 26 21:25:29 sentry-docker00.cs.umd.edu systemd-udevd[62227]: Could not generate persistent MAC address for veth3d5bc35: No such file or directory Jul 26 21:25:29 sentry-docker00.cs.umd.edu systemd-udevd[62228]: Could not generate persistent MAC address for vethd031b2c: No such file or directory Jul 26 21:25:29 sentry-docker00.cs.umd.edu systemd-udevd[62252]: Could not generate persistent MAC address for veth0eba534: No such file or directory Jul 26 21:25:29 sentry-docker00.cs.umd.edu systemd-udevd[62236]: Could not generate persistent MAC address for vethcba84f2: No such file or directory Jul 26 21:25:29 sentry-docker00.cs.umd.edu systemd-udevd[62255]: Could not generate persistent MAC address for veth7cc320c: No such file or directory Jul 26 21:25:29 sentry-docker00.cs.umd.edu systemd-udevd[62256]: Could not generate persistent MAC address for veth9bf2700: No such file or directory Jul 26 21:25:29 sentry-docker00.cs.umd.edu systemd-udevd[62280]: Could not generate persistent MAC address for veth59e65cf: No such file or directory Jul 26 21:25:29 sentry-docker00.cs.umd.edu systemd-udevd[62275]: Could not generate persistent MAC address for vethc12d6c3: No such file or directory Jul 26 21:35:10 sentry-docker00.cs.umd.edu systemd-udevd[66913]: link_config: could not get ethtool features for veth1ca2d51 Jul 26 21:35:10 sentry-docker00.cs.umd.edu systemd-udevd[66913]: Could not set offload features of veth1ca2d51: No such device Jul 26 21:35:10 sentry-docker00.cs.umd.edu systemd-udevd[66929]: Could not generate persistent MAC address for veth19dd566: No such file or directory Jul 26 21:35:10 sentry-docker00.cs.umd.edu systemd-udevd[66930]: Could not generate persistent MAC address for vethe9a5e8f: No such file or directory Jul 26 21:45:36 sentry-docker00.cs.umd.edu systemd-udevd[71647]: link_config: could not get ethtool features for veth3d5bc35 Jul 26 21:45:36 sentry-docker00.cs.umd.edu systemd-udevd[71647]: Could not set offload features of veth3d5bc35: No such device Jul 26 21:45:37 sentry-docker00.cs.umd.edu systemd-udevd[71708]: Could not generate persistent MAC address for veth5e0bead: No such file or directory Jul 26 21:45:37 sentry-docker00.cs.umd.edu systemd-udevd[71709]: Could not generate persistent MAC address for vethbd09333: No such file or directory Jul 26 21:45:37 sentry-docker00.cs.umd.edu systemd-udevd[71712]: Could not generate persistent MAC address for veth8a99a68: No such file or directory Jul 26 21:45:37 sentry-docker00.cs.umd.edu systemd-udevd[71713]: Could not generate persistent MAC address for veth6a107fa: No such file or directory ... 6 more distinct messages not shown == strawberry (2 distinct, 8 total) == Jul 26 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 26 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 26 21:12:49 submit26-b9-2 setroubleshoot[260285]: 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 26 21:12:49 submit26-b9-2 setroubleshoot[260285]: 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 26 21:12:49 submit26-b9-2 setroubleshoot[260285]: 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 26 21:12:49 submit26-b9-2 setroubleshoot[260285]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.t3HyKT/repodata/repomd.xml. For complete SELinux messages run: sealert -l 1b38f2ec-01ce-4343-8059-ba7494ecc5c4 Jul 26 21:12:49 submit26-b9-2 setroubleshoot[260285]: 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 26 21:12:49 submit26-b9-2 setroubleshoot[260285]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.t3HyKT. For complete SELinux messages run: sealert -l 5c54db87-54a3-4a7c-97b4-b5c48d6c3543 Jul 26 21:12:49 submit26-b9-2 setroubleshoot[260285]: 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 26 21:12:49 submit26-b9-2 setroubleshoot[260285]: 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 26 21:12:49 submit26-b9-2 setroubleshoot[260285]: 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 26 21:20:35 submit26-b9-3 setroubleshoot[617202]: 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 26 21:20:35 submit26-b9-3 setroubleshoot[617202]: 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 26 21:20:35 submit26-b9-3 setroubleshoot[617202]: 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 26 21:20:35 submit26-b9-3 setroubleshoot[617202]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.1DNc9s/repodata/repomd.xml. For complete SELinux messages run: sealert -l 45a8019e-f6b5-4baa-92c1-862594b40d46 Jul 26 21:20:35 submit26-b9-3 setroubleshoot[617202]: 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 26 21:20:35 submit26-b9-3 setroubleshoot[617202]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.1DNc9s. For complete SELinux messages run: sealert -l 0b17cc3d-cdc6-4fe2-a11f-3892e7c41dc7 Jul 26 21:20:35 submit26-b9-3 setroubleshoot[617202]: 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 26 21:20:35 submit26-b9-3 setroubleshoot[617202]: 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 26 21:20:35 submit26-b9-3 setroubleshoot[617202]: 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-clnb9 (9 distinct, 9 total) == Jul 26 21:31:53 submit26-clnb9 setroubleshoot[1361427]: 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 Jul 26 21:31:53 submit26-clnb9 setroubleshoot[1361427]: 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 Jul 26 21:31:53 submit26-clnb9 setroubleshoot[1361427]: 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 26 21:31:53 submit26-clnb9 setroubleshoot[1361427]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.A5sE2b/repodata/repomd.xml. For complete SELinux messages run: sealert -l 001acdb5-31ef-4e52-b10b-90f467a89ddc Jul 26 21:31:53 submit26-clnb9 setroubleshoot[1361427]: 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 26 21:31:53 submit26-clnb9 setroubleshoot[1361427]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.A5sE2b. For complete SELinux messages run: sealert -l 62b3782e-4730-4488-8178-94dafe9b552c Jul 26 21:31:53 submit26-clnb9 setroubleshoot[1361427]: 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 Jul 26 21:31:53 submit26-clnb9 setroubleshoot[1361427]: 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 26 21:31:53 submit26-clnb9 setroubleshoot[1361427]: 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 == zfs00.cs.umd.edu (1 distinct, 1 total) == Jul 26 21:58:29 zfs00.cs.umd.edu rsyslogd: imrelp[2514]: error 'server closed relp session, session broken', object 'lstn 2514: conn to clt 10.73.255.10/frozone.cs.umd.edu' - input may not work as intended [v8.2604.0 try https://www.rsyslog.com/e/2353 ]