Command: /usr/local/sbin/syslog-digest.py Time : 0.5054s Status : exited 0 Output : Syslog digest — 2026-08-04 22:05 EDT Processed 4,224 lines, filtered 3,371 (79%). 853 unknown (100 distinct) from 21 host(s). == abadi-computer (3 distinct, 3 total) == Aug 4 21:12:39 abadi-computer falcon-sensor-bpf[529]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225 Aug 4 21:12:39 abadi-computer falcon-sensor-bpf[529]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225 Aug 4 21:23:17 abadi-computer kernel: kauditd_printk_skb: 1 callbacks suppressed == abuse (1 distinct, 346 total) == Aug 4 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] == b0b02.cs.umd.edu (1 distinct, 1 total) == Aug 4 21:45:34 b0b02.cs.umd.edu rustdesk[2990843]: cannot open display: == contest (10 distinct, 45 total) == Aug 4 21:05:42 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') [x34] Aug 4 21:48:17 contest setroubleshoot[637665]: SELinux is preventing /usr/libexec/platform-python3.6 from create access on the directory libdnf.NKHysb. For complete SELinux messages run: sealert -l cb6b25c6-4765-4cf2-88a0-9b3b508e94e9 Aug 4 21:48:18 contest setroubleshoot[637665]: 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 Aug 4 21:48:18 contest setroubleshoot[637665]: 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 Aug 4 21:48:18 contest setroubleshoot[637665]: 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 [x2] Aug 4 21:48:18 contest setroubleshoot[637665]: SELinux is preventing /usr/libexec/platform-python3.6 from read access on the directory libdnf.NKHysb. For complete SELinux messages run: sealert -l 45d103b6-0810-4890-a705-990118577ce8 Aug 4 21:48:18 contest setroubleshoot[637665]: 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] Aug 4 21:48:18 contest setroubleshoot[637665]: 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 Aug 4 21:48:20 contest setroubleshoot[637665]: SELinux is preventing /usr/libexec/platform-python3.6 from create access on the file repomd.xml. For complete SELinux messages run: sealert -l fc20ff92-ea83-4f38-a24b-ddfd737a3141 Aug 4 21:48:33 contest setroubleshoot[637725]: 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 == csfw00a (2 distinct, 274 total) == Aug 4 21:04:56 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x262] Aug 4 21:30:19 csfw00a ospf6d[1477]: [EC 100663307] Could not send entire message [x12] == hackerman (7 distinct, 12 total) == Aug 4 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.0BM0T3”: Permission denied Aug 4 21:20:04 hackerman gnome-software[2060381]: can't reliably fixup error code 4 in domain g-io-error-quark: Not a directory [x4] Aug 4 21:20:12 hackerman gnome-software[2060381]: Only 0 apps for recent list, hiding Aug 4 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.67FXT3”: Permission denied Aug 4 21:20:28 hackerman packagekitd[3919367]: Failed to get cache filename for libreoffice [x2] Aug 4 21:20:28 hackerman packagekitd[3919367]: Failed to get cache filename for kernel [x2] Aug 4 21:20:37 hackerman packagekitd[3919367]: failed to parse public key for /etc/pki/rpm-gpg/RPM-GPG-KEY-PQC-redhat-release == idm00 (1 distinct, 1 total) == Aug 4 21:51:17 idm00 named[1455]: client @0x7f330c44bf28 10.73.240.42#60281: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Aug 4 21:36:01 idmp0 named[5198]: client @0x7f9924011de8 10.73.240.43#52929: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 38 total) == Aug 4 21:08:07 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x38] == mcstic (1 distinct, 2 total) == Aug 4 21:25:54 mcstic krb5_child[2125072]: Client 'admin@UMD.EDU' not found in Kerberos database [x2] == munin (2 distinct, 4 total) == Aug 4 21:52:49 munin sudo[1839815]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x2] Aug 4 21:52:49 munin sudo[1839815]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x2] == newhonors2 (1 distinct, 24 total) == Aug 4 21:13:03 newhonors2 dhcpcd[742502]: dhcpcd is not running [x24] == outbound00.cs.umd.edu (1 distinct, 6 total) == Aug 4 21:09:09 outbound00.cs.umd.edu python3[2942162]: ldapdb [x6] == outbound01.cs.umd.edu (2 distinct, 7 total) == Aug 4 21:13:06 outbound01.cs.umd.edu python3[976082]: ldapdb [x6] Aug 4 21:46:02 outbound01.cs.umd.edu krb5_child[983963]: Client 'admin@UMD.EDU' not found in Kerberos database == sebatinsky.cs.umd.edu (1 distinct, 1 total) == Aug 4 22:03:05 sebatinsky.cs.umd.edu setroubleshoot[1577330]: SELinux is preventing /usr/sbin/pdns_server from name_bind access on the udp_socket port 10082. For complete SELinux messages run: sealert -l af222830-ab0f-4bc8-91ab-730551076ae5 == sentry-docker00.cs.umd.edu (34 distinct, 34 total) == Aug 4 21:14:17 sentry-docker00.cs.umd.edu systemd-udevd[1989163]: link_config: could not get ethtool features for vethad61965 Aug 4 21:14:17 sentry-docker00.cs.umd.edu systemd-udevd[1989163]: Could not set offload features of vethad61965: No such device Aug 4 21:14:17 sentry-docker00.cs.umd.edu systemd-udevd[1989179]: Could not generate persistent MAC address for vethb6ab69b: No such file or directory Aug 4 21:14:17 sentry-docker00.cs.umd.edu systemd-udevd[1989180]: Could not generate persistent MAC address for vethf601b17: No such file or directory Aug 4 21:14:17 sentry-docker00.cs.umd.edu systemd-udevd[1989207]: Could not generate persistent MAC address for veth80a73e2: No such file or directory Aug 4 21:14:17 sentry-docker00.cs.umd.edu systemd-udevd[1989208]: Could not generate persistent MAC address for vethe2736de: No such file or directory Aug 4 21:14:17 sentry-docker00.cs.umd.edu systemd-udevd[1989226]: Could not generate persistent MAC address for vetha0ac0a9: No such file or directory Aug 4 21:14:17 sentry-docker00.cs.umd.edu systemd-udevd[1989218]: Could not generate persistent MAC address for vetha5f9170: No such file or directory Aug 4 21:14:18 sentry-docker00.cs.umd.edu systemd-udevd[1989218]: Could not generate persistent MAC address for vethfbb5445: No such file or directory Aug 4 21:14:18 sentry-docker00.cs.umd.edu systemd-udevd[1989212]: Could not generate persistent MAC address for vethac59ad5: No such file or directory Aug 4 21:14:18 sentry-docker00.cs.umd.edu systemd-udevd[1989218]: Could not generate persistent MAC address for veth15280d9: No such file or directory Aug 4 21:14:18 sentry-docker00.cs.umd.edu systemd-udevd[1989216]: Could not generate persistent MAC address for vethbde5982: No such file or directory Aug 4 21:34:26 sentry-docker00.cs.umd.edu systemd-udevd[1998790]: Could not generate persistent MAC address for veth8f65daf: No such file or directory Aug 4 21:34:26 sentry-docker00.cs.umd.edu systemd-udevd[1998789]: Could not generate persistent MAC address for vethd1f491d: No such file or directory Aug 4 21:34:26 sentry-docker00.cs.umd.edu systemd-udevd[1998793]: Could not generate persistent MAC address for veth83cd022: No such file or directory Aug 4 21:34:26 sentry-docker00.cs.umd.edu systemd-udevd[1998794]: Could not generate persistent MAC address for vetha924c82: No such file or directory Aug 4 21:34:26 sentry-docker00.cs.umd.edu systemd-udevd[1998817]: Could not generate persistent MAC address for veth885db96: No such file or directory Aug 4 21:34:26 sentry-docker00.cs.umd.edu systemd-udevd[1998818]: Could not generate persistent MAC address for veth4d06649: No such file or directory Aug 4 21:34:26 sentry-docker00.cs.umd.edu systemd-udevd[1998837]: Could not generate persistent MAC address for veth924308e: No such file or directory Aug 4 21:34:26 sentry-docker00.cs.umd.edu systemd-udevd[1998824]: Could not generate persistent MAC address for veth4caaa28: No such file or directory Aug 4 21:34:26 sentry-docker00.cs.umd.edu systemd-udevd[1998824]: Could not generate persistent MAC address for veth44f3849: No such file or directory Aug 4 21:34:26 sentry-docker00.cs.umd.edu systemd-udevd[1998832]: Could not generate persistent MAC address for veth9b28083: No such file or directory Aug 4 21:54:34 sentry-docker00.cs.umd.edu systemd-udevd[2008079]: link_config: could not get ethtool features for veth885db96 Aug 4 21:54:34 sentry-docker00.cs.umd.edu systemd-udevd[2008079]: Could not set offload features of veth885db96: No such device Aug 4 21:54:34 sentry-docker00.cs.umd.edu systemd-udevd[2008167]: Could not generate persistent MAC address for vethcdb73ee: No such file or directory Aug 4 21:54:34 sentry-docker00.cs.umd.edu systemd-udevd[2008168]: Could not generate persistent MAC address for veth5cee715: No such file or directory Aug 4 21:54:34 sentry-docker00.cs.umd.edu systemd-udevd[2008171]: Could not generate persistent MAC address for veth977e5ba: No such file or directory Aug 4 21:54:34 sentry-docker00.cs.umd.edu systemd-udevd[2008172]: Could not generate persistent MAC address for veth8ad8ccf: No such file or directory Aug 4 21:54:34 sentry-docker00.cs.umd.edu systemd-udevd[2008195]: Could not generate persistent MAC address for vetha4ae83a: No such file or directory Aug 4 21:54:34 sentry-docker00.cs.umd.edu systemd-udevd[2008196]: Could not generate persistent MAC address for veth28c97ef: No such file or directory ... 4 more distinct messages not shown == strawberry (2 distinct, 8 total) == Aug 4 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] Aug 4 21:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-2 (10 distinct, 18 total) == Aug 4 21:06:52 submit26-b9-2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x6] Aug 4 21:12:52 submit26-b9-2 setroubleshoot[1050252]: 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 Aug 4 21:12:52 submit26-b9-2 setroubleshoot[1050252]: 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 Aug 4 21:12:52 submit26-b9-2 setroubleshoot[1050252]: 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 [x2] Aug 4 21:12:52 submit26-b9-2 setroubleshoot[1050252]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.ZwBQ0n/repodata/repomd.xml. For complete SELinux messages run: sealert -l 1b38f2ec-01ce-4343-8059-ba7494ecc5c4 [x2] Aug 4 21:12:52 submit26-b9-2 setroubleshoot[1050252]: 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 [x2] Aug 4 21:12:53 submit26-b9-2 setroubleshoot[1050252]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.ZwBQ0n. For complete SELinux messages run: sealert -l 5c54db87-54a3-4a7c-97b4-b5c48d6c3543 Aug 4 21:12:53 submit26-b9-2 setroubleshoot[1050252]: 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 Aug 4 21:12:53 submit26-b9-2 setroubleshoot[1050252]: 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 Aug 4 21:12:53 submit26-b9-2 setroubleshoot[1050252]: 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, 11 total) == Aug 4 21:20:39 submit26-b9-3 setroubleshoot[838880]: 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 [x2] Aug 4 21:20:39 submit26-b9-3 setroubleshoot[838880]: 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 [x2] Aug 4 21:20:39 submit26-b9-3 setroubleshoot[838880]: 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 Aug 4 21:20:39 submit26-b9-3 setroubleshoot[838880]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.2WRO5y/repodata/repomd.xml. For complete SELinux messages run: sealert -l 45a8019e-f6b5-4baa-92c1-862594b40d46 Aug 4 21:20:39 submit26-b9-3 setroubleshoot[838880]: 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 Aug 4 21:20:39 submit26-b9-3 setroubleshoot[838880]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.2WRO5y. For complete SELinux messages run: sealert -l 0b17cc3d-cdc6-4fe2-a11f-3892e7c41dc7 Aug 4 21:20:39 submit26-b9-3 setroubleshoot[838880]: 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 Aug 4 21:20:39 submit26-b9-3 setroubleshoot[838880]: 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 Aug 4 21:20:39 submit26-b9-3 setroubleshoot[838880]: 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, 8 total) == Aug 4 21:05:05 submit26-b9-4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x8] == submit26-clnb9 (9 distinct, 9 total) == Aug 4 21:31:57 submit26-clnb9 setroubleshoot[1802284]: 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 Aug 4 21:31:57 submit26-clnb9 setroubleshoot[1802284]: 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 Aug 4 21:31:57 submit26-clnb9 setroubleshoot[1802284]: 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 Aug 4 21:31:57 submit26-clnb9 setroubleshoot[1802284]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.5WmUbf/repodata/repomd.xml. For complete SELinux messages run: sealert -l 001acdb5-31ef-4e52-b10b-90f467a89ddc Aug 4 21:31:57 submit26-clnb9 setroubleshoot[1802284]: 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 Aug 4 21:31:57 submit26-clnb9 setroubleshoot[1802284]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.5WmUbf. For complete SELinux messages run: sealert -l 62b3782e-4730-4488-8178-94dafe9b552c Aug 4 21:31:57 submit26-clnb9 setroubleshoot[1802284]: 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 Aug 4 21:31:57 submit26-clnb9 setroubleshoot[1802284]: 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 Aug 4 21:31:58 submit26-clnb9 setroubleshoot[1802284]: 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