Command: /usr/local/sbin/syslog-digest.py Time : 0.5691s Status : exited 0 Output : Syslog digest — 2026-07-25 02:05 EDT Processed 6,758 lines, filtered 5,866 (86%). 892 unknown (110 distinct) from 23 host(s). == abuse (1 distinct, 347 total) == Jul 25 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] == alec.cs.umd.edu (3 distinct, 60 total) == Jul 25 01:05:21 alec.cs.umd.edu setroubleshoot[2758763]: failed to retrieve rpm info for path '/run/netns/netns-9dfd0347-71eb-5698-085c-c769043aa5c3': [x12] Jul 25 01:05:22 alec.cs.umd.edu sedispatch[1526]: AVC Message regarding setroubleshoot, ignoring message [x24] Jul 25 01:05:22 alec.cs.umd.edu setroubleshoot[2758763]: 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 25 01:54:21 b0b02.cs.umd.edu rustdesk[250407]: cannot open display: == bac102 (2 distinct, 2 total) == Jul 25 01:43:33 bac102 systemd-resolved[895]: Using degraded feature set UDP instead of UDP+EDNS0 for DNS server 10.73.244.10. Jul 25 01:43:43 bac102 systemd-resolved[895]: Using degraded feature set UDP instead of UDP+EDNS0 for DNS server 10.211.55.1. == bachata (1 distinct, 2 total) == Jul 25 01:20:08 bachata setroubleshoot[1867514]: SELinux is preventing /usr/sbin/smbd from name_bind access on the udp_socket port 712. For complete SELinux messages run: sealert -l 8f7247f1-69a5-4a62-a4f0-88a324bfd75c [x2] == contest (9 distinct, 41 total) == Jul 25 01:06:11 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 25 01:48:12 contest setroubleshoot[38785]: SELinux is preventing /usr/libexec/platform-python3.6 from create access on the directory libdnf.3nne1q. For complete SELinux messages run: sealert -l cb6b25c6-4765-4cf2-88a0-9b3b508e94e9 Jul 25 01:48:12 contest setroubleshoot[38785]: 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 25 01:48:12 contest setroubleshoot[38785]: 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 25 01:48:12 contest setroubleshoot[38785]: 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 25 01:48:13 contest setroubleshoot[38785]: SELinux is preventing /usr/libexec/platform-python3.6 from read access on the directory libdnf.3nne1q. For complete SELinux messages run: sealert -l 45d103b6-0810-4890-a705-990118577ce8 Jul 25 01:48:17 contest setroubleshoot[38785]: 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 25 01:48:20 contest setroubleshoot[38785]: 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 25 01:48:33 contest setroubleshoot[38835]: 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, 206 total) == Jul 25 01:05:17 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x206] == dojo (1 distinct, 1 total) == Jul 25 01:13:54 dojo sshd[221787]: error: Protocol major versions differ: 2 vs. 1 == emaar (1 distinct, 1 total) == Jul 25 01:25:10 emaar systemd[1]: cgroup compatibility translation between legacy and unified hierarchy settings activated. See cgroup-compat debug messages for details. == hackerman (1 distinct, 1 total) == Jul 25 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.AQF5S3”: Permission denied == hazfs.cs.umd.edu (11 distinct, 66 total) == Jul 25 01:55:28 hazfs.cs.umd.edu snmpd[1431]: send response: Failure in sendto [x6] Jul 25 01:55:28 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userweb" [x6] Jul 25 01:55:28 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."zfslist" [x6] Jul 25 01:55:28 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userhome" [x6] Jul 25 01:55:28 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userweb" [x6] Jul 25 01:55:28 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."zfslist" [x6] Jul 25 01:55:28 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userhome" [x6] Jul 25 01:55:28 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userweb" [x6] Jul 25 01:55:28 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."zfslist" [x6] Jul 25 01:55:28 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userhome" [x6] Jul 25 01:55:28 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutNumLines."userweb" [x6] == idm00 (1 distinct, 1 total) == Jul 25 01:51:05 idm00 named[1455]: client @0x7f3314ae55e8 10.73.240.42#59359: update '73.10.in-addr.arpa/IN' denied == idmp0 (2 distinct, 2 total) == Jul 25 01:23:59 idmp0 named[5198]: client @0x7f98fc033ea8 10.73.245.12#50777: update '73.10.in-addr.arpa/IN' denied Jul 25 01:34:56 idmp0 named[5198]: client @0x7f992c0104c8 10.73.240.43#55023: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 38 total) == Jul 25 01:08:04 itmon02 sshd[1834]: error: beginning MaxStartups throttling [x38] == newhonors2 (1 distinct, 24 total) == Jul 25 01:13:03 newhonors2 dhcpcd[243482]: dhcpcd is not running [x24] == outbound00.cs.umd.edu (1 distinct, 6 total) == Jul 25 01:09:09 outbound00.cs.umd.edu python3[3483766]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Jul 25 01:13:06 outbound01.cs.umd.edu python3[1512571]: ldapdb [x6] == sentry-docker00.cs.umd.edu (40 distinct, 40 total) == Jul 25 01:07:10 sentry-docker00.cs.umd.edu systemd-udevd[2999136]: link_config: could not get ethtool features for veth80b9956 Jul 25 01:07:10 sentry-docker00.cs.umd.edu systemd-udevd[2999136]: Could not set offload features of veth80b9956: No such device Jul 25 01:07:10 sentry-docker00.cs.umd.edu systemd-udevd[2999140]: link_config: could not get ethtool features for vethd5ca691 Jul 25 01:07:10 sentry-docker00.cs.umd.edu systemd-udevd[2999140]: Could not set offload features of vethd5ca691: No such device Jul 25 01:07:10 sentry-docker00.cs.umd.edu systemd-udevd[2999164]: Could not generate persistent MAC address for veth2ee849a: No such file or directory Jul 25 01:07:10 sentry-docker00.cs.umd.edu systemd-udevd[2999165]: Could not generate persistent MAC address for veth57b95b4: No such file or directory Jul 25 01:07:10 sentry-docker00.cs.umd.edu systemd-udevd[2999168]: Could not generate persistent MAC address for veth7d2a970: No such file or directory Jul 25 01:07:10 sentry-docker00.cs.umd.edu systemd-udevd[2999185]: Could not generate persistent MAC address for vetha9ed6e0: No such file or directory Jul 25 01:07:10 sentry-docker00.cs.umd.edu systemd-udevd[2999165]: Could not generate persistent MAC address for veth49996da: No such file or directory Jul 25 01:07:10 sentry-docker00.cs.umd.edu systemd-udevd[2999181]: Could not generate persistent MAC address for vethb81665b: No such file or directory Jul 25 01:07:10 sentry-docker00.cs.umd.edu systemd-udevd[2999177]: Could not generate persistent MAC address for vethfeb94aa: No such file or directory Jul 25 01:07:10 sentry-docker00.cs.umd.edu systemd-udevd[2999165]: Could not generate persistent MAC address for veth943d8a7: No such file or directory Jul 25 01:20:00 sentry-docker00.cs.umd.edu systemd-udevd[3005732]: Could not generate persistent MAC address for veth64ceb70: No such file or directory Jul 25 01:20:00 sentry-docker00.cs.umd.edu systemd-udevd[3005733]: Could not generate persistent MAC address for vethf83297c: No such file or directory Jul 25 01:27:18 sentry-docker00.cs.umd.edu systemd-udevd[3008720]: link_config: could not get ethtool features for vethb81665b Jul 25 01:27:18 sentry-docker00.cs.umd.edu systemd-udevd[3008720]: Could not set offload features of vethb81665b: No such device Jul 25 01:27:18 sentry-docker00.cs.umd.edu systemd-udevd[3008792]: Could not generate persistent MAC address for veth715281d: No such file or directory Jul 25 01:27:18 sentry-docker00.cs.umd.edu systemd-udevd[3008793]: Could not generate persistent MAC address for vethed49e9d: No such file or directory Jul 25 01:27:18 sentry-docker00.cs.umd.edu systemd-udevd[3008796]: Could not generate persistent MAC address for veth476e269: No such file or directory Jul 25 01:27:18 sentry-docker00.cs.umd.edu systemd-udevd[3008797]: Could not generate persistent MAC address for vetha128410: No such file or directory Jul 25 01:27:18 sentry-docker00.cs.umd.edu systemd-udevd[3008808]: Could not generate persistent MAC address for veth771a6c1: No such file or directory Jul 25 01:27:18 sentry-docker00.cs.umd.edu systemd-udevd[3008804]: Could not generate persistent MAC address for veth9e6e405: No such file or directory Jul 25 01:27:18 sentry-docker00.cs.umd.edu systemd-udevd[3008822]: Could not generate persistent MAC address for veth22683e1: No such file or directory Jul 25 01:27:18 sentry-docker00.cs.umd.edu systemd-udevd[3008823]: Could not generate persistent MAC address for vethbcd080a: No such file or directory Jul 25 01:40:04 sentry-docker00.cs.umd.edu systemd-udevd[3015376]: Could not generate persistent MAC address for veth59b55a5: No such file or directory Jul 25 01:40:04 sentry-docker00.cs.umd.edu systemd-udevd[3015377]: Could not generate persistent MAC address for vethedf7db0: No such file or directory Jul 25 01:47:26 sentry-docker00.cs.umd.edu systemd-udevd[3018170]: link_config: could not get ethtool features for veth715281d Jul 25 01:47:26 sentry-docker00.cs.umd.edu systemd-udevd[3018170]: Could not set offload features of veth715281d: No such device Jul 25 01:47:27 sentry-docker00.cs.umd.edu systemd-udevd[3018194]: Could not generate persistent MAC address for vethb85c352: No such file or directory Jul 25 01:47:27 sentry-docker00.cs.umd.edu systemd-udevd[3018195]: Could not generate persistent MAC address for vethdf61aec: No such file or directory ... 10 more distinct messages not shown == strawberry (2 distinct, 8 total) == Jul 25 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] Jul 25 01:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-2 (10 distinct, 12 total) == Jul 25 01:08:06 submit26-b9-2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x3] Jul 25 01:12:48 submit26-b9-2 setroubleshoot[150831]: 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 25 01:12:48 submit26-b9-2 setroubleshoot[150831]: 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 25 01:12:48 submit26-b9-2 setroubleshoot[150831]: 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 25 01:12:48 submit26-b9-2 setroubleshoot[150831]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.yovXGY/repodata/repomd.xml. For complete SELinux messages run: sealert -l 1b38f2ec-01ce-4343-8059-ba7494ecc5c4 Jul 25 01:12:48 submit26-b9-2 setroubleshoot[150831]: 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 25 01:12:48 submit26-b9-2 setroubleshoot[150831]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.yovXGY. For complete SELinux messages run: sealert -l 5c54db87-54a3-4a7c-97b4-b5c48d6c3543 Jul 25 01:12:48 submit26-b9-2 setroubleshoot[150831]: 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 25 01:12:48 submit26-b9-2 setroubleshoot[150831]: 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 25 01:12:48 submit26-b9-2 setroubleshoot[150831]: 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 25 01:20:34 submit26-b9-3 setroubleshoot[572023]: 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 25 01:20:34 submit26-b9-3 setroubleshoot[572023]: 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 25 01:20:34 submit26-b9-3 setroubleshoot[572023]: 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 25 01:20:34 submit26-b9-3 setroubleshoot[572023]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.YGm2GL/repodata/repomd.xml. For complete SELinux messages run: sealert -l 45a8019e-f6b5-4baa-92c1-862594b40d46 Jul 25 01:20:34 submit26-b9-3 setroubleshoot[572023]: 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 25 01:20:34 submit26-b9-3 setroubleshoot[572023]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.YGm2GL. For complete SELinux messages run: sealert -l 0b17cc3d-cdc6-4fe2-a11f-3892e7c41dc7 Jul 25 01:20:34 submit26-b9-3 setroubleshoot[572023]: 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 25 01:20:34 submit26-b9-3 setroubleshoot[572023]: 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 25 01:20:34 submit26-b9-3 setroubleshoot[572023]: 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, 6 total) == Jul 25 01:08:06 submit26-b9-4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x6] == submit26-clnb9 (9 distinct, 12 total) == Jul 25 01:31:52 submit26-clnb9 setroubleshoot[1271478]: 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 25 01:31:52 submit26-clnb9 setroubleshoot[1271478]: 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 25 01:31:52 submit26-clnb9 setroubleshoot[1271478]: 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 25 01:31:52 submit26-clnb9 setroubleshoot[1271478]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.EYNcim/repodata/repomd.xml. For complete SELinux messages run: sealert -l 001acdb5-31ef-4e52-b10b-90f467a89ddc [x2] Jul 25 01:31:52 submit26-clnb9 setroubleshoot[1271478]: 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 25 01:31:52 submit26-clnb9 setroubleshoot[1271478]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.EYNcim. For complete SELinux messages run: sealert -l 62b3782e-4730-4488-8178-94dafe9b552c Jul 25 01:31:52 submit26-clnb9 setroubleshoot[1271478]: 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 25 01:31:52 submit26-clnb9 setroubleshoot[1271478]: 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 25 01:31:52 submit26-clnb9 setroubleshoot[1271478]: 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