Command: /usr/local/sbin/syslog-digest.py Time : 0.0465s Status : exited 0 Output : Syslog digest — 2026-10-02 22:05 EDT Processed 1,627 lines, filtered 1,274 (78%). 353 unknown (174 distinct) from 17 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Oct 2 21:10:45 b0b02.cs.umd.edu rustdesk[3733233]: cannot open display: == idm00 (1 distinct, 1 total) == Oct 2 21:54:36 idm00 named[4166701]: client @0x7f11a8c67778 10.73.240.42#51286: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Oct 2 21:39:24 idmp0 named[1598691]: client @0x7f2d14036638 10.73.240.43#64324: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 2 total) == Oct 2 21:53:05 itmon02 sshd[805675]: error: beginning MaxStartups throttling [x2] == munin (2 distinct, 34 total) == Oct 2 21:23:53 munin sudo[3067607]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x17] Oct 2 21:23:53 munin sudo[3067607]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x17] == netman.cs.umd.edu (1 distinct, 2 total) == Oct 2 21:29:18 netman.cs.umd.edu krb5_child[3705278]: Client 'admin@UMD.EDU' not found in Kerberos database [x2] == newhonors2 (1 distinct, 24 total) == Oct 2 21:13:03 newhonors2 dhcpcd[3474988]: dhcpcd is not running [x24] == ntop00 (96 distinct, 96 total) == Oct 2 21:05:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2050) *** Oct 2 21:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2050) *** Oct 2 21:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2050, QN: 51/51, ET: 0) *** Oct 2 21:05:08 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2050, QN: 5468/5468, ET: 7) *** Oct 2 21:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 2051) *** Oct 2 21:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 2051) *** Oct 2 21:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 2051, QN: 55/55, ET: 0) *** Oct 2 21:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 2051, QN: 6475/6475, ET: 0) *** Oct 2 21:10:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2052) *** Oct 2 21:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2052) *** Oct 2 21:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2052, QN: 53/53, ET: 0) *** Oct 2 21:10:10 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2052, QN: 6981/6981, ET: 9) *** Oct 2 21:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 2053) *** Oct 2 21:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 2053, QN: 6542/6542, ET: 0) *** Oct 2 21:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 2053) *** Oct 2 21:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 2053, QN: 59/59, ET: 0) *** Oct 2 21:15:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2054) *** Oct 2 21:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2054) *** Oct 2 21:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2054, QN: 61/61, ET: 0) *** Oct 2 21:15:10 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2054, QN: 6090/6090, ET: 9) *** Oct 2 21:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 2055) *** Oct 2 21:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 2055, QN: 5654/5654, ET: 0) *** Oct 2 21:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 2055) *** Oct 2 21:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 2055, QN: 56/56, ET: 0) *** Oct 2 21:20:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2056) *** Oct 2 21:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2056) *** Oct 2 21:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2056, QN: 60/60, ET: 0) *** Oct 2 21:20:11 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2056, QN: 6549/6549, ET: 10) *** Oct 2 21:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 2057) *** Oct 2 21:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 2057, QN: 6730/6730, ET: 0) *** ... 66 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Oct 2 21:09:09 outbound00.cs.umd.edu python3[2100597]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Oct 2 21:13:06 outbound01.cs.umd.edu python3[172402]: ldapdb [x6] == portal (1 distinct, 70 total) == Oct 2 21:05:50 portal setroubleshoot[313279]: 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 [x70] == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Oct 2 21:20:21 sentry-docker00.cs.umd.edu systemd-udevd[146711]: link_config: could not get ethtool features for veth576d0d2 Oct 2 21:20:21 sentry-docker00.cs.umd.edu systemd-udevd[146711]: Could not set offload features of veth576d0d2: No such device Oct 2 21:20:21 sentry-docker00.cs.umd.edu systemd-udevd[146742]: Could not generate persistent MAC address for veth9f79d01: No such file or directory Oct 2 21:20:21 sentry-docker00.cs.umd.edu systemd-udevd[146743]: Could not generate persistent MAC address for veth1a03128: No such file or directory Oct 2 21:20:21 sentry-docker00.cs.umd.edu systemd-udevd[146746]: Could not generate persistent MAC address for veth9e9f763: No such file or directory Oct 2 21:20:21 sentry-docker00.cs.umd.edu systemd-udevd[146747]: Could not generate persistent MAC address for veth0c16791: No such file or directory Oct 2 21:20:21 sentry-docker00.cs.umd.edu systemd-udevd[146770]: Could not generate persistent MAC address for veth3ff36dc: No such file or directory Oct 2 21:20:21 sentry-docker00.cs.umd.edu systemd-udevd[146771]: Could not generate persistent MAC address for veth4df5fa4: No such file or directory Oct 2 21:20:21 sentry-docker00.cs.umd.edu systemd-udevd[146771]: Could not generate persistent MAC address for vethad9020c: No such file or directory Oct 2 21:20:21 sentry-docker00.cs.umd.edu systemd-udevd[146789]: Could not generate persistent MAC address for vethd84d96e: No such file or directory Oct 2 21:20:21 sentry-docker00.cs.umd.edu systemd-udevd[146834]: Could not generate persistent MAC address for vethdf209ad: No such file or directory Oct 2 21:20:21 sentry-docker00.cs.umd.edu systemd-udevd[146835]: Could not generate persistent MAC address for veth38ffefc: No such file or directory Oct 2 21:40:29 sentry-docker00.cs.umd.edu systemd-udevd[156094]: Could not generate persistent MAC address for veth02368dd: No such file or directory Oct 2 21:40:29 sentry-docker00.cs.umd.edu systemd-udevd[156095]: Could not generate persistent MAC address for vethe799245: No such file or directory Oct 2 21:40:29 sentry-docker00.cs.umd.edu systemd-udevd[156113]: Could not generate persistent MAC address for veth987899e: No such file or directory Oct 2 21:40:29 sentry-docker00.cs.umd.edu systemd-udevd[156114]: Could not generate persistent MAC address for veth5af935d: No such file or directory Oct 2 21:40:29 sentry-docker00.cs.umd.edu systemd-udevd[156104]: Could not generate persistent MAC address for veth7e784d2: No such file or directory Oct 2 21:40:29 sentry-docker00.cs.umd.edu systemd-udevd[156120]: Could not generate persistent MAC address for veth50b7031: No such file or directory Oct 2 21:40:29 sentry-docker00.cs.umd.edu systemd-udevd[156095]: Could not generate persistent MAC address for vethcd11a0f: No such file or directory Oct 2 21:40:29 sentry-docker00.cs.umd.edu systemd-udevd[156119]: Could not generate persistent MAC address for vethd99a48f: No such file or directory Oct 2 21:40:29 sentry-docker00.cs.umd.edu systemd-udevd[156119]: Could not generate persistent MAC address for veth52883ea: No such file or directory Oct 2 21:40:29 sentry-docker00.cs.umd.edu systemd-udevd[156104]: Could not generate persistent MAC address for vetha2f3315: No such file or directory Oct 2 22:00:37 sentry-docker00.cs.umd.edu systemd-udevd[165663]: link_config: could not get ethtool features for veth987899e Oct 2 22:00:37 sentry-docker00.cs.umd.edu systemd-udevd[165663]: Could not set offload features of veth987899e: No such device Oct 2 22:00:38 sentry-docker00.cs.umd.edu systemd-udevd[165677]: link_config: could not set ethtool features for veth02368dd Oct 2 22:00:38 sentry-docker00.cs.umd.edu systemd-udevd[165677]: Could not set offload features of veth02368dd: Operation not permitted Oct 2 22:00:38 sentry-docker00.cs.umd.edu systemd-udevd[165709]: Could not generate persistent MAC address for vethca1a316: No such file or directory Oct 2 22:00:38 sentry-docker00.cs.umd.edu systemd-udevd[165710]: Could not generate persistent MAC address for veth573dc5e: No such file or directory Oct 2 22:00:38 sentry-docker00.cs.umd.edu systemd-udevd[165713]: Could not generate persistent MAC address for veth84cbc08: No such file or directory Oct 2 22:00:38 sentry-docker00.cs.umd.edu systemd-udevd[165714]: Could not generate persistent MAC address for vethf3126e8: No such file or directory ... 6 more distinct messages not shown == strawberry (7 distinct, 38 total) == Oct 2 21:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Oct 2 21:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Oct 2 21:07:04 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Oct 2 21:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Oct 2 21:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Oct 2 21:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Oct 2 21:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (1 distinct, 1 total) == Oct 2 22:00:07 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-f2 (1 distinct, 1 total) == Oct 2 22:00:07 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-f3 (10 distinct, 19 total) == Oct 2 21:06:47 submit26-b9-f3 setroubleshoot[615756]: 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 2 21:06:47 submit26-b9-f3 setroubleshoot[615756]: 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 2 21:06:47 submit26-b9-f3 setroubleshoot[615756]: 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 [x2] Oct 2 21:06:47 submit26-b9-f3 setroubleshoot[615756]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.1CmYNj/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f [x2] Oct 2 21:06:47 submit26-b9-f3 setroubleshoot[615756]: 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 [x2] Oct 2 21:06:47 submit26-b9-f3 setroubleshoot[615756]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.1CmYNj. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Oct 2 21:06:47 submit26-b9-f3 setroubleshoot[615756]: 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 2 21:06:47 submit26-b9-f3 setroubleshoot[615756]: 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 2 21:06:47 submit26-b9-f3 setroubleshoot[615756]: 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 2 21:13:07 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x7] == submit26-b9-f4 (12 distinct, 15 total) == Oct 2 21:15:07 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x4] Oct 2 21:24:50 submit26-b9-f4 setroubleshoot[3481800]: 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 2 21:24:50 submit26-b9-f4 setroubleshoot[3481800]: 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 2 21:24:51 submit26-b9-f4 setroubleshoot[3481800]: 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 2 21:24:51 submit26-b9-f4 setroubleshoot[3481800]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.IBtlef/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Oct 2 21:24:51 submit26-b9-f4 setroubleshoot[3481800]: 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 2 21:24:51 submit26-b9-f4 setroubleshoot[3481800]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.IBtlef. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Oct 2 21:24:51 submit26-b9-f4 setroubleshoot[3481800]: 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 2 21:24:51 submit26-b9-f4 setroubleshoot[3481800]: 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 2 21:24:51 submit26-b9-f4 setroubleshoot[3481800]: 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 Oct 2 22:04:07 submit26-b9-f4 systemd-coredump[3488159]: Process 3488156 (release13) of user 1001 dumped core.#012#012Stack trace of thread 3488156:#012#0 0x00007febeecae0ea __strlen_sse2 (libc.so.6 + 0xae0ea)#012#1 0x00000000004013b0 compact (release13 + 0x13b0)#012#2 0x00000000004011f1 main (release13 + 0x11f1)#012#3 0x00007febeec2a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007febeec2a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x0000000000401085 _start (release13 + 0x1085)#012ELF object binary architecture: AMD x86-64 Oct 2 22:04:07 submit26-b9-f4 systemd-coredump[3488187]: Process 3488180 (release15) of user 1001 dumped core.#012#012Stack trace of thread 3488180:#012#0 0x00007f42c88ae0ea __strlen_sse2 (libc.so.6 + 0xae0ea)#012#1 0x00000000004013bd compact (release15 + 0x13bd)#012#2 0x00000000004011f1 main (release15 + 0x11f1)#012#3 0x00007f42c882a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007f42c882a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x0000000000401085 _start (release15 + 0x1085)#012ELF object binary architecture: AMD x86-64