Command: /usr/local/sbin/syslog-digest.py Time : 0.5179s Status : exited 0 Output : Syslog digest — 2026-08-06 02:05 EDT Processed 4,271 lines, filtered 3,361 (78%). 910 unknown (120 distinct) from 24 host(s). == abuse (1 distinct, 347 total) == Aug 6 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 6 01:47:12 b0b02.cs.umd.edu rustdesk[3416828]: cannot open display: == bachata (1 distinct, 1 total) == Aug 6 01:47:02 bachata setroubleshoot[2537582]: SELinux is preventing /usr/sbin/smbd from name_bind access on the udp_socket port 628. For complete SELinux messages run: sealert -l 8f7247f1-69a5-4a62-a4f0-88a324bfd75c == cheezit.cs.umd.edu (4 distinct, 4 total) == Aug 6 02:04:50 cheezit.cs.umd.edu sshd-session[1536948]: pam_access(sshd:auth): access denied for user `admin' from `34.79.217.97' Aug 6 02:04:50 cheezit.cs.umd.edu krb5_child[1536950]: Client 'admin@UMD.EDU' not found in Kerberos database Aug 6 02:04:50 cheezit.cs.umd.edu sshd-session[1536946]: error: PAM: System error for admin from 34.79.217.97 Aug 6 02:04:54 cheezit.cs.umd.edu sshd-session[1536959]: error: Protocol major versions differ: 2 vs. 1 == contest (12 distinct, 47 total) == Aug 6 01: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 6 01:48:18 contest setroubleshoot[702207]: SELinux is preventing /usr/libexec/platform-python3.6 from create access on the directory libdnf.Rwm2mo. For complete SELinux messages run: sealert -l cb6b25c6-4765-4cf2-88a0-9b3b508e94e9 Aug 6 01:48:18 contest setroubleshoot[702207]: 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 6 01:48:18 contest setroubleshoot[702207]: 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 6 01:48:18 contest setroubleshoot[702207]: 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 6 01:48:18 contest setroubleshoot[702207]: 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 6 01:48:18 contest setroubleshoot[702207]: SELinux is preventing /usr/libexec/platform-python3.6 from read access on the directory libdnf.Rwm2mo. For complete SELinux messages run: sealert -l 45d103b6-0810-4890-a705-990118577ce8 Aug 6 01:48:18 contest setroubleshoot[702207]: 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 6 01:48:18 contest setroubleshoot[702207]: 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 6 01:48:20 contest setroubleshoot[702207]: SELinux is preventing /usr/libexec/platform-python3.6 from create access on the directory libdnf.lhEdgW. For complete SELinux messages run: sealert -l cb6b25c6-4765-4cf2-88a0-9b3b508e94e9 Aug 6 01:48:26 contest setroubleshoot[702207]: 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 6 01:48:39 contest setroubleshoot[702275]: 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 (1 distinct, 270 total) == Aug 6 01:04:44 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x270] == hackerman (1 distinct, 1 total) == Aug 6 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.LY7NT3”: Permission denied == hazfs.cs.umd.edu (11 distinct, 66 total) == Aug 6 01:51:53 hazfs.cs.umd.edu snmpd[1431]: send response: Failure in sendto [x6] Aug 6 01:51:53 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userweb" [x6] Aug 6 01:51:53 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."zfslist" [x6] Aug 6 01:51:53 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userhome" [x6] Aug 6 01:51:53 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userweb" [x6] Aug 6 01:51:53 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."zfslist" [x6] Aug 6 01:51:53 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userhome" [x6] Aug 6 01:51:53 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userweb" [x6] Aug 6 01:51:53 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."zfslist" [x6] Aug 6 01:51:53 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userhome" [x6] Aug 6 01:51:53 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutNumLines."userweb" [x6] == idm00 (2 distinct, 2 total) == Aug 6 01:24:07 idm00 named[1455]: client @0x7f3304b3d148 10.73.245.12#64323: update '73.10.in-addr.arpa/IN' denied Aug 6 01:51:18 idm00 named[1455]: client @0x7f33048c7d98 10.73.240.42#63782: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Aug 6 01:36:07 idmp0 named[5198]: client @0x7f9924011de8 10.73.240.43#50538: update '73.10.in-addr.arpa/IN' denied == inbound00.cs.umd.edu (2 distinct, 2 total) == Aug 6 01:58:54 inbound00.cs.umd.edu krb5_child[3395650]: Client 'admin@UMD.EDU' not found in Kerberos database Aug 6 01:59:08 inbound00.cs.umd.edu sshd-session[3395657]: error: Protocol major versions differ: 2 vs. 1 == itmon02 (1 distinct, 34 total) == Aug 6 01:07:49 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x34] == krispykreme.cs.umd.edu (3 distinct, 3 total) == Aug 6 02:01:34 krispykreme.cs.umd.edu sshd-session[3830841]: pam_access(sshd:auth): access denied for user `admin' from `34.77.217.24' Aug 6 02:01:35 krispykreme.cs.umd.edu krb5_child[3830843]: Client 'admin@UMD.EDU' not found in Kerberos database Aug 6 02:01:35 krispykreme.cs.umd.edu sshd-session[3830839]: error: PAM: System error for admin from 34.77.217.24 == netman.cs.umd.edu (2 distinct, 5 total) == Aug 6 01:35:48 netman.cs.umd.edu krb5_child[1326278]: Client 'admin@UMD.EDU' not found in Kerberos database [x4] Aug 6 01:35:53 netman.cs.umd.edu sshd[1326275]: error: PAM: Authentication failure for admin from 202.129.35.8 == newhonors2 (1 distinct, 24 total) == Aug 6 01:13:02 newhonors2 dhcpcd[795802]: dhcpcd is not running [x24] == outbound00.cs.umd.edu (1 distinct, 6 total) == Aug 6 01:09:09 outbound00.cs.umd.edu python3[3335183]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Aug 6 01:13:06 outbound01.cs.umd.edu python3[1369819]: ldapdb [x6] == sentry-docker00.cs.umd.edu (40 distinct, 40 total) == Aug 6 01:05:48 sentry-docker00.cs.umd.edu systemd-udevd[2776740]: link_config: could not get ethtool features for vethbf9dc25 Aug 6 01:05:48 sentry-docker00.cs.umd.edu systemd-udevd[2776740]: Could not set offload features of vethbf9dc25: No such device Aug 6 01:05:48 sentry-docker00.cs.umd.edu systemd-udevd[2776820]: Could not generate persistent MAC address for veth98d0e73: No such file or directory Aug 6 01:05:48 sentry-docker00.cs.umd.edu systemd-udevd[2776821]: Could not generate persistent MAC address for veth9ed0b2c: No such file or directory Aug 6 01:05:48 sentry-docker00.cs.umd.edu systemd-udevd[2776824]: Could not generate persistent MAC address for vethab254b5: No such file or directory Aug 6 01:05:48 sentry-docker00.cs.umd.edu systemd-udevd[2776825]: Could not generate persistent MAC address for vethf246302: No such file or directory Aug 6 01:05:48 sentry-docker00.cs.umd.edu systemd-udevd[2776826]: Could not generate persistent MAC address for vethf19b451: No such file or directory Aug 6 01:05:48 sentry-docker00.cs.umd.edu systemd-udevd[2776842]: Could not generate persistent MAC address for veth2ea431d: No such file or directory Aug 6 01:05:48 sentry-docker00.cs.umd.edu systemd-udevd[2776850]: Could not generate persistent MAC address for vethe957216: No such file or directory Aug 6 01:05:48 sentry-docker00.cs.umd.edu systemd-udevd[2776851]: Could not generate persistent MAC address for vethe77ca4e: No such file or directory Aug 6 01:05:48 sentry-docker00.cs.umd.edu systemd-udevd[2776875]: Could not generate persistent MAC address for veth9144038: No such file or directory Aug 6 01:05:48 sentry-docker00.cs.umd.edu systemd-udevd[2776855]: Could not generate persistent MAC address for vethea89b40: No such file or directory Aug 6 01:25:56 sentry-docker00.cs.umd.edu systemd-udevd[2786376]: link_config: could not get ethtool features for veth98d0e73 Aug 6 01:25:56 sentry-docker00.cs.umd.edu systemd-udevd[2786376]: Could not set offload features of veth98d0e73: No such device Aug 6 01:25:56 sentry-docker00.cs.umd.edu systemd-udevd[2786381]: link_config: could not get ethtool features for vethab254b5 Aug 6 01:25:56 sentry-docker00.cs.umd.edu systemd-udevd[2786381]: Could not set offload features of vethab254b5: No such device Aug 6 01:25:57 sentry-docker00.cs.umd.edu systemd-udevd[2786413]: Could not generate persistent MAC address for veth62d5ff4: No such file or directory Aug 6 01:25:57 sentry-docker00.cs.umd.edu systemd-udevd[2786414]: Could not generate persistent MAC address for vethecc95ee: No such file or directory Aug 6 01:25:57 sentry-docker00.cs.umd.edu systemd-udevd[2786417]: Could not generate persistent MAC address for veth7ec964a: No such file or directory Aug 6 01:25:57 sentry-docker00.cs.umd.edu systemd-udevd[2786418]: Could not generate persistent MAC address for veth100b82a: No such file or directory Aug 6 01:25:57 sentry-docker00.cs.umd.edu systemd-udevd[2786421]: Could not generate persistent MAC address for veth76c082e: No such file or directory Aug 6 01:25:57 sentry-docker00.cs.umd.edu systemd-udevd[2786428]: Could not generate persistent MAC address for vethc3d1276: No such file or directory Aug 6 01:25:57 sentry-docker00.cs.umd.edu systemd-udevd[2786443]: Could not generate persistent MAC address for vetheddddef: No such file or directory Aug 6 01:25:57 sentry-docker00.cs.umd.edu systemd-udevd[2786444]: Could not generate persistent MAC address for veth2bf48d9: No such file or directory Aug 6 01:25:57 sentry-docker00.cs.umd.edu systemd-udevd[2786528]: Could not generate persistent MAC address for vethf939ffc: No such file or directory Aug 6 01:25:57 sentry-docker00.cs.umd.edu systemd-udevd[2786518]: Could not generate persistent MAC address for veth60f62d8: No such file or directory Aug 6 01:46:05 sentry-docker00.cs.umd.edu systemd-udevd[2795818]: link_config: could not set ethtool features for veth60f62d8 Aug 6 01:46:05 sentry-docker00.cs.umd.edu systemd-udevd[2795818]: Could not set offload features of veth60f62d8: Operation not permitted Aug 6 01:46:05 sentry-docker00.cs.umd.edu systemd-udevd[2795820]: link_config: could not get ethtool features for vetheddddef Aug 6 01:46:05 sentry-docker00.cs.umd.edu systemd-udevd[2795820]: Could not set offload features of vetheddddef: No such device ... 10 more distinct messages not shown == strawberry (2 distinct, 8 total) == Aug 6 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 6 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 6 01:12:53 submit26-b9-2 setroubleshoot[1129889]: 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 [x2] Aug 6 01:12:53 submit26-b9-2 setroubleshoot[1129889]: 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 [x2] Aug 6 01:12:53 submit26-b9-2 setroubleshoot[1129889]: 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 6 01:12:53 submit26-b9-2 setroubleshoot[1129889]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.0CYayg/repodata/repomd.xml. For complete SELinux messages run: sealert -l 1b38f2ec-01ce-4343-8059-ba7494ecc5c4 Aug 6 01:12:53 submit26-b9-2 setroubleshoot[1129889]: 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 6 01:12:53 submit26-b9-2 setroubleshoot[1129889]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.0CYayg. For complete SELinux messages run: sealert -l 5c54db87-54a3-4a7c-97b4-b5c48d6c3543 Aug 6 01:12:53 submit26-b9-2 setroubleshoot[1129889]: 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 [x2] Aug 6 01:12:53 submit26-b9-2 setroubleshoot[1129889]: 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 6 01:12:53 submit26-b9-2 setroubleshoot[1129889]: 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 [x2] Aug 6 01:12:53 submit26-b9-2 setroubleshoot[1129889]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.6yVVeS. For complete SELinux messages run: sealert -l 5c54db87-54a3-4a7c-97b4-b5c48d6c3543 == submit26-b9-3 (9 distinct, 9 total) == Aug 6 01:20:39 submit26-b9-3 setroubleshoot[867611]: 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 6 01:20:39 submit26-b9-3 setroubleshoot[867611]: 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 6 01:20:39 submit26-b9-3 setroubleshoot[867611]: 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 6 01:20:39 submit26-b9-3 setroubleshoot[867611]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.osEymi/repodata/repomd.xml. For complete SELinux messages run: sealert -l 45a8019e-f6b5-4baa-92c1-862594b40d46 Aug 6 01:20:39 submit26-b9-3 setroubleshoot[867611]: 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 6 01:20:39 submit26-b9-3 setroubleshoot[867611]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.osEymi. For complete SELinux messages run: sealert -l 0b17cc3d-cdc6-4fe2-a11f-3892e7c41dc7 Aug 6 01:20:39 submit26-b9-3 setroubleshoot[867611]: 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 6 01:20:39 submit26-b9-3 setroubleshoot[867611]: 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 6 01:20:39 submit26-b9-3 setroubleshoot[867611]: 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-clnb9 (10 distinct, 14 total) == Aug 6 01:31:58 submit26-clnb9 setroubleshoot[1859465]: 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 [x2] Aug 6 01:31:58 submit26-clnb9 setroubleshoot[1859465]: 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 [x2] Aug 6 01:31:58 submit26-clnb9 setroubleshoot[1859465]: 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 6 01:31:58 submit26-clnb9 setroubleshoot[1859465]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.XevcMc/repodata/repomd.xml. For complete SELinux messages run: sealert -l 001acdb5-31ef-4e52-b10b-90f467a89ddc Aug 6 01:31:58 submit26-clnb9 setroubleshoot[1859465]: 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 6 01:31:58 submit26-clnb9 setroubleshoot[1859465]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.XevcMc. For complete SELinux messages run: sealert -l 62b3782e-4730-4488-8178-94dafe9b552c Aug 6 01:31:58 submit26-clnb9 setroubleshoot[1859465]: 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 [x2] Aug 6 01:31:58 submit26-clnb9 setroubleshoot[1859465]: 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 6 01:31:58 submit26-clnb9 setroubleshoot[1859465]: 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 [x2] Aug 6 01:31:58 submit26-clnb9 setroubleshoot[1859465]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.bOx0OB. For complete SELinux messages run: sealert -l 62b3782e-4730-4488-8178-94dafe9b552c == teaching-awards (2 distinct, 4 total) == Aug 6 01:30:04 teaching-awards krb5_child[1952850]: Client 'admin@UMD.EDU' not found in Kerberos database Aug 6 01:30:20 teaching-awards sshd-session[1952854]: error: Protocol major versions differ: 2 vs. 1 [x3] == tma-0 (1 distinct, 1 total) == Aug 6 01:05:11 tma-0 sshd[3770]: error: PAM: Authentication failure for admin from 49.231.241.35.bc.googleusercontent.com