Command: /usr/local/sbin/syslog-digest.py Time : 0.0540s Status : exited 0 Output : Syslog digest — 2026-09-19 16:05 EDT Processed 2,861 lines, filtered 2,367 (82%). 494 unknown (163 distinct) from 17 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 19 15:51:07 b0b02.cs.umd.edu rustdesk[2938419]: cannot open display: == bale (5 distinct, 86 total) == Sep 19 15:05:20 bale setroubleshoot[896120]: failed to retrieve rpm info for /dev/nvme0 [x36] Sep 19 15:05:21 bale setroubleshoot[896120]: 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 [x13] Sep 19 15:05:23 bale setroubleshoot[896120]: SELinux is preventing smartctl from read access on the chr_file nvme0. For complete SELinux messages run: sealert -l fc305ce6-663c-4aa2-8640-0ee0f8dce1a9 [x14] Sep 19 15:05:27 bale setroubleshoot[896120]: 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 [x10] Sep 19 15:05:38 bale setroubleshoot[896749]: 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 [x13] == csfw00a (1 distinct, 134 total) == Sep 19 15:03:53 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x134] == idm00 (1 distinct, 1 total) == Sep 19 15:53:59 idm00 named[4166701]: client @0x7f1198074538 10.73.240.42#62912: update '73.10.in-addr.arpa/IN' denied == idmp0 (2 distinct, 2 total) == Sep 19 15:37:56 idmp0 named[1598691]: client @0x7f2d2402e528 10.73.240.43#53313: update '73.10.in-addr.arpa/IN' denied Sep 19 15:52:52 idmp0 named[1598691]: client @0x7f2d34053c48 10.73.245.12#55061: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 2 total) == Sep 19 15:08:22 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x2] == munin (2 distinct, 6 total) == Sep 19 15:08:37 munin sudo[333851]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x3] Sep 19 15:08:37 munin sudo[333851]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x3] == newhonors2 (1 distinct, 24 total) == Sep 19 15:13:03 newhonors2 dhcpcd[2863993]: dhcpcd is not running [x24] == ntop00 (99 distinct, 143 total) == Sep 19 15:05:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 178) *** Sep 19 15:05:30 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 178, QN: 8954/8954, ET: 29) *** Sep 19 15:05:30 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 178, QN: 53/53, ET: 29) *** Sep 19 15:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 179) *** Sep 19 15:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 179, QN: 8888/8888, ET: 0) *** Sep 19 15:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 179) *** Sep 19 15:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 179, QN: 51/51, ET: 0) *** Sep 19 15:08:02 ntop00 setroubleshoot[658796]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l 977904f2-b1d5-479f-af5f-8f979ecc6b5a [x12] Sep 19 15:08:02 ntop00 setroubleshoot[658796]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 7ff4701c-77ae-4c43-938b-2b711cad9847 [x12] Sep 19 15:08:02 ntop00 setroubleshoot[658796]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12] Sep 19 15:08:02 ntop00 setroubleshoot[658796]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l c2ce2f7a-3ea8-46d2-8a8a-6e46548752ef [x12] Sep 19 15:10:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 180) *** Sep 19 15:10:02 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 180) *** Sep 19 15:10:31 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 180, QN: 8865/8865, ET: 30) *** Sep 19 15:10:32 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 180, QN: 49/49, ET: 30) *** Sep 19 15:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 181) *** Sep 19 15:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 181) *** Sep 19 15:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 181, QN: 46/46, ET: 0) *** Sep 19 15:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 181, QN: 8672/8672, ET: 0) *** Sep 19 15:15:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 182) *** Sep 19 15:15:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 182) *** Sep 19 15:15:32 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 182, QN: 9107/9107, ET: 31) *** Sep 19 15:15:32 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 182, QN: 44/44, ET: 31) *** Sep 19 15:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 183) *** Sep 19 15:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 183, QN: 9899/9899, ET: 0) *** Sep 19 15:18:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 183) *** Sep 19 15:18:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 183, QN: 57/57, ET: 0) *** Sep 19 15:20:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 184) *** Sep 19 15:20:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 184) *** Sep 19 15:20:36 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 184, QN: 9988/9988, ET: 35) *** ... 69 more distinct messages not shown == outbound00.cs.umd.edu (2 distinct, 7 total) == Sep 19 15:09:09 outbound00.cs.umd.edu python3[1736726]: ldapdb [x6] Sep 19 15:34:44 outbound00.cs.umd.edu krb5_child[1742686]: Preauthentication failed == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 19 15:13:06 outbound01.cs.umd.edu python3[3995431]: ldapdb [x6] == sentry-docker00.cs.umd.edu (34 distinct, 34 total) == Sep 19 15:08:33 sentry-docker00.cs.umd.edu systemd-udevd[3711058]: Could not generate persistent MAC address for veth42ff2ea: No such file or directory Sep 19 15:08:33 sentry-docker00.cs.umd.edu systemd-udevd[3711059]: Could not generate persistent MAC address for veth1b8a79e: No such file or directory Sep 19 15:08:33 sentry-docker00.cs.umd.edu systemd-udevd[3711062]: Could not generate persistent MAC address for veth1a4de93: No such file or directory Sep 19 15:08:33 sentry-docker00.cs.umd.edu systemd-udevd[3711080]: Could not generate persistent MAC address for vethe8f8853: No such file or directory Sep 19 15:08:33 sentry-docker00.cs.umd.edu systemd-udevd[3711078]: Could not generate persistent MAC address for veth1baac28: No such file or directory Sep 19 15:08:33 sentry-docker00.cs.umd.edu systemd-udevd[3711081]: Could not generate persistent MAC address for vethcd6db72: No such file or directory Sep 19 15:08:33 sentry-docker00.cs.umd.edu systemd-udevd[3711058]: Could not generate persistent MAC address for veth9a85fcf: No such file or directory Sep 19 15:08:33 sentry-docker00.cs.umd.edu systemd-udevd[3711065]: Could not generate persistent MAC address for veth1df5ba6: No such file or directory Sep 19 15:08:33 sentry-docker00.cs.umd.edu systemd-udevd[3711121]: Could not generate persistent MAC address for veth02a898b: No such file or directory Sep 19 15:08:33 sentry-docker00.cs.umd.edu systemd-udevd[3711126]: Could not generate persistent MAC address for veth8594bb0: No such file or directory Sep 19 15:28:41 sentry-docker00.cs.umd.edu systemd-udevd[3720443]: link_config: could not set ethtool features for veth1df5ba6 Sep 19 15:28:41 sentry-docker00.cs.umd.edu systemd-udevd[3720443]: Could not set offload features of veth1df5ba6: Operation not permitted Sep 19 15:28:42 sentry-docker00.cs.umd.edu systemd-udevd[3720467]: Could not generate persistent MAC address for vethf8e747a: No such file or directory Sep 19 15:28:42 sentry-docker00.cs.umd.edu systemd-udevd[3720468]: Could not generate persistent MAC address for veth53b2dfd: No such file or directory Sep 19 15:28:42 sentry-docker00.cs.umd.edu systemd-udevd[3720486]: Could not generate persistent MAC address for veth7fdc3bf: No such file or directory Sep 19 15:28:42 sentry-docker00.cs.umd.edu systemd-udevd[3720472]: Could not generate persistent MAC address for veth0f7e5c3: No such file or directory Sep 19 15:28:42 sentry-docker00.cs.umd.edu systemd-udevd[3720471]: Could not generate persistent MAC address for veth107e4e9: No such file or directory Sep 19 15:28:42 sentry-docker00.cs.umd.edu systemd-udevd[3720473]: Could not generate persistent MAC address for veth0044d51: No such file or directory Sep 19 15:28:42 sentry-docker00.cs.umd.edu systemd-udevd[3720497]: Could not generate persistent MAC address for veth6f01cc8: No such file or directory Sep 19 15:28:42 sentry-docker00.cs.umd.edu systemd-udevd[3720498]: Could not generate persistent MAC address for veth50440e2: No such file or directory Sep 19 15:28:42 sentry-docker00.cs.umd.edu systemd-udevd[3720551]: Could not generate persistent MAC address for vethb33a88b: No such file or directory Sep 19 15:28:42 sentry-docker00.cs.umd.edu systemd-udevd[3720553]: Could not generate persistent MAC address for vethe99c145: No such file or directory Sep 19 15:48:50 sentry-docker00.cs.umd.edu systemd-udevd[3729812]: link_config: could not get ethtool features for vethb33a88b Sep 19 15:48:50 sentry-docker00.cs.umd.edu systemd-udevd[3729812]: Could not set offload features of vethb33a88b: No such device Sep 19 15:48:50 sentry-docker00.cs.umd.edu systemd-udevd[3729882]: Could not generate persistent MAC address for veth03e4d4a: No such file or directory Sep 19 15:48:50 sentry-docker00.cs.umd.edu systemd-udevd[3729883]: Could not generate persistent MAC address for vethbc5d159: No such file or directory Sep 19 15:48:50 sentry-docker00.cs.umd.edu systemd-udevd[3729886]: Could not generate persistent MAC address for veth9187930: No such file or directory Sep 19 15:48:50 sentry-docker00.cs.umd.edu systemd-udevd[3729887]: Could not generate persistent MAC address for veth6675eda: No such file or directory Sep 19 15:48:50 sentry-docker00.cs.umd.edu systemd-udevd[3729890]: Could not generate persistent MAC address for veth92c5839: No such file or directory Sep 19 15:48:50 sentry-docker00.cs.umd.edu systemd-udevd[3729906]: Could not generate persistent MAC address for veth16e0c87: No such file or directory ... 4 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 19 15:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 19 15:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 19 15:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 19 15:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 19 15:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 19 15:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 19 15:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (1 distinct, 1 total) == Sep 19 15:58:40 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-f2 (1 distinct, 2 total) == Sep 19 15:39:28 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x2] == submit26-b9-f3 (3 distinct, 6 total) == Sep 19 15:20:06 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x4] Sep 19 15:20:07 submit26-b9-f3 systemd-coredump[2007494]: Process 2007491 (grades) of user 1001 dumped core.#012#012Stack trace of thread 2007491:#012#0 0x0000000000401a31 main (grades + 0x1a31)#012#1 0x00007f68dae2a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#2 0x00007f68dae2a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#3 0x00000000004010d5 _start (grades + 0x10d5)#012ELF object binary architecture: AMD x86-64 Sep 19 15:20:08 submit26-b9-f3 systemd-coredump[2007508]: Process 2007505 (grades) of user 1001 dumped core.#012#012Stack trace of thread 2007505:#012#0 0x0000000000401a31 main (grades + 0x1a31)#012#1 0x00007f27e942a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#2 0x00007f27e942a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#3 0x00000000004010d5 _start (grades + 0x10d5)#012ELF object binary architecture: AMD x86-64 == submit26-b9-f4 (1 distinct, 1 total) == Sep 19 15:39:37 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL
participants (1)
-
cron/syslog01.cs.umd.edu