Command: /usr/local/sbin/syslog-digest.py Time : 0.5111s Status : exited 0 Output : Syslog digest — 2026-07-31 22:05 EDT Processed 4,186 lines, filtered 3,302 (78%). 884 unknown (127 distinct) from 20 host(s). == abuse (1 distinct, 345 total) == Jul 31 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 ] [x345] == atif01.cs.umd.edu (24 distinct, 46 total) == Jul 31 21:05:15 atif01.cs.umd.edu sshd[12796]: error: maximum authentication attempts exceeded for root from 41.63.0.139 port 52805 ssh2 [preauth] Jul 31 21:05:15 atif01.cs.umd.edu sshd[12796]: PAM service(sshd) ignoring max retries; 6 > 3 [x23] Jul 31 21:05:30 atif01.cs.umd.edu sshd[12804]: error: maximum authentication attempts exceeded for root from 41.63.0.139 port 55362 ssh2 [preauth] Jul 31 21:05:45 atif01.cs.umd.edu sshd[12822]: error: maximum authentication attempts exceeded for root from 41.63.0.139 port 57733 ssh2 [preauth] Jul 31 21:06:00 atif01.cs.umd.edu sshd[12830]: error: maximum authentication attempts exceeded for root from 41.63.0.139 port 60103 ssh2 [preauth] Jul 31 21:06:18 atif01.cs.umd.edu sshd[12840]: error: maximum authentication attempts exceeded for root from 41.63.0.139 port 62519 ssh2 [preauth] Jul 31 21:06:34 atif01.cs.umd.edu sshd[12858]: error: maximum authentication attempts exceeded for root from 41.63.0.139 port 65125 ssh2 [preauth] Jul 31 21:06:50 atif01.cs.umd.edu sshd[12866]: error: maximum authentication attempts exceeded for root from 41.63.0.139 port 51303 ssh2 [preauth] Jul 31 21:07:07 atif01.cs.umd.edu sshd[12876]: error: maximum authentication attempts exceeded for root from 41.63.0.139 port 53712 ssh2 [preauth] Jul 31 21:07:24 atif01.cs.umd.edu sshd[12894]: error: maximum authentication attempts exceeded for root from 41.63.0.139 port 56204 ssh2 [preauth] Jul 31 21:07:40 atif01.cs.umd.edu sshd[12910]: error: maximum authentication attempts exceeded for root from 41.63.0.139 port 58783 ssh2 [preauth] Jul 31 21:07:57 atif01.cs.umd.edu sshd[12920]: error: maximum authentication attempts exceeded for root from 41.63.0.139 port 61106 ssh2 [preauth] Jul 31 21:08:13 atif01.cs.umd.edu sshd[12930]: error: maximum authentication attempts exceeded for root from 41.63.0.139 port 63694 ssh2 [preauth] Jul 31 21:08:30 atif01.cs.umd.edu sshd[12938]: error: maximum authentication attempts exceeded for root from 41.63.0.139 port 49618 ssh2 [preauth] Jul 31 21:08:46 atif01.cs.umd.edu sshd[12956]: error: maximum authentication attempts exceeded for root from 41.63.0.139 port 52144 ssh2 [preauth] Jul 31 21:09:02 atif01.cs.umd.edu sshd[12965]: error: maximum authentication attempts exceeded for root from 41.63.0.139 port 54572 ssh2 [preauth] Jul 31 21:09:19 atif01.cs.umd.edu sshd[12975]: error: maximum authentication attempts exceeded for root from 41.63.0.139 port 57090 ssh2 [preauth] Jul 31 21:09:34 atif01.cs.umd.edu sshd[12993]: error: maximum authentication attempts exceeded for root from 41.63.0.139 port 59650 ssh2 [preauth] Jul 31 21:09:51 atif01.cs.umd.edu sshd[13001]: error: maximum authentication attempts exceeded for root from 41.63.0.139 port 62127 ssh2 [preauth] Jul 31 21:10:07 atif01.cs.umd.edu sshd[13011]: error: maximum authentication attempts exceeded for root from 41.63.0.139 port 64710 ssh2 [preauth] Jul 31 21:10:22 atif01.cs.umd.edu sshd[13032]: error: maximum authentication attempts exceeded for root from 41.63.0.139 port 50871 ssh2 [preauth] Jul 31 21:10:38 atif01.cs.umd.edu sshd[13051]: error: maximum authentication attempts exceeded for root from 41.63.0.139 port 53198 ssh2 [preauth] Jul 31 21:10:53 atif01.cs.umd.edu sshd[13061]: error: maximum authentication attempts exceeded for root from 41.63.0.139 port 55666 ssh2 [preauth] Jul 31 21:11:09 atif01.cs.umd.edu sshd[13071]: error: maximum authentication attempts exceeded for root from 41.63.0.139 port 58143 ssh2 [preauth] == b0b02.cs.umd.edu (1 distinct, 1 total) == Jul 31 21:39:45 b0b02.cs.umd.edu rustdesk[1531536]: cannot open display: == contest (8 distinct, 41 total) == Jul 31 21:06:28 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 31 21:48:16 contest setroubleshoot[416120]: SELinux is preventing /usr/libexec/platform-python3.6 from create access on the directory libdnf.z4SZIi. For complete SELinux messages run: sealert -l cb6b25c6-4765-4cf2-88a0-9b3b508e94e9 Jul 31 21:48:16 contest setroubleshoot[416120]: 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 31 21:48:16 contest setroubleshoot[416120]: 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 Jul 31 21:48:16 contest setroubleshoot[416120]: 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 31 21:48:16 contest setroubleshoot[416120]: SELinux is preventing /usr/libexec/platform-python3.6 from read access on the directory libdnf.z4SZIi. For complete SELinux messages run: sealert -l 45d103b6-0810-4890-a705-990118577ce8 Jul 31 21:48:16 contest setroubleshoot[416120]: 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 31 21:48:18 contest setroubleshoot[416120]: 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, 284 total) == Jul 31 21:04:53 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x284] == hackerman (7 distinct, 12 total) == Jul 31 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.A4W3S3”: Permission denied Jul 31 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 31 21:20:12 hackerman gnome-software[2060381]: Only 0 apps for recent list, hiding Jul 31 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.TUJDT3”: Permission denied Jul 31 21:20:28 hackerman packagekitd[2599036]: Failed to get cache filename for libreoffice [x2] Jul 31 21:20:28 hackerman packagekitd[2599036]: Failed to get cache filename for kernel [x2] Jul 31 21:20:37 hackerman packagekitd[2599036]: failed to parse public key for /etc/pki/rpm-gpg/RPM-GPG-KEY-PQC-redhat-release == idm00 (1 distinct, 1 total) == Jul 31 21:51:13 idm00 named[1455]: client @0x7f3315c6a838 10.73.240.42#59499: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Jul 31 21:36:02 idmp0 named[5198]: client @0x7f9920005d68 10.73.240.43#53838: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 21 total) == Jul 31 21:07:59 itmon02 sshd[1834]: error: beginning MaxStartups throttling [x21] == newhonors2 (1 distinct, 24 total) == Jul 31 21:13:03 newhonors2 dhcpcd[559196]: dhcpcd is not running [x24] == outbound00.cs.umd.edu (1 distinct, 6 total) == Jul 31 21:09:09 outbound00.cs.umd.edu python3[1593269]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Jul 31 21:13:06 outbound01.cs.umd.edu python3[3820376]: ldapdb [x6] == sebatinsky.cs.umd.edu (1 distinct, 1 total) == Jul 31 21:53:42 sebatinsky.cs.umd.edu setroubleshoot[699249]: SELinux is preventing /usr/sbin/pdns_server from name_bind access on the udp_socket port 16509. For complete SELinux messages run: sealert -l c40f9216-4e23-4184-838a-6a4f5ec6ccb3 == sentry-docker00.cs.umd.edu (44 distinct, 44 total) == Jul 31 21:14:38 sentry-docker00.cs.umd.edu systemd-udevd[3461315]: link_config: could not get ethtool features for vetheb11e68 Jul 31 21:14:38 sentry-docker00.cs.umd.edu systemd-udevd[3461315]: Could not set offload features of vetheb11e68: No such device Jul 31 21:14:38 sentry-docker00.cs.umd.edu systemd-udevd[3461337]: Could not generate persistent MAC address for veth54418d2: No such file or directory Jul 31 21:14:38 sentry-docker00.cs.umd.edu systemd-udevd[3461338]: Could not generate persistent MAC address for veth5ef05a1: No such file or directory Jul 31 21:14:38 sentry-docker00.cs.umd.edu systemd-udevd[3461341]: Could not generate persistent MAC address for veth5a951d0: No such file or directory Jul 31 21:14:38 sentry-docker00.cs.umd.edu systemd-udevd[3461342]: Could not generate persistent MAC address for veth430739a: No such file or directory Jul 31 21:14:38 sentry-docker00.cs.umd.edu systemd-udevd[3461348]: Could not generate persistent MAC address for veth447890b: No such file or directory Jul 31 21:14:38 sentry-docker00.cs.umd.edu systemd-udevd[3461349]: Could not generate persistent MAC address for veth03505da: No such file or directory Jul 31 21:14:38 sentry-docker00.cs.umd.edu systemd-udevd[3461378]: Could not generate persistent MAC address for veth1f5b902: No such file or directory Jul 31 21:14:38 sentry-docker00.cs.umd.edu systemd-udevd[3461382]: Could not generate persistent MAC address for vethb3868ea: No such file or directory Jul 31 21:18:27 sentry-docker00.cs.umd.edu systemd-udevd[3464122]: link_config: could not get ethtool features for veth99fce85 Jul 31 21:18:27 sentry-docker00.cs.umd.edu systemd-udevd[3464122]: Could not set offload features of veth99fce85: No such device Jul 31 21:18:27 sentry-docker00.cs.umd.edu systemd-udevd[3464141]: Could not generate persistent MAC address for vethaa6d8e0: No such file or directory Jul 31 21:18:27 sentry-docker00.cs.umd.edu systemd-udevd[3464142]: Could not generate persistent MAC address for vethe5dfede: No such file or directory Jul 31 21:34:46 sentry-docker00.cs.umd.edu systemd-udevd[3470942]: link_config: could not get ethtool features for veth5a951d0 Jul 31 21:34:46 sentry-docker00.cs.umd.edu systemd-udevd[3470942]: Could not set offload features of veth5a951d0: No such device Jul 31 21:34:46 sentry-docker00.cs.umd.edu systemd-udevd[3470942]: link_config: could not get ethtool features for veth1f5b902 Jul 31 21:34:46 sentry-docker00.cs.umd.edu systemd-udevd[3470942]: Could not set offload features of veth1f5b902: No such device Jul 31 21:34:46 sentry-docker00.cs.umd.edu systemd-udevd[3471009]: Could not generate persistent MAC address for veth7645250: No such file or directory Jul 31 21:34:46 sentry-docker00.cs.umd.edu systemd-udevd[3471010]: Could not generate persistent MAC address for vethf976b1b: No such file or directory Jul 31 21:34:46 sentry-docker00.cs.umd.edu systemd-udevd[3471013]: Could not generate persistent MAC address for vethc7795ba: No such file or directory Jul 31 21:34:46 sentry-docker00.cs.umd.edu systemd-udevd[3471025]: Could not generate persistent MAC address for veth214aeef: No such file or directory Jul 31 21:34:46 sentry-docker00.cs.umd.edu systemd-udevd[3471016]: Could not generate persistent MAC address for veth525bafd: No such file or directory Jul 31 21:34:46 sentry-docker00.cs.umd.edu systemd-udevd[3471020]: Could not generate persistent MAC address for veth9bfde24: No such file or directory Jul 31 21:34:46 sentry-docker00.cs.umd.edu systemd-udevd[3471047]: Could not generate persistent MAC address for vethda78c6e: No such file or directory Jul 31 21:34:46 sentry-docker00.cs.umd.edu systemd-udevd[3471049]: Could not generate persistent MAC address for vethf407f16: No such file or directory Jul 31 21:38:31 sentry-docker00.cs.umd.edu systemd-udevd[3473757]: link_config: could not get ethtool features for vethaa6d8e0 Jul 31 21:38:31 sentry-docker00.cs.umd.edu systemd-udevd[3473757]: Could not set offload features of vethaa6d8e0: No such device Jul 31 21:38:32 sentry-docker00.cs.umd.edu systemd-udevd[3473773]: Could not generate persistent MAC address for veth0eb9331: No such file or directory Jul 31 21:38:32 sentry-docker00.cs.umd.edu systemd-udevd[3473774]: Could not generate persistent MAC address for veth5bf4104: No such file or directory ... 14 more distinct messages not shown == soul (1 distinct, 1 total) == Jul 31 21:12:09 soul sshd-session[2908118]: error: Protocol major versions differ: 2 vs. 1 == strawberry (2 distinct, 8 total) == Jul 31 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 31 21:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-2 (10 distinct, 11 total) == Jul 31 21:12:51 submit26-b9-2 setroubleshoot[735471]: 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 31 21:12:51 submit26-b9-2 setroubleshoot[735471]: 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 31 21:12:51 submit26-b9-2 setroubleshoot[735471]: 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 31 21:12:51 submit26-b9-2 setroubleshoot[735471]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.t9S88V/repodata/repomd.xml. For complete SELinux messages run: sealert -l 1b38f2ec-01ce-4343-8059-ba7494ecc5c4 Jul 31 21:12:51 submit26-b9-2 setroubleshoot[735471]: 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 31 21:12:51 submit26-b9-2 setroubleshoot[735471]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.t9S88V. For complete SELinux messages run: sealert -l 5c54db87-54a3-4a7c-97b4-b5c48d6c3543 Jul 31 21:12:51 submit26-b9-2 setroubleshoot[735471]: 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 31 21:12:51 submit26-b9-2 setroubleshoot[735471]: 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 31 21:12:51 submit26-b9-2 setroubleshoot[735471]: 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 Jul 31 21:58:06 submit26-b9-2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x2] == submit26-b9-3 (10 distinct, 14 total) == Jul 31 21:20:37 submit26-b9-3 setroubleshoot[740352]: 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] Jul 31 21:20:37 submit26-b9-3 setroubleshoot[740352]: 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] Jul 31 21:20:37 submit26-b9-3 setroubleshoot[740352]: 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 31 21:20:37 submit26-b9-3 setroubleshoot[740352]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.nr7AAS/repodata/repomd.xml. For complete SELinux messages run: sealert -l 45a8019e-f6b5-4baa-92c1-862594b40d46 Jul 31 21:20:37 submit26-b9-3 setroubleshoot[740352]: 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 31 21:20:37 submit26-b9-3 setroubleshoot[740352]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.nr7AAS. For complete SELinux messages run: sealert -l 0b17cc3d-cdc6-4fe2-a11f-3892e7c41dc7 Jul 31 21:20:37 submit26-b9-3 setroubleshoot[740352]: 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 [x2] Jul 31 21:20:37 submit26-b9-3 setroubleshoot[740352]: 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 31 21:20:37 submit26-b9-3 setroubleshoot[740352]: 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 [x2] Jul 31 21:20:37 submit26-b9-3 setroubleshoot[740352]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.OylYQf. For complete SELinux messages run: sealert -l 0b17cc3d-cdc6-4fe2-a11f-3892e7c41dc7 == submit26-b9-4 (1 distinct, 4 total) == Jul 31 21:16:27 submit26-b9-4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x4] == submit26-clnb9 (10 distinct, 13 total) == Jul 31 21:31:55 submit26-clnb9 setroubleshoot[1606230]: 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 31 21:31:55 submit26-clnb9 setroubleshoot[1606230]: 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 31 21:31:55 submit26-clnb9 setroubleshoot[1606230]: 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 [x2] Jul 31 21:31:55 submit26-clnb9 setroubleshoot[1606230]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.cJbXeK/repodata/repomd.xml. For complete SELinux messages run: sealert -l 001acdb5-31ef-4e52-b10b-90f467a89ddc Jul 31 21:31:55 submit26-clnb9 setroubleshoot[1606230]: 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 [x2] Jul 31 21:31:55 submit26-clnb9 setroubleshoot[1606230]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.cJbXeK. For complete SELinux messages run: sealert -l 62b3782e-4730-4488-8178-94dafe9b552c Jul 31 21:31:55 submit26-clnb9 setroubleshoot[1606230]: 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 31 21:31:55 submit26-clnb9 setroubleshoot[1606230]: 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 [x2] Jul 31 21:31:55 submit26-clnb9 setroubleshoot[1606230]: 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 Jul 31 21:31:55 submit26-clnb9 setroubleshoot[1606230]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.OsH8FQ/repodata/repomd.xml. For complete SELinux messages run: sealert -l 001acdb5-31ef-4e52-b10b-90f467a89ddc