Command: /usr/local/sbin/syslog-digest.py Time : 0.4661s Status : exited 0 Output : Syslog digest — 2026-07-22 06:05 EDT Processed 3,837 lines, filtered 3,178 (82%). 659 unknown (109 distinct) from 22 host(s). == abuse (1 distinct, 346 total) == Jul 22 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, 5 total) == Jul 22 05:10:41 b0b02.cs.umd.edu rustdesk[1571339]: cannot open display: Jul 22 05:39:38 b0b02.cs.umd.edu setroubleshoot[1578399]: 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 [x2] Jul 22 05:39:41 b0b02.cs.umd.edu setroubleshoot[1578399]: 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 Jul 22 05:39:44 b0b02.cs.umd.edu setroubleshoot[1578399]: 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 == biggulp.cs.umd.edu (3 distinct, 3 total) == Jul 22 05:55:42 biggulp.cs.umd.edu sshd-session[3627837]: pam_access(sshd:auth): access denied for user `admin' from `45.154.244.149' Jul 22 05:55:43 biggulp.cs.umd.edu krb5_child[3627839]: Client 'admin@UMD.EDU' not found in Kerberos database Jul 22 05:55:43 biggulp.cs.umd.edu sshd-session[3627835]: error: PAM: System error for admin from 45.154.244.149 == contest (1 distinct, 34 total) == Jul 22 05:05:47 contest goferd[994]: [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] == csfw00a (1 distinct, 88 total) == Jul 22 05:05:00 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x88] == dojo (10 distinct, 10 total) == Jul 22 05:54:58 dojo systemd[1]: networkd-dispatcher.service: Got notification message from PID 15780, but reception only permitted for main PID 2296 Jul 22 05:55:07 dojo kernel: kauditd_printk_skb: 9 callbacks suppressed Jul 22 05:55:08 dojo systemd[1]: networkd-dispatcher.service: Got notification message from PID 15879, but reception only permitted for main PID 2296 Jul 22 05:55:08 dojo systemd[1]: networkd-dispatcher.service: Got notification message from PID 15884, but reception only permitted for main PID 2296 Jul 22 05:55:13 dojo kernel: kauditd_printk_skb: 10 callbacks suppressed Jul 22 05:55:30 dojo systemd[1]: networkd-dispatcher.service: Got notification message from PID 15994, but reception only permitted for main PID 2296 Jul 22 05:55:30 dojo systemd[1]: networkd-dispatcher.service: Got notification message from PID 15999, but reception only permitted for main PID 2296 Jul 22 05:55:39 dojo kernel: kauditd_printk_skb: 6 callbacks suppressed Jul 22 05:55:44 dojo systemd[1]: networkd-dispatcher.service: Got notification message from PID 16124, but reception only permitted for main PID 2296 Jul 22 05:55:59 dojo kernel: kauditd_printk_skb: 1 callbacks suppressed == grades01.cs.umd.edu (1 distinct, 1 total) == Jul 22 05:48:04 grades01.cs.umd.edu puppet-agent[27890]: 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) == Jul 22 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.BKMCT3”: Permission denied == idm00 (1 distinct, 1 total) == Jul 22 05:51:03 idm00 named[1455]: client @0x7f3315c58ef8 10.73.240.42#60945: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Jul 22 05:34:57 idmp0 named[5198]: client @0x7f9920014e58 10.73.240.43#52156: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 40 total) == Jul 22 05:08:09 itmon02 sshd[1904]: error: beginning MaxStartups throttling [x40] == matrix (11 distinct, 13 total) == Jul 22 05:32:39 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 3419668, but reception only permitted for main PID 720 Jul 22 05:32:39 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 3419681, but reception only permitted for main PID 720 Jul 22 05:32:47 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 3419775, but reception only permitted for main PID 720 Jul 22 05:32:47 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 3419781, but reception only permitted for main PID 720 Jul 22 05:32:47 matrix networkctl[3419791]: Interface "veth71af2ad" not found. Jul 22 05:32:47 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 3419791, but reception only permitted for main PID 720 [x2] Jul 22 05:32:47 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 3419864, but reception only permitted for main PID 720 Jul 22 05:32:56 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 3419956, but reception only permitted for main PID 720 Jul 22 05:32:56 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 3419962, but reception only permitted for main PID 720 Jul 22 05:32:56 matrix networkctl[3419972]: Interface "veth611bd96" not found. Jul 22 05:32:56 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 3419972, but reception only permitted for main PID 720 [x2] == mcstic (1 distinct, 2 total) == Jul 22 05:55:58 mcstic krb5_child[1477428]: Preauthentication failed [x2] == newhonors2 (1 distinct, 24 total) == Jul 22 05:13:03 newhonors2 dhcpcd[112116]: dhcpcd is not running [x24] == outbound00.cs.umd.edu (3 distinct, 8 total) == Jul 22 05:09:08 outbound00.cs.umd.edu python3[2529346]: ldapdb [x6] Jul 22 05:28:42 outbound00.cs.umd.edu krb5_child[2534062]: Client 'admin@UMD.EDU' not found in Kerberos database Jul 22 05:57:19 outbound00.cs.umd.edu krb5_child[2540661]: Preauthentication failed == outbound01.cs.umd.edu (2 distinct, 8 total) == Jul 22 05:08:18 outbound01.cs.umd.edu python3[555552]: ldapdb [x7] Jul 22 05:09:26 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. == sebatinsky.cs.umd.edu (1 distinct, 1 total) == Jul 22 05:31:33 sebatinsky.cs.umd.edu setroubleshoot[2750267]: SELinux is preventing /usr/sbin/pdns_server from name_bind access on the udp_socket port 16514. For complete SELinux messages run: sealert -l c40f9216-4e23-4184-838a-6a4f5ec6ccb3 == sentry-docker00.cs.umd.edu (42 distinct, 42 total) == Jul 22 05:16:21 sentry-docker00.cs.umd.edu systemd-udevd[999534]: link_config: could not get ethtool features for vethf665014 Jul 22 05:16:21 sentry-docker00.cs.umd.edu systemd-udevd[999534]: Could not set offload features of vethf665014: No such device Jul 22 05:16:21 sentry-docker00.cs.umd.edu systemd-udevd[999552]: Could not generate persistent MAC address for vethdbb9c36: No such file or directory Jul 22 05:16:21 sentry-docker00.cs.umd.edu systemd-udevd[999553]: Could not generate persistent MAC address for vetha0e2c14: No such file or directory Jul 22 05:19:21 sentry-docker00.cs.umd.edu systemd-udevd[1001557]: link_config: could not get ethtool features for vethf7f2380 Jul 22 05:19:21 sentry-docker00.cs.umd.edu systemd-udevd[1001557]: Could not set offload features of vethf7f2380: No such device Jul 22 05:19:21 sentry-docker00.cs.umd.edu systemd-udevd[1001611]: link_config: could not get ethtool features for veth587feeb Jul 22 05:19:21 sentry-docker00.cs.umd.edu systemd-udevd[1001611]: Could not set offload features of veth587feeb: No such device Jul 22 05:19:22 sentry-docker00.cs.umd.edu systemd-udevd[1001623]: Could not generate persistent MAC address for vethf988a5a: No such file or directory Jul 22 05:19:22 sentry-docker00.cs.umd.edu systemd-udevd[1001624]: Could not generate persistent MAC address for veth0a3035d: No such file or directory Jul 22 05:19:22 sentry-docker00.cs.umd.edu systemd-udevd[1001627]: Could not generate persistent MAC address for veth4457f23: No such file or directory Jul 22 05:19:22 sentry-docker00.cs.umd.edu systemd-udevd[1001628]: Could not generate persistent MAC address for veth0022f7a: No such file or directory Jul 22 05:19:22 sentry-docker00.cs.umd.edu systemd-udevd[1001651]: Could not generate persistent MAC address for vethf2a0189: No such file or directory Jul 22 05:19:22 sentry-docker00.cs.umd.edu systemd-udevd[1001652]: Could not generate persistent MAC address for veth57ba0fc: No such file or directory Jul 22 05:19:22 sentry-docker00.cs.umd.edu systemd-udevd[1001670]: Could not generate persistent MAC address for veth9a74e55: No such file or directory Jul 22 05:19:22 sentry-docker00.cs.umd.edu systemd-udevd[1001664]: Could not generate persistent MAC address for veth2ea9753: No such file or directory Jul 22 05:36:25 sentry-docker00.cs.umd.edu systemd-udevd[1008965]: link_config: could not get ethtool features for vethdbb9c36 Jul 22 05:36:25 sentry-docker00.cs.umd.edu systemd-udevd[1008965]: Could not set offload features of vethdbb9c36: No such device Jul 22 05:36:25 sentry-docker00.cs.umd.edu systemd-udevd[1008981]: Could not generate persistent MAC address for veth2f1b48b: No such file or directory Jul 22 05:36:25 sentry-docker00.cs.umd.edu systemd-udevd[1008982]: Could not generate persistent MAC address for vethd057141: No such file or directory Jul 22 05:39:30 sentry-docker00.cs.umd.edu systemd-udevd[1011047]: link_config: could not get ethtool features for vethf2a0189 Jul 22 05:39:30 sentry-docker00.cs.umd.edu systemd-udevd[1011047]: Could not set offload features of vethf2a0189: No such device Jul 22 05:39:30 sentry-docker00.cs.umd.edu systemd-udevd[1011096]: Could not generate persistent MAC address for veth06efd37: No such file or directory Jul 22 05:39:30 sentry-docker00.cs.umd.edu systemd-udevd[1011097]: Could not generate persistent MAC address for vetha0a58ba: No such file or directory Jul 22 05:39:30 sentry-docker00.cs.umd.edu systemd-udevd[1011122]: Could not generate persistent MAC address for veth1487e32: No such file or directory Jul 22 05:39:30 sentry-docker00.cs.umd.edu systemd-udevd[1011123]: Could not generate persistent MAC address for veth0d245ed: No such file or directory Jul 22 05:39:30 sentry-docker00.cs.umd.edu systemd-udevd[1011141]: Could not generate persistent MAC address for vethdb6286b: No such file or directory Jul 22 05:39:30 sentry-docker00.cs.umd.edu systemd-udevd[1011145]: Could not generate persistent MAC address for veth1fac007: No such file or directory Jul 22 05:39:30 sentry-docker00.cs.umd.edu systemd-udevd[1011140]: Could not generate persistent MAC address for vethf913056: No such file or directory Jul 22 05:39:30 sentry-docker00.cs.umd.edu systemd-udevd[1011136]: Could not generate persistent MAC address for veth93828c5: No such file or directory ... 12 more distinct messages not shown == strawberry (2 distinct, 8 total) == Jul 22 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] Jul 22 05:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-3 (9 distinct, 9 total) == Jul 22 05:20:33 submit26-b9-3 setroubleshoot[502327]: 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 22 05:20:33 submit26-b9-3 setroubleshoot[502327]: 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 22 05:20:33 submit26-b9-3 setroubleshoot[502327]: 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 22 05:20:33 submit26-b9-3 setroubleshoot[502327]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.hP1w9a/repodata/repomd.xml. For complete SELinux messages run: sealert -l 45a8019e-f6b5-4baa-92c1-862594b40d46 Jul 22 05:20:33 submit26-b9-3 setroubleshoot[502327]: 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 22 05:20:33 submit26-b9-3 setroubleshoot[502327]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.hP1w9a. For complete SELinux messages run: sealert -l 0b17cc3d-cdc6-4fe2-a11f-3892e7c41dc7 Jul 22 05:20:33 submit26-b9-3 setroubleshoot[502327]: 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 22 05:20:33 submit26-b9-3 setroubleshoot[502327]: 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 22 05:20:33 submit26-b9-3 setroubleshoot[502327]: 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, 11 total) == Jul 22 05:31:51 submit26-clnb9 setroubleshoot[1129407]: 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] Jul 22 05:31:51 submit26-clnb9 setroubleshoot[1129407]: 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] Jul 22 05:31:51 submit26-clnb9 setroubleshoot[1129407]: 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 Jul 22 05:31:51 submit26-clnb9 setroubleshoot[1129407]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.5RGzsf/repodata/repomd.xml. For complete SELinux messages run: sealert -l 001acdb5-31ef-4e52-b10b-90f467a89ddc Jul 22 05:31:51 submit26-clnb9 setroubleshoot[1129407]: 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 Jul 22 05:31:51 submit26-clnb9 setroubleshoot[1129407]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.5RGzsf. For complete SELinux messages run: sealert -l 62b3782e-4730-4488-8178-94dafe9b552c Jul 22 05:31:51 submit26-clnb9 setroubleshoot[1129407]: 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 22 05:31:51 submit26-clnb9 setroubleshoot[1129407]: 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 22 05:31:51 submit26-clnb9 setroubleshoot[1129407]: 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 == updates00.cs.umd.edu (3 distinct, 3 total) == Jul 22 05:18:35 updates00.cs.umd.edu puppet-agent[18996]: 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 Jul 22 05:18:35 updates00.cs.umd.edu puppet-agent[18996]: Not using cache on failed catalog Jul 22 05:18:35 updates00.cs.umd.edu puppet-agent[18996]: Could not retrieve catalog; skipping run