Command: /usr/local/sbin/syslog-digest.py Time : 0.0513s Status : exited 0 Output : Syslog digest — 2026-09-23 21:05 EDT Processed 2,423 lines, filtered 2,007 (82%). 416 unknown (184 distinct) from 21 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 23 20:57:31 b0b02.cs.umd.edu rustdesk[357466]: cannot open display: == bale (5 distinct, 90 total) == Sep 23 20:05:46 bale setroubleshoot[2220254]: failed to retrieve rpm info for /dev/nvme0 [x39] Sep 23 20:05:46 bale setroubleshoot[2220254]: SELinux is preventing /usr/libexec/platform-python3.6 from getattr access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l e098d0bd-ac29-4737-9018-de9a71e328ee [x12] Sep 23 20:05:49 bale setroubleshoot[2220254]: SELinux is preventing smartctl from read access on the chr_file nvme0. For complete SELinux messages run: sealert -l fc305ce6-663c-4aa2-8640-0ee0f8dce1a9 [x12] Sep 23 20:05:52 bale setroubleshoot[2220254]: SELinux is preventing smartctl from open access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l 2c1d6b29-3343-488c-84c7-92d46f8010b6 [x12] Sep 23 20:06:04 bale setroubleshoot[2220869]: SELinux is preventing /usr/sbin/smartctl from ioctl access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l 8ea740c2-97d8-42fb-b550-a236b114507d [x15] == cheezit.cs.umd.edu (2 distinct, 6 total) == Sep 23 20:15:31 cheezit.cs.umd.edu sshd-session[2445993]: error: send_error: write: Connection reset by peer [x4] Sep 23 20:25:41 cheezit.cs.umd.edu sshd-session[2448702]: pam_access(sshd:auth): access denied for user `anwar' from `71.241.227.222' [x2] == galax (2 distinct, 2 total) == Sep 23 20:07:03 galax kernel: workqueue: dm_irq_work_func [amdgpu] hogged CPU for >10000us 131 times, consider switching to WQ_UNBOUND Sep 23 20:30:08 galax kernel: workqueue: dm_irq_work_func [amdgpu] hogged CPU for >10000us 259 times, consider switching to WQ_UNBOUND == gle-dind04 (1 distinct, 1 total) == Sep 23 20:37:47 gle-dind04 falcon-sensor-bpf[1017]: CrowdStrike(4): SSLSocket Disconnected from Cloud. == idm00 (1 distinct, 1 total) == Sep 23 20:54:05 idm00 named[4166701]: client @0x7f1198099188 10.73.240.42#57989: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 23 20:39:31 idmp0 named[1598691]: client @0x7f2d2c0368e8 10.73.240.43#60769: update '73.10.in-addr.arpa/IN' denied == inbound01.cs.umd.edu (1 distinct, 1 total) == Sep 23 20:10:08 inbound01.cs.umd.edu krb5_child[1356890]: Client 'admin@UMD.EDU' not found in Kerberos database == itmon02 (1 distinct, 5 total) == Sep 23 20:23:29 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x5] == munin (2 distinct, 18 total) == Sep 23 20:08:09 munin sudo[2529181]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x9] Sep 23 20:08:09 munin sudo[2529181]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x9] == newhonors2 (1 distinct, 24 total) == Sep 23 20:13:03 newhonors2 dhcpcd[3056214]: dhcpcd is not running [x24] == ntop00 (102 distinct, 142 total) == Sep 23 20:05:01 ntop00 nfacctd[9659]: INFO ( m1/mysql ): *** Purging cache - START (PID: 182) *** Sep 23 20:06:44 ntop00 sfacctd[9573]: INFO ( m1/mysql ): *** Purging cache - END (PID: 182, QN: 6387/6387, ET: 103) *** Sep 23 20:06:46 ntop00 nfacctd[9659]: INFO ( m1/mysql ): *** Purging cache - END (PID: 182, QN: 53/53, ET: 105) *** Sep 23 20:08:01 ntop00 sfacctd[9573]: INFO ( p1/print ): *** Purging cache - START (PID: 183) *** Sep 23 20:08:01 ntop00 sfacctd[9573]: INFO ( p1/print ): *** Purging cache - END (PID: 183, QN: 6685/6685, ET: 0) *** Sep 23 20:08:01 ntop00 nfacctd[9659]: INFO ( p1/print ): *** Purging cache - START (PID: 183) *** Sep 23 20:08:01 ntop00 nfacctd[9659]: INFO ( p1/print ): *** Purging cache - END (PID: 183, QN: 60/60, ET: 0) *** Sep 23 20:08:02 ntop00 setroubleshoot[75918]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l 5b65c96c-a9fa-4175-8126-0641b1ec385c [x11] Sep 23 20:08:02 ntop00 setroubleshoot[75918]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 0d1f7214-3aae-48d5-8fed-48565bd90d17 [x11] Sep 23 20:08:02 ntop00 setroubleshoot[75918]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x11] Sep 23 20:08:02 ntop00 setroubleshoot[75918]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l 4a9c8c49-4f0d-4ad5-b926-84fe3642d3ee [x11] Sep 23 20:10:01 ntop00 sfacctd[9573]: INFO ( m1/mysql ): *** Purging cache - START (PID: 184) *** Sep 23 20:10:01 ntop00 nfacctd[9659]: INFO ( m1/mysql ): *** Purging cache - START (PID: 184) *** Sep 23 20:13:01 ntop00 sfacctd[9573]: INFO ( p1/print ): *** Purging cache - START (PID: 185) *** Sep 23 20:13:01 ntop00 sfacctd[9573]: INFO ( p1/print ): *** Purging cache - END (PID: 185, QN: 6639/6639, ET: 0) *** Sep 23 20:13:01 ntop00 nfacctd[9659]: INFO ( p1/print ): *** Purging cache - START (PID: 185) *** Sep 23 20:13:01 ntop00 nfacctd[9659]: INFO ( p1/print ): *** Purging cache - END (PID: 185, QN: 43/43, ET: 0) *** Sep 23 20:13:09 ntop00 sfacctd[9573]: INFO ( m1/mysql ): *** Purging cache - END (PID: 184, QN: 6803/6803, ET: 188) *** Sep 23 20:13:10 ntop00 nfacctd[9659]: INFO ( m1/mysql ): *** Purging cache - END (PID: 184, QN: 46/46, ET: 189) *** Sep 23 20:15:01 ntop00 sfacctd[9573]: INFO ( m1/mysql ): *** Purging cache - START (PID: 186) *** Sep 23 20:15:01 ntop00 nfacctd[9659]: INFO ( m1/mysql ): *** Purging cache - START (PID: 186) *** Sep 23 20:17:10 ntop00 sfacctd[9573]: INFO ( m1/mysql ): *** Purging cache - END (PID: 186, QN: 5998/5998, ET: 129) *** Sep 23 20:17:10 ntop00 nfacctd[9659]: INFO ( m1/mysql ): *** Purging cache - END (PID: 186, QN: 52/52, ET: 129) *** Sep 23 20:18:01 ntop00 sfacctd[9573]: INFO ( p1/print ): *** Purging cache - START (PID: 187) *** Sep 23 20:18:01 ntop00 sfacctd[9573]: INFO ( p1/print ): *** Purging cache - END (PID: 187, QN: 6367/6367, ET: 0) *** Sep 23 20:18:01 ntop00 nfacctd[9659]: INFO ( p1/print ): *** Purging cache - START (PID: 187) *** Sep 23 20:18:01 ntop00 nfacctd[9659]: INFO ( p1/print ): *** Purging cache - END (PID: 187, QN: 49/49, ET: 0) *** Sep 23 20:20:01 ntop00 sfacctd[9573]: INFO ( m1/mysql ): *** Purging cache - START (PID: 188) *** Sep 23 20:20:01 ntop00 nfacctd[9659]: INFO ( m1/mysql ): *** Purging cache - START (PID: 188) *** Sep 23 20:21:34 ntop00 sfacctd[9573]: INFO ( m1/mysql ): *** Purging cache - END (PID: 188, QN: 7068/7068, ET: 93) *** ... 72 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 23 20:09:09 outbound00.cs.umd.edu python3[3194091]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 23 20:13:06 outbound01.cs.umd.edu python3[1260139]: ldapdb [x6] == sentry-docker00.cs.umd.edu (38 distinct, 38 total) == Sep 23 20:10:17 sentry-docker00.cs.umd.edu systemd-udevd[2392632]: link_config: could not get ethtool features for veth98e8871 Sep 23 20:10:17 sentry-docker00.cs.umd.edu systemd-udevd[2392632]: Could not set offload features of veth98e8871: No such device Sep 23 20:10:17 sentry-docker00.cs.umd.edu systemd-udevd[2392635]: link_config: could not get ethtool features for veth61ba222 Sep 23 20:10:17 sentry-docker00.cs.umd.edu systemd-udevd[2392635]: Could not set offload features of veth61ba222: No such device Sep 23 20:10:18 sentry-docker00.cs.umd.edu systemd-udevd[2392665]: Could not generate persistent MAC address for veth5e1c649: No such file or directory Sep 23 20:10:18 sentry-docker00.cs.umd.edu systemd-udevd[2392666]: Could not generate persistent MAC address for veth8d46c22: No such file or directory Sep 23 20:10:18 sentry-docker00.cs.umd.edu systemd-udevd[2392669]: Could not generate persistent MAC address for veth8d40bac: No such file or directory Sep 23 20:10:18 sentry-docker00.cs.umd.edu systemd-udevd[2392670]: Could not generate persistent MAC address for vethb675beb: No such file or directory Sep 23 20:10:18 sentry-docker00.cs.umd.edu systemd-udevd[2392669]: Could not generate persistent MAC address for vethd5d6057: No such file or directory Sep 23 20:10:18 sentry-docker00.cs.umd.edu systemd-udevd[2392683]: Could not generate persistent MAC address for veth4b36302: No such file or directory Sep 23 20:10:18 sentry-docker00.cs.umd.edu systemd-udevd[2392666]: Could not generate persistent MAC address for veth1e89c75: No such file or directory Sep 23 20:10:18 sentry-docker00.cs.umd.edu systemd-udevd[2392669]: Could not generate persistent MAC address for veth2b11513: No such file or directory Sep 23 20:10:18 sentry-docker00.cs.umd.edu systemd-udevd[2392753]: Could not generate persistent MAC address for vethe7b06de: No such file or directory Sep 23 20:10:18 sentry-docker00.cs.umd.edu systemd-udevd[2392752]: Could not generate persistent MAC address for veth0d398c3: No such file or directory Sep 23 20:30:26 sentry-docker00.cs.umd.edu systemd-udevd[2402065]: link_config: could not get ethtool features for veth2b11513 Sep 23 20:30:26 sentry-docker00.cs.umd.edu systemd-udevd[2402065]: Could not set offload features of veth2b11513: No such device Sep 23 20:30:26 sentry-docker00.cs.umd.edu systemd-udevd[2402100]: Could not generate persistent MAC address for veth6a2b237: No such file or directory Sep 23 20:30:26 sentry-docker00.cs.umd.edu systemd-udevd[2402101]: Could not generate persistent MAC address for veth90ea233: No such file or directory Sep 23 20:30:26 sentry-docker00.cs.umd.edu systemd-udevd[2402104]: Could not generate persistent MAC address for vethbe2c5c9: No such file or directory Sep 23 20:30:26 sentry-docker00.cs.umd.edu systemd-udevd[2402117]: Could not generate persistent MAC address for veth39cc616: No such file or directory Sep 23 20:30:26 sentry-docker00.cs.umd.edu systemd-udevd[2402128]: Could not generate persistent MAC address for veth705d935: No such file or directory Sep 23 20:30:26 sentry-docker00.cs.umd.edu systemd-udevd[2402129]: Could not generate persistent MAC address for vethfcdf06f: No such file or directory Sep 23 20:30:26 sentry-docker00.cs.umd.edu systemd-udevd[2402147]: Could not generate persistent MAC address for vethed14bbc: No such file or directory Sep 23 20:30:26 sentry-docker00.cs.umd.edu systemd-udevd[2402128]: Could not generate persistent MAC address for veth0968f82: No such file or directory Sep 23 20:30:26 sentry-docker00.cs.umd.edu systemd-udevd[2402229]: Could not generate persistent MAC address for veth48111b4: No such file or directory Sep 23 20:30:26 sentry-docker00.cs.umd.edu systemd-udevd[2402239]: Could not generate persistent MAC address for vethed35e97: No such file or directory Sep 23 20:50:34 sentry-docker00.cs.umd.edu systemd-udevd[2411759]: link_config: could not get ethtool features for veth48111b4 Sep 23 20:50:34 sentry-docker00.cs.umd.edu systemd-udevd[2411759]: Could not set offload features of veth48111b4: No such device Sep 23 20:50:34 sentry-docker00.cs.umd.edu systemd-udevd[2411879]: Could not generate persistent MAC address for veth86bdf2e: No such file or directory Sep 23 20:50:34 sentry-docker00.cs.umd.edu systemd-udevd[2411880]: Could not generate persistent MAC address for veth3afe65e: No such file or directory ... 8 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 23 20:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 23 20:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 23 20:07:04 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 23 20:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 23 20:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 23 20:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 23 20:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (1 distinct, 7 total) == Sep 23 20:09:13 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x7] == submit26-b9-f2 (1 distinct, 5 total) == Sep 23 20:13:07 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x5] == submit26-b9-f3 (5 distinct, 9 total) == Sep 23 20:15:05 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x5] Sep 23 20:20:08 submit26-b9-f3 systemd-coredump[2857389]: Process 2857386 (grades) of user 1001 dumped core.#012#012Stack trace of thread 2857386:#012#0 0x00007f0f4d68d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007f0f4d63fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007f0f4d629873 abort (libc.so.6 + 0x29873)#012#3 0x00007f0f4d62a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007f0f4d71d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007f0f4d71e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x00000000004018fe main (grades + 0x18fe)#012#7 0x0000000000000002 n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64 Sep 23 20:20:08 submit26-b9-f3 systemd-coredump[2857400]: Process 2857396 (grades) of user 1001 dumped core.#012#012Stack trace of thread 2857396:#012#0 0x00007f6af628d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007f6af623fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007f6af6229873 abort (libc.so.6 + 0x29873)#012#3 0x00007f6af622a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007f6af631d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007f6af631e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x00000000004018fe main (grades + 0x18fe)#012#7 0x0000000000000002 n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64 Sep 23 20:23:38 submit26-b9-f3 systemd-coredump[2858637]: Process 2858634 (grades) of user 1001 dumped core.#012#012Stack trace of thread 2858634:#012#0 0x00007f5f60e8d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007f5f60e3fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007f5f60e29873 abort (libc.so.6 + 0x29873)#012#3 0x00007f5f60e2a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007f5f60f1d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007f5f60f1e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x0000000000401908 main (grades + 0x1908)#012#7 0x0000000000000002 n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64 Sep 23 20:23:38 submit26-b9-f3 systemd-coredump[2858647]: Process 2858644 (grades) of user 1001 dumped core.#012#012Stack trace of thread 2858644:#012#0 0x00007fdfe868d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007fdfe863fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007fdfe8629873 abort (libc.so.6 + 0x29873)#012#3 0x00007fdfe862a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007fdfe871d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007fdfe871e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x0000000000401908 main (grades + 0x1908)#012#7 0x0000000000000002 n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64 == submit26-b9-f4 (1 distinct, 6 total) == Sep 23 20:17:45 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x6] == submit26-b9-fclone (9 distinct, 9 total) == Sep 23 20:22:00 submit26-b9-fclone setroubleshoot[372964]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 9355d9d9-a311-48d2-bd37-6c0f6947dfff Sep 23 20:22:00 submit26-b9-fclone setroubleshoot[372964]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l cc4658d7-9db1-405d-9eee-de0ccee5857f Sep 23 20:22:00 submit26-b9-fclone setroubleshoot[372964]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 568a2429-0b1b-49df-af41-49b5cd298ae8 Sep 23 20:22:00 submit26-b9-fclone setroubleshoot[372964]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.xoVQTz/repodata/repomd.xml. For complete SELinux messages run: sealert -l 03e2f521-0e7c-481f-8e92-0602c6adeedc Sep 23 20:22:00 submit26-b9-fclone setroubleshoot[372964]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 0d6b7b1f-ebe3-4beb-915a-b06b63bf2566 Sep 23 20:22:00 submit26-b9-fclone setroubleshoot[372964]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.xoVQTz. For complete SELinux messages run: sealert -l 887adbf9-2bb9-4009-b800-36ddf9ba0db5 Sep 23 20:22:00 submit26-b9-fclone setroubleshoot[372964]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 092e0644-8373-4017-b77f-1afa6c6da4ac Sep 23 20:22:00 submit26-b9-fclone setroubleshoot[372964]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l ce429a92-56de-4de1-b859-cbfb69ae123c Sep 23 20:22:00 submit26-b9-fclone setroubleshoot[372964]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 99b886eb-497b-406d-8206-afe76a1086b4