Command: /usr/local/sbin/syslog-digest.py Time : 0.0480s Status : exited 0 Output : Syslog digest — 2026-10-01 06:05 EDT Processed 2,158 lines, filtered 1,813 (84%). 345 unknown (175 distinct) from 19 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Oct 1 05:08:09 b0b02.cs.umd.edu rustdesk[3056711]: cannot open display: == grades01.cs.umd.edu (1 distinct, 1 total) == Oct 1 05:48:03 grades01.cs.umd.edu puppet-agent[10568]: 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 == idm00 (1 distinct, 1 total) == Oct 1 05:54:25 idm00 named[4166701]: client @0x7f11a004fb78 10.73.240.42#59593: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Oct 1 05:39:27 idmp0 named[1598691]: client @0x7f2d5002e408 10.73.240.43#60479: update '73.10.in-addr.arpa/IN' denied == irb2156 (2 distinct, 2 total) == Oct 1 05:06:05 irb2156 falcon-sensor-bpf[3902]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225 Oct 1 05:06:05 irb2156 falcon-sensor-bpf[3902]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225 == itmon02 (1 distinct, 2 total) == Oct 1 05:08:54 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x2] == munin (2 distinct, 34 total) == Oct 1 05:08:58 munin sudo[2192432]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x17] Oct 1 05:08:58 munin sudo[2192432]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x17] == neodontcare.cs.umd.edu (1 distinct, 2 total) == Oct 1 06:04:47 neodontcare.cs.umd.edu packagekitd[4155320]: failed to parse public key for /etc/pki/rpm-gpg/RPM-GPG-KEY-PQC-redhat-release [x2] == newhonors2 (1 distinct, 24 total) == Oct 1 05:13:02 newhonors2 dhcpcd[3399535]: dhcpcd is not running [x24] == ntop00 (95 distinct, 95 total) == Oct 1 05:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1090) *** Oct 1 05:05:02 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1090, QN: 49/49, ET: 1) *** Oct 1 05:05:05 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1090, QN: 3527/3527, ET: 4) *** Oct 1 05:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 1091) *** Oct 1 05:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 1091, QN: 3473/3473, ET: 0) *** Oct 1 05:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 1091) *** Oct 1 05:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 1091, QN: 52/52, ET: 0) *** Oct 1 05:10:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1092) *** Oct 1 05:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1092) *** Oct 1 05:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1092, QN: 49/49, ET: 0) *** Oct 1 05:10:05 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1092, QN: 3430/3430, ET: 4) *** Oct 1 05:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 1093) *** Oct 1 05:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 1093, QN: 54/54, ET: 0) *** Oct 1 05:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 1093) *** Oct 1 05:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 1093, QN: 3914/3914, ET: 0) *** Oct 1 05:15:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1094) *** Oct 1 05:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1094) *** Oct 1 05:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1094, QN: 68/68, ET: 0) *** Oct 1 05:15:06 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1094, QN: 4037/4037, ET: 5) *** Oct 1 05:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 1095) *** Oct 1 05:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 1095, QN: 68/68, ET: 0) *** Oct 1 05:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 1095) *** Oct 1 05:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 1095, QN: 3729/3729, ET: 0) *** Oct 1 05:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1096) *** Oct 1 05:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1096, QN: 56/56, ET: 0) *** Oct 1 05:20:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1096) *** Oct 1 05:20:06 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1096, QN: 3508/3508, ET: 5) *** Oct 1 05:23:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 1097) *** Oct 1 05:23:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 1097, QN: 58/58, ET: 0) *** Oct 1 05:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 1097) *** ... 65 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Oct 1 05:09:09 outbound00.cs.umd.edu python3[1507834]: ldapdb [x6] == outbound01.cs.umd.edu (2 distinct, 9 total) == Oct 1 05:08:18 outbound01.cs.umd.edu python3[3771612]: ldapdb [x7] Oct 1 05:09:32 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. [x2] == portal (1 distinct, 71 total) == Oct 1 05:05:28 portal setroubleshoot[3975072]: SELinux is preventing /usr/local/bin/traefik from connectto access on the unix_stream_socket /run/podman/podman.sock. For complete SELinux messages run: sealert -l e0a307a3-2c22-4320-8f9d-6a166c45222d [x71] == sebatinsky.cs.umd.edu (1 distinct, 1 total) == Oct 1 05:15:46 sebatinsky.cs.umd.edu kernel: hpet1: lost 1 rtc interrupts == sentry-docker00.cs.umd.edu (32 distinct, 32 total) == Oct 1 05:23:43 sentry-docker00.cs.umd.edu systemd-udevd[3211098]: link_config: could not get ethtool features for veth28f95e3 Oct 1 05:23:43 sentry-docker00.cs.umd.edu systemd-udevd[3211098]: Could not set offload features of veth28f95e3: No such device Oct 1 05:23:43 sentry-docker00.cs.umd.edu systemd-udevd[3211133]: Could not generate persistent MAC address for veth8d97a8c: No such file or directory Oct 1 05:23:43 sentry-docker00.cs.umd.edu systemd-udevd[3211134]: Could not generate persistent MAC address for vethb92b790: No such file or directory Oct 1 05:23:43 sentry-docker00.cs.umd.edu systemd-udevd[3211137]: Could not generate persistent MAC address for veth2b66bd5: No such file or directory Oct 1 05:23:43 sentry-docker00.cs.umd.edu systemd-udevd[3211138]: Could not generate persistent MAC address for veth209b7f6: No such file or directory Oct 1 05:23:43 sentry-docker00.cs.umd.edu systemd-udevd[3211148]: Could not generate persistent MAC address for veth06136be: No such file or directory Oct 1 05:23:43 sentry-docker00.cs.umd.edu systemd-udevd[3211156]: Could not generate persistent MAC address for veth70262cd: No such file or directory Oct 1 05:23:43 sentry-docker00.cs.umd.edu systemd-udevd[3211148]: Could not generate persistent MAC address for veth8b42dc5: No such file or directory Oct 1 05:23:43 sentry-docker00.cs.umd.edu systemd-udevd[3211139]: Could not generate persistent MAC address for veth7eb27c0: No such file or directory Oct 1 05:23:43 sentry-docker00.cs.umd.edu systemd-udevd[3211188]: Could not generate persistent MAC address for vethb505860: No such file or directory Oct 1 05:23:43 sentry-docker00.cs.umd.edu systemd-udevd[3211190]: Could not generate persistent MAC address for veth95ddd94: No such file or directory Oct 1 05:43:51 sentry-docker00.cs.umd.edu systemd-udevd[3220545]: Could not generate persistent MAC address for veth2174089: No such file or directory Oct 1 05:43:51 sentry-docker00.cs.umd.edu systemd-udevd[3220546]: Could not generate persistent MAC address for vetha47df1f: No such file or directory Oct 1 05:43:51 sentry-docker00.cs.umd.edu systemd-udevd[3220578]: Could not generate persistent MAC address for veth0cd1dea: No such file or directory Oct 1 05:43:51 sentry-docker00.cs.umd.edu systemd-udevd[3220580]: Could not generate persistent MAC address for veth26c33b2: No such file or directory Oct 1 05:43:51 sentry-docker00.cs.umd.edu systemd-udevd[3220614]: Could not generate persistent MAC address for veth04bf505: No such file or directory Oct 1 05:43:51 sentry-docker00.cs.umd.edu systemd-udevd[3220615]: Could not generate persistent MAC address for veth0578336: No such file or directory Oct 1 05:43:51 sentry-docker00.cs.umd.edu systemd-udevd[3220621]: Could not generate persistent MAC address for veth2a8cd80: No such file or directory Oct 1 05:43:51 sentry-docker00.cs.umd.edu systemd-udevd[3220632]: Could not generate persistent MAC address for veth7005ae2: No such file or directory Oct 1 05:43:51 sentry-docker00.cs.umd.edu systemd-udevd[3220641]: Could not generate persistent MAC address for veth62f9dcf: No such file or directory Oct 1 05:43:51 sentry-docker00.cs.umd.edu systemd-udevd[3220623]: Could not generate persistent MAC address for veth54de61f: No such file or directory Oct 1 06:03:59 sentry-docker00.cs.umd.edu systemd-udevd[3230019]: Could not generate persistent MAC address for veth4b68de7: No such file or directory Oct 1 06:03:59 sentry-docker00.cs.umd.edu systemd-udevd[3230020]: Could not generate persistent MAC address for vethdcdce76: No such file or directory Oct 1 06:03:59 sentry-docker00.cs.umd.edu systemd-udevd[3230023]: Could not generate persistent MAC address for vethe6c71cd: No such file or directory Oct 1 06:03:59 sentry-docker00.cs.umd.edu systemd-udevd[3230024]: Could not generate persistent MAC address for veth8cfa64f: No such file or directory Oct 1 06:03:59 sentry-docker00.cs.umd.edu systemd-udevd[3230033]: Could not generate persistent MAC address for veth8252865: No such file or directory Oct 1 06:03:59 sentry-docker00.cs.umd.edu systemd-udevd[3230045]: Could not generate persistent MAC address for vethe1b0171: No such file or directory Oct 1 06:03:59 sentry-docker00.cs.umd.edu systemd-udevd[3230041]: Could not generate persistent MAC address for veth723048e: No such file or directory Oct 1 06:03:59 sentry-docker00.cs.umd.edu systemd-udevd[3230024]: Could not generate persistent MAC address for veth8a75b86: No such file or directory ... 2 more distinct messages not shown == strawberry (7 distinct, 38 total) == Oct 1 05:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Oct 1 05:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Oct 1 05:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Oct 1 05:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Oct 1 05:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Oct 1 05:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Oct 1 05:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f2 (4 distinct, 4 total) == Oct 1 06:00:37 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL Oct 1 06:00:39 submit26-b9-f2 systemd-coredump[3714455]: Process 3714452 (release03) of user 1001 dumped core.#012#012Stack trace of thread 3714452:#012#0 0x00007f9f0f16f37c __strlen_evex (libc.so.6 + 0x16f37c)#012#1 0x000000000040128b right_align (release03 + 0x128b)#012#2 0x00000000004011e5 main (release03 + 0x11e5)#012#3 0x00007f9f0f02a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007f9f0f02a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x0000000000401085 _start (release03 + 0x1085)#012ELF object binary architecture: AMD x86-64 Oct 1 06:00:39 submit26-b9-f2 systemd-coredump[3714483]: Process 3714480 (release13) of user 1001 dumped core.#012#012Stack trace of thread 3714480:#012#0 0x00007f20e2f6f37c __strlen_evex (libc.so.6 + 0x16f37c)#012#1 0x00000000004014c4 compact (release13 + 0x14c4)#012#2 0x00000000004011f1 main (release13 + 0x11f1)#012#3 0x00007f20e2e2a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007f20e2e2a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x0000000000401085 _start (release13 + 0x1085)#012ELF object binary architecture: AMD x86-64 Oct 1 06:00:39 submit26-b9-f2 systemd-coredump[3714493]: Process 3714490 (release15) of user 1001 dumped core.#012#012Stack trace of thread 3714490:#012#0 0x00007f275ff6f37c __strlen_evex (libc.so.6 + 0x16f37c)#012#1 0x00000000004014d1 compact (release15 + 0x14d1)#012#2 0x00000000004011f1 main (release15 + 0x11f1)#012#3 0x00007f275fe2a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007f275fe2a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x0000000000401085 _start (release15 + 0x1085)#012ELF object binary architecture: AMD x86-64 == submit26-b9-f3 (12 distinct, 12 total) == Oct 1 05:06:47 submit26-b9-f3 setroubleshoot[400319]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l a653b772-cbcd-438b-bae5-23c3dc69b31b Oct 1 05:06:47 submit26-b9-f3 setroubleshoot[400319]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 3e904634-6caa-4202-8c92-f139db798859 Oct 1 05:06:47 submit26-b9-f3 setroubleshoot[400319]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 580b20e4-ec2c-433d-905c-5bd417fba033 Oct 1 05:06:47 submit26-b9-f3 setroubleshoot[400319]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.2Uxz98/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Oct 1 05:06:47 submit26-b9-f3 setroubleshoot[400319]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l bff72452-d40a-430b-9060-dd0a48f5b6ba Oct 1 05:06:47 submit26-b9-f3 setroubleshoot[400319]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.2Uxz98. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Oct 1 05:06:47 submit26-b9-f3 setroubleshoot[400319]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 6da64b94-7024-45a9-b8c2-3b9812517407 Oct 1 05:06:47 submit26-b9-f3 setroubleshoot[400319]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 64cbe179-abf1-4d5a-bade-bb164897ee65 Oct 1 05:06:47 submit26-b9-f3 setroubleshoot[400319]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l d2e35b1a-e27c-4f91-9217-2bb1204e1e68 Oct 1 05:59:29 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL Oct 1 05:59:31 submit26-b9-f3 systemd-coredump[402503]: Process 402500 (release03) of user 1001 dumped core.#012#012Stack trace of thread 402500:#012#0 0x00007fbcb6b6677d __strlen_avx2_rtm (libc.so.6 + 0x16677d)#012#1 0x000000000040128b right_align (release03 + 0x128b)#012#2 0x00000000004011e5 main (release03 + 0x11e5)#012#3 0x00007fbcb6a2a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007fbcb6a2a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x0000000000401085 _start (release03 + 0x1085)#012ELF object binary architecture: AMD x86-64 Oct 1 05:59:31 submit26-b9-f3 systemd-coredump[402512]: Process 402508 (release04) of user 1001 dumped core.#012#012Stack trace of thread 402508:#012#0 0x0000000000401340 right_align (release04 + 0x1340)#012#1 0x00000000004011e3 main (release04 + 0x11e3)#012#2 0x00007f2092a2a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007f2092a2a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x0000000000401085 _start (release04 + 0x1085)#012ELF object binary architecture: AMD x86-64 == submit26-b9-f4 (9 distinct, 9 total) == Oct 1 05:24:50 submit26-b9-f4 setroubleshoot[3323396]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l ee160f23-b161-4f4a-9985-c4edfd3a5beb Oct 1 05:24:50 submit26-b9-f4 setroubleshoot[3323396]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 89a83821-4b24-4081-9973-0a79ca6ed5b4 Oct 1 05:24:50 submit26-b9-f4 setroubleshoot[3323396]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l f73955d6-1416-45f9-bab6-ff1f3ea07e9d Oct 1 05:24:50 submit26-b9-f4 setroubleshoot[3323396]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.15pE49/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Oct 1 05:24:50 submit26-b9-f4 setroubleshoot[3323396]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 20293136-86a3-40ba-a651-cff48d36059e Oct 1 05:24:50 submit26-b9-f4 setroubleshoot[3323396]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.15pE49. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Oct 1 05:24:50 submit26-b9-f4 setroubleshoot[3323396]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l eec250fb-073f-456d-93bc-f98776fd476d Oct 1 05:24:50 submit26-b9-f4 setroubleshoot[3323396]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l c9209e04-a349-43d5-8cb2-3e303e48df74 Oct 1 05:24:50 submit26-b9-f4 setroubleshoot[3323396]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 3178d5f5-80e9-404b-92b7-9bef397a8915