Command: /usr/local/sbin/syslog-digest.py Time : 0.5027s Status : exited 0 Output : Syslog digest — 2026-08-04 02:05 EDT Processed 4,157 lines, filtered 3,318 (79%). 839 unknown (104 distinct) from 22 host(s). == abuse (1 distinct, 347 total) == Aug 4 01: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] == b0b02.cs.umd.edu (1 distinct, 1 total) == Aug 4 01:44:22 b0b02.cs.umd.edu rustdesk[2686851]: cannot open display: == contest (10 distinct, 44 total) == Aug 4 01:06:01 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 01:48:17 contest setroubleshoot[591587]: SELinux is preventing /usr/libexec/platform-python3.6 from create access on the directory libdnf.CKbySB. For complete SELinux messages run: sealert -l cb6b25c6-4765-4cf2-88a0-9b3b508e94e9 Aug 4 01:48:18 contest setroubleshoot[591587]: 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 01:48:18 contest setroubleshoot[591587]: 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 01:48:18 contest setroubleshoot[591587]: 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 Aug 4 01:48:18 contest setroubleshoot[591587]: SELinux is preventing /usr/bin/gpgconf from add_name access on the directory repomd.xml.asc. For complete SELinux messages run: sealert -l 41cf7b1b-0f34-4609-98f2-b66e7825fef7 Aug 4 01:48:18 contest setroubleshoot[591587]: SELinux is preventing /usr/libexec/platform-python3.6 from read access on the directory libdnf.CKbySB. For complete SELinux messages run: sealert -l 45d103b6-0810-4890-a705-990118577ce8 Aug 4 01:48:18 contest setroubleshoot[591587]: 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 01:48:18 contest setroubleshoot[591587]: 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 01:48:19 contest setroubleshoot[591587]: SELinux is preventing /usr/libexec/platform-python3.6 from create access on the directory libdnf.I2R0TW. For complete SELinux messages run: sealert -l cb6b25c6-4765-4cf2-88a0-9b3b508e94e9 == csfw00a (1 distinct, 218 total) == Aug 4 01:04:55 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x218] == dojo (1 distinct, 1 total) == Aug 4 01:46:36 dojo sshd[1049409]: error: Protocol major versions differ: 2 vs. 1 == frabjous (2 distinct, 2 total) == Aug 4 01:52:05 frabjous krb5_child[2972448]: Client 'admin@UMD.EDU' not found in Kerberos database Aug 4 01:52:07 frabjous sshd-session[2972444]: error: PAM: Authentication failure for admin from 34.38.14.198 == hackerman (1 distinct, 1 total) == Aug 4 01: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.GTLYT3”: Permission denied == hazfs.cs.umd.edu (11 distinct, 66 total) == Aug 4 01:52:28 hazfs.cs.umd.edu snmpd[1431]: send response: Failure in sendto [x6] Aug 4 01:52:28 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userweb" [x6] Aug 4 01:52:28 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."zfslist" [x6] Aug 4 01:52:28 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userhome" [x6] Aug 4 01:52:28 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userweb" [x6] Aug 4 01:52:28 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."zfslist" [x6] Aug 4 01:52:28 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userhome" [x6] Aug 4 01:52:28 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userweb" [x6] Aug 4 01:52:28 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."zfslist" [x6] Aug 4 01:52:28 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userhome" [x6] Aug 4 01:52:28 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutNumLines."userweb" [x6] == idm00 (2 distinct, 2 total) == Aug 4 01:24:05 idm00 named[1455]: client @0x7f33157df218 10.73.245.12#63922: update '73.10.in-addr.arpa/IN' denied Aug 4 01:51:16 idm00 named[1455]: client @0x7f3310552688 10.73.240.42#58039: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Aug 4 01:36:02 idmp0 named[5198]: client @0x7f9924071208 10.73.240.43#53708: update '73.10.in-addr.arpa/IN' denied == inbound00.cs.umd.edu (1 distinct, 1 total) == Aug 4 01:54:19 inbound00.cs.umd.edu sshd-session[2711745]: fatal: userauth_pubkey: parse publickey packet: incomplete message [preauth] == itmon02 (1 distinct, 39 total) == Aug 4 01:08:13 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x39] == newhonors2 (1 distinct, 24 total) == Aug 4 01:13:03 newhonors2 dhcpcd[704385]: dhcpcd is not running [x24] == outbound00.cs.umd.edu (1 distinct, 6 total) == Aug 4 01:09:09 outbound00.cs.umd.edu python3[2661088]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Aug 4 01:13:06 outbound01.cs.umd.edu python3[695043]: ldapdb [x6] == sentry-docker00.cs.umd.edu (34 distinct, 34 total) == Aug 4 01:05:58 sentry-docker00.cs.umd.edu systemd-udevd[1419439]: Could not generate persistent MAC address for veth0b4ca6f: No such file or directory Aug 4 01:05:58 sentry-docker00.cs.umd.edu systemd-udevd[1419440]: Could not generate persistent MAC address for veth430d9d7: No such file or directory Aug 4 01:05:58 sentry-docker00.cs.umd.edu systemd-udevd[1419443]: Could not generate persistent MAC address for veth3a163ca: No such file or directory Aug 4 01:05:58 sentry-docker00.cs.umd.edu systemd-udevd[1419444]: Could not generate persistent MAC address for vethce3520e: No such file or directory Aug 4 01:05:58 sentry-docker00.cs.umd.edu systemd-udevd[1419466]: Could not generate persistent MAC address for veth6bb3a59: No such file or directory Aug 4 01:05:58 sentry-docker00.cs.umd.edu systemd-udevd[1419465]: Could not generate persistent MAC address for veth73c552f: No such file or directory Aug 4 01:05:58 sentry-docker00.cs.umd.edu systemd-udevd[1419458]: Could not generate persistent MAC address for vethadc0424: No such file or directory Aug 4 01:05:58 sentry-docker00.cs.umd.edu systemd-udevd[1419446]: Could not generate persistent MAC address for veth10c868f: No such file or directory Aug 4 01:05:58 sentry-docker00.cs.umd.edu systemd-udevd[1419466]: Could not generate persistent MAC address for veth39b4306: No such file or directory Aug 4 01:05:58 sentry-docker00.cs.umd.edu systemd-udevd[1419463]: Could not generate persistent MAC address for veth17dfdb2: No such file or directory Aug 4 01:26:06 sentry-docker00.cs.umd.edu systemd-udevd[1428924]: link_config: could not get ethtool features for vethadc0424 Aug 4 01:26:06 sentry-docker00.cs.umd.edu systemd-udevd[1428924]: Could not set offload features of vethadc0424: No such device Aug 4 01:26:07 sentry-docker00.cs.umd.edu systemd-udevd[1429017]: Could not generate persistent MAC address for vethe7dcde6: No such file or directory Aug 4 01:26:07 sentry-docker00.cs.umd.edu systemd-udevd[1429018]: Could not generate persistent MAC address for veth8b222cb: No such file or directory Aug 4 01:26:07 sentry-docker00.cs.umd.edu systemd-udevd[1429021]: Could not generate persistent MAC address for vetha27f423: No such file or directory Aug 4 01:26:07 sentry-docker00.cs.umd.edu systemd-udevd[1429022]: Could not generate persistent MAC address for veth42fe57a: No such file or directory Aug 4 01:26:07 sentry-docker00.cs.umd.edu systemd-udevd[1429018]: Could not generate persistent MAC address for veth95aa580: No such file or directory Aug 4 01:26:07 sentry-docker00.cs.umd.edu systemd-udevd[1429043]: Could not generate persistent MAC address for vethbaae21c: No such file or directory Aug 4 01:26:07 sentry-docker00.cs.umd.edu systemd-udevd[1429047]: Could not generate persistent MAC address for veth644e6be: No such file or directory Aug 4 01:26:07 sentry-docker00.cs.umd.edu systemd-udevd[1429048]: Could not generate persistent MAC address for veth39248a5: No such file or directory Aug 4 01:26:07 sentry-docker00.cs.umd.edu systemd-udevd[1429067]: Could not generate persistent MAC address for veth936803b: No such file or directory Aug 4 01:26:07 sentry-docker00.cs.umd.edu systemd-udevd[1429051]: Could not generate persistent MAC address for veth7aea59a: No such file or directory Aug 4 01:46:15 sentry-docker00.cs.umd.edu systemd-udevd[1438343]: link_config: could not get ethtool features for veth936803b Aug 4 01:46:15 sentry-docker00.cs.umd.edu systemd-udevd[1438343]: Could not set offload features of veth936803b: No such device Aug 4 01:46:15 sentry-docker00.cs.umd.edu systemd-udevd[1438413]: Could not generate persistent MAC address for vethd73cee5: No such file or directory Aug 4 01:46:15 sentry-docker00.cs.umd.edu systemd-udevd[1438414]: Could not generate persistent MAC address for veth76a36db: No such file or directory Aug 4 01:46:15 sentry-docker00.cs.umd.edu systemd-udevd[1438417]: Could not generate persistent MAC address for veth59e3bb9: No such file or directory Aug 4 01:46:15 sentry-docker00.cs.umd.edu systemd-udevd[1438418]: Could not generate persistent MAC address for veth97a185c: No such file or directory Aug 4 01:46:15 sentry-docker00.cs.umd.edu systemd-udevd[1438423]: Could not generate persistent MAC address for vethc24ab1e: No such file or directory Aug 4 01:46:15 sentry-docker00.cs.umd.edu systemd-udevd[1438431]: Could not generate persistent MAC address for veth8d50f67: No such file or directory ... 4 more distinct messages not shown == strawberry (2 distinct, 8 total) == Aug 4 01: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 01:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-2 (11 distinct, 14 total) == Aug 4 01:12:52 submit26-b9-2 setroubleshoot[982824]: 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 01:12:52 submit26-b9-2 setroubleshoot[982824]: 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 01:12:52 submit26-b9-2 setroubleshoot[982824]: 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 01:12:52 submit26-b9-2 setroubleshoot[982824]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.FTd0uv/repodata/repomd.xml. For complete SELinux messages run: sealert -l 1b38f2ec-01ce-4343-8059-ba7494ecc5c4 Aug 4 01:12:52 submit26-b9-2 setroubleshoot[982824]: 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 01:12:52 submit26-b9-2 setroubleshoot[982824]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.FTd0uv. For complete SELinux messages run: sealert -l 5c54db87-54a3-4a7c-97b4-b5c48d6c3543 Aug 4 01:12:52 submit26-b9-2 setroubleshoot[982824]: 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 01:12:52 submit26-b9-2 setroubleshoot[982824]: 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 [x2] Aug 4 01:12:52 submit26-b9-2 setroubleshoot[982824]: 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 Aug 4 01:12:52 submit26-b9-2 setroubleshoot[982824]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.oHXH4y/repodata/repomd.xml. For complete SELinux messages run: sealert -l 1b38f2ec-01ce-4343-8059-ba7494ecc5c4 Aug 4 01:28:37 submit26-b9-2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-3 (10 distinct, 13 total) == Aug 4 01:20:38 submit26-b9-3 setroubleshoot[818360]: 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 Aug 4 01:20:38 submit26-b9-3 setroubleshoot[818360]: 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 Aug 4 01:20:38 submit26-b9-3 setroubleshoot[818360]: 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 [x2] Aug 4 01:20:38 submit26-b9-3 setroubleshoot[818360]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.luOhjQ/repodata/repomd.xml. For complete SELinux messages run: sealert -l 45a8019e-f6b5-4baa-92c1-862594b40d46 Aug 4 01:20:38 submit26-b9-3 setroubleshoot[818360]: 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 [x2] Aug 4 01:20:38 submit26-b9-3 setroubleshoot[818360]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.luOhjQ. For complete SELinux messages run: sealert -l 0b17cc3d-cdc6-4fe2-a11f-3892e7c41dc7 Aug 4 01:20:38 submit26-b9-3 setroubleshoot[818360]: 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 01:20:38 submit26-b9-3 setroubleshoot[818360]: 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 [x2] Aug 4 01:20:38 submit26-b9-3 setroubleshoot[818360]: 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 Aug 4 01:20:38 submit26-b9-3 setroubleshoot[818360]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.fmKBiv/repodata/repomd.xml. For complete SELinux messages run: sealert -l 45a8019e-f6b5-4baa-92c1-862594b40d46 == submit26-b9-4 (1 distinct, 1 total) == Aug 4 01:50:05 submit26-b9-4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-clnb9 (9 distinct, 9 total) == Aug 4 01:31:57 submit26-clnb9 setroubleshoot[1761443]: 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 01:31:57 submit26-clnb9 setroubleshoot[1761443]: 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 01:31:57 submit26-clnb9 setroubleshoot[1761443]: 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 01:31:57 submit26-clnb9 setroubleshoot[1761443]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.ZfpLWU/repodata/repomd.xml. For complete SELinux messages run: sealert -l 001acdb5-31ef-4e52-b10b-90f467a89ddc Aug 4 01:31:57 submit26-clnb9 setroubleshoot[1761443]: 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 01:31:57 submit26-clnb9 setroubleshoot[1761443]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.ZfpLWU. For complete SELinux messages run: sealert -l 62b3782e-4730-4488-8178-94dafe9b552c Aug 4 01:31:57 submit26-clnb9 setroubleshoot[1761443]: 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 01:31:57 submit26-clnb9 setroubleshoot[1761443]: 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 01:31:57 submit26-clnb9 setroubleshoot[1761443]: 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 == zwicker-computer (1 distinct, 1 total) == Aug 4 02:01:47 zwicker-computer pipewire[843669]: mod.jackdbus-detect: Failed to receive jackdbus reply: org.freedesktop.DBus.Error.ServiceUnknown: The name org.jackaudio.service was not provided by any .service files