Command: /usr/local/sbin/syslog-digest.py
Time : 7.4423s
Status : exited 0
Output :
Syslog digest — 2026-09-27 01:05 EDT
Processed 118,796 lines, filtered 1,362 (1%). 117,434 unknown (182 distinct) from 31 host(s).
== abuse (3 distinct, 4 total) ==
Sep 27 00:10:14 abuse systemd[1]: New main PID 1414 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 27 00:10:33 abuse systemd[1]: Daemon never wrote its PID file. Failing.
Sep 27 00:10:44 abuse systemd[1]: pmlogger.service: Supervising process 8889 which is not our child. We'll most likely not notice when it exits.
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 27 01:02:18 b0b02.cs.umd.edu rustdesk[1523543]: cannot open display:
== biggulp.cs.umd.edu (1 distinct, 3 total) ==
Sep 27 00:21:15 biggulp.cs.umd.edu sshd-session[340731]: error: send_error: write: Connection reset by peer [x3]
== forge00 (1 distinct, 1 total) ==
Sep 27 00:45:23 forge00 (httpd)[1350202]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
== galax (1 distinct, 1 total) ==
Sep 27 00:55:19 galax systemctl[363401]: Warning: The unit file, source configuration file or drop-ins of cups.service changed on disk. Run 'systemctl daemon-reload' to reload units.
== grades01.cs.umd.edu (3 distinct, 4 total) ==
Sep 27 00:10:13 grades01.cs.umd.edu systemd[1]: New main PID 466 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 27 00:10:34 grades01.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 27 00:10:49 grades01.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 7922 which is not our child. We'll most likely not notice when it exits.
== idm00 (1 distinct, 1 total) ==
Sep 27 00:54:09 idm00 named[4166701]: client @0x7f11a93f2098 10.73.240.42#53448: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 27 00:39:28 idmp0 named[1598691]: client @0x7f2d2000e0b8 10.73.240.43#59784: update '73.10.in-addr.arpa/IN' denied
== itmon02 (2 distinct, 9 total) ==
Sep 27 00:12:57 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x8]
Sep 27 00:16:40 itmon02 (httpd)[505799]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
== jubjub.cs.umd.edu (3 distinct, 4 total) ==
Sep 27 00:10:13 jubjub.cs.umd.edu systemd[1]: New main PID 1583415 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 27 00:10:33 jubjub.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 27 00:10:41 jubjub.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 1590694 which is not our child. We'll most likely not notice when it exits.
== librenms (1 distinct, 1 total) ==
Sep 27 00:39:34 librenms (httpd)[3017198]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
== lifepix (1 distinct, 1 total) ==
Sep 27 00:07:40 lifepix (httpd)[346712]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
== mirrors.cs.umd.edu (4 distinct, 6 total) ==
Sep 27 00:10:34 mirrors.cs.umd.edu root[5629]: pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily-K.log
Sep 27 00:10:34 mirrors.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing. [x2]
Sep 27 00:10:37 mirrors.cs.umd.edu systemd[1]: New main PID 4554 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 27 00:11:56 mirrors.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 21293 which is not our child. We'll most likely not notice when it exits.
== misty.cs.umd.edu (3 distinct, 4 total) ==
Sep 27 00:10:15 misty.cs.umd.edu systemd[1]: New main PID 20648 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 27 00:10:35 misty.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 27 00:10:50 misty.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 28276 which is not our child. We'll most likely not notice when it exits.
== munin (3 distinct, 51 total) ==
Sep 27 00:08:07 munin sudo[4185241]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x25]
Sep 27 00:08:07 munin sudo[4185241]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x25]
Sep 27 00:47:53 munin (httpd)[4840]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
== newhonors2 (1 distinct, 24 total) ==
Sep 27 00:13:02 newhonors2 dhcpcd[3207165]: dhcpcd is not running [x24]
== ntop00 (76 distinct, 117196 total) ==
Sep 27 00:05:08 ntop00 rsyslogd[1208]: file '/var/log/messages'[13] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x55862]
Sep 27 00:05:08 ntop00 rsyslogd[1208]: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x53214]
Sep 27 00:05:08 ntop00 rsyslogd[1208]: file '/var/log/maillog'[15] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x231]
Sep 27 00:05:08 ntop00 rsyslogd[1208]: action 'action-3-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x231]
Sep 27 00:05:09 ntop00 rsyslogd[1208]: imjournal: open() failed for path: '/var/lib/rsyslog/imjournal.state.tmp': No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2433 ] [x7546]
Sep 27 00:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 971) ***
Sep 27 00:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 971, QN: 4433/4433, ET: 0) ***
Sep 27 00:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 971) ***
Sep 27 00:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 971, QN: 46/46, ET: 0) ***
Sep 27 00:15:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x11]
Sep 27 00:15:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x11]
Sep 27 00:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 974) ***
Sep 27 00:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 974, QN: 0/4075, ET: 0) ***
Sep 27 00:15:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x10]
Sep 27 00:15:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x10]
Sep 27 00:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 974) ***
Sep 27 00:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 974, QN: 0/59, ET: 0) ***
Sep 27 00:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 975) ***
Sep 27 00:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 975, QN: 4016/4016, ET: 0) ***
Sep 27 00:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 975) ***
Sep 27 00:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 975, QN: 55/55, ET: 0) ***
Sep 27 00:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 976) ***
Sep 27 00:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 976, QN: 0/4174, ET: 0) ***
Sep 27 00:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 976) ***
Sep 27 00:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 976, QN: 0/56, ET: 0) ***
Sep 27 00:24:02 ntop00 rsyslogd[1208]: action 'action-1-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x4]
Sep 27 00:25:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 978) ***
Sep 27 00:25:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 978, QN: 0/4703, ET: 0) ***
Sep 27 00:25:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 978) ***
Sep 27 00:25:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 978, QN: 0/47, ET: 0) ***
... 46 more distinct messages not shown
== openrepo (1 distinct, 1 total) ==
Sep 27 00:32:53 openrepo (nin-node)[4020573]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
== openvox08-board (1 distinct, 1 total) ==
Sep 27 00:48:33 openvox08-board (httpd)[2013639]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 27 00:09:09 outbound00.cs.umd.edu python3[73876]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 27 00:13:06 outbound01.cs.umd.edu python3[2336538]: ldapdb [x6]
== portal (1 distinct, 1 total) ==
Sep 27 00:21:49 portal (httpd)[2878492]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
== sentry-docker00.cs.umd.edu (38 distinct, 38 total) ==
Sep 27 00:21:50 sentry-docker00.cs.umd.edu systemd-udevd[354073]: link_config: could not get ethtool features for veth496d50f
Sep 27 00:21:50 sentry-docker00.cs.umd.edu systemd-udevd[354073]: Could not set offload features of veth496d50f: No such device
Sep 27 00:21:50 sentry-docker00.cs.umd.edu systemd-udevd[354147]: Could not generate persistent MAC address for vethf211124: No such file or directory
Sep 27 00:21:50 sentry-docker00.cs.umd.edu systemd-udevd[354148]: Could not generate persistent MAC address for vethbe0a607: No such file or directory
Sep 27 00:21:50 sentry-docker00.cs.umd.edu systemd-udevd[354151]: Could not generate persistent MAC address for veth9d3fb8a: No such file or directory
Sep 27 00:21:50 sentry-docker00.cs.umd.edu systemd-udevd[354152]: Could not generate persistent MAC address for veth2226217: No such file or directory
Sep 27 00:21:50 sentry-docker00.cs.umd.edu systemd-udevd[354176]: Could not generate persistent MAC address for vethb2c546a: No such file or directory
Sep 27 00:21:50 sentry-docker00.cs.umd.edu systemd-udevd[354175]: Could not generate persistent MAC address for vethc16b0ed: No such file or directory
Sep 27 00:21:50 sentry-docker00.cs.umd.edu systemd-udevd[354204]: Could not generate persistent MAC address for veth80f9703: No such file or directory
Sep 27 00:21:50 sentry-docker00.cs.umd.edu systemd-udevd[354196]: Could not generate persistent MAC address for veth6709cff: No such file or directory
Sep 27 00:21:50 sentry-docker00.cs.umd.edu systemd-udevd[354197]: Could not generate persistent MAC address for vethcd74ccb: No such file or directory
Sep 27 00:21:50 sentry-docker00.cs.umd.edu systemd-udevd[354218]: Could not generate persistent MAC address for vetha208387: No such file or directory
Sep 27 00:41:58 sentry-docker00.cs.umd.edu systemd-udevd[363487]: link_config: could not get ethtool features for veth9d3fb8a
Sep 27 00:41:58 sentry-docker00.cs.umd.edu systemd-udevd[363487]: Could not set offload features of veth9d3fb8a: No such device
Sep 27 00:41:59 sentry-docker00.cs.umd.edu systemd-udevd[363534]: Could not generate persistent MAC address for veth4a6ce82: No such file or directory
Sep 27 00:41:59 sentry-docker00.cs.umd.edu systemd-udevd[363535]: Could not generate persistent MAC address for vetheed2974: No such file or directory
Sep 27 00:41:59 sentry-docker00.cs.umd.edu systemd-udevd[363538]: Could not generate persistent MAC address for vethe3c3859: No such file or directory
Sep 27 00:41:59 sentry-docker00.cs.umd.edu systemd-udevd[363539]: Could not generate persistent MAC address for vethf4f45fe: No such file or directory
Sep 27 00:41:59 sentry-docker00.cs.umd.edu systemd-udevd[363563]: Could not generate persistent MAC address for vethd64d534: No such file or directory
Sep 27 00:41:59 sentry-docker00.cs.umd.edu systemd-udevd[363562]: Could not generate persistent MAC address for vethb9ebac8: No such file or directory
Sep 27 00:41:59 sentry-docker00.cs.umd.edu systemd-udevd[363581]: Could not generate persistent MAC address for vethbc5595f: No such file or directory
Sep 27 00:41:59 sentry-docker00.cs.umd.edu systemd-udevd[363582]: Could not generate persistent MAC address for vethb44e5e7: No such file or directory
Sep 27 00:41:59 sentry-docker00.cs.umd.edu systemd-udevd[363567]: Could not generate persistent MAC address for veth1973eb1: No such file or directory
Sep 27 00:41:59 sentry-docker00.cs.umd.edu systemd-udevd[363584]: Could not generate persistent MAC address for veth238a5e4: No such file or directory
Sep 27 01:02:07 sentry-docker00.cs.umd.edu systemd-udevd[372904]: link_config: could not get ethtool features for veth238a5e4
Sep 27 01:02:07 sentry-docker00.cs.umd.edu systemd-udevd[372904]: Could not set offload features of veth238a5e4: No such device
Sep 27 01:02:07 sentry-docker00.cs.umd.edu systemd-udevd[372909]: link_config: could not get ethtool features for veth4a6ce82
Sep 27 01:02:07 sentry-docker00.cs.umd.edu systemd-udevd[372909]: Could not set offload features of veth4a6ce82: No such device
Sep 27 01:02:07 sentry-docker00.cs.umd.edu systemd-udevd[372955]: Could not generate persistent MAC address for veth88e107d: No such file or directory
Sep 27 01:02:07 sentry-docker00.cs.umd.edu systemd-udevd[372954]: Could not generate persistent MAC address for veth4a6d039: No such file or directory
... 8 more distinct messages not shown
== strawberry (8 distinct, 39 total) ==
Sep 27 00:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 27 00:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 27 00:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 27 00:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 27 00:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 27 00:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 27 00:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
Sep 27 01:04:42 strawberry smartd[5314]: Device: /dev/sda [SAT], not capable of Offline or Self-Testing.
== submit10-cln25 (3 distinct, 4 total) ==
Sep 27 00:10:11 submit10-cln25 systemd: New main PID 20126 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 27 00:10:30 submit10-cln25 systemd: Daemon never wrote its PID file. Failing.
Sep 27 00:10:36 submit10-cln25 systemd: pmlogger.service: Supervising process 27027 which is not our child. We'll most likely not notice when it exits.
== submit26-b9-fclone (9 distinct, 9 total) ==
Sep 27 00:22:00 submit26-b9-fclone setroubleshoot[557947]: 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 27 00:22:00 submit26-b9-fclone setroubleshoot[557947]: 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 27 00:22:01 submit26-b9-fclone setroubleshoot[557947]: 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 27 00:22:01 submit26-b9-fclone setroubleshoot[557947]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.eZ1COU/repodata/repomd.xml. For complete SELinux messages run: sealert -l 03e2f521-0e7c-481f-8e92-0602c6adeedc
Sep 27 00:22:01 submit26-b9-fclone setroubleshoot[557947]: 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 27 00:22:01 submit26-b9-fclone setroubleshoot[557947]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.eZ1COU. For complete SELinux messages run: sealert -l 887adbf9-2bb9-4009-b800-36ddf9ba0db5
Sep 27 00:22:01 submit26-b9-fclone setroubleshoot[557947]: 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 27 00:22:01 submit26-b9-fclone setroubleshoot[557947]: 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 27 00:22:01 submit26-b9-fclone setroubleshoot[557947]: 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
== tlsrpt (1 distinct, 1 total) ==
Sep 27 00:46:28 tlsrpt (httpd)[3257055]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
== tma-0 (3 distinct, 4 total) ==
Sep 27 00:10:13 tma-0 systemd[1]: New main PID 12000 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 27 00:10:30 tma-0 systemd[1]: Daemon never wrote its PID file. Failing.
Sep 27 00:10:38 tma-0 systemd[1]: pmlogger.service: Supervising process 18961 which is not our child. We'll most likely not notice when it exits.
== uffish.cs.umd.edu (3 distinct, 4 total) ==
Sep 27 00:10:12 uffish.cs.umd.edu systemd[1]: New main PID 4056007 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 27 00:10:39 uffish.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 27 00:10:55 uffish.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 4063615 which is not our child. We'll most likely not notice when it exits.
== vacuum.cs.umd.edu (3 distinct, 4 total) ==
Sep 27 00:10:15 vacuum.cs.umd.edu systemd[1]: New main PID 19378 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 27 00:10:33 vacuum.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 27 00:10:45 vacuum.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 26477 which is not our child. We'll most likely not notice when it exits.
== whiffle.cs.umd.edu (3 distinct, 4 total) ==
Sep 27 00:10:14 whiffle.cs.umd.edu systemd[1]: New main PID 3584881 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 27 00:10:33 whiffle.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 27 00:10:46 whiffle.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 3592422 which is not our child. We'll most likely not notice when it exits.
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 7.4605s
Status : exited 0
Output :
Syslog digest — 2026-09-27 00:05 EDT
Processed 119,291 lines, filtered 1,419 (1%). 117,872 unknown (130 distinct) from 26 host(s).
== abadi-computer (1 distinct, 1 total) ==
Sep 27 00:00:00 abadi-computer systemctl[1121849]: Warning: The unit file, source configuration file or drop-ins of cups.service changed on disk. Run 'systemctl daemon-reload' to reload units.
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 27 00:02:14 b0b02.cs.umd.edu rustdesk[1507398]: cannot open display:
== borogove.cs.umd.edu (1 distinct, 1 total) ==
Sep 27 00:00:02 borogove.cs.umd.edu rsyslogd[1921]: imfile: internal error? inotify provided watch descriptor 442 which we could not find in our tables - ignored [v8.2510.0-2.el9 try https://www.rsyslog.com/e/2175 ]
== hspc (1 distinct, 1 total) ==
Sep 27 00:00:04 hspc kernel: kauditd_printk_skb: 2 callbacks suppressed
== idm00 (2 distinct, 5 total) ==
Sep 26 23:54:09 idm00 named[4166701]: client @0x7f11a9464788 10.73.240.42#62006: update '73.10.in-addr.arpa/IN' denied
Sep 27 00:00:00 idm00 named[4166701]: checkhints: unable to get root NS rrset from cache: not found [x4]
== idmh1 (1 distinct, 2 total) ==
Sep 27 00:00:00 idmh1 named[3565631]: checkhints: unable to get root NS rrset from cache: not found [x2]
== idmp0 (2 distinct, 4 total) ==
Sep 26 23:39:28 idmp0 named[1598691]: client @0x7f2d1403a698 10.73.240.43#51537: update '73.10.in-addr.arpa/IN' denied
Sep 27 00:00:05 idmp0 named[1598691]: checkhints: unable to get root NS rrset from cache: not found [x3]
== idmv0 (1 distinct, 2 total) ==
Sep 27 00:00:01 idmv0 named[3973338]: checkhints: unable to get root NS rrset from cache: not found [x2]
== inbound01.cs.umd.edu (1 distinct, 1 total) ==
Sep 26 23:06:44 inbound01.cs.umd.edu sshd-session[2423320]: fatal: userauth_pubkey: parse publickey packet: incomplete message [preauth]
== itmon02 (1 distinct, 4 total) ==
Sep 26 23:08:22 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x4]
== jaws.cs.umd.edu (1 distinct, 1 total) ==
Sep 27 00:00:02 jaws.cs.umd.edu rsyslogd[1739]: imfile: poll_tree cannot stat file '/var/log/httpd/helpdesk.cs.umd.edu-ssl-8413_error_ssl.log' - ignored: No such file or directory [v8.2510.0-2.el9]
== krispykreme.cs.umd.edu (1 distinct, 5 total) ==
Sep 26 23:13:17 krispykreme.cs.umd.edu sshd-session[3012206]: error: send_error: write: Connection reset by peer [x5]
== matrix (1 distinct, 1 total) ==
Sep 27 00:00:13 matrix (nin-node)[189836]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
== munin (2 distinct, 20 total) ==
Sep 26 23:08:27 munin sudo[4162770]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x10]
Sep 26 23:08:27 munin sudo[4162770]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x10]
== neo-gizmonic (1 distinct, 1 total) ==
Sep 27 00:00:01 neo-gizmonic (nin-node)[2596289]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
== neoavion (1 distinct, 1 total) ==
Sep 27 00:00:25 neoavion (nin-node)[777229]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
== netbox (1 distinct, 1 total) ==
Sep 27 00:05:01 netbox (httpd)[819363]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
== newhonors2 (2 distinct, 25 total) ==
Sep 26 23:13:03 newhonors2 dhcpcd[3204959]: dhcpcd is not running [x24]
Sep 27 00:00:16 newhonors2 (nin-node)[3206621]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
== ntop00 (58 distinct, 117704 total) ==
Sep 26 23:05:08 ntop00 rsyslogd[1208]: file '/var/log/messages'[13] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x56107]
Sep 26 23:05:08 ntop00 rsyslogd[1208]: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x53273]
Sep 26 23:05:08 ntop00 rsyslogd[1208]: file '/var/log/maillog'[15] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x235]
Sep 26 23:05:08 ntop00 rsyslogd[1208]: action 'action-3-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x235]
Sep 26 23:05:09 ntop00 rsyslogd[1208]: imjournal: open() failed for path: '/var/lib/rsyslog/imjournal.state.tmp': No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2433 ] [x7779]
Sep 26 23:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 947) ***
Sep 26 23:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 947, QN: 3814/3814, ET: 0) ***
Sep 26 23:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 947) ***
Sep 26 23:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 947, QN: 58/58, ET: 0) ***
Sep 26 23:15:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6]
Sep 26 23:15:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x6]
Sep 26 23:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 950) ***
Sep 26 23:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 950, QN: 0/4919, ET: 0) ***
Sep 26 23:15:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6]
Sep 26 23:15:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x6]
Sep 26 23:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 950) ***
Sep 26 23:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 950, QN: 0/65, ET: 0) ***
Sep 26 23:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 951) ***
Sep 26 23:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 951, QN: 5420/5420, ET: 0) ***
Sep 26 23:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 951) ***
Sep 26 23:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 951, QN: 58/58, ET: 0) ***
Sep 26 23:25:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 954) ***
Sep 26 23:25:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 954, QN: 0/4224, ET: 0) ***
Sep 26 23:25:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 954) ***
Sep 26 23:25:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 954, QN: 0/49, ET: 0) ***
Sep 26 23:28:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 955) ***
Sep 26 23:28:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 955, QN: 4614/4614, ET: 0) ***
Sep 26 23:28:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 955) ***
Sep 26 23:28:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 955, QN: 58/58, ET: 0) ***
Sep 26 23:35:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 958) ***
... 28 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 26 23:09:09 outbound00.cs.umd.edu python3[59649]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 26 23:13:06 outbound01.cs.umd.edu python3[2321762]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (34 distinct, 34 total) ==
Sep 26 23:21:25 sentry-docker00.cs.umd.edu systemd-udevd[325956]: Could not generate persistent MAC address for veth899fb62: No such file or directory
Sep 26 23:21:25 sentry-docker00.cs.umd.edu systemd-udevd[325957]: Could not generate persistent MAC address for vethd856b08: No such file or directory
Sep 26 23:21:25 sentry-docker00.cs.umd.edu systemd-udevd[325960]: Could not generate persistent MAC address for veth9f82678: No such file or directory
Sep 26 23:21:25 sentry-docker00.cs.umd.edu systemd-udevd[325961]: Could not generate persistent MAC address for veth87e918e: No such file or directory
Sep 26 23:21:25 sentry-docker00.cs.umd.edu systemd-udevd[325977]: Could not generate persistent MAC address for vethb9ca596: No such file or directory
Sep 26 23:21:25 sentry-docker00.cs.umd.edu systemd-udevd[325972]: Could not generate persistent MAC address for veth2f10a4f: No such file or directory
Sep 26 23:21:25 sentry-docker00.cs.umd.edu systemd-udevd[325976]: Could not generate persistent MAC address for vethd00bd7e: No such file or directory
Sep 26 23:21:25 sentry-docker00.cs.umd.edu systemd-udevd[325983]: Could not generate persistent MAC address for veth5c46ee1: No such file or directory
Sep 26 23:21:25 sentry-docker00.cs.umd.edu systemd-udevd[325977]: Could not generate persistent MAC address for veth0de1000: No such file or directory
Sep 26 23:21:25 sentry-docker00.cs.umd.edu systemd-udevd[325976]: Could not generate persistent MAC address for vethf9c0f30: No such file or directory
Sep 26 23:41:33 sentry-docker00.cs.umd.edu systemd-udevd[335311]: link_config: could not get ethtool features for veth5c46ee1
Sep 26 23:41:33 sentry-docker00.cs.umd.edu systemd-udevd[335311]: Could not set offload features of veth5c46ee1: No such device
Sep 26 23:41:34 sentry-docker00.cs.umd.edu systemd-udevd[335346]: Could not generate persistent MAC address for veth39cc5ef: No such file or directory
Sep 26 23:41:34 sentry-docker00.cs.umd.edu systemd-udevd[335347]: Could not generate persistent MAC address for veth8908d8f: No such file or directory
Sep 26 23:41:34 sentry-docker00.cs.umd.edu systemd-udevd[335365]: Could not generate persistent MAC address for veth2e61ba8: No such file or directory
Sep 26 23:41:34 sentry-docker00.cs.umd.edu systemd-udevd[335372]: Could not generate persistent MAC address for veth25346a9: No such file or directory
Sep 26 23:41:34 sentry-docker00.cs.umd.edu systemd-udevd[335359]: Could not generate persistent MAC address for veth815b9aa: No such file or directory
Sep 26 23:41:34 sentry-docker00.cs.umd.edu systemd-udevd[335363]: Could not generate persistent MAC address for veth39dff53: No such file or directory
Sep 26 23:41:34 sentry-docker00.cs.umd.edu systemd-udevd[335354]: Could not generate persistent MAC address for veth10b989c: No such file or directory
Sep 26 23:41:34 sentry-docker00.cs.umd.edu systemd-udevd[335361]: Could not generate persistent MAC address for veth78879aa: No such file or directory
Sep 26 23:41:34 sentry-docker00.cs.umd.edu systemd-udevd[335359]: Could not generate persistent MAC address for vethc24d6a9: No such file or directory
Sep 26 23:41:34 sentry-docker00.cs.umd.edu systemd-udevd[335363]: Could not generate persistent MAC address for vethd6c1bef: No such file or directory
Sep 27 00:01:42 sentry-docker00.cs.umd.edu systemd-udevd[344659]: link_config: could not get ethtool features for veth10b989c
Sep 27 00:01:42 sentry-docker00.cs.umd.edu systemd-udevd[344659]: Could not set offload features of veth10b989c: No such device
Sep 27 00:01:42 sentry-docker00.cs.umd.edu systemd-udevd[344694]: Could not generate persistent MAC address for veth59f9c3f: No such file or directory
Sep 27 00:01:42 sentry-docker00.cs.umd.edu systemd-udevd[344695]: Could not generate persistent MAC address for vethf9d3ef8: No such file or directory
Sep 27 00:01:42 sentry-docker00.cs.umd.edu systemd-udevd[344698]: Could not generate persistent MAC address for veth662baab: No such file or directory
Sep 27 00:01:42 sentry-docker00.cs.umd.edu systemd-udevd[344703]: Could not generate persistent MAC address for veth5388f8b: No such file or directory
Sep 27 00:01:42 sentry-docker00.cs.umd.edu systemd-udevd[344699]: Could not generate persistent MAC address for vethd711ca3: No such file or directory
Sep 27 00:01:42 sentry-docker00.cs.umd.edu systemd-udevd[344710]: Could not generate persistent MAC address for vethda79bf0: No such file or directory
... 4 more distinct messages not shown
== strawberry (9 distinct, 40 total) ==
Sep 26 23:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 26 23:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 26 23:07:04 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 26 23:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 26 23:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 26 23:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 26 23:21:27 strawberry kernel: kauditd_printk_skb: 2 callbacks suppressed
Sep 26 23:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
Sep 27 00:00:03 strawberry kernel: kauditd_printk_skb: 4 callbacks suppressed
== tma-0 (2 distinct, 2 total) ==
Sep 26 23:58:19 tma-0 sshd[8697]: error: maximum authentication attempts exceeded for root from 184.153.171.150 port 54408 ssh2 [preauth]
Sep 26 23:58:19 tma-0 sshd[8697]: PAM service(sshd) ignoring max retries; 6 > 3
== unknown (1 distinct, 1 total) ==
using-explainable-ai
== wraith (2 distinct, 2 total) ==
Sep 27 00:00:07 wraith kernel: kauditd_printk_skb: 29 callbacks suppressed
Sep 27 00:00:07 wraith (nin-node)[101056]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 7.4279s
Status : exited 0
Output :
Syslog digest — 2026-09-26 23:05 EDT
Processed 119,024 lines, filtered 1,658 (1%). 117,366 unknown (156 distinct) from 16 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 26 23:02:10 b0b02.cs.umd.edu rustdesk[1492210]: cannot open display:
== idm00 (1 distinct, 1 total) ==
Sep 26 22:54:08 idm00 named[4166701]: client @0x7f11a9468268 10.73.240.42#63308: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 26 22:39:28 idmp0 named[1598691]: client @0x7f2d38010098 10.73.240.43#53231: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 2 total) ==
Sep 26 22:28:31 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x2]
== munin (2 distinct, 8 total) ==
Sep 26 22:28:31 munin sudo[4147910]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x4]
Sep 26 22:28:31 munin sudo[4147910]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x4]
== newhonors.cs.umd.edu (1 distinct, 1 total) ==
Sep 26 23:03:41 newhonors.cs.umd.edu systemd-tmpfiles: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
== newhonors2 (1 distinct, 24 total) ==
Sep 26 22:13:03 newhonors2 dhcpcd[3203115]: dhcpcd is not running [x24]
== ntop00 (77 distinct, 117212 total) ==
Sep 26 22:05:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x7]
Sep 26 22:05:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x7]
Sep 26 22:05:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 922) ***
Sep 26 22:05:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 922, QN: 0/5081, ET: 0) ***
Sep 26 22:05:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x7]
Sep 26 22:05:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x7]
Sep 26 22:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 922) ***
Sep 26 22:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 922, QN: 0/54, ET: 0) ***
Sep 26 22:05:08 ntop00 rsyslogd[1208]: file '/var/log/messages'[13] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x55919]
Sep 26 22:05:08 ntop00 rsyslogd[1208]: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x53141]
Sep 26 22:05:08 ntop00 rsyslogd[1208]: file '/var/log/maillog'[15] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x233]
Sep 26 22:05:08 ntop00 rsyslogd[1208]: action 'action-3-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x233]
Sep 26 22:05:08 ntop00 rsyslogd[1208]: imjournal: open() failed for path: '/var/lib/rsyslog/imjournal.state.tmp': No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2433 ] [x7590]
Sep 26 22:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 923) ***
Sep 26 22:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 923, QN: 4760/4760, ET: 0) ***
Sep 26 22:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 923) ***
Sep 26 22:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 923, QN: 49/49, ET: 0) ***
Sep 26 22:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 925) ***
Sep 26 22:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 925, QN: 5849/5849, ET: 0) ***
Sep 26 22:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 925) ***
Sep 26 22:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 925, QN: 54/54, ET: 0) ***
Sep 26 22:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 926) ***
Sep 26 22:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 926, QN: 0/6362, ET: 0) ***
Sep 26 22:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 926) ***
Sep 26 22:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 926, QN: 0/55, ET: 0) ***
Sep 26 22:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 927) ***
Sep 26 22:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 927, QN: 6786/6786, ET: 0) ***
Sep 26 22:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 927) ***
Sep 26 22:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 927, QN: 55/55, ET: 0) ***
Sep 26 22:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 929) ***
... 47 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 26 22:09:09 outbound00.cs.umd.edu python3[45516]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 26 22:13:06 outbound01.cs.umd.edu python3[2307789]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 26 22:21:00 sentry-docker00.cs.umd.edu systemd-udevd[297664]: link_config: could not get ethtool features for veth2e1202a
Sep 26 22:21:00 sentry-docker00.cs.umd.edu systemd-udevd[297664]: Could not set offload features of veth2e1202a: No such device
Sep 26 22:21:00 sentry-docker00.cs.umd.edu systemd-udevd[297721]: Could not generate persistent MAC address for vethe21f61f: No such file or directory
Sep 26 22:21:00 sentry-docker00.cs.umd.edu systemd-udevd[297722]: Could not generate persistent MAC address for veth58dd69f: No such file or directory
Sep 26 22:21:00 sentry-docker00.cs.umd.edu systemd-udevd[297725]: Could not generate persistent MAC address for veth1db2bc8: No such file or directory
Sep 26 22:21:00 sentry-docker00.cs.umd.edu systemd-udevd[297747]: Could not generate persistent MAC address for veth47d75cf: No such file or directory
Sep 26 22:21:00 sentry-docker00.cs.umd.edu systemd-udevd[297736]: Could not generate persistent MAC address for veth3e16485: No such file or directory
Sep 26 22:21:00 sentry-docker00.cs.umd.edu systemd-udevd[297732]: Could not generate persistent MAC address for veth86ad1aa: No such file or directory
Sep 26 22:21:01 sentry-docker00.cs.umd.edu systemd-udevd[297758]: Could not generate persistent MAC address for veth5b84c0b: No such file or directory
Sep 26 22:21:01 sentry-docker00.cs.umd.edu systemd-udevd[297760]: Could not generate persistent MAC address for vetha51c2d9: No such file or directory
Sep 26 22:21:01 sentry-docker00.cs.umd.edu systemd-udevd[297817]: Could not generate persistent MAC address for veth28463b5: No such file or directory
Sep 26 22:21:01 sentry-docker00.cs.umd.edu systemd-udevd[297815]: Could not generate persistent MAC address for vethb1df683: No such file or directory
Sep 26 22:41:09 sentry-docker00.cs.umd.edu systemd-udevd[307103]: link_config: could not set ethtool features for vethe21f61f
Sep 26 22:41:09 sentry-docker00.cs.umd.edu systemd-udevd[307103]: Could not set offload features of vethe21f61f: Operation not permitted
Sep 26 22:41:09 sentry-docker00.cs.umd.edu systemd-udevd[307128]: Could not generate persistent MAC address for vethf6f7fd9: No such file or directory
Sep 26 22:41:09 sentry-docker00.cs.umd.edu systemd-udevd[307129]: Could not generate persistent MAC address for veth59eb317: No such file or directory
Sep 26 22:41:09 sentry-docker00.cs.umd.edu systemd-udevd[307177]: Could not generate persistent MAC address for vethd8f0375: No such file or directory
Sep 26 22:41:09 sentry-docker00.cs.umd.edu systemd-udevd[307178]: Could not generate persistent MAC address for veth49c13ea: No such file or directory
Sep 26 22:41:09 sentry-docker00.cs.umd.edu systemd-udevd[307184]: Could not generate persistent MAC address for vethf3e8ddc: No such file or directory
Sep 26 22:41:09 sentry-docker00.cs.umd.edu systemd-udevd[307203]: Could not generate persistent MAC address for veth6a8e398: No such file or directory
Sep 26 22:41:09 sentry-docker00.cs.umd.edu systemd-udevd[307204]: Could not generate persistent MAC address for vethf5a7b94: No such file or directory
Sep 26 22:41:09 sentry-docker00.cs.umd.edu systemd-udevd[307196]: Could not generate persistent MAC address for veth7d77425: No such file or directory
Sep 26 22:41:09 sentry-docker00.cs.umd.edu systemd-udevd[307224]: Could not generate persistent MAC address for veth6395a10: No such file or directory
Sep 26 22:41:09 sentry-docker00.cs.umd.edu systemd-udevd[307221]: Could not generate persistent MAC address for vethfae786d: No such file or directory
Sep 26 23:01:17 sentry-docker00.cs.umd.edu systemd-udevd[316523]: link_config: could not get ethtool features for vethf5a7b94
Sep 26 23:01:17 sentry-docker00.cs.umd.edu systemd-udevd[316523]: Could not set offload features of vethf5a7b94: No such device
Sep 26 23:01:17 sentry-docker00.cs.umd.edu systemd-udevd[316563]: Could not generate persistent MAC address for veth65e6ffe: No such file or directory
Sep 26 23:01:17 sentry-docker00.cs.umd.edu systemd-udevd[316564]: Could not generate persistent MAC address for vethefb9db5: No such file or directory
Sep 26 23:01:17 sentry-docker00.cs.umd.edu systemd-udevd[316567]: Could not generate persistent MAC address for vethe7ed892: No such file or directory
Sep 26 23:01:17 sentry-docker00.cs.umd.edu systemd-udevd[316568]: Could not generate persistent MAC address for veth31c184e: No such file or directory
... 6 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 26 22:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 26 22:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 26 22:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 26 22:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 26 22:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 26 22:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 26 22:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (11 distinct, 15 total) ==
Sep 26 22:25:57 submit26-b9-f1 setroubleshoot[3843149]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 3ef7d677-731f-46bf-9c34-c2c55fea665c [x2]
Sep 26 22:25:57 submit26-b9-f1 setroubleshoot[3843149]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l aa60e26f-72e1-45f1-bc12-aa8b3b669e36 [x2]
Sep 26 22:25:57 submit26-b9-f1 setroubleshoot[3843149]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l d088fb43-23ee-4ae8-ae6a-5d1c041ee2d6
Sep 26 22:25:57 submit26-b9-f1 setroubleshoot[3843149]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.EDBZpQ/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d
Sep 26 22:25:57 submit26-b9-f1 setroubleshoot[3843149]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 0fd3339f-3ef2-45f3-9e58-65a58b42f3ee
Sep 26 22:25:57 submit26-b9-f1 setroubleshoot[3843149]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.EDBZpQ. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8
Sep 26 22:25:57 submit26-b9-f1 setroubleshoot[3843149]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 405a8556-cf9f-4ef4-8525-0dca18d4259d [x2]
Sep 26 22:25:57 submit26-b9-f1 setroubleshoot[3843149]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 3c38e23e-3631-4cb5-81c7-992675c836d9
Sep 26 22:25:57 submit26-b9-f1 setroubleshoot[3843149]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l a070e9b5-2867-47d6-b2e3-3b7d99725848 [x2]
Sep 26 22:25:57 submit26-b9-f1 setroubleshoot[3843149]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.lGUl89. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8
Sep 26 22:30:07 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
== submit26-b9-f2 (10 distinct, 10 total) ==
Sep 26 22:06:51 submit26-b9-f2 setroubleshoot[2912230]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 0659d546-3107-4f75-b00f-008c85f41dc6
Sep 26 22:06:51 submit26-b9-f2 setroubleshoot[2912230]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 156d9270-3466-4356-b86f-1a128825961a
Sep 26 22:06:51 submit26-b9-f2 setroubleshoot[2912230]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l c8a40bf5-2fc4-46b3-b813-8592b3523339
Sep 26 22:06:51 submit26-b9-f2 setroubleshoot[2912230]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.WApS6Z/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876
Sep 26 22:06:51 submit26-b9-f2 setroubleshoot[2912230]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 988123da-b724-4e6a-900c-33a2723fdaf1
Sep 26 22:06:51 submit26-b9-f2 setroubleshoot[2912230]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.WApS6Z. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8
Sep 26 22:06:51 submit26-b9-f2 setroubleshoot[2912230]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 3a749560-1cec-40ca-a4dc-596841be3885
Sep 26 22:06:51 submit26-b9-f2 setroubleshoot[2912230]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 0aa52f08-94f8-474e-96d8-e818846941af
Sep 26 22:06:51 submit26-b9-f2 setroubleshoot[2912230]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l de019dc4-408f-439c-902a-676d18dfe8e7
Sep 26 22:50:07 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
== submit26-b9-f4 (1 distinct, 1 total) ==
Sep 26 22:09:57 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
== vacuum.cs.umd.edu (4 distinct, 4 total) ==
Sep 26 22:11:58 vacuum.cs.umd.edu abrt-hook-ccpp[21121]: Process 16701 (driver) of user 33 killed by SIGABRT - dumping core
Sep 26 22:11:58 vacuum.cs.umd.edu abrt-server[21123]: Package 'amanda-backup_server' isn't signed with proper key
Sep 26 22:11:58 vacuum.cs.umd.edu abrt-server[21123]: 'post-create' on '/var/spool/abrt/ccpp-2026-09-26-22:11:58-16701' exited with 1
Sep 26 22:11:58 vacuum.cs.umd.edu abrt-server[21123]: Deleting problem directory '/var/spool/abrt/ccpp-2026-09-26-22:11:58-16701'
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 7.4429s
Status : exited 0
Output :
Syslog digest — 2026-09-26 22:05 EDT
Processed 118,790 lines, filtered 1,429 (1%). 117,361 unknown (154 distinct) from 15 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 26 22:02:05 b0b02.cs.umd.edu rustdesk[1476984]: cannot open display:
== idm00 (1 distinct, 1 total) ==
Sep 26 21:54:08 idm00 named[4166701]: client @0x7f11a9464788 10.73.240.42#51606: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 26 21:39:28 idmp0 named[1598691]: client @0x7f2d440131e8 10.73.240.43#65192: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 3 total) ==
Sep 26 21:18:25 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x3]
== munin (2 distinct, 12 total) ==
Sep 26 21:13:18 munin sudo[4121178]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x6]
Sep 26 21:13:18 munin sudo[4121178]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x6]
== newhonors2 (1 distinct, 24 total) ==
Sep 26 21:13:02 newhonors2 dhcpcd[3201272]: dhcpcd is not running [x24]
== ntop00 (79 distinct, 117210 total) ==
Sep 26 21:05:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6]
Sep 26 21:05:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x6]
Sep 26 21:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 898) ***
Sep 26 21:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 898, QN: 0/73, ET: 0) ***
Sep 26 21:05:08 ntop00 rsyslogd[1208]: file '/var/log/messages'[13] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x55882]
Sep 26 21:05:08 ntop00 rsyslogd[1208]: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x52984]
Sep 26 21:05:08 ntop00 rsyslogd[1208]: file '/var/log/maillog'[15] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x234]
Sep 26 21:05:08 ntop00 rsyslogd[1208]: action 'action-3-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x234]
Sep 26 21:05:08 ntop00 rsyslogd[1208]: imjournal: open() failed for path: '/var/lib/rsyslog/imjournal.state.tmp': No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2433 ] [x7784]
Sep 26 21:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 899) ***
Sep 26 21:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 899, QN: 5328/5328, ET: 0) ***
Sep 26 21:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 899) ***
Sep 26 21:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 899, QN: 68/68, ET: 0) ***
Sep 26 21:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 901) ***
Sep 26 21:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 901, QN: 4647/4647, ET: 0) ***
Sep 26 21:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 901) ***
Sep 26 21:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 901, QN: 45/45, ET: 0) ***
Sep 26 21:15:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x5]
Sep 26 21:15:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x5]
Sep 26 21:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 902) ***
Sep 26 21:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 902, QN: 0/5272, ET: 0) ***
Sep 26 21:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 902) ***
Sep 26 21:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 902, QN: 0/44, ET: 0) ***
Sep 26 21:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 903) ***
Sep 26 21:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 903, QN: 5500/5500, ET: 0) ***
Sep 26 21:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 903) ***
Sep 26 21:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 903, QN: 58/58, ET: 0) ***
Sep 26 21:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 905) ***
Sep 26 21:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 905, QN: 5631/5631, ET: 0) ***
Sep 26 21:23:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 905) ***
... 49 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 26 21:09:08 outbound00.cs.umd.edu python3[31513]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 26 21:13:06 outbound01.cs.umd.edu python3[2293657]: ldapdb [x6]
== sebatinsky.cs.umd.edu (1 distinct, 1 total) ==
Sep 26 21:09:43 sebatinsky.cs.umd.edu kernel: hpet1: lost 1 rtc interrupts
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 26 21:20:35 sentry-docker00.cs.umd.edu systemd-udevd[268804]: link_config: could not get ethtool features for vetha3ad32c
Sep 26 21:20:35 sentry-docker00.cs.umd.edu systemd-udevd[268804]: Could not set offload features of vetha3ad32c: No such device
Sep 26 21:20:35 sentry-docker00.cs.umd.edu systemd-udevd[268875]: Could not generate persistent MAC address for veth10b8e87: No such file or directory
Sep 26 21:20:35 sentry-docker00.cs.umd.edu systemd-udevd[268876]: Could not generate persistent MAC address for vethb3a8ff2: No such file or directory
Sep 26 21:20:35 sentry-docker00.cs.umd.edu systemd-udevd[268894]: Could not generate persistent MAC address for veth2ee57b4: No such file or directory
Sep 26 21:20:35 sentry-docker00.cs.umd.edu systemd-udevd[268888]: Could not generate persistent MAC address for veth6daa879: No such file or directory
Sep 26 21:20:35 sentry-docker00.cs.umd.edu systemd-udevd[268903]: Could not generate persistent MAC address for vethe5e086b: No such file or directory
Sep 26 21:20:35 sentry-docker00.cs.umd.edu systemd-udevd[268904]: Could not generate persistent MAC address for vethedb7e54: No such file or directory
Sep 26 21:20:35 sentry-docker00.cs.umd.edu systemd-udevd[268929]: Could not generate persistent MAC address for veth4b684fc: No such file or directory
Sep 26 21:20:35 sentry-docker00.cs.umd.edu systemd-udevd[268930]: Could not generate persistent MAC address for veth2056814: No such file or directory
Sep 26 21:20:35 sentry-docker00.cs.umd.edu systemd-udevd[268955]: Could not generate persistent MAC address for veth3167755: No such file or directory
Sep 26 21:20:35 sentry-docker00.cs.umd.edu systemd-udevd[268956]: Could not generate persistent MAC address for veth12bad31: No such file or directory
Sep 26 21:40:44 sentry-docker00.cs.umd.edu systemd-udevd[278574]: link_config: could not get ethtool features for veth2ee57b4
Sep 26 21:40:44 sentry-docker00.cs.umd.edu systemd-udevd[278574]: Could not set offload features of veth2ee57b4: No such device
Sep 26 21:40:44 sentry-docker00.cs.umd.edu systemd-udevd[278608]: Could not generate persistent MAC address for veth3433dfc: No such file or directory
Sep 26 21:40:44 sentry-docker00.cs.umd.edu systemd-udevd[278609]: Could not generate persistent MAC address for vethc6b2c20: No such file or directory
Sep 26 21:40:44 sentry-docker00.cs.umd.edu systemd-udevd[278612]: Could not generate persistent MAC address for veth79afbe4: No such file or directory
Sep 26 21:40:44 sentry-docker00.cs.umd.edu systemd-udevd[278613]: Could not generate persistent MAC address for veth85a9632: No such file or directory
Sep 26 21:40:44 sentry-docker00.cs.umd.edu systemd-udevd[278624]: Could not generate persistent MAC address for veth82497ff: No such file or directory
Sep 26 21:40:44 sentry-docker00.cs.umd.edu systemd-udevd[278609]: Could not generate persistent MAC address for veth9dfd391: No such file or directory
Sep 26 21:40:44 sentry-docker00.cs.umd.edu systemd-udevd[278638]: Could not generate persistent MAC address for vethfdb77e7: No such file or directory
Sep 26 21:40:44 sentry-docker00.cs.umd.edu systemd-udevd[278639]: Could not generate persistent MAC address for veth57a07e2: No such file or directory
Sep 26 21:40:44 sentry-docker00.cs.umd.edu systemd-udevd[278657]: Could not generate persistent MAC address for veth7935464: No such file or directory
Sep 26 21:40:44 sentry-docker00.cs.umd.edu systemd-udevd[278651]: Could not generate persistent MAC address for veth0174e24: No such file or directory
Sep 26 22:00:52 sentry-docker00.cs.umd.edu systemd-udevd[288198]: link_config: could not get ethtool features for veth3433dfc
Sep 26 22:00:52 sentry-docker00.cs.umd.edu systemd-udevd[288198]: Could not set offload features of veth3433dfc: No such device
Sep 26 22:00:52 sentry-docker00.cs.umd.edu systemd-udevd[288252]: Could not generate persistent MAC address for veth2e641b5: No such file or directory
Sep 26 22:00:52 sentry-docker00.cs.umd.edu systemd-udevd[288253]: Could not generate persistent MAC address for veth054e8bc: No such file or directory
Sep 26 22:00:52 sentry-docker00.cs.umd.edu systemd-udevd[288256]: Could not generate persistent MAC address for veth2e1202a: No such file or directory
Sep 26 22:00:52 sentry-docker00.cs.umd.edu systemd-udevd[288257]: Could not generate persistent MAC address for veth67b719d: No such file or directory
... 6 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 26 21:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 26 21:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 26 21:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 26 21:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 26 21:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 26 21:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 26 21:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f3 (10 distinct, 10 total) ==
Sep 26 21:06:45 submit26-b9-f3 setroubleshoot[3597515]: 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
Sep 26 21:06:45 submit26-b9-f3 setroubleshoot[3597515]: 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
Sep 26 21:06:45 submit26-b9-f3 setroubleshoot[3597515]: 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
Sep 26 21:06:45 submit26-b9-f3 setroubleshoot[3597515]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.bCbZti/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f
Sep 26 21:06:45 submit26-b9-f3 setroubleshoot[3597515]: 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
Sep 26 21:06:45 submit26-b9-f3 setroubleshoot[3597515]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.bCbZti. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd
Sep 26 21:06:45 submit26-b9-f3 setroubleshoot[3597515]: 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
Sep 26 21:06:45 submit26-b9-f3 setroubleshoot[3597515]: 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
Sep 26 21:06:45 submit26-b9-f3 setroubleshoot[3597515]: 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
Sep 26 21:10:06 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
== submit26-b9-f4 (10 distinct, 10 total) ==
Sep 26 21:24:48 submit26-b9-f4 setroubleshoot[2633888]: 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
Sep 26 21:24:48 submit26-b9-f4 setroubleshoot[2633888]: 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
Sep 26 21:24:48 submit26-b9-f4 setroubleshoot[2633888]: 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
Sep 26 21:24:48 submit26-b9-f4 setroubleshoot[2633888]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.ORXJ1O/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0
Sep 26 21:24:48 submit26-b9-f4 setroubleshoot[2633888]: 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
Sep 26 21:24:49 submit26-b9-f4 setroubleshoot[2633888]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.ORXJ1O. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c
Sep 26 21:24:49 submit26-b9-f4 setroubleshoot[2633888]: 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
Sep 26 21:24:49 submit26-b9-f4 setroubleshoot[2633888]: 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
Sep 26 21:24:49 submit26-b9-f4 setroubleshoot[2633888]: 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
Sep 26 21:30:09 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
== wraith (2 distinct, 2 total) ==
Sep 26 21:48:47 wraith kernel: workqueue: i915_hpd_poll_init_work [i915] hogged CPU for >10000us 4099 times, consider switching to WQ_UNBOUND
Sep 26 21:50:22 wraith kernel: workqueue: output_poll_execute hogged CPU for >10000us 4099 times, consider switching to WQ_UNBOUND
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 7.4814s
Status : exited 0
Output :
Syslog digest — 2026-09-26 21:05 EDT
Processed 119,536 lines, filtered 1,708 (1%). 117,828 unknown (141 distinct) from 15 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 26 21:02:01 b0b02.cs.umd.edu rustdesk[1461804]: cannot open display:
== cheezit.cs.umd.edu (1 distinct, 3 total) ==
Sep 26 21:02:58 cheezit.cs.umd.edu sshd-session[3469736]: error: PAM: Authentication failure for adamnguy from 10.174.62.191 [x3]
== galax (1 distinct, 1 total) ==
Sep 26 20:59:49 galax kernel: workqueue: dm_irq_work_func [amdgpu] hogged CPU for >10000us 8195 times, consider switching to WQ_UNBOUND
== idm00 (1 distinct, 1 total) ==
Sep 26 20:54:08 idm00 named[4166701]: client @0x7f119807baf8 10.73.240.42#50435: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 26 20:39:28 idmp0 named[1598691]: client @0x7f2d280332b8 10.73.240.43#51139: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 3 total) ==
Sep 26 20:08:21 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x3]
== munin (2 distinct, 4 total) ==
Sep 26 20:23:19 munin sudo[4102400]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x2]
Sep 26 20:23:19 munin sudo[4102400]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x2]
== newhonors2 (1 distinct, 24 total) ==
Sep 26 20:13:03 newhonors2 dhcpcd[3199432]: dhcpcd is not running [x24]
== ntop00 (81 distinct, 117697 total) ==
Sep 26 20:05:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6]
Sep 26 20:05:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x6]
Sep 26 20:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 874) ***
Sep 26 20:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 874, QN: 0/61, ET: 0) ***
Sep 26 20:05:08 ntop00 rsyslogd[1208]: file '/var/log/messages'[13] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x56110]
Sep 26 20:05:08 ntop00 rsyslogd[1208]: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x53328]
Sep 26 20:05:08 ntop00 rsyslogd[1208]: file '/var/log/maillog'[15] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x237]
Sep 26 20:05:08 ntop00 rsyslogd[1208]: action 'action-3-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x237]
Sep 26 20:05:09 ntop00 rsyslogd[1208]: imjournal: open() failed for path: '/var/lib/rsyslog/imjournal.state.tmp': No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2433 ] [x7689]
Sep 26 20:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 875) ***
Sep 26 20:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 875, QN: 7964/7964, ET: 0) ***
Sep 26 20:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 875) ***
Sep 26 20:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 875, QN: 61/61, ET: 0) ***
Sep 26 20:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 877) ***
Sep 26 20:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 877, QN: 65/65, ET: 0) ***
Sep 26 20:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 877) ***
Sep 26 20:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 877, QN: 8920/8920, ET: 0) ***
Sep 26 20:15:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6]
Sep 26 20:15:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x6]
Sep 26 20:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 878) ***
Sep 26 20:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 878, QN: 0/9655, ET: 0) ***
Sep 26 20:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 878) ***
Sep 26 20:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 878, QN: 0/59, ET: 0) ***
Sep 26 20:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 879) ***
Sep 26 20:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 879, QN: 9156/9156, ET: 0) ***
Sep 26 20:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 879) ***
Sep 26 20:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 879, QN: 57/57, ET: 0) ***
Sep 26 20:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 881) ***
Sep 26 20:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 881, QN: 9975/9975, ET: 0) ***
Sep 26 20:23:02 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 881) ***
... 51 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 26 20:09:09 outbound00.cs.umd.edu python3[17585]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 26 20:13:06 outbound01.cs.umd.edu python3[2279605]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (32 distinct, 32 total) ==
Sep 26 20:20:10 sentry-docker00.cs.umd.edu systemd-udevd[240674]: Could not generate persistent MAC address for veth0cb3890: No such file or directory
Sep 26 20:20:10 sentry-docker00.cs.umd.edu systemd-udevd[240675]: Could not generate persistent MAC address for veth3c2d252: No such file or directory
Sep 26 20:20:10 sentry-docker00.cs.umd.edu systemd-udevd[240678]: Could not generate persistent MAC address for veth3c2a590: No such file or directory
Sep 26 20:20:10 sentry-docker00.cs.umd.edu systemd-udevd[240690]: Could not generate persistent MAC address for vethcd3686e: No such file or directory
Sep 26 20:20:10 sentry-docker00.cs.umd.edu systemd-udevd[240698]: Could not generate persistent MAC address for vethdbd59d4: No such file or directory
Sep 26 20:20:10 sentry-docker00.cs.umd.edu systemd-udevd[240687]: Could not generate persistent MAC address for veth13de5de: No such file or directory
Sep 26 20:20:10 sentry-docker00.cs.umd.edu systemd-udevd[240706]: Could not generate persistent MAC address for veth8ade4f6: No such file or directory
Sep 26 20:20:10 sentry-docker00.cs.umd.edu systemd-udevd[240707]: Could not generate persistent MAC address for veth9bd96c7: No such file or directory
Sep 26 20:20:10 sentry-docker00.cs.umd.edu systemd-udevd[240718]: Could not generate persistent MAC address for veth38522ca: No such file or directory
Sep 26 20:20:10 sentry-docker00.cs.umd.edu systemd-udevd[240722]: Could not generate persistent MAC address for veth5ef6cbb: No such file or directory
Sep 26 20:40:19 sentry-docker00.cs.umd.edu systemd-udevd[249991]: link_config: could not get ethtool features for veth0cb3890
Sep 26 20:40:19 sentry-docker00.cs.umd.edu systemd-udevd[249991]: Could not set offload features of veth0cb3890: No such device
Sep 26 20:40:19 sentry-docker00.cs.umd.edu systemd-udevd[250071]: Could not generate persistent MAC address for veth4b44127: No such file or directory
Sep 26 20:40:19 sentry-docker00.cs.umd.edu systemd-udevd[250072]: Could not generate persistent MAC address for veth93ed0c0: No such file or directory
Sep 26 20:40:19 sentry-docker00.cs.umd.edu systemd-udevd[250075]: Could not generate persistent MAC address for veth96a6062: No such file or directory
Sep 26 20:40:19 sentry-docker00.cs.umd.edu systemd-udevd[250089]: Could not generate persistent MAC address for vethe1f95bc: No such file or directory
Sep 26 20:40:19 sentry-docker00.cs.umd.edu systemd-udevd[250099]: Could not generate persistent MAC address for veth82dd944: No such file or directory
Sep 26 20:40:19 sentry-docker00.cs.umd.edu systemd-udevd[250100]: Could not generate persistent MAC address for veth48266a2: No such file or directory
Sep 26 20:40:19 sentry-docker00.cs.umd.edu systemd-udevd[250118]: Could not generate persistent MAC address for vethe005dc8: No such file or directory
Sep 26 20:40:19 sentry-docker00.cs.umd.edu systemd-udevd[250116]: Could not generate persistent MAC address for veth6039b8b: No such file or directory
Sep 26 20:40:19 sentry-docker00.cs.umd.edu systemd-udevd[250171]: Could not generate persistent MAC address for veth7bf394a: No such file or directory
Sep 26 20:40:19 sentry-docker00.cs.umd.edu systemd-udevd[250173]: Could not generate persistent MAC address for veth019b195: No such file or directory
Sep 26 21:00:27 sentry-docker00.cs.umd.edu systemd-udevd[259751]: Could not generate persistent MAC address for veth55cccb1: No such file or directory
Sep 26 21:00:27 sentry-docker00.cs.umd.edu systemd-udevd[259752]: Could not generate persistent MAC address for veth650c18d: No such file or directory
Sep 26 21:00:27 sentry-docker00.cs.umd.edu systemd-udevd[259755]: Could not generate persistent MAC address for vethd85018c: No such file or directory
Sep 26 21:00:27 sentry-docker00.cs.umd.edu systemd-udevd[259756]: Could not generate persistent MAC address for vethd726dcb: No such file or directory
Sep 26 21:00:27 sentry-docker00.cs.umd.edu systemd-udevd[259762]: Could not generate persistent MAC address for vethf0e3b71: No such file or directory
Sep 26 21:00:27 sentry-docker00.cs.umd.edu systemd-udevd[259776]: Could not generate persistent MAC address for veth4f93a12: No such file or directory
Sep 26 21:00:27 sentry-docker00.cs.umd.edu systemd-udevd[259776]: Could not generate persistent MAC address for veth3eaba64: No such file or directory
Sep 26 21:00:27 sentry-docker00.cs.umd.edu systemd-udevd[259760]: Could not generate persistent MAC address for vethfa12872: No such file or directory
... 2 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 26 20:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 26 20:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 26 20:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 26 20:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 26 20:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 26 20:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 26 20:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f4 (1 distinct, 1 total) ==
Sep 26 20:48:59 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
== submit26-b9-fclone (9 distinct, 10 total) ==
Sep 26 20:22:01 submit26-b9-fclone setroubleshoot[548203]: 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 [x2]
Sep 26 20:22:01 submit26-b9-fclone setroubleshoot[548203]: 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 26 20:22:01 submit26-b9-fclone setroubleshoot[548203]: 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 26 20:22:01 submit26-b9-fclone setroubleshoot[548203]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.3PkJow/repodata/repomd.xml. For complete SELinux messages run: sealert -l 03e2f521-0e7c-481f-8e92-0602c6adeedc
Sep 26 20:22:01 submit26-b9-fclone setroubleshoot[548203]: 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 26 20:22:01 submit26-b9-fclone setroubleshoot[548203]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.3PkJow. For complete SELinux messages run: sealert -l 887adbf9-2bb9-4009-b800-36ddf9ba0db5
Sep 26 20:22:01 submit26-b9-fclone setroubleshoot[548203]: 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 26 20:22:02 submit26-b9-fclone setroubleshoot[548203]: 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 26 20:22:02 submit26-b9-fclone setroubleshoot[548203]: 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
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 7.4278s
Status : exited 0
Output :
Syslog digest — 2026-09-26 20:05 EDT
Processed 118,708 lines, filtered 1,357 (1%). 117,351 unknown (135 distinct) from 15 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 26 20:01:57 b0b02.cs.umd.edu rustdesk[1446452]: cannot open display:
== bachata (10 distinct, 10 total) ==
Sep 26 20:03:30 bachata smbd[1231700]: [2026/09/26 20:03:30.040920, 0] ../../source3/smbd/smb2_service.c:117(chdir_current_service)
Sep 26 20:03:30 bachata smbd[1231700]: chdir_current_service: vfs_ChDir(/fs/junkfood/nelson) failed: Permission denied. Current token: uid=20608, gid=20608, 19 groups: 20608 31006 30043 319050000 30736 30871 25274 15248 15206 25025 15294 15228 319000009 30872 25057 30742 25200 25038 25195
Sep 26 20:03:30 bachata smbd[1231700]: [2026/09/26 20:03:30.042739, 0] ../../source3/smbd/smbXsrv_tcon.c:914(smbXsrv_tcon_disconnect)
Sep 26 20:03:30 bachata smbd[1231700]: smbXsrv_tcon_disconnect: disconnect(0x3c03e40b, 'nelson'): chdir_current_service() failed: NT_STATUS_INTERNAL_ERROR
Sep 26 20:03:30 bachata smbd[1231700]: [2026/09/26 20:03:30.044078, 0] ../../source3/smbd/smbXsrv_tcon.c:1028(smbXsrv_tcon_disconnect_all)
Sep 26 20:03:30 bachata smbd[1231700]: smbXsrv_tcon_disconnect_all: count[3] errors[1] first[NT_STATUS_INTERNAL_ERROR]
Sep 26 20:03:30 bachata smbd[1231700]: [2026/09/26 20:03:30.044198, 0] ../../source3/smbd/smbXsrv_session.c:1900(smbXsrv_session_logoff)
Sep 26 20:03:30 bachata smbd[1231700]: smbXsrv_session_logoff: smbXsrv_session_logoff(0xc621d034): smb2srv_tcon_disconnect_all() failed: NT_STATUS_INTERNAL_ERROR
Sep 26 20:03:30 bachata smbd[1231700]: [2026/09/26 20:03:30.044313, 0] ../../source3/smbd/smbXsrv_session.c:1728(smbXsrv_session_remove_channel_done)
Sep 26 20:03:30 bachata smbd[1231700]: smbXsrv_session_remove_channel_done: smbXsrv_session_logoff(3324104756) failed: NT_STATUS_INTERNAL_ERROR
== gle-dind04 (1 distinct, 1 total) ==
Sep 26 19:15:49 gle-dind04 lldpd[1171]: unable to send packet on real device for veth77a44fe: No such device or address
== idm00 (1 distinct, 1 total) ==
Sep 26 19:54:08 idm00 named[4166701]: client @0x7f119807baf8 10.73.240.42#51949: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 26 19:39:28 idmp0 named[1598691]: client @0x7f2d4c0213e8 10.73.240.43#53582: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 1 total) ==
Sep 26 19:33:57 itmon02 sshd[1483508]: error: beginning MaxStartups throttling
== krispykreme.cs.umd.edu (2 distinct, 2 total) ==
Sep 26 19:14:37 krispykreme.cs.umd.edu krb5_child[2947883]: Preauthentication failed
Sep 26 19:14:37 krispykreme.cs.umd.edu sshd-session[2947874]: error: PAM: Authentication failure for avarhade from 10.206.0.172
== munin (2 distinct, 10 total) ==
Sep 26 19:23:31 munin sudo[4081513]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x5]
Sep 26 19:23:31 munin sudo[4081513]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x5]
== newhonors2 (1 distinct, 24 total) ==
Sep 26 19:13:03 newhonors2 dhcpcd[3197612]: dhcpcd is not running [x24]
== ntop00 (67 distinct, 117211 total) ==
Sep 26 19:05:08 ntop00 rsyslogd[1208]: imjournal: open() failed for path: '/var/lib/rsyslog/imjournal.state.tmp': No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2433 ] [x7501]
Sep 26 19:05:08 ntop00 rsyslogd[1208]: file '/var/log/messages'[13] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x55902]
Sep 26 19:05:08 ntop00 rsyslogd[1208]: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x53258]
Sep 26 19:05:08 ntop00 rsyslogd[1208]: file '/var/log/maillog'[15] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x235]
Sep 26 19:05:08 ntop00 rsyslogd[1208]: action 'action-3-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x235]
Sep 26 19:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 853) ***
Sep 26 19:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 853) ***
Sep 26 19:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 853, QN: 67/67, ET: 0) ***
Sep 26 19:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 853, QN: 8036/8036, ET: 0) ***
Sep 26 19:15:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x5]
Sep 26 19:15:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x5]
Sep 26 19:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 854) ***
Sep 26 19:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 854, QN: 0/59, ET: 0) ***
Sep 26 19:15:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6]
Sep 26 19:15:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x6]
Sep 26 19:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 854) ***
Sep 26 19:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 854, QN: 0/8089, ET: 0) ***
Sep 26 19:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 857) ***
Sep 26 19:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 857, QN: 7871/7871, ET: 0) ***
Sep 26 19:23:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 857) ***
Sep 26 19:23:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 857, QN: 54/54, ET: 0) ***
Sep 26 19:25:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 858) ***
Sep 26 19:25:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 858, QN: 0/8340, ET: 0) ***
Sep 26 19:25:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 858) ***
Sep 26 19:25:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 858, QN: 0/61, ET: 0) ***
Sep 26 19:33:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 861) ***
Sep 26 19:33:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 861, QN: 8339/8339, ET: 0) ***
Sep 26 19:33:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 861) ***
Sep 26 19:33:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 861, QN: 73/73, ET: 0) ***
Sep 26 19:35:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 862) ***
... 37 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 26 19:09:09 outbound00.cs.umd.edu python3[3606]: ldapdb [x6]
== outbound01.cs.umd.edu (2 distinct, 7 total) ==
Sep 26 19:13:07 outbound01.cs.umd.edu python3[2265517]: ldapdb [x6]
Sep 26 19:48:55 outbound01.cs.umd.edu krb5_child[2273577]: Client 'admin(a)UMD.EDU' not found in Kerberos database
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 26 19:19:45 sentry-docker00.cs.umd.edu systemd-udevd[212359]: link_config: could not get ethtool features for veth1d1645a
Sep 26 19:19:45 sentry-docker00.cs.umd.edu systemd-udevd[212359]: Could not set offload features of veth1d1645a: No such device
Sep 26 19:19:46 sentry-docker00.cs.umd.edu systemd-udevd[212391]: Could not generate persistent MAC address for veth89c2db5: No such file or directory
Sep 26 19:19:46 sentry-docker00.cs.umd.edu systemd-udevd[212392]: Could not generate persistent MAC address for veth8974d59: No such file or directory
Sep 26 19:19:46 sentry-docker00.cs.umd.edu systemd-udevd[212395]: Could not generate persistent MAC address for veth08a4cee: No such file or directory
Sep 26 19:19:46 sentry-docker00.cs.umd.edu systemd-udevd[212396]: Could not generate persistent MAC address for veth84ae7d6: No such file or directory
Sep 26 19:19:46 sentry-docker00.cs.umd.edu systemd-udevd[212419]: Could not generate persistent MAC address for veth3266ce0: No such file or directory
Sep 26 19:19:46 sentry-docker00.cs.umd.edu systemd-udevd[212420]: Could not generate persistent MAC address for veth61e9153: No such file or directory
Sep 26 19:19:46 sentry-docker00.cs.umd.edu systemd-udevd[212446]: Could not generate persistent MAC address for vethc209e8c: No such file or directory
Sep 26 19:19:46 sentry-docker00.cs.umd.edu systemd-udevd[212445]: Could not generate persistent MAC address for veth2c667e3: No such file or directory
Sep 26 19:19:46 sentry-docker00.cs.umd.edu systemd-udevd[212461]: Could not generate persistent MAC address for veth7c2a00e: No such file or directory
Sep 26 19:19:46 sentry-docker00.cs.umd.edu systemd-udevd[212451]: Could not generate persistent MAC address for vethcfe7570: No such file or directory
Sep 26 19:39:54 sentry-docker00.cs.umd.edu systemd-udevd[221739]: link_config: could not get ethtool features for veth3266ce0
Sep 26 19:39:54 sentry-docker00.cs.umd.edu systemd-udevd[221739]: Could not set offload features of veth3266ce0: No such device
Sep 26 19:39:54 sentry-docker00.cs.umd.edu systemd-udevd[221779]: Could not generate persistent MAC address for veth544341d: No such file or directory
Sep 26 19:39:54 sentry-docker00.cs.umd.edu systemd-udevd[221780]: Could not generate persistent MAC address for veth96593f6: No such file or directory
Sep 26 19:39:54 sentry-docker00.cs.umd.edu systemd-udevd[221783]: Could not generate persistent MAC address for vethcedfc87: No such file or directory
Sep 26 19:39:54 sentry-docker00.cs.umd.edu systemd-udevd[221784]: Could not generate persistent MAC address for veth5360b62: No such file or directory
Sep 26 19:39:54 sentry-docker00.cs.umd.edu systemd-udevd[221794]: Could not generate persistent MAC address for vethddddae7: No such file or directory
Sep 26 19:39:54 sentry-docker00.cs.umd.edu systemd-udevd[221784]: Could not generate persistent MAC address for veth94288d9: No such file or directory
Sep 26 19:39:54 sentry-docker00.cs.umd.edu systemd-udevd[221794]: Could not generate persistent MAC address for veth7554e76: No such file or directory
Sep 26 19:39:54 sentry-docker00.cs.umd.edu systemd-udevd[221784]: Could not generate persistent MAC address for veth0affb8d: No such file or directory
Sep 26 19:39:54 sentry-docker00.cs.umd.edu systemd-udevd[221884]: Could not generate persistent MAC address for veth24b39c3: No such file or directory
Sep 26 19:39:54 sentry-docker00.cs.umd.edu systemd-udevd[221890]: Could not generate persistent MAC address for veth96e5aac: No such file or directory
Sep 26 20:00:02 sentry-docker00.cs.umd.edu systemd-udevd[231169]: link_config: could not get ethtool features for vethcedfc87
Sep 26 20:00:02 sentry-docker00.cs.umd.edu systemd-udevd[231169]: Could not set offload features of vethcedfc87: No such device
Sep 26 20:00:02 sentry-docker00.cs.umd.edu systemd-udevd[231245]: Could not generate persistent MAC address for veth4b65fad: No such file or directory
Sep 26 20:00:02 sentry-docker00.cs.umd.edu systemd-udevd[231246]: Could not generate persistent MAC address for vethbd887cc: No such file or directory
Sep 26 20:00:02 sentry-docker00.cs.umd.edu systemd-udevd[231249]: Could not generate persistent MAC address for veth5d8280a: No such file or directory
Sep 26 20:00:02 sentry-docker00.cs.umd.edu systemd-udevd[231260]: Could not generate persistent MAC address for veth78d4780: No such file or directory
... 6 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 26 19:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 26 19:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 26 19:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 26 19:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 26 19:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 26 19:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 26 19:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== teaching-awards (2 distinct, 2 total) ==
Sep 26 19:43:49 teaching-awards krb5_child[1743714]: Client 'backup(a)UMD.EDU' not found in Kerberos database
Sep 26 19:43:57 teaching-awards krb5_child[1743722]: Client 'admin(a)UMD.EDU' not found in Kerberos database
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 7.4710s
Status : exited 0
Output :
Syslog digest — 2026-09-26 19:05 EDT
Processed 119,167 lines, filtered 1,292 (1%). 117,875 unknown (154 distinct) from 18 host(s).
== b0b02.cs.umd.edu (4 distinct, 4 total) ==
Sep 26 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-09-26T22:10:59.432674077Z" level=info msg="PurgeUploads starting: olderThan=2026-09-19 22:10:59.432582124 +0000 UTC m=+4667820.192510430, actuallyDelete=true"
Sep 26 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-09-26T22:10:59.433177891Z" level=info msg="Purge uploads finished. Num deleted=0, num errors=1"
Sep 26 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-09-26T22:10:59.433198191Z" level=info msg="Starting upload purge in 24h0m0s" go.version=go1.11.2 instance.id=68469aa4-7857-4a69-bf12-c2190b4f96d8 service=registry version=v2.7.1
Sep 26 19:01:53 b0b02.cs.umd.edu rustdesk[1431264]: cannot open display:
== bachata (10 distinct, 10 total) ==
Sep 26 18:31:45 bachata smbd[1238547]: [2026/09/26 18:31:45.015446, 0] ../../source3/smbd/smb2_service.c:117(chdir_current_service)
Sep 26 18:31:45 bachata smbd[1238547]: chdir_current_service: vfs_ChDir(/fs/junkfood/mount) failed: Permission denied. Current token: uid=11255, gid=11255, 12 groups: 11255 319000009 25038 15294 15229 755 25030 25025 30880 25029 770 15026
Sep 26 18:31:45 bachata smbd[1238547]: [2026/09/26 18:31:45.017071, 0] ../../source3/smbd/smbXsrv_tcon.c:914(smbXsrv_tcon_disconnect)
Sep 26 18:31:45 bachata smbd[1238547]: smbXsrv_tcon_disconnect: disconnect(0x33599d29, 'mount'): chdir_current_service() failed: NT_STATUS_INTERNAL_ERROR
Sep 26 18:31:45 bachata smbd[1238547]: [2026/09/26 18:31:45.017314, 0] ../../source3/smbd/smbXsrv_tcon.c:1028(smbXsrv_tcon_disconnect_all)
Sep 26 18:31:45 bachata smbd[1238547]: smbXsrv_tcon_disconnect_all: count[2] errors[1] first[NT_STATUS_INTERNAL_ERROR]
Sep 26 18:31:45 bachata smbd[1238547]: [2026/09/26 18:31:45.017378, 0] ../../source3/smbd/smbXsrv_session.c:1900(smbXsrv_session_logoff)
Sep 26 18:31:45 bachata smbd[1238547]: smbXsrv_session_logoff: smbXsrv_session_logoff(0xb34c0db1): smb2srv_tcon_disconnect_all() failed: NT_STATUS_INTERNAL_ERROR
Sep 26 18:31:45 bachata smbd[1238547]: [2026/09/26 18:31:45.017480, 0] ../../source3/smbd/smbXsrv_session.c:1728(smbXsrv_session_remove_channel_done)
Sep 26 18:31:45 bachata smbd[1238547]: smbXsrv_session_remove_channel_done: smbXsrv_session_logoff(3008105905) failed: NT_STATUS_INTERNAL_ERROR
== galax (1 distinct, 1 total) ==
Sep 26 18:54:54 galax kernel: rtw89_8922ae 0000:06:00.0: failed to wait RF DACK
== idm00 (1 distinct, 1 total) ==
Sep 26 18:54:08 idm00 named[4166701]: client @0x7f11a429b368 10.73.240.42#51239: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 26 18:39:28 idmp0 named[1598691]: client @0x7f2d4c0213e8 10.73.240.43#51841: update '73.10.in-addr.arpa/IN' denied
== inbound01.cs.umd.edu (1 distinct, 2 total) ==
Sep 26 18:06:58 inbound01.cs.umd.edu krb5_child[2353005]: Preauthentication failed [x2]
== itmon02 (1 distinct, 4 total) ==
Sep 26 18:28:07 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x4]
== munin (2 distinct, 4 total) ==
Sep 26 18:43:15 munin sudo[4067370]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x2]
Sep 26 18:43:15 munin sudo[4067370]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x2]
== newhonors2 (1 distinct, 24 total) ==
Sep 26 18:13:03 newhonors2 dhcpcd[3195748]: dhcpcd is not running [x24]
== ntop00 (59 distinct, 117703 total) ==
Sep 26 18:05:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x7]
Sep 26 18:05:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x7]
Sep 26 18:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 826) ***
Sep 26 18:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 826, QN: 0/75, ET: 0) ***
Sep 26 18:05:08 ntop00 rsyslogd[1208]: imjournal: open() failed for path: '/var/lib/rsyslog/imjournal.state.tmp': No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2433 ] [x7498]
Sep 26 18:05:08 ntop00 rsyslogd[1208]: file '/var/log/messages'[13] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x56157]
Sep 26 18:05:08 ntop00 rsyslogd[1208]: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x53500]
Sep 26 18:05:08 ntop00 rsyslogd[1208]: file '/var/log/maillog'[15] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x236]
Sep 26 18:05:08 ntop00 rsyslogd[1208]: action 'action-3-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x236]
Sep 26 18:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 829) ***
Sep 26 18:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 829, QN: 74/74, ET: 0) ***
Sep 26 18:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 829) ***
Sep 26 18:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 829, QN: 14603/14603, ET: 0) ***
Sep 26 18:15:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6]
Sep 26 18:15:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x6]
Sep 26 18:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 830) ***
Sep 26 18:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 830, QN: 0/15080, ET: 0) ***
Sep 26 18:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 830) ***
Sep 26 18:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 830, QN: 0/62, ET: 0) ***
Sep 26 18:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 833) ***
Sep 26 18:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 833, QN: 11982/11982, ET: 0) ***
Sep 26 18:23:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 833) ***
Sep 26 18:23:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 833, QN: 54/54, ET: 0) ***
Sep 26 18:25:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 834) ***
Sep 26 18:25:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 834, QN: 0/12326, ET: 0) ***
Sep 26 18:25:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 834) ***
Sep 26 18:25:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 834, QN: 0/51, ET: 0) ***
Sep 26 18:33:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 837) ***
Sep 26 18:33:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 837, QN: 13345/13345, ET: 0) ***
Sep 26 18:33:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 837) ***
... 29 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 26 18:09:09 outbound00.cs.umd.edu python3[4183303]: ldapdb [x6]
== outbound01.cs.umd.edu (3 distinct, 10 total) ==
Sep 26 18:05:25 outbound01.cs.umd.edu krb5_child[2249448]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x3]
Sep 26 18:13:06 outbound01.cs.umd.edu python3[2251251]: ldapdb [x6]
Sep 26 18:25:49 outbound01.cs.umd.edu krb5_child[2254648]: Preauthentication failed
== sentry-docker00.cs.umd.edu (40 distinct, 40 total) ==
Sep 26 18:19:20 sentry-docker00.cs.umd.edu systemd-udevd[183981]: link_config: could not get ethtool features for veth61e1ba7
Sep 26 18:19:20 sentry-docker00.cs.umd.edu systemd-udevd[183981]: Could not set offload features of veth61e1ba7: No such device
Sep 26 18:19:20 sentry-docker00.cs.umd.edu systemd-udevd[183981]: link_config: could not get ethtool features for veth2d0190e
Sep 26 18:19:20 sentry-docker00.cs.umd.edu systemd-udevd[183981]: Could not set offload features of veth2d0190e: No such device
Sep 26 18:19:21 sentry-docker00.cs.umd.edu systemd-udevd[184104]: Could not generate persistent MAC address for veth9ba8551: No such file or directory
Sep 26 18:19:21 sentry-docker00.cs.umd.edu systemd-udevd[184103]: Could not generate persistent MAC address for vethff86a8f: No such file or directory
Sep 26 18:19:21 sentry-docker00.cs.umd.edu systemd-udevd[184107]: Could not generate persistent MAC address for vetha89d4cd: No such file or directory
Sep 26 18:19:21 sentry-docker00.cs.umd.edu systemd-udevd[184108]: Could not generate persistent MAC address for veth7699f67: No such file or directory
Sep 26 18:19:21 sentry-docker00.cs.umd.edu systemd-udevd[184129]: Could not generate persistent MAC address for veth894f636: No such file or directory
Sep 26 18:19:21 sentry-docker00.cs.umd.edu systemd-udevd[184128]: Could not generate persistent MAC address for veth563736b: No such file or directory
Sep 26 18:19:21 sentry-docker00.cs.umd.edu systemd-udevd[184133]: Could not generate persistent MAC address for veth5abad6b: No such file or directory
Sep 26 18:19:21 sentry-docker00.cs.umd.edu systemd-udevd[184134]: Could not generate persistent MAC address for veth59b201e: No such file or directory
Sep 26 18:19:21 sentry-docker00.cs.umd.edu systemd-udevd[184193]: Could not generate persistent MAC address for veth3158d12: No such file or directory
Sep 26 18:19:21 sentry-docker00.cs.umd.edu systemd-udevd[184197]: Could not generate persistent MAC address for vethe91f429: No such file or directory
Sep 26 18:39:29 sentry-docker00.cs.umd.edu systemd-udevd[193545]: link_config: could not get ethtool features for vetha89d4cd
Sep 26 18:39:29 sentry-docker00.cs.umd.edu systemd-udevd[193545]: Could not set offload features of vetha89d4cd: No such device
Sep 26 18:39:29 sentry-docker00.cs.umd.edu systemd-udevd[193550]: link_config: could not set ethtool features for veth5abad6b
Sep 26 18:39:29 sentry-docker00.cs.umd.edu systemd-udevd[193550]: Could not set offload features of veth5abad6b: Operation not permitted
Sep 26 18:39:29 sentry-docker00.cs.umd.edu systemd-udevd[193583]: Could not generate persistent MAC address for vethbdfa9d4: No such file or directory
Sep 26 18:39:29 sentry-docker00.cs.umd.edu systemd-udevd[193584]: Could not generate persistent MAC address for vethe441da5: No such file or directory
Sep 26 18:39:29 sentry-docker00.cs.umd.edu systemd-udevd[193587]: Could not generate persistent MAC address for veth41c81c7: No such file or directory
Sep 26 18:39:29 sentry-docker00.cs.umd.edu systemd-udevd[193588]: Could not generate persistent MAC address for vethc42657c: No such file or directory
Sep 26 18:39:29 sentry-docker00.cs.umd.edu systemd-udevd[193602]: Could not generate persistent MAC address for vethca493be: No such file or directory
Sep 26 18:39:29 sentry-docker00.cs.umd.edu systemd-udevd[193605]: Could not generate persistent MAC address for vetha1e8baf: No such file or directory
Sep 26 18:39:29 sentry-docker00.cs.umd.edu systemd-udevd[193606]: Could not generate persistent MAC address for veth36a3406: No such file or directory
Sep 26 18:39:29 sentry-docker00.cs.umd.edu systemd-udevd[193603]: Could not generate persistent MAC address for veth29de73e: No such file or directory
Sep 26 18:39:29 sentry-docker00.cs.umd.edu systemd-udevd[193587]: Could not generate persistent MAC address for vethc9e4e70: No such file or directory
Sep 26 18:39:29 sentry-docker00.cs.umd.edu systemd-udevd[193603]: Could not generate persistent MAC address for veth9132a1c: No such file or directory
Sep 26 18:59:37 sentry-docker00.cs.umd.edu systemd-udevd[202932]: link_config: could not get ethtool features for veth9132a1c
Sep 26 18:59:37 sentry-docker00.cs.umd.edu systemd-udevd[202932]: Could not set offload features of veth9132a1c: No such device
... 10 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 26 18:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 26 18:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 26 18:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 26 18:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 26 18:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 26 18:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 26 18:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (10 distinct, 14 total) ==
Sep 26 18:25:57 submit26-b9-f1 setroubleshoot[3802851]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 3ef7d677-731f-46bf-9c34-c2c55fea665c [x2]
Sep 26 18:25:57 submit26-b9-f1 setroubleshoot[3802851]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l aa60e26f-72e1-45f1-bc12-aa8b3b669e36 [x2]
Sep 26 18:25:57 submit26-b9-f1 setroubleshoot[3802851]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l d088fb43-23ee-4ae8-ae6a-5d1c041ee2d6
Sep 26 18:25:57 submit26-b9-f1 setroubleshoot[3802851]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.U2SsKm/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d
Sep 26 18:25:57 submit26-b9-f1 setroubleshoot[3802851]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 0fd3339f-3ef2-45f3-9e58-65a58b42f3ee
Sep 26 18:25:57 submit26-b9-f1 setroubleshoot[3802851]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.U2SsKm. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8
Sep 26 18:25:57 submit26-b9-f1 setroubleshoot[3802851]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 405a8556-cf9f-4ef4-8525-0dca18d4259d [x2]
Sep 26 18:25:57 submit26-b9-f1 setroubleshoot[3802851]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 3c38e23e-3631-4cb5-81c7-992675c836d9
Sep 26 18:25:57 submit26-b9-f1 setroubleshoot[3802851]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l a070e9b5-2867-47d6-b2e3-3b7d99725848 [x2]
Sep 26 18:25:57 submit26-b9-f1 setroubleshoot[3802851]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.D3pnXd. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8
== submit26-b9-f2 (10 distinct, 11 total) ==
Sep 26 18:06:51 submit26-b9-f2 setroubleshoot[2879654]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 0659d546-3107-4f75-b00f-008c85f41dc6
Sep 26 18:06:51 submit26-b9-f2 setroubleshoot[2879654]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 156d9270-3466-4356-b86f-1a128825961a
Sep 26 18:06:51 submit26-b9-f2 setroubleshoot[2879654]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l c8a40bf5-2fc4-46b3-b813-8592b3523339
Sep 26 18:06:51 submit26-b9-f2 setroubleshoot[2879654]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.XC0XgU/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876
Sep 26 18:06:51 submit26-b9-f2 setroubleshoot[2879654]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 988123da-b724-4e6a-900c-33a2723fdaf1
Sep 26 18:06:51 submit26-b9-f2 setroubleshoot[2879654]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.XC0XgU. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8
Sep 26 18:06:51 submit26-b9-f2 setroubleshoot[2879654]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 3a749560-1cec-40ca-a4dc-596841be3885
Sep 26 18:06:51 submit26-b9-f2 setroubleshoot[2879654]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 0aa52f08-94f8-474e-96d8-e818846941af
Sep 26 18:06:51 submit26-b9-f2 setroubleshoot[2879654]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l de019dc4-408f-439c-902a-676d18dfe8e7
Sep 26 18:28:08 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x2]
== submit26-b9-f3 (1 distinct, 1 total) ==
Sep 26 18:07:40 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
== wraith (1 distinct, 1 total) ==
Sep 26 18:56:31 wraith kernel: kauditd_printk_skb: 20 callbacks suppressed
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 7.4267s
Status : exited 0
Output :
Syslog digest — 2026-09-26 18:05 EDT
Processed 118,853 lines, filtered 1,472 (1%). 117,381 unknown (139 distinct) from 16 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 26 18:01:52 b0b02.cs.umd.edu rustdesk[1416015]: cannot open display:
== frozone (1 distinct, 1 total) ==
Sep 26 17:35:46 frozone systemd-tmpfiles[2785556]: Failed to remove "/var/tmp/test.log", ignoring: Operation not permitted
== gle-dind04 (7 distinct, 7 total) ==
Sep 26 17:37:11 gle-dind04 systemd-coredump[3143165]: Process 3143163 (ctr) of user 0 dumped core.#012#012Stack trace of thread 3143163:#012#0 0x0000558965dca2ee n/a (/usr/bin/ctr + 0xe2ee)#012#1 0x0000558965de92c7 n/a (/usr/bin/ctr + 0x2d2c7)#012#2 0x0000558965de8fc9 n/a (/usr/bin/ctr + 0x2cfc9)#012#3 0x0000558965de41d0 n/a (/usr/bin/ctr + 0x281d0)#012#4 0x0000558965de40a8 n/a (/usr/bin/ctr + 0x280a8)#012#5 0x0000558965de4065 n/a (/usr/bin/ctr + 0x28065)#012#6 0x0000558965e08ada n/a (/usr/bin/ctr + 0x4cada)#012#7 0x0000558965e02651 n/a (/usr/bin/ctr + 0x46651)#012#8 0x0000558965dfe7a5 n/a (/usr/bin/ctr + 0x427a5)#012#9 0x0000558965de1edd n/a (/usr/bin/ctr + 0x25edd)#012#10 0x0000558965e12b52 n/a (/usr/bin/ctr + 0x56b52)#012#11 0x0000558965e4ca47 n/a (/usr/bin/ctr + 0x90a47)#012ELF object binary architecture: AMD x86-64
Sep 26 17:37:11 gle-dind04 systemd-coredump[3143173]: Process 3143171 (ctr) of user 0 dumped core.#012#012Stack trace of thread 3143171:#012#0 0x000055e81a82b2ee n/a (/usr/bin/ctr + 0xe2ee)#012#1 0x000055e81a84a2c7 n/a (/usr/bin/ctr + 0x2d2c7)#012#2 0x000055e81a849fc9 n/a (/usr/bin/ctr + 0x2cfc9)#012#3 0x000055e81a8451d0 n/a (/usr/bin/ctr + 0x281d0)#012#4 0x000055e81a8450a8 n/a (/usr/bin/ctr + 0x280a8)#012#5 0x000055e81a845065 n/a (/usr/bin/ctr + 0x28065)#012#6 0x000055e81a869ada n/a (/usr/bin/ctr + 0x4cada)#012#7 0x000055e81a863651 n/a (/usr/bin/ctr + 0x46651)#012#8 0x000055e81a85f7a5 n/a (/usr/bin/ctr + 0x427a5)#012#9 0x000055e81a842edd n/a (/usr/bin/ctr + 0x25edd)#012#10 0x000055e81a873b52 n/a (/usr/bin/ctr + 0x56b52)#012#11 0x000055e81a8ada47 n/a (/usr/bin/ctr + 0x90a47)#012ELF object binary architecture: AMD x86-64
Sep 26 17:37:12 gle-dind04 systemd-coredump[3143180]: Process 3143178 (ctr) of user 0 dumped core.#012#012Stack trace of thread 3143178:#012#0 0x00005579a327b2ee n/a (/usr/bin/ctr + 0xe2ee)#012#1 0x00005579a329a2c7 n/a (/usr/bin/ctr + 0x2d2c7)#012#2 0x00005579a3299fc9 n/a (/usr/bin/ctr + 0x2cfc9)#012#3 0x00005579a32951d0 n/a (/usr/bin/ctr + 0x281d0)#012#4 0x00005579a32950a8 n/a (/usr/bin/ctr + 0x280a8)#012#5 0x00005579a3295065 n/a (/usr/bin/ctr + 0x28065)#012#6 0x00005579a32b9ada n/a (/usr/bin/ctr + 0x4cada)#012#7 0x00005579a32b3651 n/a (/usr/bin/ctr + 0x46651)#012#8 0x00005579a32af7a5 n/a (/usr/bin/ctr + 0x427a5)#012#9 0x00005579a3292edd n/a (/usr/bin/ctr + 0x25edd)#012#10 0x00005579a32c3b52 n/a (/usr/bin/ctr + 0x56b52)#012#11 0x00005579a32fda47 n/a (/usr/bin/ctr + 0x90a47)#012ELF object binary architecture: AMD x86-64
Sep 26 17:37:12 gle-dind04 systemd-coredump[3143188]: Process 3143186 (ctr) of user 0 dumped core.#012#012Stack trace of thread 3143186:#012#0 0x0000563449a072ee n/a (/usr/bin/ctr + 0xe2ee)#012#1 0x0000563449a262c7 n/a (/usr/bin/ctr + 0x2d2c7)#012#2 0x0000563449a25fc9 n/a (/usr/bin/ctr + 0x2cfc9)#012#3 0x0000563449a211d0 n/a (/usr/bin/ctr + 0x281d0)#012#4 0x0000563449a210a8 n/a (/usr/bin/ctr + 0x280a8)#012#5 0x0000563449a21065 n/a (/usr/bin/ctr + 0x28065)#012#6 0x0000563449a45ada n/a (/usr/bin/ctr + 0x4cada)#012#7 0x0000563449a3f651 n/a (/usr/bin/ctr + 0x46651)#012#8 0x0000563449a3b7a5 n/a (/usr/bin/ctr + 0x427a5)#012#9 0x0000563449a1eedd n/a (/usr/bin/ctr + 0x25edd)#012#10 0x0000563449a4fb52 n/a (/usr/bin/ctr + 0x56b52)#012#11 0x0000563449a89a47 n/a (/usr/bin/ctr + 0x90a47)#012ELF object binary architecture: AMD x86-64
Sep 26 17:37:12 gle-dind04 systemd-coredump[3143195]: Process 3143193 (ctr) of user 0 dumped core.#012#012Stack trace of thread 3143193:#012#0 0x0000564a962a32ee n/a (/usr/bin/ctr + 0xe2ee)#012#1 0x0000564a962c22c7 n/a (/usr/bin/ctr + 0x2d2c7)#012#2 0x0000564a962c1fc9 n/a (/usr/bin/ctr + 0x2cfc9)#012#3 0x0000564a962bd1d0 n/a (/usr/bin/ctr + 0x281d0)#012#4 0x0000564a962bd0a8 n/a (/usr/bin/ctr + 0x280a8)#012#5 0x0000564a962bd065 n/a (/usr/bin/ctr + 0x28065)#012#6 0x0000564a962e1ada n/a (/usr/bin/ctr + 0x4cada)#012#7 0x0000564a962db651 n/a (/usr/bin/ctr + 0x46651)#012#8 0x0000564a962d77a5 n/a (/usr/bin/ctr + 0x427a5)#012#9 0x0000564a962baedd n/a (/usr/bin/ctr + 0x25edd)#012#10 0x0000564a962ebb52 n/a (/usr/bin/ctr + 0x56b52)#012#11 0x0000564a96325a47 n/a (/usr/bin/ctr + 0x90a47)#012ELF object binary architecture: AMD x86-64
Sep 26 17:37:12 gle-dind04 systemd-coredump[3143202]: Process 3143200 (ctr) of user 0 dumped core.#012#012Stack trace of thread 3143200:#012#0 0x0000563f125f82ee n/a (/usr/bin/ctr + 0xe2ee)#012#1 0x0000563f126172c7 n/a (/usr/bin/ctr + 0x2d2c7)#012#2 0x0000563f12616fc9 n/a (/usr/bin/ctr + 0x2cfc9)#012#3 0x0000563f126121d0 n/a (/usr/bin/ctr + 0x281d0)#012#4 0x0000563f126120a8 n/a (/usr/bin/ctr + 0x280a8)#012#5 0x0000563f12612065 n/a (/usr/bin/ctr + 0x28065)#012#6 0x0000563f12636ada n/a (/usr/bin/ctr + 0x4cada)#012#7 0x0000563f12630651 n/a (/usr/bin/ctr + 0x46651)#012#8 0x0000563f1262c7a5 n/a (/usr/bin/ctr + 0x427a5)#012#9 0x0000563f1260fedd n/a (/usr/bin/ctr + 0x25edd)#012#10 0x0000563f12640b52 n/a (/usr/bin/ctr + 0x56b52)#012#11 0x0000563f1267aa47 n/a (/usr/bin/ctr + 0x90a47)#012ELF object binary architecture: AMD x86-64
Sep 26 17:37:12 gle-dind04 systemd-coredump[3143209]: Process 3143207 (ctr) of user 0 dumped core.#012#012Stack trace of thread 3143207:#012#0 0x000055aed118e2ee n/a (/usr/bin/ctr + 0xe2ee)#012#1 0x000055aed11ad2c7 n/a (/usr/bin/ctr + 0x2d2c7)#012#2 0x000055aed11acfc9 n/a (/usr/bin/ctr + 0x2cfc9)#012#3 0x000055aed11a81d0 n/a (/usr/bin/ctr + 0x281d0)#012#4 0x000055aed11a80a8 n/a (/usr/bin/ctr + 0x280a8)#012#5 0x000055aed11a8065 n/a (/usr/bin/ctr + 0x28065)#012#6 0x000055aed11ccada n/a (/usr/bin/ctr + 0x4cada)#012#7 0x000055aed11c6651 n/a (/usr/bin/ctr + 0x46651)#012#8 0x000055aed11c27a5 n/a (/usr/bin/ctr + 0x427a5)#012#9 0x000055aed11a5edd n/a (/usr/bin/ctr + 0x25edd)#012#10 0x000055aed11d6b52 n/a (/usr/bin/ctr + 0x56b52)#012#11 0x000055aed1210a47 n/a (/usr/bin/ctr + 0x90a47)#012ELF object binary architecture: AMD x86-64
== idm00 (1 distinct, 1 total) ==
Sep 26 17:54:08 idm00 named[4166701]: client @0x7f11980696f8 10.73.240.42#49790: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 26 17:39:28 idmp0 named[1598691]: client @0x7f2d44011478 10.73.240.43#63408: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 1 total) ==
Sep 26 17:28:11 itmon02 sshd[1483508]: error: beginning MaxStartups throttling
== munin (2 distinct, 20 total) ==
Sep 26 17:33:02 munin sudo[4041106]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x10]
Sep 26 17:33:02 munin sudo[4041106]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x10]
== newhonors2 (1 distinct, 24 total) ==
Sep 26 17:13:02 newhonors2 dhcpcd[3193871]: dhcpcd is not running [x24]
== ntop00 (58 distinct, 117211 total) ==
Sep 26 17:05:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6]
Sep 26 17:05:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x6]
Sep 26 17:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 802) ***
Sep 26 17:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 802, QN: 0/55, ET: 0) ***
Sep 26 17:05:07 ntop00 rsyslogd[1208]: file '/var/log/messages'[13] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x55962]
Sep 26 17:05:07 ntop00 rsyslogd[1208]: imjournal: open() failed for path: '/var/lib/rsyslog/imjournal.state.tmp': No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2433 ] [x7380]
Sep 26 17:05:07 ntop00 rsyslogd[1208]: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x53339]
Sep 26 17:05:07 ntop00 rsyslogd[1208]: file '/var/log/maillog'[15] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x223]
Sep 26 17:05:07 ntop00 rsyslogd[1208]: action 'action-3-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x223]
Sep 26 17:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 805) ***
Sep 26 17:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 805, QN: 8274/8274, ET: 0) ***
Sep 26 17:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 805) ***
Sep 26 17:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 805, QN: 55/55, ET: 0) ***
Sep 26 17:14:03 ntop00 rsyslogd[1208]: action 'action-1-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x12]
Sep 26 17:15:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6]
Sep 26 17:15:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x6]
Sep 26 17:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 806) ***
Sep 26 17:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 806, QN: 0/11482, ET: 0) ***
Sep 26 17:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 806) ***
Sep 26 17:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 806, QN: 0/51, ET: 0) ***
Sep 26 17:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 809) ***
Sep 26 17:23:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 809) ***
Sep 26 17:23:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 809, QN: 59/59, ET: 0) ***
Sep 26 17:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 809, QN: 16970/16970, ET: 0) ***
Sep 26 17:25:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 810) ***
Sep 26 17:25:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 810, QN: 0/58, ET: 0) ***
Sep 26 17:25:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 810) ***
Sep 26 17:25:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 810, QN: 0/16972, ET: 0) ***
Sep 26 17:33:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 813) ***
Sep 26 17:33:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 813, QN: 15591/15591, ET: 0) ***
... 28 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 26 17:09:09 outbound00.cs.umd.edu python3[4169402]: ldapdb [x6]
== outbound01.cs.umd.edu (3 distinct, 12 total) ==
Sep 26 17:13:07 outbound01.cs.umd.edu python3[2236152]: ldapdb [x6]
Sep 26 17:28:58 outbound01.cs.umd.edu krb5_child[2240374]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x4]
Sep 26 17:38:45 outbound01.cs.umd.edu krb5_child[2242553]: Client 'backup(a)UMD.EDU' not found in Kerberos database [x2]
== sentry-docker00.cs.umd.edu (34 distinct, 34 total) ==
Sep 26 17:18:55 sentry-docker00.cs.umd.edu systemd-udevd[155560]: link_config: could not get ethtool features for vethc6e21fc
Sep 26 17:18:55 sentry-docker00.cs.umd.edu systemd-udevd[155560]: Could not set offload features of vethc6e21fc: No such device
Sep 26 17:18:56 sentry-docker00.cs.umd.edu systemd-udevd[155593]: Could not generate persistent MAC address for veth01f0a3c: No such file or directory
Sep 26 17:18:56 sentry-docker00.cs.umd.edu systemd-udevd[155594]: Could not generate persistent MAC address for vethc388015: No such file or directory
Sep 26 17:18:56 sentry-docker00.cs.umd.edu systemd-udevd[155597]: Could not generate persistent MAC address for vethde49559: No such file or directory
Sep 26 17:18:56 sentry-docker00.cs.umd.edu systemd-udevd[155598]: Could not generate persistent MAC address for veth7a11789: No such file or directory
Sep 26 17:18:56 sentry-docker00.cs.umd.edu systemd-udevd[155611]: Could not generate persistent MAC address for vethe61a9bf: No such file or directory
Sep 26 17:18:56 sentry-docker00.cs.umd.edu systemd-udevd[155610]: Could not generate persistent MAC address for veth790305e: No such file or directory
Sep 26 17:18:56 sentry-docker00.cs.umd.edu systemd-udevd[155610]: Could not generate persistent MAC address for veth92f56bd: No such file or directory
Sep 26 17:18:56 sentry-docker00.cs.umd.edu systemd-udevd[155600]: Could not generate persistent MAC address for vethe0ab2c5: No such file or directory
Sep 26 17:18:56 sentry-docker00.cs.umd.edu systemd-udevd[155668]: Could not generate persistent MAC address for vethf76a300: No such file or directory
Sep 26 17:18:56 sentry-docker00.cs.umd.edu systemd-udevd[155672]: Could not generate persistent MAC address for veth0e5aa32: No such file or directory
Sep 26 17:39:04 sentry-docker00.cs.umd.edu systemd-udevd[165239]: link_config: could not get ethtool features for veth01f0a3c
Sep 26 17:39:04 sentry-docker00.cs.umd.edu systemd-udevd[165239]: Could not set offload features of veth01f0a3c: No such device
Sep 26 17:39:04 sentry-docker00.cs.umd.edu systemd-udevd[165275]: Could not generate persistent MAC address for veth60ca094: No such file or directory
Sep 26 17:39:04 sentry-docker00.cs.umd.edu systemd-udevd[165276]: Could not generate persistent MAC address for vethd6c78ce: No such file or directory
Sep 26 17:39:04 sentry-docker00.cs.umd.edu systemd-udevd[165279]: Could not generate persistent MAC address for veth7bcc2f7: No such file or directory
Sep 26 17:39:04 sentry-docker00.cs.umd.edu systemd-udevd[165280]: Could not generate persistent MAC address for veth66422d1: No such file or directory
Sep 26 17:39:04 sentry-docker00.cs.umd.edu systemd-udevd[165286]: Could not generate persistent MAC address for veth882d87c: No such file or directory
Sep 26 17:39:04 sentry-docker00.cs.umd.edu systemd-udevd[165295]: Could not generate persistent MAC address for veth313dc4d: No such file or directory
Sep 26 17:39:04 sentry-docker00.cs.umd.edu systemd-udevd[165305]: Could not generate persistent MAC address for vethcfc076b: No such file or directory
Sep 26 17:39:04 sentry-docker00.cs.umd.edu systemd-udevd[165306]: Could not generate persistent MAC address for vethb345a09: No such file or directory
Sep 26 17:39:04 sentry-docker00.cs.umd.edu systemd-udevd[165320]: Could not generate persistent MAC address for veth4721839: No such file or directory
Sep 26 17:39:04 sentry-docker00.cs.umd.edu systemd-udevd[165311]: Could not generate persistent MAC address for veth3d82b5c: No such file or directory
Sep 26 17:59:12 sentry-docker00.cs.umd.edu systemd-udevd[174650]: Could not generate persistent MAC address for veth2d0190e: No such file or directory
Sep 26 17:59:12 sentry-docker00.cs.umd.edu systemd-udevd[174651]: Could not generate persistent MAC address for vethd2d888e: No such file or directory
Sep 26 17:59:12 sentry-docker00.cs.umd.edu systemd-udevd[174654]: Could not generate persistent MAC address for vethf335ea8: No such file or directory
Sep 26 17:59:12 sentry-docker00.cs.umd.edu systemd-udevd[174655]: Could not generate persistent MAC address for vethb009203: No such file or directory
Sep 26 17:59:12 sentry-docker00.cs.umd.edu systemd-udevd[174654]: Could not generate persistent MAC address for vethf9af350: No such file or directory
Sep 26 17:59:12 sentry-docker00.cs.umd.edu systemd-udevd[174655]: Could not generate persistent MAC address for veth09c07d6: No such file or directory
... 4 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 26 17:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 26 17:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 26 17:07:04 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 26 17:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 26 17:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 26 17:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 26 17:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (1 distinct, 1 total) ==
Sep 26 17:18:08 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
== submit26-b9-f3 (10 distinct, 10 total) ==
Sep 26 17:06:45 submit26-b9-f3 setroubleshoot[3563633]: 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
Sep 26 17:06:45 submit26-b9-f3 setroubleshoot[3563633]: 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
Sep 26 17:06:45 submit26-b9-f3 setroubleshoot[3563633]: 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
Sep 26 17:06:45 submit26-b9-f3 setroubleshoot[3563633]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.PEEKpg/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f
Sep 26 17:06:45 submit26-b9-f3 setroubleshoot[3563633]: 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
Sep 26 17:06:45 submit26-b9-f3 setroubleshoot[3563633]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.PEEKpg. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd
Sep 26 17:06:45 submit26-b9-f3 setroubleshoot[3563633]: 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
Sep 26 17:06:45 submit26-b9-f3 setroubleshoot[3563633]: 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
Sep 26 17:06:45 submit26-b9-f3 setroubleshoot[3563633]: 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
Sep 26 17:20:06 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
== submit26-b9-f4 (10 distinct, 13 total) ==
Sep 26 17:24:48 submit26-b9-f4 setroubleshoot[2608143]: 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
Sep 26 17:24:48 submit26-b9-f4 setroubleshoot[2608143]: 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
Sep 26 17:24:48 submit26-b9-f4 setroubleshoot[2608143]: 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 [x2]
Sep 26 17:24:48 submit26-b9-f4 setroubleshoot[2608143]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.O6QBOK/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 [x2]
Sep 26 17:24:48 submit26-b9-f4 setroubleshoot[2608143]: 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 [x2]
Sep 26 17:24:48 submit26-b9-f4 setroubleshoot[2608143]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.O6QBOK. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c
Sep 26 17:24:48 submit26-b9-f4 setroubleshoot[2608143]: 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
Sep 26 17:24:48 submit26-b9-f4 setroubleshoot[2608143]: 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
Sep 26 17:24:48 submit26-b9-f4 setroubleshoot[2608143]: 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
Sep 26 17:38:10 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 7.4683s
Status : exited 0
Output :
Syslog digest — 2026-09-26 17:05 EDT
Processed 119,137 lines, filtered 1,275 (1%). 117,862 unknown (129 distinct) from 19 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 26 17:01:47 b0b02.cs.umd.edu rustdesk[1400816]: cannot open display:
== cheezit.cs.umd.edu (1 distinct, 1 total) ==
Sep 26 16:36:51 cheezit.cs.umd.edu sshd-session[3407893]: error: send_error: write: Connection reset by peer
== idm00 (1 distinct, 1 total) ==
Sep 26 16:54:08 idm00 named[4166701]: client @0x7f11980829a8 10.73.240.42#61394: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 26 16:39:28 idmp0 named[1598691]: client @0x7f2d2c0368e8 10.73.240.43#64708: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 7 total) ==
Sep 26 16:08:08 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x7]
== jaws.cs.umd.edu (3 distinct, 3 total) ==
Sep 26 17:01:50 jaws.cs.umd.edu systemd-coredump[498888]: Process 498873 (podman) of user 0 dumped core.#012#012Stack trace of thread 498873:#012#0 0x000055fd5cb1946e internal/runtime/syscall/linux.Syscall6 (podman + 0x48c46e)#012#1 0x000055fd5cbf9326 syscall.Syscall (podman + 0x56c326)#012#2 0x000055fd5cbf9ed0 syscall.Syscall.abi0 (podman + 0x56ced0)#012#3 0x000055fd5cd6436e github.com/containers/podman/vendor/golang.org/x/sys/unix.OpenTree (podman + 0x6d736e)#012#4 0x000055fd5d3c144b github.com/containers/podman/vendor/github.com/cyphar/filepath-securejoin/p… (podman + 0xd3444b)#012#5 0x000055fd5d3c1354 github.com/containers/podman/vendor/github.com/cyphar/filepath-securejoin/p… (podman + 0xd34354)#012#6 0x000055fd5cbacf8c sync.(*Once).doSlow (podman + 0x51ff8c)#012#7 0x000055fd5cbaceb9 sync.(*Once).Do (podman + 0x51feb9)#012#8 0x000055fd5d3c12c5 gi
thub.com/containers/podman/vendor/github.com/cyphar/filepath-securejoin/pat… (podman + 0xd342c5)#012#9 0x000055fd5d3c28e2 github.com/containers/podman/vendor/github.com/cyphar/filepath-securejoin/p… (podman + 0xd358e2)#012#10 0x000055fd5d3c2cf3 github.com/containers/podman/vendor/github.com/cyphar/filepath-securejoin/p… (podman + 0xd35cf3)#012#11 0x000055fd5d3c1e1c github.com/containers/podman/vendor/github.com/cyphar/filepath-securejoin/p… (podman + 0xd34e1c)#012#12 0x000055fd5d3c1858 github.com/containers/podman/vendor/github.com/cyphar/filepath-securejoin/p… (podman + 0xd34858)#012#13 0x000055fd5cbacf8c sync.(*Once).doSlow (podman + 0x51ff8c)#012#14 0x000055fd5cbaceb9 sync.(*Once).Do (po
dman + 0x51feb9)#012#15 0x000055fd5d3c17c5 github.com/containers/podman/vendor/github.com/cyphar/filepath-securejoin/p… (podman + 0xd347c5)#012#16 0x000055fd5d3c2c9a github.com/containers/podman/vendor/github.com/cyphar/filepath-securejoin/p… (podman + 0xd35c9a)#012#17 0x000055fd5d3c984e github.com/containers/podman/vendor/github.com/opencontainers/selinux/go-se… (podman + 0xd3c84e)#012#18 0x000055fd5d3c9d38 github.com/containers/podman/vendor/github.com/opencontainers/selinux/go-se… (podman + 0xd3cd38)#012#19 0x000055fd5d3c8adf github.com/containers/podman/vendor/github.com/opencontainers/selinux/go-se… (podman + 0xd3badf)#012#20 0x000055fd5d3c8d73 github.com/containers/podman/vendor/github.com/opencontainers/selinux/go-se… (podman + 0xd3bd73)#012#21 0x000055fd
5d5c26cb github.com/containers/podman/vendor/go.podman.io/common/pkg/config.defaultC… (podman + 0xf356cb)#012#22 0x000055fd5d5c60b2 github.com/containers/podman/vendor/go.podman.io/common/pkg/config.newLocked (podman + 0xf390b2)#012#23 0x000055fd5d5c5da5 github.com/containers/podman/vendor/go.podman.io/common/pkg/config.New (podman + 0xf38da5)#012#24 0x000055fd5dd427d3 github.com/containers/podman/cmd/podman/registry.newPodmanConfig (podman + 0x16b57d3)#012#25 0x000055fd5cbacf8c sync.(*Once).doSlow (podman + 0x51ff8c)#012#26 0x000055fd5dd63550 github.com/containers/podman/cmd/podman/common.init (podman + 0x16d6550)#012#27 0x000055fd5cb72af7 runtime.doInit1 (podman + 0x4e5af7)#012#28 0x000055fd5cb63030 runtime.main (podman + 0x4d6030)#012#29 0x000055fd5cba3061 runtime.goexit.abi0 (podman + 0x516061)#012ELF object binary architecture: AMD x86-64
Sep 26 17:01:51 jaws.cs.umd.edu systemd-coredump[498902]: Process 498894 (podman) of user 0 dumped core.#012#012Stack trace of thread 498894:#012#0 0x00005567eac7146e internal/runtime/syscall/linux.Syscall6 (podman + 0x48c46e)#012#1 0x00005567ead51326 syscall.Syscall (podman + 0x56c326)#012#2 0x00005567ead51ed0 syscall.Syscall.abi0 (podman + 0x56ced0)#012#3 0x00005567eaebc36e github.com/containers/podman/vendor/golang.org/x/sys/unix.OpenTree (podman + 0x6d736e)#012#4 0x00005567eb51944b github.com/containers/podman/vendor/github.com/cyphar/filepath-securejoin/p… (podman + 0xd3444b)#012#5 0x00005567eb519354 github.com/containers/podman/vendor/github.com/cyphar/filepath-securejoin/p… (podman + 0xd34354)#012#6 0x00005567ead04f8c sync.(*Once).doSlow (podman + 0x51ff8c)#012#7 0x00005567ead04eb9 sync.(*Once).Do (podman + 0x51feb9)#012#8 0x00005567eb5192c5 gi
thub.com/containers/podman/vendor/github.com/cyphar/filepath-securejoin/pat… (podman + 0xd342c5)#012#9 0x00005567eb51a8e2 github.com/containers/podman/vendor/github.com/cyphar/filepath-securejoin/p… (podman + 0xd358e2)#012#10 0x00005567eb51acf3 github.com/containers/podman/vendor/github.com/cyphar/filepath-securejoin/p… (podman + 0xd35cf3)#012#11 0x00005567eb519e1c github.com/containers/podman/vendor/github.com/cyphar/filepath-securejoin/p… (podman + 0xd34e1c)#012#12 0x00005567eb519858 github.com/containers/podman/vendor/github.com/cyphar/filepath-securejoin/p… (podman + 0xd34858)#012#13 0x00005567ead04f8c sync.(*Once).doSlow (podman + 0x51ff8c)#012#14 0x00005567ead04eb9 sync.(*Once).Do (po
dman + 0x51feb9)#012#15 0x00005567eb5197c5 github.com/containers/podman/vendor/github.com/cyphar/filepath-securejoin/p… (podman + 0xd347c5)#012#16 0x00005567eb51ac9a github.com/containers/podman/vendor/github.com/cyphar/filepath-securejoin/p… (podman + 0xd35c9a)#012#17 0x00005567eb52184e github.com/containers/podman/vendor/github.com/opencontainers/selinux/go-se… (podman + 0xd3c84e)#012#18 0x00005567eb521d38 github.com/containers/podman/vendor/github.com/opencontainers/selinux/go-se… (podman + 0xd3cd38)#012#19 0x00005567eb520adf github.com/containers/podman/vendor/github.com/opencontainers/selinux/go-se… (podman + 0xd3badf)#012#20 0x00005567eb520d73 github.com/containers/podman/vendor/github.com/opencontainers/selinux/go-se… (podman + 0xd3bd73)#012#21 0x00005567
eb71a6cb github.com/containers/podman/vendor/go.podman.io/common/pkg/config.defaultC… (podman + 0xf356cb)#012#22 0x00005567eb71e0b2 github.com/containers/podman/vendor/go.podman.io/common/pkg/config.newLocked (podman + 0xf390b2)#012#23 0x00005567eb71dda5 github.com/containers/podman/vendor/go.podman.io/common/pkg/config.New (podman + 0xf38da5)#012#24 0x00005567ebe9a7d3 github.com/containers/podman/cmd/podman/registry.newPodmanConfig (podman + 0x16b57d3)#012#25 0x00005567ead04f8c sync.(*Once).doSlow (podman + 0x51ff8c)#012#26 0x00005567ebebb550 github.com/containers/podman/cmd/podman/common.init (podman + 0x16d6550)#012#27 0x00005567eaccaaf7 runtime.doInit1 (podman + 0x4e5af7)#012#28 0x00005567eacbb030 runtime.main (podman + 0x4d6030)#012#29 0x00005567eacfb061 runtime.goexit.abi0 (podman + 0x516061)#012ELF object binary architecture: AMD x86-64
Sep 26 17:01:52 jaws.cs.umd.edu systemd-coredump[498924]: Process 498907 (podman) of user 0 dumped core.#012#012Stack trace of thread 498907:#012#0 0x000055e645b0046e internal/runtime/syscall/linux.Syscall6 (podman + 0x48c46e)#012#1 0x000055e645be0326 syscall.Syscall (podman + 0x56c326)#012#2 0x000055e645be0ed0 syscall.Syscall.abi0 (podman + 0x56ced0)#012#3 0x000055e645d4b36e github.com/containers/podman/vendor/golang.org/x/sys/unix.OpenTree (podman + 0x6d736e)#012#4 0x000055e6463a844b github.com/containers/podman/vendor/github.com/cyphar/filepath-securejoin/p… (podman + 0xd3444b)#012#5 0x000055e6463a8354 github.com/containers/podman/vendor/github.com/cyphar/filepath-securejoin/p… (podman + 0xd34354)#012#6 0x000055e645b93f8c sync.(*Once).doSlow (podman + 0x51ff8c)#012#7 0x000055e645b93eb9 sync.(*Once).Do (podman + 0x51feb9)#012#8 0x000055e6463a82c5 gi
thub.com/containers/podman/vendor/github.com/cyphar/filepath-securejoin/pat… (podman + 0xd342c5)#012#9 0x000055e6463a98e2 github.com/containers/podman/vendor/github.com/cyphar/filepath-securejoin/p… (podman + 0xd358e2)#012#10 0x000055e6463a9cf3 github.com/containers/podman/vendor/github.com/cyphar/filepath-securejoin/p… (podman + 0xd35cf3)#012#11 0x000055e6463a8e1c github.com/containers/podman/vendor/github.com/cyphar/filepath-securejoin/p… (podman + 0xd34e1c)#012#12 0x000055e6463a8858 github.com/containers/podman/vendor/github.com/cyphar/filepath-securejoin/p… (podman + 0xd34858)#012#13 0x000055e645b93f8c sync.(*Once).doSlow (podman + 0x51ff8c)#012#14 0x000055e645b93eb9 sync.(*Once).Do (po
dman + 0x51feb9)#012#15 0x000055e6463a87c5 github.com/containers/podman/vendor/github.com/cyphar/filepath-securejoin/p… (podman + 0xd347c5)#012#16 0x000055e6463a9c9a github.com/containers/podman/vendor/github.com/cyphar/filepath-securejoin/p… (podman + 0xd35c9a)#012#17 0x000055e6463b084e github.com/containers/podman/vendor/github.com/opencontainers/selinux/go-se… (podman + 0xd3c84e)#012#18 0x000055e6463b0d38 github.com/containers/podman/vendor/github.com/opencontainers/selinux/go-se… (podman + 0xd3cd38)#012#19 0x000055e6463afadf github.com/containers/podman/vendor/github.com/opencontainers/selinux/go-se… (podman + 0xd3badf)#012#20 0x000055e6463afd73 github.com/containers/podman/vendor/github.com/opencontainers/selinux/go-se… (podman + 0xd3bd73)#012#21 0x000055e6
465a96cb github.com/containers/podman/vendor/go.podman.io/common/pkg/config.defaultC… (podman + 0xf356cb)#012#22 0x000055e6465ad0b2 github.com/containers/podman/vendor/go.podman.io/common/pkg/config.newLocked (podman + 0xf390b2)#012#23 0x000055e6465acda5 github.com/containers/podman/vendor/go.podman.io/common/pkg/config.New (podman + 0xf38da5)#012#24 0x000055e646d297d3 github.com/containers/podman/cmd/podman/registry.newPodmanConfig (podman + 0x16b57d3)#012#25 0x000055e645b93f8c sync.(*Once).doSlow (podman + 0x51ff8c)#012#26 0x000055e646d4a550 github.com/containers/podman/cmd/podman/common.init (podman + 0x16d6550)#012#27 0x000055e645b59af7 runtime.doInit1 (podman + 0x4e5af7)#012#28 0x000055e645b4a030 runtime.main (podman + 0x4d6030)#012#29 0x000055e645b8a061 runtime.goexit.abi0 (podman + 0x516061)#012ELF object binary architecture: AMD x86-64
== krispykreme.cs.umd.edu (2 distinct, 10 total) ==
Sep 26 16:09:32 krispykreme.cs.umd.edu falcon-sensor-bpf[1298]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225 [x5]
Sep 26 16:09:32 krispykreme.cs.umd.edu falcon-sensor-bpf[1298]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225 [x5]
== munin (2 distinct, 6 total) ==
Sep 26 16:08:24 munin sudo[4011439]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x3]
Sep 26 16:08:24 munin sudo[4011439]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x3]
== newhonors2 (1 distinct, 24 total) ==
Sep 26 16:13:03 newhonors2 dhcpcd[3192029]: dhcpcd is not running [x24]
== ntop00 (60 distinct, 117704 total) ==
Sep 26 16:05:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x7]
Sep 26 16:05:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x7]
Sep 26 16:05:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 778) ***
Sep 26 16:05:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 778, QN: 0/7950, ET: 0) ***
Sep 26 16:05:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6]
Sep 26 16:05:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x6]
Sep 26 16:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 778) ***
Sep 26 16:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 778, QN: 0/50, ET: 0) ***
Sep 26 16:05:07 ntop00 rsyslogd[1208]: file '/var/log/messages'[13] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x56173]
Sep 26 16:05:07 ntop00 rsyslogd[1208]: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x53327]
Sep 26 16:05:07 ntop00 rsyslogd[1208]: file '/var/log/maillog'[15] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x233]
Sep 26 16:05:07 ntop00 rsyslogd[1208]: action 'action-3-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x233]
Sep 26 16:05:07 ntop00 rsyslogd[1208]: imjournal: open() failed for path: '/var/lib/rsyslog/imjournal.state.tmp': No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2433 ] [x7661]
Sep 26 16:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 781) ***
Sep 26 16:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 781, QN: 7738/7738, ET: 0) ***
Sep 26 16:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 781) ***
Sep 26 16:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 781, QN: 68/68, ET: 0) ***
Sep 26 16:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 782) ***
Sep 26 16:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 782, QN: 0/8126, ET: 0) ***
Sep 26 16:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 782) ***
Sep 26 16:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 782, QN: 0/63, ET: 0) ***
Sep 26 16:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 785) ***
Sep 26 16:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 785, QN: 7865/7865, ET: 0) ***
Sep 26 16:23:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 785) ***
Sep 26 16:23:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 785, QN: 66/66, ET: 0) ***
Sep 26 16:25:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 786) ***
Sep 26 16:25:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 786, QN: 0/8100, ET: 0) ***
Sep 26 16:25:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 786) ***
Sep 26 16:25:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 786, QN: 0/57, ET: 0) ***
Sep 26 16:33:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 789) ***
... 30 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 26 16:09:09 outbound00.cs.umd.edu python3[4155435]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 26 16:13:07 outbound01.cs.umd.edu python3[2222155]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (34 distinct, 34 total) ==
Sep 26 16:18:30 sentry-docker00.cs.umd.edu systemd-udevd[127307]: link_config: could not get ethtool features for vethdabbc7e
Sep 26 16:18:30 sentry-docker00.cs.umd.edu systemd-udevd[127307]: Could not set offload features of vethdabbc7e: No such device
Sep 26 16:18:31 sentry-docker00.cs.umd.edu systemd-udevd[127343]: Could not generate persistent MAC address for vethe5a58d2: No such file or directory
Sep 26 16:18:31 sentry-docker00.cs.umd.edu systemd-udevd[127344]: Could not generate persistent MAC address for veth7db51ab: No such file or directory
Sep 26 16:18:31 sentry-docker00.cs.umd.edu systemd-udevd[127369]: Could not generate persistent MAC address for veth05f8ba3: No such file or directory
Sep 26 16:18:31 sentry-docker00.cs.umd.edu systemd-udevd[127370]: Could not generate persistent MAC address for vethce85848: No such file or directory
Sep 26 16:18:31 sentry-docker00.cs.umd.edu systemd-udevd[127384]: Could not generate persistent MAC address for veth5a543fe: No such file or directory
Sep 26 16:18:31 sentry-docker00.cs.umd.edu systemd-udevd[127388]: Could not generate persistent MAC address for veth0caa798: No such file or directory
Sep 26 16:18:31 sentry-docker00.cs.umd.edu systemd-udevd[127387]: Could not generate persistent MAC address for vethe7b44f3: No such file or directory
Sep 26 16:18:31 sentry-docker00.cs.umd.edu systemd-udevd[127374]: Could not generate persistent MAC address for vethed2ed46: No such file or directory
Sep 26 16:18:31 sentry-docker00.cs.umd.edu systemd-udevd[127492]: Could not generate persistent MAC address for vethb007a49: No such file or directory
Sep 26 16:18:31 sentry-docker00.cs.umd.edu systemd-udevd[127495]: Could not generate persistent MAC address for vetha7f6292: No such file or directory
Sep 26 16:38:39 sentry-docker00.cs.umd.edu systemd-udevd[136774]: link_config: could not get ethtool features for vethb007a49
Sep 26 16:38:39 sentry-docker00.cs.umd.edu systemd-udevd[136774]: Could not set offload features of vethb007a49: No such device
Sep 26 16:38:39 sentry-docker00.cs.umd.edu systemd-udevd[136808]: Could not generate persistent MAC address for vethdb5ba9c: No such file or directory
Sep 26 16:38:39 sentry-docker00.cs.umd.edu systemd-udevd[136809]: Could not generate persistent MAC address for vethcefc6ce: No such file or directory
Sep 26 16:38:39 sentry-docker00.cs.umd.edu systemd-udevd[136812]: Could not generate persistent MAC address for veth002f2f1: No such file or directory
Sep 26 16:38:39 sentry-docker00.cs.umd.edu systemd-udevd[136813]: Could not generate persistent MAC address for vethd8b7b57: No such file or directory
Sep 26 16:38:39 sentry-docker00.cs.umd.edu systemd-udevd[136826]: Could not generate persistent MAC address for veth0702411: No such file or directory
Sep 26 16:38:39 sentry-docker00.cs.umd.edu systemd-udevd[136835]: Could not generate persistent MAC address for vethb743051: No such file or directory
Sep 26 16:38:39 sentry-docker00.cs.umd.edu systemd-udevd[136838]: Could not generate persistent MAC address for veth7a85799: No such file or directory
Sep 26 16:38:39 sentry-docker00.cs.umd.edu systemd-udevd[136839]: Could not generate persistent MAC address for veth08cfdfe: No such file or directory
Sep 26 16:38:39 sentry-docker00.cs.umd.edu systemd-udevd[136857]: Could not generate persistent MAC address for vethc09ad90: No such file or directory
Sep 26 16:38:39 sentry-docker00.cs.umd.edu systemd-udevd[136856]: Could not generate persistent MAC address for vethd814406: No such file or directory
Sep 26 16:58:47 sentry-docker00.cs.umd.edu systemd-udevd[146207]: Could not generate persistent MAC address for veth7e33d28: No such file or directory
Sep 26 16:58:47 sentry-docker00.cs.umd.edu systemd-udevd[146206]: Could not generate persistent MAC address for vethc6e21fc: No such file or directory
Sep 26 16:58:47 sentry-docker00.cs.umd.edu systemd-udevd[146230]: Could not generate persistent MAC address for veth24997a6: No such file or directory
Sep 26 16:58:47 sentry-docker00.cs.umd.edu systemd-udevd[146226]: Could not generate persistent MAC address for veth5e884c7: No such file or directory
Sep 26 16:58:47 sentry-docker00.cs.umd.edu systemd-udevd[146207]: Could not generate persistent MAC address for vethb64d6c2: No such file or directory
Sep 26 16:58:47 sentry-docker00.cs.umd.edu systemd-udevd[146225]: Could not generate persistent MAC address for vethbac975f: No such file or directory
... 4 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 26 16:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 26 16:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 26 16:07:04 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 26 16:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 26 16:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 26 16:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 26 16:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (1 distinct, 4 total) ==
Sep 26 16:09:11 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x4]
== submit26-b9-f2 (1 distinct, 3 total) ==
Sep 26 16:33:08 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x3]
== submit26-b9-f3 (1 distinct, 3 total) ==
Sep 26 16:14:14 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x3]
== submit26-b9-f4 (1 distinct, 1 total) ==
Sep 26 16:55:09 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
== submit26-b9-fclone (9 distinct, 9 total) ==
Sep 26 16:22:00 submit26-b9-fclone setroubleshoot[538487]: 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 26 16:22:00 submit26-b9-fclone setroubleshoot[538487]: 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 26 16:22:00 submit26-b9-fclone setroubleshoot[538487]: 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 26 16:22:01 submit26-b9-fclone setroubleshoot[538487]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.dS4NUM/repodata/repomd.xml. For complete SELinux messages run: sealert -l 03e2f521-0e7c-481f-8e92-0602c6adeedc
Sep 26 16:22:01 submit26-b9-fclone setroubleshoot[538487]: 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 26 16:22:01 submit26-b9-fclone setroubleshoot[538487]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.dS4NUM. For complete SELinux messages run: sealert -l 887adbf9-2bb9-4009-b800-36ddf9ba0db5
Sep 26 16:22:01 submit26-b9-fclone setroubleshoot[538487]: 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 26 16:22:01 submit26-b9-fclone setroubleshoot[538487]: 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 26 16:22:01 submit26-b9-fclone setroubleshoot[538487]: 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
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 7.4679s
Status : exited 0
Output :
Syslog digest — 2026-09-26 16:05 EDT
Processed 119,216 lines, filtered 1,403 (1%). 117,813 unknown (122 distinct) from 12 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 26 16:01:43 b0b02.cs.umd.edu rustdesk[1385465]: cannot open display:
== idm00 (1 distinct, 1 total) ==
Sep 26 15:54:10 idm00 named[4166701]: client @0x7f11a945b458 10.73.240.42#53865: update '73.10.in-addr.arpa/IN' denied
== idmp0 (2 distinct, 2 total) ==
Sep 26 15:39:27 idmp0 named[1598691]: client @0x7f2d5002a688 10.73.240.43#64884: update '73.10.in-addr.arpa/IN' denied
Sep 26 15:53:05 idmp0 named[1598691]: client @0x7f2d280427b8 10.73.245.12#64201: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 4 total) ==
Sep 26 15:13:59 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x4]
== munin (2 distinct, 4 total) ==
Sep 26 15:08:23 munin sudo[3989713]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x2]
Sep 26 15:08:23 munin sudo[3989713]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x2]
== newhonors2 (1 distinct, 24 total) ==
Sep 26 15:13:03 newhonors2 dhcpcd[3190204]: dhcpcd is not running [x24]
== ntop00 (68 distinct, 117690 total) ==
Sep 26 15:05:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x9]
Sep 26 15:05:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x9]
Sep 26 15:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 754) ***
Sep 26 15:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 754, QN: 0/79, ET: 0) ***
Sep 26 15:05:07 ntop00 rsyslogd[1208]: file '/var/log/messages'[13] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x56122]
Sep 26 15:05:07 ntop00 rsyslogd[1208]: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x53350]
Sep 26 15:05:07 ntop00 rsyslogd[1208]: file '/var/log/maillog'[15] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x224]
Sep 26 15:05:07 ntop00 rsyslogd[1208]: action 'action-3-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x224]
Sep 26 15:05:07 ntop00 rsyslogd[1208]: imjournal: open() failed for path: '/var/lib/rsyslog/imjournal.state.tmp': No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2433 ] [x7674]
Sep 26 15:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 756) ***
Sep 26 15:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 756, QN: 0/67, ET: 0) ***
Sep 26 15:10:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x8]
Sep 26 15:10:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x8]
Sep 26 15:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 756) ***
Sep 26 15:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 756, QN: 0/7866, ET: 0) ***
Sep 26 15:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 757) ***
Sep 26 15:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 757, QN: 8809/8809, ET: 0) ***
Sep 26 15:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 757) ***
Sep 26 15:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 757, QN: 59/59, ET: 0) ***
Sep 26 15:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 758) ***
Sep 26 15:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 758, QN: 0/8552, ET: 0) ***
Sep 26 15:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 758) ***
Sep 26 15:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 758, QN: 0/49, ET: 0) ***
Sep 26 15:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 760) ***
Sep 26 15:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 760, QN: 0/67, ET: 0) ***
Sep 26 15:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 760) ***
Sep 26 15:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 760, QN: 0/8289, ET: 0) ***
Sep 26 15:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 761) ***
Sep 26 15:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 761, QN: 7776/7776, ET: 0) ***
Sep 26 15:23:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 761) ***
... 38 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 26 15:09:09 outbound00.cs.umd.edu python3[4141435]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 26 15:13:07 outbound01.cs.umd.edu python3[2208129]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 26 15:18:05 sentry-docker00.cs.umd.edu systemd-udevd[98219]: link_config: could not get ethtool features for veth7b2b189
Sep 26 15:18:05 sentry-docker00.cs.umd.edu systemd-udevd[98219]: Could not set offload features of veth7b2b189: No such device
Sep 26 15:18:06 sentry-docker00.cs.umd.edu systemd-udevd[98318]: Could not generate persistent MAC address for veth7167805: No such file or directory
Sep 26 15:18:06 sentry-docker00.cs.umd.edu systemd-udevd[98319]: Could not generate persistent MAC address for veth1a05ca9: No such file or directory
Sep 26 15:18:06 sentry-docker00.cs.umd.edu systemd-udevd[98322]: Could not generate persistent MAC address for veth419f80c: No such file or directory
Sep 26 15:18:06 sentry-docker00.cs.umd.edu systemd-udevd[98323]: Could not generate persistent MAC address for veth963d846: No such file or directory
Sep 26 15:18:06 sentry-docker00.cs.umd.edu systemd-udevd[98327]: Could not generate persistent MAC address for veth63b20a2: No such file or directory
Sep 26 15:18:06 sentry-docker00.cs.umd.edu systemd-udevd[98322]: Could not generate persistent MAC address for veth06b3f29: No such file or directory
Sep 26 15:18:06 sentry-docker00.cs.umd.edu systemd-udevd[98327]: Could not generate persistent MAC address for vethb5e2d8d: No such file or directory
Sep 26 15:18:06 sentry-docker00.cs.umd.edu systemd-udevd[98325]: Could not generate persistent MAC address for veth4829401: No such file or directory
Sep 26 15:18:06 sentry-docker00.cs.umd.edu systemd-udevd[98322]: Could not generate persistent MAC address for veth37d59ba: No such file or directory
Sep 26 15:18:06 sentry-docker00.cs.umd.edu systemd-udevd[98327]: Could not generate persistent MAC address for veth347765b: No such file or directory
Sep 26 15:38:14 sentry-docker00.cs.umd.edu systemd-udevd[108411]: link_config: could not set ethtool features for veth06b3f29
Sep 26 15:38:14 sentry-docker00.cs.umd.edu systemd-udevd[108411]: Could not set offload features of veth06b3f29: Operation not permitted
Sep 26 15:38:14 sentry-docker00.cs.umd.edu systemd-udevd[108437]: Could not generate persistent MAC address for veth1f75c77: No such file or directory
Sep 26 15:38:14 sentry-docker00.cs.umd.edu systemd-udevd[108436]: Could not generate persistent MAC address for veth06ca82d: No such file or directory
Sep 26 15:38:14 sentry-docker00.cs.umd.edu systemd-udevd[108462]: Could not generate persistent MAC address for veth76f43d6: No such file or directory
Sep 26 15:38:14 sentry-docker00.cs.umd.edu systemd-udevd[108463]: Could not generate persistent MAC address for veth3e6e11c: No such file or directory
Sep 26 15:38:14 sentry-docker00.cs.umd.edu systemd-udevd[108481]: Could not generate persistent MAC address for vetha13fe53: No such file or directory
Sep 26 15:38:14 sentry-docker00.cs.umd.edu systemd-udevd[108487]: Could not generate persistent MAC address for vethff07b65: No such file or directory
Sep 26 15:38:14 sentry-docker00.cs.umd.edu systemd-udevd[108473]: Could not generate persistent MAC address for veth0b45a9f: No such file or directory
Sep 26 15:38:14 sentry-docker00.cs.umd.edu systemd-udevd[108474]: Could not generate persistent MAC address for veth6feca00: No such file or directory
Sep 26 15:38:14 sentry-docker00.cs.umd.edu systemd-udevd[108473]: Could not generate persistent MAC address for vethe353561: No such file or directory
Sep 26 15:38:14 sentry-docker00.cs.umd.edu systemd-udevd[108474]: Could not generate persistent MAC address for vethfc0996b: No such file or directory
Sep 26 15:58:22 sentry-docker00.cs.umd.edu systemd-udevd[117758]: link_config: could not get ethtool features for vetha13fe53
Sep 26 15:58:22 sentry-docker00.cs.umd.edu systemd-udevd[117758]: Could not set offload features of vetha13fe53: No such device
Sep 26 15:58:22 sentry-docker00.cs.umd.edu systemd-udevd[117853]: Could not generate persistent MAC address for vethb5cab3d: No such file or directory
Sep 26 15:58:22 sentry-docker00.cs.umd.edu systemd-udevd[117854]: Could not generate persistent MAC address for vethc817e78: No such file or directory
Sep 26 15:58:22 sentry-docker00.cs.umd.edu systemd-udevd[117857]: Could not generate persistent MAC address for vethdabbc7e: No such file or directory
Sep 26 15:58:22 sentry-docker00.cs.umd.edu systemd-udevd[117858]: Could not generate persistent MAC address for veth1f234e9: No such file or directory
... 6 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 26 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 26 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 26 15:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 26 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 26 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 26 15:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 26 15:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f3 (1 distinct, 1 total) ==
Sep 26 15:49:06 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
1
0