Command: /usr/local/sbin/syslog-digest.py Time : 0.4984s Status : exited 0 Output : Syslog digest — 2026-08-06 06:05 EDT Processed 4,343 lines, filtered 3,574 (82%). 769 unknown (100 distinct) from 23 host(s). == abuse (1 distinct, 346 total) == Aug 6 05: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 (4 distinct, 4 total) == Aug 6 05:41:55 b0b02.cs.umd.edu setroubleshoot[3476492]: SELinux is preventing /usr/bin/python3.9 from getattr access on the file /etc/authselect/nsswitch.conf. For complete SELinux messages run: sealert -l 9a1e2952-3fde-4937-a8ab-f7f59791a458 Aug 6 05:41:58 b0b02.cs.umd.edu setroubleshoot[3476492]: SELinux is preventing /usr/bin/python3.9 from read access on the file /etc/authselect/nsswitch.conf. For complete SELinux messages run: sealert -l 97d74423-e027-4cd6-8810-ad80944900b5 Aug 6 05:42:01 b0b02.cs.umd.edu setroubleshoot[3476492]: SELinux is preventing /usr/bin/python3.9 from open access on the file /etc/authselect/nsswitch.conf. For complete SELinux messages run: sealert -l 4f253f6a-62d6-46dd-8eaf-0b4d29df41c6 Aug 6 05:47:28 b0b02.cs.umd.edu rustdesk[3477467]: cannot open display: == bachata (1 distinct, 2 total) == Aug 6 05:48:06 bachata setroubleshoot[2547425]: 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 [x2] == contest (10 distinct, 43 total) == Aug 6 05:06: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') [x33] Aug 6 05:48:18 contest setroubleshoot[711480]: SELinux is preventing /usr/libexec/platform-python3.6 from create access on the directory libdnf.TS2JdO. For complete SELinux messages run: sealert -l cb6b25c6-4765-4cf2-88a0-9b3b508e94e9 Aug 6 05:48:18 contest setroubleshoot[711480]: 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 05:48:19 contest setroubleshoot[711480]: 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 05:48:19 contest setroubleshoot[711480]: 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 6 05:48:19 contest setroubleshoot[711480]: 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 05:48:19 contest setroubleshoot[711480]: SELinux is preventing /usr/libexec/platform-python3.6 from read access on the directory libdnf.TS2JdO. For complete SELinux messages run: sealert -l 45d103b6-0810-4890-a705-990118577ce8 Aug 6 05:48:19 contest setroubleshoot[711480]: 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 05:48:19 contest setroubleshoot[711480]: 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 05:48:21 contest setroubleshoot[711480]: SELinux is preventing /usr/libexec/platform-python3.6 from create access on the directory libdnf.dugtFo. For complete SELinux messages run: sealert -l cb6b25c6-4765-4cf2-88a0-9b3b508e94e9 == csfw00a (1 distinct, 224 total) == Aug 6 05:04:24 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x224] == frabjous (2 distinct, 2 total) == Aug 6 05:46:00 frabjous krb5_child[3344643]: Client 'admin@UMD.EDU' not found in Kerberos database Aug 6 05:46:02 frabjous sshd-session[3344639]: error: PAM: Authentication failure for admin from 94.183.187.22 == grades01.cs.umd.edu (1 distinct, 1 total) == Aug 6 05:48:40 grades01.cs.umd.edu puppet-agent[32273]: The directory '/srv/grades' contains 2471 entries, which exceeds the default soft limit 1000 and may cause excessive resource consumption and degraded performance. To remove this warning set a value for `max_files` parameter or consider using an alternate method to manage large directory trees == hackerman (1 distinct, 1 total) == Aug 6 05: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.5JPST3”: Permission denied == idm00 (1 distinct, 1 total) == Aug 6 05:51:19 idm00 named[1455]: client @0x7f330c467a48 10.73.240.42#54528: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Aug 6 05:36:07 idmp0 named[5198]: client @0x7f99000dfeb8 10.73.240.43#55356: update '73.10.in-addr.arpa/IN' denied == inbound00.cs.umd.edu (1 distinct, 1 total) == Aug 6 05:32:32 inbound00.cs.umd.edu cockpit-ws[3445756]: /usr/share/cockpit/static/login.js/favicon.ico: Failed to open file “/usr/share/cockpit/static/login.js/favicon.ico”: open() failed: Not a directory == inbound01.cs.umd.edu (2 distinct, 4 total) == Aug 6 05:32:33 inbound01.cs.umd.edu cockpit-ws[1460148]: /usr/share/cockpit/static/login.js/favicon.ico: Failed to open file “/usr/share/cockpit/static/login.js/favicon.ico”: open() failed: Not a directory [x3] Aug 6 05:41:51 inbound01.cs.umd.edu krb5_child[1462132]: Client 'admin@UMD.EDU' not found in Kerberos database == itmon02 (1 distinct, 22 total) == Aug 6 05:13:06 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x22] == newhonors2 (1 distinct, 24 total) == Aug 6 05:13:02 newhonors2 dhcpcd[803189]: dhcpcd is not running [x24] == outbound00.cs.umd.edu (2 distinct, 8 total) == Aug 6 05:09:09 outbound00.cs.umd.edu python3[3391602]: ldapdb [x6] Aug 6 05:30:31 outbound00.cs.umd.edu cockpit-ws[3397005]: /usr/share/cockpit/static/login.js/favicon.ico: Failed to open file “/usr/share/cockpit/static/login.js/favicon.ico”: open() failed: Not a directory [x2] == outbound01.cs.umd.edu (3 distinct, 11 total) == Aug 6 05:08:24 outbound01.cs.umd.edu python3[1424683]: ldapdb [x7] Aug 6 05:09:31 outbound01.cs.umd.edu systemd[1]: Configuration file /usr/lib/systemd/system/authentication_milter.service is marked executable. Please remove executable permission bits. Proceeding anyway. Aug 6 06:03:35 outbound01.cs.umd.edu cockpit-ws[1438441]: /usr/share/cockpit/static/login.js/favicon.ico: Failed to open file “/usr/share/cockpit/static/login.js/favicon.ico”: open() failed: Not a directory [x3] == sentry-docker00.cs.umd.edu (34 distinct, 34 total) == Aug 6 05:07:28 sentry-docker00.cs.umd.edu systemd-udevd[2890797]: link_config: could not get ethtool features for veth14f3274 Aug 6 05:07:28 sentry-docker00.cs.umd.edu systemd-udevd[2890797]: Could not set offload features of veth14f3274: No such device Aug 6 05:07:28 sentry-docker00.cs.umd.edu systemd-udevd[2890826]: Could not generate persistent MAC address for vethefb9944: No such file or directory Aug 6 05:07:28 sentry-docker00.cs.umd.edu systemd-udevd[2890827]: Could not generate persistent MAC address for veth0dfbfeb: No such file or directory Aug 6 05:07:28 sentry-docker00.cs.umd.edu systemd-udevd[2890834]: Could not generate persistent MAC address for vethd630ad5: No such file or directory Aug 6 05:07:28 sentry-docker00.cs.umd.edu systemd-udevd[2890832]: Could not generate persistent MAC address for vethafd54d5: No such file or directory Aug 6 05:07:28 sentry-docker00.cs.umd.edu systemd-udevd[2890832]: Could not generate persistent MAC address for veth0461a8a: No such file or directory Aug 6 05:07:28 sentry-docker00.cs.umd.edu systemd-udevd[2890826]: Could not generate persistent MAC address for veth7342480: No such file or directory Aug 6 05:07:28 sentry-docker00.cs.umd.edu systemd-udevd[2890858]: Could not generate persistent MAC address for veth724fc30: No such file or directory Aug 6 05:07:28 sentry-docker00.cs.umd.edu systemd-udevd[2890859]: Could not generate persistent MAC address for vethbea723a: No such file or directory Aug 6 05:07:28 sentry-docker00.cs.umd.edu systemd-udevd[2890889]: Could not generate persistent MAC address for veth735f062: No such file or directory Aug 6 05:07:28 sentry-docker00.cs.umd.edu systemd-udevd[2890891]: Could not generate persistent MAC address for veth68fa6e5: No such file or directory Aug 6 05:27:36 sentry-docker00.cs.umd.edu systemd-udevd[2900439]: Could not generate persistent MAC address for vethaa8b90d: No such file or directory Aug 6 05:27:36 sentry-docker00.cs.umd.edu systemd-udevd[2900440]: Could not generate persistent MAC address for veth00bb72a: No such file or directory Aug 6 05:27:36 sentry-docker00.cs.umd.edu systemd-udevd[2900464]: Could not generate persistent MAC address for veth9329151: No such file or directory Aug 6 05:27:36 sentry-docker00.cs.umd.edu systemd-udevd[2900465]: Could not generate persistent MAC address for veth12e6897: No such file or directory Aug 6 05:27:36 sentry-docker00.cs.umd.edu systemd-udevd[2900483]: Could not generate persistent MAC address for veth2f1736d: No such file or directory Aug 6 05:27:36 sentry-docker00.cs.umd.edu systemd-udevd[2900478]: Could not generate persistent MAC address for veth2578c4b: No such file or directory Aug 6 05:27:36 sentry-docker00.cs.umd.edu systemd-udevd[2900492]: Could not generate persistent MAC address for veth2a01fcd: No such file or directory Aug 6 05:27:36 sentry-docker00.cs.umd.edu systemd-udevd[2900493]: Could not generate persistent MAC address for vethd70ac0b: No such file or directory Aug 6 05:27:36 sentry-docker00.cs.umd.edu systemd-udevd[2900533]: Could not generate persistent MAC address for veth1dd58af: No such file or directory Aug 6 05:27:36 sentry-docker00.cs.umd.edu systemd-udevd[2900536]: Could not generate persistent MAC address for vethc9bff15: No such file or directory Aug 6 05:47:44 sentry-docker00.cs.umd.edu systemd-udevd[2909887]: link_config: could not set ethtool features for veth2f1736d Aug 6 05:47:44 sentry-docker00.cs.umd.edu systemd-udevd[2909887]: Could not set offload features of veth2f1736d: Operation not permitted Aug 6 05:47:45 sentry-docker00.cs.umd.edu systemd-udevd[2909917]: Could not generate persistent MAC address for veth339529c: No such file or directory Aug 6 05:47:45 sentry-docker00.cs.umd.edu systemd-udevd[2909918]: Could not generate persistent MAC address for veth33c4554: No such file or directory Aug 6 05:47:45 sentry-docker00.cs.umd.edu systemd-udevd[2909929]: Could not generate persistent MAC address for vethb274a78: No such file or directory Aug 6 05:47:45 sentry-docker00.cs.umd.edu systemd-udevd[2909942]: Could not generate persistent MAC address for veth8522892: No such file or directory Aug 6 05:47:45 sentry-docker00.cs.umd.edu systemd-udevd[2909938]: Could not generate persistent MAC address for veth2087767: No such file or directory Aug 6 05:47:45 sentry-docker00.cs.umd.edu systemd-udevd[2909929]: Could not generate persistent MAC address for veth23c93ce: No such file or directory ... 4 more distinct messages not shown == strawberry (2 distinct, 8 total) == Aug 6 05: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 05:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-2 (9 distinct, 9 total) == Aug 6 05:12:53 submit26-b9-2 setroubleshoot[1139706]: 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 6 05:12:53 submit26-b9-2 setroubleshoot[1139706]: 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 6 05:12:53 submit26-b9-2 setroubleshoot[1139706]: 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 05:12:53 submit26-b9-2 setroubleshoot[1139706]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.n3dp7N/repodata/repomd.xml. For complete SELinux messages run: sealert -l 1b38f2ec-01ce-4343-8059-ba7494ecc5c4 Aug 6 05:12:53 submit26-b9-2 setroubleshoot[1139706]: 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 05:12:53 submit26-b9-2 setroubleshoot[1139706]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.n3dp7N. For complete SELinux messages run: sealert -l 5c54db87-54a3-4a7c-97b4-b5c48d6c3543 Aug 6 05:12:53 submit26-b9-2 setroubleshoot[1139706]: 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 6 05:12:53 submit26-b9-2 setroubleshoot[1139706]: 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 05:12:53 submit26-b9-2 setroubleshoot[1139706]: 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) == Aug 6 05:20:39 submit26-b9-3 setroubleshoot[871781]: 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 05:20:39 submit26-b9-3 setroubleshoot[871781]: 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 05:20:39 submit26-b9-3 setroubleshoot[871781]: 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 05:20:39 submit26-b9-3 setroubleshoot[871781]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.aWCusx/repodata/repomd.xml. For complete SELinux messages run: sealert -l 45a8019e-f6b5-4baa-92c1-862594b40d46 Aug 6 05:20:39 submit26-b9-3 setroubleshoot[871781]: 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 05:20:39 submit26-b9-3 setroubleshoot[871781]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.aWCusx. For complete SELinux messages run: sealert -l 0b17cc3d-cdc6-4fe2-a11f-3892e7c41dc7 Aug 6 05:20:39 submit26-b9-3 setroubleshoot[871781]: 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 05:20:39 submit26-b9-3 setroubleshoot[871781]: 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 05:20:39 submit26-b9-3 setroubleshoot[871781]: 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 (9 distinct, 9 total) == Aug 6 05:31:58 submit26-clnb9 setroubleshoot[1867748]: 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 6 05:31:58 submit26-clnb9 setroubleshoot[1867748]: 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 6 05:31:58 submit26-clnb9 setroubleshoot[1867748]: 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 05:31:58 submit26-clnb9 setroubleshoot[1867748]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.VW6DvJ/repodata/repomd.xml. For complete SELinux messages run: sealert -l 001acdb5-31ef-4e52-b10b-90f467a89ddc Aug 6 05:31:58 submit26-clnb9 setroubleshoot[1867748]: 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 05:31:58 submit26-clnb9 setroubleshoot[1867748]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.VW6DvJ. For complete SELinux messages run: sealert -l 62b3782e-4730-4488-8178-94dafe9b552c Aug 6 05:31:58 submit26-clnb9 setroubleshoot[1867748]: 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 6 05:31:58 submit26-clnb9 setroubleshoot[1867748]: 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 05:31:58 submit26-clnb9 setroubleshoot[1867748]: 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 == talkhosts9 (1 distinct, 2 total) == Aug 6 05:09:32 talkhosts9 setroubleshoot[1598656]: SELinux is preventing /usr/bin/lsof from getattr access on the unix_stream_socket unix_stream_socket. For complete SELinux messages run: sealert -l a6df89b3-c497-469c-8232-c4fde0508abf [x2] == updates00.cs.umd.edu (3 distinct, 3 total) == Aug 6 05:18:31 updates00.cs.umd.edu puppet-agent[17062]: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Function lookup() did not find a value for the name 'vault::kerberos' on node updates00.cs.umd.edu Aug 6 05:18:31 updates00.cs.umd.edu puppet-agent[17062]: Not using cache on failed catalog Aug 6 05:18:31 updates00.cs.umd.edu puppet-agent[17062]: Could not retrieve catalog; skipping run
participants (1)
-
cron/zfs00.cs.umd.edu