Command: /usr/local/sbin/syslog-digest.py Time : 0.4857s Status : exited 0 Output : Syslog digest — 2026-07-24 06:05 EDT Processed 4,742 lines, filtered 4,124 (86%). 618 unknown (107 distinct) from 23 host(s). == abadi-computer (2 distinct, 2 total) == Jul 24 05:54:16 abadi-computer kernel: kauditd_printk_skb: 31 callbacks suppressed Jul 24 06:00:37 abadi-computer kernel: kauditd_printk_skb: 20 callbacks suppressed == abuse (1 distinct, 346 total) == Jul 24 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] == alec.cs.umd.edu (3 distinct, 60 total) == Jul 24 05:05:30 alec.cs.umd.edu setroubleshoot[2461267]: failed to retrieve rpm info for path '/run/netns/netns-a2b2cc2d-7532-4db7-6a36-b1dd3d5f51db': [x12] Jul 24 05:05:30 alec.cs.umd.edu sedispatch[1526]: AVC Message regarding setroubleshoot, ignoring message [x24] Jul 24 05:05:30 alec.cs.umd.edu setroubleshoot[2461267]: SELinux is preventing /usr/bin/df from getattr access on the file /run/netns/netns-a2b2cc2d-7532-4db7-6a36-b1dd3d5f51db. For complete SELinux messages run: sealert -l 23f93208-3063-4aac-b78a-bb0fcb40740c [x24] == atif01.cs.umd.edu (3 distinct, 5 total) == Jul 24 05:12:25 atif01.cs.umd.edu kernel: net_ratelimit: 9 callbacks suppressed Jul 24 05:12:25 atif01.cs.umd.edu kernel: nfsd: peername failed (err 107)! [x3] Jul 24 05:12:30 atif01.cs.umd.edu kernel: net_ratelimit: 5 callbacks suppressed == csfw00a (1 distinct, 6 total) == Jul 24 05:24:37 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x6] == grades01.cs.umd.edu (1 distinct, 1 total) == Jul 24 05:50:22 grades01.cs.umd.edu puppet-agent[25308]: 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 24 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.O0SDT3”: Permission denied == idm00 (1 distinct, 1 total) == Jul 24 05:51:05 idm00 named[1455]: client @0x7f3304d076b8 10.73.240.42#58225: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Jul 24 05:34:56 idmp0 named[5198]: client @0x7f990400e5f8 10.73.240.43#58416: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 60 total) == Jul 24 05:07:58 itmon02 sshd[1834]: error: beginning MaxStartups throttling [x60] == krispykreme.cs.umd.edu (3 distinct, 4 total) == Jul 24 05:14:56 krispykreme.cs.umd.edu sshd-session[2906441]: pam_access(sshd:auth): access denied for user `admin' from `98.203.110.23' [x2] Jul 24 05:14:57 krispykreme.cs.umd.edu krb5_child[2906443]: Client 'admin@UMD.EDU' not found in Kerberos database Jul 24 05:14:57 krispykreme.cs.umd.edu sshd-session[2906439]: error: PAM: System error for admin from 98.203.110.23 == matrix (11 distinct, 13 total) == Jul 24 05:52:59 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 900370, but reception only permitted for main PID 720 Jul 24 05:52:59 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 900384, but reception only permitted for main PID 720 Jul 24 05:53:07 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 900459, but reception only permitted for main PID 720 Jul 24 05:53:07 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 900465, but reception only permitted for main PID 720 Jul 24 05:53:07 matrix networkctl[900476]: Interface "veth3380a70" not found. Jul 24 05:53:07 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 900476, but reception only permitted for main PID 720 [x2] Jul 24 05:53:07 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 900536, but reception only permitted for main PID 720 Jul 24 05:53:07 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 900544, but reception only permitted for main PID 720 Jul 24 05:53:17 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 900663, but reception only permitted for main PID 720 Jul 24 05:53:17 matrix networkctl[900674]: Interface "veth8971337" not found. Jul 24 05:53:17 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 900674, but reception only permitted for main PID 720 [x2] == netman.cs.umd.edu (1 distinct, 1 total) == Jul 24 05:56:20 netman.cs.umd.edu sshd[394044]: error: PAM: Authentication failure for postgres from 122.160.103.228 == newhonors2 (1 distinct, 24 total) == Jul 24 05:13:03 newhonors2 dhcpcd[205209]: dhcpcd is not running [x24] == outbound00.cs.umd.edu (1 distinct, 6 total) == Jul 24 05:09:08 outbound00.cs.umd.edu python3[3204923]: ldapdb [x6] == outbound01.cs.umd.edu (2 distinct, 8 total) == Jul 24 05:08:22 outbound01.cs.umd.edu python3[1231241]: ldapdb [x7] Jul 24 05:09:27 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 24 05:23:27 sebatinsky.cs.umd.edu setroubleshoot[3188191]: SELinux is preventing /usr/sbin/pdns_server from name_bind access on the udp_socket port 10082. For complete SELinux messages run: sealert -l af222830-ab0f-4bc8-91ab-730551076ae5 == sentry-docker00.cs.umd.edu (40 distinct, 40 total) == Jul 24 05:12:42 sentry-docker00.cs.umd.edu systemd-udevd[2357928]: link_config: could not get ethtool features for veth7ced978 Jul 24 05:12:42 sentry-docker00.cs.umd.edu systemd-udevd[2357928]: Could not set offload features of veth7ced978: No such device Jul 24 05:12:42 sentry-docker00.cs.umd.edu systemd-udevd[2357937]: Could not generate persistent MAC address for vethd51f59f: No such file or directory Jul 24 05:12:42 sentry-docker00.cs.umd.edu systemd-udevd[2357938]: Could not generate persistent MAC address for veth654c016: No such file or directory Jul 24 05:18:59 sentry-docker00.cs.umd.edu systemd-udevd[2361185]: link_config: could not get ethtool features for veth3cac076 Jul 24 05:18:59 sentry-docker00.cs.umd.edu systemd-udevd[2361185]: Could not set offload features of veth3cac076: No such device Jul 24 05:18:59 sentry-docker00.cs.umd.edu systemd-udevd[2361236]: Could not generate persistent MAC address for vethb5414e3: No such file or directory Jul 24 05:18:59 sentry-docker00.cs.umd.edu systemd-udevd[2361237]: Could not generate persistent MAC address for veth34e4573: No such file or directory Jul 24 05:18:59 sentry-docker00.cs.umd.edu systemd-udevd[2361240]: Could not generate persistent MAC address for veth6106b1b: No such file or directory Jul 24 05:18:59 sentry-docker00.cs.umd.edu systemd-udevd[2361241]: Could not generate persistent MAC address for vethf5cfc3c: No such file or directory Jul 24 05:18:59 sentry-docker00.cs.umd.edu systemd-udevd[2361253]: Could not generate persistent MAC address for veth240a3ea: No such file or directory Jul 24 05:18:59 sentry-docker00.cs.umd.edu systemd-udevd[2361254]: Could not generate persistent MAC address for veth63e59d0: No such file or directory Jul 24 05:18:59 sentry-docker00.cs.umd.edu systemd-udevd[2361293]: Could not generate persistent MAC address for veth81df93b: No such file or directory Jul 24 05:18:59 sentry-docker00.cs.umd.edu systemd-udevd[2361305]: Could not generate persistent MAC address for veth6db3735: No such file or directory Jul 24 05:32:46 sentry-docker00.cs.umd.edu systemd-udevd[2367362]: Could not generate persistent MAC address for vethb575850: No such file or directory Jul 24 05:32:46 sentry-docker00.cs.umd.edu systemd-udevd[2367363]: Could not generate persistent MAC address for vethc9fa846: No such file or directory Jul 24 05:39:07 sentry-docker00.cs.umd.edu systemd-udevd[2370580]: link_config: could not get ethtool features for vethb5414e3 Jul 24 05:39:07 sentry-docker00.cs.umd.edu systemd-udevd[2370580]: Could not set offload features of vethb5414e3: No such device Jul 24 05:39:07 sentry-docker00.cs.umd.edu systemd-udevd[2370647]: Could not generate persistent MAC address for vetha318c57: No such file or directory Jul 24 05:39:07 sentry-docker00.cs.umd.edu systemd-udevd[2370648]: Could not generate persistent MAC address for veth21e638b: No such file or directory Jul 24 05:39:07 sentry-docker00.cs.umd.edu systemd-udevd[2370651]: Could not generate persistent MAC address for veth58c506e: No such file or directory Jul 24 05:39:07 sentry-docker00.cs.umd.edu systemd-udevd[2370652]: Could not generate persistent MAC address for veth139d1b9: No such file or directory Jul 24 05:39:07 sentry-docker00.cs.umd.edu systemd-udevd[2370663]: Could not generate persistent MAC address for vethcedd409: No such file or directory Jul 24 05:39:07 sentry-docker00.cs.umd.edu systemd-udevd[2370667]: Could not generate persistent MAC address for veth73a3f4f: No such file or directory Jul 24 05:39:07 sentry-docker00.cs.umd.edu systemd-udevd[2370664]: Could not generate persistent MAC address for veth2fe4ef3: No such file or directory Jul 24 05:39:07 sentry-docker00.cs.umd.edu systemd-udevd[2370667]: Could not generate persistent MAC address for vethf7a4dd2: No such file or directory Jul 24 05:52:55 sentry-docker00.cs.umd.edu systemd-udevd[2376769]: link_config: could not get ethtool features for vethb575850 Jul 24 05:52:55 sentry-docker00.cs.umd.edu systemd-udevd[2376769]: Could not set offload features of vethb575850: No such device Jul 24 05:52:55 sentry-docker00.cs.umd.edu systemd-udevd[2376779]: Could not generate persistent MAC address for vethbc0db9f: No such file or directory Jul 24 05:52:55 sentry-docker00.cs.umd.edu systemd-udevd[2376780]: Could not generate persistent MAC address for veth20cf9d6: No such file or directory ... 10 more distinct messages not shown == strawberry (2 distinct, 8 total) == Jul 24 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 24 05:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-2 (9 distinct, 9 total) == Jul 24 05:12:48 submit26-b9-2 setroubleshoot[86098]: 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 24 05:12:48 submit26-b9-2 setroubleshoot[86098]: 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 24 05:12:48 submit26-b9-2 setroubleshoot[86098]: 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 24 05:12:48 submit26-b9-2 setroubleshoot[86098]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.CngLuh/repodata/repomd.xml. For complete SELinux messages run: sealert -l 1b38f2ec-01ce-4343-8059-ba7494ecc5c4 Jul 24 05:12:48 submit26-b9-2 setroubleshoot[86098]: 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 24 05:12:48 submit26-b9-2 setroubleshoot[86098]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.CngLuh. For complete SELinux messages run: sealert -l 5c54db87-54a3-4a7c-97b4-b5c48d6c3543 Jul 24 05:12:48 submit26-b9-2 setroubleshoot[86098]: 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 24 05:12:48 submit26-b9-2 setroubleshoot[86098]: 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 24 05:12:48 submit26-b9-2 setroubleshoot[86098]: 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 24 05:20:34 submit26-b9-3 setroubleshoot[551585]: 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 24 05:20:34 submit26-b9-3 setroubleshoot[551585]: 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 24 05:20:34 submit26-b9-3 setroubleshoot[551585]: 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 24 05:20:34 submit26-b9-3 setroubleshoot[551585]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.Uk2TaJ/repodata/repomd.xml. For complete SELinux messages run: sealert -l 45a8019e-f6b5-4baa-92c1-862594b40d46 Jul 24 05:20:34 submit26-b9-3 setroubleshoot[551585]: 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 24 05:20:34 submit26-b9-3 setroubleshoot[551585]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.Uk2TaJ. For complete SELinux messages run: sealert -l 0b17cc3d-cdc6-4fe2-a11f-3892e7c41dc7 Jul 24 05:20:34 submit26-b9-3 setroubleshoot[551585]: 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 24 05:20:34 submit26-b9-3 setroubleshoot[551585]: 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 24 05:20:34 submit26-b9-3 setroubleshoot[551585]: 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) == Jul 24 05:31:52 submit26-clnb9 setroubleshoot[1230774]: 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 24 05:31:52 submit26-clnb9 setroubleshoot[1230774]: 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 24 05:31:52 submit26-clnb9 setroubleshoot[1230774]: 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 24 05:31:52 submit26-clnb9 setroubleshoot[1230774]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.pZoYuZ/repodata/repomd.xml. For complete SELinux messages run: sealert -l 001acdb5-31ef-4e52-b10b-90f467a89ddc Jul 24 05:31:52 submit26-clnb9 setroubleshoot[1230774]: 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 24 05:31:52 submit26-clnb9 setroubleshoot[1230774]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.pZoYuZ. For complete SELinux messages run: sealert -l 62b3782e-4730-4488-8178-94dafe9b552c Jul 24 05:31:52 submit26-clnb9 setroubleshoot[1230774]: 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 24 05:31:52 submit26-clnb9 setroubleshoot[1230774]: 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 24 05:31:52 submit26-clnb9 setroubleshoot[1230774]: 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 24 05:18:25 updates00.cs.umd.edu puppet-agent[1586]: 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 24 05:18:25 updates00.cs.umd.edu puppet-agent[1586]: Not using cache on failed catalog Jul 24 05:18:25 updates00.cs.umd.edu puppet-agent[1586]: Could not retrieve catalog; skipping run