Command: /usr/local/sbin/syslog-digest.py Time : 0.5162s Status : exited 0 Output : Syslog digest — 2026-08-03 02:05 EDT Processed 4,352 lines, filtered 3,464 (79%). 888 unknown (108 distinct) from 21 host(s). == abuse (1 distinct, 346 total) == Aug 3 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 ] [x346] == b0b02.cs.umd.edu (1 distinct, 1 total) == Aug 3 01:42:51 b0b02.cs.umd.edu rustdesk[2321972]: cannot open display: == contest (10 distinct, 47 total) == Aug 3 01:05:18 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 3 01:48:17 contest setroubleshoot[536120]: SELinux is preventing /usr/libexec/platform-python3.6 from create access on the directory libdnf.Cx6w9V. For complete SELinux messages run: sealert -l cb6b25c6-4765-4cf2-88a0-9b3b508e94e9 Aug 3 01:48:17 contest setroubleshoot[536120]: 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] Aug 3 01:48:17 contest setroubleshoot[536120]: 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 3 01:48:17 contest setroubleshoot[536120]: 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 3 01:48:17 contest setroubleshoot[536120]: SELinux is preventing /usr/libexec/platform-python3.6 from read access on the directory libdnf.Cx6w9V. For complete SELinux messages run: sealert -l 45d103b6-0810-4890-a705-990118577ce8 Aug 3 01:48:17 contest setroubleshoot[536120]: 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 [x3] Aug 3 01:48:18 contest setroubleshoot[536120]: 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 [x2] Aug 3 01:48:18 contest setroubleshoot[536120]: SELinux is preventing /usr/libexec/platform-python3.6 from create access on the directory libdnf.zQjTat. For complete SELinux messages run: sealert -l cb6b25c6-4765-4cf2-88a0-9b3b508e94e9 Aug 3 01:48:25 contest setroubleshoot[536120]: SELinux is preventing /usr/libexec/platform-python3.6 from read access on the directory libdnf.zQjTat. For complete SELinux messages run: sealert -l 45d103b6-0810-4890-a705-990118577ce8 == csfw00a (2 distinct, 258 total) == Aug 3 01:05:06 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x246] Aug 3 01:33:49 csfw00a ospf6d[1477]: [EC 100663307] Could not send entire message [x12] == hackerman (1 distinct, 1 total) == Aug 3 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.SQCYT3”: Permission denied == hazfs.cs.umd.edu (11 distinct, 66 total) == Aug 3 01:50:54 hazfs.cs.umd.edu snmpd[1431]: send response: Failure in sendto [x6] Aug 3 01:50:54 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userweb" [x6] Aug 3 01:50:54 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."zfslist" [x6] Aug 3 01:50:54 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userhome" [x6] Aug 3 01:50:54 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userweb" [x6] Aug 3 01:50:54 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."zfslist" [x6] Aug 3 01:50:54 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userhome" [x6] Aug 3 01:50:54 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userweb" [x6] Aug 3 01:50:54 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."zfslist" [x6] Aug 3 01:50:54 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userhome" [x6] Aug 3 01:50:54 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutNumLines."userweb" [x6] == idm00 (2 distinct, 2 total) == Aug 3 01:24:05 idm00 named[1455]: client @0x7f3304247948 10.73.245.12#53809: update '73.10.in-addr.arpa/IN' denied Aug 3 01:51:15 idm00 named[1455]: client @0x7f3310a9be68 10.73.240.42#64781: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Aug 3 01:36:01 idmp0 named[5198]: client @0x7f98fc0059e8 10.73.240.43#64507: update '73.10.in-addr.arpa/IN' denied == inbound00.cs.umd.edu (1 distinct, 1 total) == Aug 3 01:52:48 inbound00.cs.umd.edu krb5_child[2370506]: Client 'admin@UMD.EDU' not found in Kerberos database == itmon02 (1 distinct, 35 total) == Aug 3 01:07:50 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x35] == mcstic (2 distinct, 5 total) == Aug 3 01:13:34 mcstic krb5_child[2038451]: Client 'admin@UMD.EDU' not found in Kerberos database [x4] Aug 3 01:13:40 mcstic sshd[2038446]: error: PAM: Authentication failure for admin from 34.78.35.91 == newhonors2 (1 distinct, 24 total) == Aug 3 01:13:03 newhonors2 dhcpcd[658656]: dhcpcd is not running [x24] == outbound00.cs.umd.edu (3 distinct, 8 total) == Aug 3 01:09:09 outbound00.cs.umd.edu python3[2324162]: ldapdb [x6] Aug 3 01:46:42 outbound00.cs.umd.edu krb5_child[2332693]: Preauthentication failed Aug 3 01:55:20 outbound00.cs.umd.edu krb5_child[2335142]: Client 'admin@UMD.EDU' not found in Kerberos database == outbound01.cs.umd.edu (1 distinct, 6 total) == Aug 3 01:13:06 outbound01.cs.umd.edu python3[356863]: ldapdb [x6] == sebatinsky.cs.umd.edu (1 distinct, 2 total) == Aug 3 01:50:32 sebatinsky.cs.umd.edu setroubleshoot[1173928]: SELinux is preventing /usr/libexec/platform-python3.6 from add_name access on the directory .dbenv.lock. For complete SELinux messages run: sealert -l 26d5bc02-bfff-4827-a9f2-b991fef962b5 [x2] == sentry-docker00.cs.umd.edu (38 distinct, 38 total) == Aug 3 01:16:07 sentry-docker00.cs.umd.edu systemd-udevd[743841]: link_config: could not get ethtool features for veth80c2fa7 Aug 3 01:16:07 sentry-docker00.cs.umd.edu systemd-udevd[743841]: Could not set offload features of veth80c2fa7: No such device Aug 3 01:16:08 sentry-docker00.cs.umd.edu systemd-udevd[743862]: Could not generate persistent MAC address for veth69e8293: No such file or directory Aug 3 01:16:08 sentry-docker00.cs.umd.edu systemd-udevd[743863]: Could not generate persistent MAC address for vethbfae673: No such file or directory Aug 3 01:16:08 sentry-docker00.cs.umd.edu systemd-udevd[743881]: Could not generate persistent MAC address for veth55e32df: No such file or directory Aug 3 01:16:08 sentry-docker00.cs.umd.edu systemd-udevd[743875]: Could not generate persistent MAC address for vethf9c3d14: No such file or directory Aug 3 01:16:08 sentry-docker00.cs.umd.edu systemd-udevd[743890]: Could not generate persistent MAC address for veth026f297: No such file or directory Aug 3 01:16:08 sentry-docker00.cs.umd.edu systemd-udevd[743891]: Could not generate persistent MAC address for veth527ab39: No such file or directory Aug 3 01:16:08 sentry-docker00.cs.umd.edu systemd-udevd[743927]: Could not generate persistent MAC address for veth00a6ba0: No such file or directory Aug 3 01:16:08 sentry-docker00.cs.umd.edu systemd-udevd[743905]: Could not generate persistent MAC address for veth50c9fff: No such file or directory Aug 3 01:17:37 sentry-docker00.cs.umd.edu systemd-udevd[744693]: link_config: could not get ethtool features for veth210cd0a Aug 3 01:17:37 sentry-docker00.cs.umd.edu systemd-udevd[744693]: Could not set offload features of veth210cd0a: No such device Aug 3 01:17:37 sentry-docker00.cs.umd.edu systemd-udevd[744710]: Could not generate persistent MAC address for vethb650166: No such file or directory Aug 3 01:17:37 sentry-docker00.cs.umd.edu systemd-udevd[744711]: Could not generate persistent MAC address for veth14a0f70: No such file or directory Aug 3 01:36:16 sentry-docker00.cs.umd.edu systemd-udevd[753548]: link_config: could not set ethtool features for veth69e8293 Aug 3 01:36:16 sentry-docker00.cs.umd.edu systemd-udevd[753548]: Could not set offload features of veth69e8293: Operation not permitted Aug 3 01:36:16 sentry-docker00.cs.umd.edu systemd-udevd[753578]: Could not generate persistent MAC address for veth7430586: No such file or directory Aug 3 01:36:16 sentry-docker00.cs.umd.edu systemd-udevd[753579]: Could not generate persistent MAC address for veth7a9c48c: No such file or directory Aug 3 01:36:16 sentry-docker00.cs.umd.edu systemd-udevd[753582]: Could not generate persistent MAC address for veth0f3f89b: No such file or directory Aug 3 01:36:16 sentry-docker00.cs.umd.edu systemd-udevd[753583]: Could not generate persistent MAC address for veth2de3d8c: No such file or directory Aug 3 01:36:16 sentry-docker00.cs.umd.edu systemd-udevd[753606]: Could not generate persistent MAC address for vetha63f6bd: No such file or directory Aug 3 01:36:16 sentry-docker00.cs.umd.edu systemd-udevd[753607]: Could not generate persistent MAC address for vetha2b3493: No such file or directory Aug 3 01:36:16 sentry-docker00.cs.umd.edu systemd-udevd[753625]: Could not generate persistent MAC address for veth42817cb: No such file or directory Aug 3 01:36:16 sentry-docker00.cs.umd.edu systemd-udevd[753627]: Could not generate persistent MAC address for vethdb24c6e: No such file or directory Aug 3 01:37:42 sentry-docker00.cs.umd.edu systemd-udevd[754380]: Could not generate persistent MAC address for veth31b248b: No such file or directory Aug 3 01:37:42 sentry-docker00.cs.umd.edu systemd-udevd[754381]: Could not generate persistent MAC address for vethbd3fd33: No such file or directory Aug 3 01:56:24 sentry-docker00.cs.umd.edu systemd-udevd[762975]: link_config: could not get ethtool features for veth7430586 Aug 3 01:56:24 sentry-docker00.cs.umd.edu systemd-udevd[762975]: Could not set offload features of veth7430586: No such device Aug 3 01:56:24 sentry-docker00.cs.umd.edu systemd-udevd[763007]: Could not generate persistent MAC address for vethc5a4247: No such file or directory Aug 3 01:56:24 sentry-docker00.cs.umd.edu systemd-udevd[763008]: Could not generate persistent MAC address for veth019f2a4: No such file or directory ... 8 more distinct messages not shown == strawberry (2 distinct, 8 total) == Aug 3 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 3 01:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-2 (10 distinct, 14 total) == Aug 3 01:12:52 submit26-b9-2 setroubleshoot[911587]: 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 3 01:12:52 submit26-b9-2 setroubleshoot[911587]: 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 3 01:12:52 submit26-b9-2 setroubleshoot[911587]: 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 Aug 3 01:12:52 submit26-b9-2 setroubleshoot[911587]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.vu2BXu/repodata/repomd.xml. For complete SELinux messages run: sealert -l 1b38f2ec-01ce-4343-8059-ba7494ecc5c4 Aug 3 01:12:52 submit26-b9-2 setroubleshoot[911587]: 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 Aug 3 01:12:52 submit26-b9-2 setroubleshoot[911587]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.vu2BXu. For complete SELinux messages run: sealert -l 5c54db87-54a3-4a7c-97b4-b5c48d6c3543 Aug 3 01:12:52 submit26-b9-2 setroubleshoot[911587]: 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 3 01:12:52 submit26-b9-2 setroubleshoot[911587]: 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 3 01:12:52 submit26-b9-2 setroubleshoot[911587]: 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 3 01:18:07 submit26-b9-2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x5] == submit26-b9-3 (9 distinct, 9 total) == Aug 3 01:20:38 submit26-b9-3 setroubleshoot[793724]: 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 3 01:20:38 submit26-b9-3 setroubleshoot[793724]: 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 3 01:20:38 submit26-b9-3 setroubleshoot[793724]: 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 3 01:20:38 submit26-b9-3 setroubleshoot[793724]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.3UbMf8/repodata/repomd.xml. For complete SELinux messages run: sealert -l 45a8019e-f6b5-4baa-92c1-862594b40d46 Aug 3 01:20:38 submit26-b9-3 setroubleshoot[793724]: 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 3 01:20:38 submit26-b9-3 setroubleshoot[793724]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.3UbMf8. For complete SELinux messages run: sealert -l 0b17cc3d-cdc6-4fe2-a11f-3892e7c41dc7 Aug 3 01:20:38 submit26-b9-3 setroubleshoot[793724]: 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 3 01:20:38 submit26-b9-3 setroubleshoot[793724]: 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 3 01:20:38 submit26-b9-3 setroubleshoot[793724]: 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, 7 total) == Aug 3 01:10:05 submit26-b9-4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x7] == submit26-clnb9 (9 distinct, 9 total) == Aug 3 01:31:56 submit26-clnb9 setroubleshoot[1712440]: 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 3 01:31:56 submit26-clnb9 setroubleshoot[1712440]: 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 3 01:31:56 submit26-clnb9 setroubleshoot[1712440]: 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 3 01:31:56 submit26-clnb9 setroubleshoot[1712440]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.QTQsKl/repodata/repomd.xml. For complete SELinux messages run: sealert -l 001acdb5-31ef-4e52-b10b-90f467a89ddc Aug 3 01:31:56 submit26-clnb9 setroubleshoot[1712440]: 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 3 01:31:56 submit26-clnb9 setroubleshoot[1712440]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.QTQsKl. For complete SELinux messages run: sealert -l 62b3782e-4730-4488-8178-94dafe9b552c Aug 3 01:31:56 submit26-clnb9 setroubleshoot[1712440]: 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 3 01:31:57 submit26-clnb9 setroubleshoot[1712440]: 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 3 01:31:57 submit26-clnb9 setroubleshoot[1712440]: 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