Command: /usr/local/sbin/syslog-digest.py
Time : 7.4761s
Status : exited 0
Output :
Syslog digest — 2026-09-26 05:05 EDT
Processed 109,587 lines, filtered 2,498 (2%). 107,089 unknown (217 distinct) from 19 host(s).
== abadi-computer (2 distinct, 2 total) ==
Sep 26 04:15:00 abadi-computer nologin[1005831]: Attempted login by UNKNOWN (UID: 65534) on UNKNOWN
Sep 26 04:15:00 abadi-computer pipewire[1005829]: mod.jackdbus-detect: Failed to receive jackdbus reply: org.freedesktop.DBus.Error.ServiceUnknown: The name org.jackaudio.service was not provided by any .service files
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 26 05:01:02 b0b02.cs.umd.edu rustdesk[1216876]: cannot open display:
== cheezit.cs.umd.edu (6 distinct, 12 total) ==
Sep 26 04:15:46 cheezit.cs.umd.edu sshd-session[3234426]: error: kex_protocol_error: type 20 seq 2 [preauth] [x2]
Sep 26 04:15:46 cheezit.cs.umd.edu sshd-session[3234426]: error: kex_protocol_error: type 30 seq 3 [preauth] [x2]
Sep 26 04:15:47 cheezit.cs.umd.edu sshd-session[3234426]: error: kex_protocol_error: type 20 seq 4 [preauth] [x2]
Sep 26 04:15:47 cheezit.cs.umd.edu sshd-session[3234426]: error: kex_protocol_error: type 30 seq 5 [preauth] [x2]
Sep 26 04:15:49 cheezit.cs.umd.edu sshd-session[3234426]: error: kex_protocol_error: type 20 seq 6 [preauth] [x2]
Sep 26 04:15:49 cheezit.cs.umd.edu sshd-session[3234426]: error: kex_protocol_error: type 30 seq 7 [preauth] [x2]
== forge00 (1 distinct, 1 total) ==
Sep 26 04:09:02 forge00 (httpd)[1231979]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
== galax (53 distinct, 54 total) ==
Sep 26 04:21:42 galax puppet-agent[105774]: Could not update: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold --force-yes install choria=0.29.4+resolute' returned 100: W: --force-yes is deprecated, use one of the options starting with --allow instead.
Sep 26 04:21:42 galax puppet-agent[105774]: E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. [x2]
Sep 26 04:21:42 galax puppet-agent[105774]: (/Stage[main]/Choria::Install/Package[choria]/ensure) change from 'absent' to '0.29.4+resolute' failed: Could not update: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold --force-yes install choria=0.29.4+resolute' returned 100: W: --force-yes is deprecated, use one of the options starting with --allow instead.
Sep 26 04:21:42 galax puppet-agent[105774]: (/Stage[main]/Choria::Install/Package[choria]/ensure) E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. (corrective)
Sep 26 04:21:42 galax puppet-agent[105774]: (/Stage[main]/Choria::Config/File[/etc/choria]) Skipping because of failed dependencies
Sep 26 04:21:42 galax puppet-agent[105774]: (/Stage[main]/Choria::Config/File[/etc/choria/policies]) Skipping because of failed dependencies
Sep 26 04:21:42 galax puppet-agent[105774]: (/Stage[main]/Choria::Config/File[/etc/choria/policies/rego]) Skipping because of failed dependencies
Sep 26 04:21:42 galax puppet-agent[105774]: (/Stage[main]/Choria::Config/File[/etc/choria/plugin.d]) Skipping because of failed dependencies
Sep 26 04:21:42 galax puppet-agent[105774]: (/Stage[main]/Choria::Config/File[/etc/choria/overrides.json]) Skipping because of failed dependencies
Sep 26 04:21:42 galax puppet-agent[105774]: (/Stage[main]/Choria::Config/File[/etc/choria/machine]) Skipping because of failed dependencies
Sep 26 04:21:42 galax puppet-agent[105774]: (/Stage[main]/Choria::Config/File[/usr/bin/choria_mcollective_agent_compat.rb]) Skipping because of failed dependencies
Sep 26 04:21:42 galax puppet-agent[105774]: (/Stage[main]/Choria::Config/File[/etc/choria/server.conf]) Skipping because of failed dependencies
Sep 26 04:21:42 galax puppet-agent[105774]: (/Stage[main]/Mcollective::Config/File[/etc/choria/server.cfg]) Skipping because of failed dependencies
Sep 26 04:21:42 galax puppet-agent[105774]: (/Stage[main]/Mcollective::Config/File[/etc/choria/client.cfg]) Skipping because of failed dependencies
Sep 26 04:21:42 galax puppet-agent[105774]: (/Stage[main]/Mcollective::Config/File[/etc/choria/policies/choria_util.policy]) Skipping because of failed dependencies
Sep 26 04:21:42 galax puppet-agent[105774]: (/Stage[main]/Mcollective::Config/File[/etc/choria/policies/rpcutil.policy]) Skipping because of failed dependencies
Sep 26 04:21:42 galax puppet-agent[105774]: (/Stage[main]/Mcollective::Config/File[/etc/choria/policies/scout.policy]) Skipping because of failed dependencies
Sep 26 04:21:42 galax puppet-agent[105774]: (/Stage[main]/Mcollective::Config/File[/etc/choria/policies/rego/default.rego]) Skipping because of failed dependencies
Sep 26 04:21:42 galax puppet-agent[105774]: Could not update: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold --force-yes install openvox-agent=8.27.0-1+ubuntu26.04' returned 100: W: --force-yes is deprecated, use one of the options starting with --allow instead.
Sep 26 04:21:42 galax puppet-agent[105774]: (/Stage[main]/Puppet::Agent::Install/Package[openvox-agent]/ensure) change from '8.29.0-1+ubuntu26.04' to '8.27.0-1+ubuntu26.04' failed: Could not update: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold --force-yes install openvox-agent=8.27.0-1+ubuntu26.04' returned 100: W: --force-yes is deprecated, use one of the options starting with --allow instead.
Sep 26 04:21:42 galax puppet-agent[105774]: (/Stage[main]/Puppet::Agent::Install/Package[openvox-agent]/ensure) E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. (corrective)
Sep 26 04:21:43 galax puppet-agent[105774]: (/Stage[main]/Choria::Config/Concat[/etc/choria/policies/groups]/Concat_file[/etc/choria/policies/groups]) Skipping because of failed dependencies
Sep 26 04:21:43 galax puppet-agent[105774]: (/Stage[main]/Choria::Config/Concat[/etc/choria/policies/groups]/File[/etc/choria/policies/groups]) Skipping because of failed dependencies
Sep 26 04:21:43 galax puppet-agent[105774]: (/Stage[main]/Mcollective::Config/Mcollective::Config_file[/etc/choria/client.conf]/File[/etc/choria/client.conf]) Skipping because of failed dependencies
Sep 26 04:21:43 galax puppet-agent[105774]: (/Stage[main]/Mcollective::Config/Mcollective::Config_file[/etc/choria/choria-shim.cfg]/File[/etc/choria/choria-shim.cfg]) Skipping because of failed dependencies
Sep 26 04:21:43 galax puppet-agent[105774]: (/Stage[main]/Mcollective::Facts/Exec[mcollective_facts_yaml_refresh]) Skipping because of failed dependencies
Sep 26 04:21:44 galax puppet-agent[105774]: (/Stage[main]/Mcollective_agent_puppet/Mcollective::Module_plugin[mcollective_agent_puppet]/File[/etc/choria/policies/puppet.policy]) Skipping because of failed dependencies
Sep 26 04:21:44 galax puppet-agent[105774]: (/Stage[main]/Mcollective_agent_service/Mcollective::Module_plugin[mcollective_agent_service]/File[/etc/choria/policies/service.policy]) Skipping because of failed dependencies
Sep 26 04:21:44 galax puppet-agent[105774]: (/Stage[main]/Mcollective_agent_package/Mcollective::Module_plugin[mcollective_agent_package]/File[/etc/choria/policies/package.policy]) Skipping because of failed dependencies
Sep 26 04:21:44 galax puppet-agent[105774]: (/Stage[main]/Mcollective_agent_filemgr/Mcollective::Module_plugin[mcollective_agent_filemgr]/File[/etc/choria/policies/filemgr.policy]) Skipping because of failed dependencies
... 23 more distinct messages not shown
== idm00 (1 distinct, 1 total) ==
Sep 26 04:54:08 idm00 named[4166701]: client @0x7f11980104c8 10.73.240.42#51285: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 26 04:39:29 idmp0 named[1598691]: client @0x7f2d14025948 10.73.240.43#51963: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 3 total) ==
Sep 26 04:32:59 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x3]
== krispykreme.cs.umd.edu (6 distinct, 12 total) ==
Sep 26 04:15:46 krispykreme.cs.umd.edu sshd-session[2700096]: error: kex_protocol_error: type 20 seq 2 [preauth] [x2]
Sep 26 04:15:46 krispykreme.cs.umd.edu sshd-session[2700096]: error: kex_protocol_error: type 30 seq 3 [preauth] [x2]
Sep 26 04:15:48 krispykreme.cs.umd.edu sshd-session[2700096]: error: kex_protocol_error: type 20 seq 4 [preauth] [x2]
Sep 26 04:15:48 krispykreme.cs.umd.edu sshd-session[2700096]: error: kex_protocol_error: type 30 seq 5 [preauth] [x2]
Sep 26 04:15:50 krispykreme.cs.umd.edu sshd-session[2700096]: error: kex_protocol_error: type 20 seq 6 [preauth] [x2]
Sep 26 04:15:50 krispykreme.cs.umd.edu sshd-session[2700096]: error: kex_protocol_error: type 30 seq 7 [preauth] [x2]
== munin (2 distinct, 48 total) ==
Sep 26 04:18:53 munin sudo[3753637]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x24]
Sep 26 04:18:53 munin sudo[3753637]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x24]
== newhonors2 (1 distinct, 24 total) ==
Sep 26 04:13:03 newhonors2 dhcpcd[3169176]: dhcpcd is not running [x24]
== ntop00 (85 distinct, 106832 total) ==
Sep 26 04:05:09 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 ] [x50808]
Sep 26 04:05:09 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 ] [x47971]
Sep 26 04: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 ] [x7597]
Sep 26 04:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 491) ***
Sep 26 04:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 491, QN: 5179/5179, ET: 0) ***
Sep 26 04:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 491) ***
Sep 26 04:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 491, QN: 56/56, ET: 0) ***
Sep 26 04:10:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x11]
Sep 26 04:10:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x11]
Sep 26 04:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 492) ***
Sep 26 04:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 492, QN: 0/49, ET: 0) ***
Sep 26 04:10:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x12]
Sep 26 04:10:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x12]
Sep 26 04:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 492) ***
Sep 26 04:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 492, QN: 0/5029, ET: 0) ***
Sep 26 04:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 493) ***
Sep 26 04:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 493, QN: 5837/5837, ET: 0) ***
Sep 26 04:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 493) ***
Sep 26 04:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 493, QN: 69/69, ET: 0) ***
Sep 26 04:14:01 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 ] [x15]
Sep 26 04:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 494) ***
Sep 26 04:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 494, QN: 0/6244, ET: 0) ***
Sep 26 04:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 494) ***
Sep 26 04:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 494, QN: 0/79, ET: 0) ***
Sep 26 04:15:15 ntop00 cronjob[544326]: 3127dca8461bf8e2ab85c7c69fb9b50d: run3 failed to run command: Error in tempfile() using template /tmp/XXXXXXXXXX: Could not create temp file /tmp/Jbsc2uEu5d: No space left on device at /usr/local/share/perl5/5.40/IPC/Run3.pm line 128.<LF>
Sep 26 04:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 495) ***
Sep 26 04:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 495, QN: 7041/7041, ET: 0) ***
Sep 26 04:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 495) ***
Sep 26 04:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 495, QN: 91/91, ET: 0) ***
Sep 26 04:19:15 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 ] [x160]
... 55 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 26 04:09:09 outbound00.cs.umd.edu python3[3986477]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 26 04:13:06 outbound01.cs.umd.edu python3[2051897]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (34 distinct, 34 total) ==
Sep 26 04:13:31 sentry-docker00.cs.umd.edu systemd-udevd[3977722]: Could not generate persistent MAC address for vetha167b12: No such file or directory
Sep 26 04:13:31 sentry-docker00.cs.umd.edu systemd-udevd[3977723]: Could not generate persistent MAC address for vethd1a935f: No such file or directory
Sep 26 04:13:31 sentry-docker00.cs.umd.edu systemd-udevd[3977726]: Could not generate persistent MAC address for veth2ad4d22: No such file or directory
Sep 26 04:13:31 sentry-docker00.cs.umd.edu systemd-udevd[3977727]: Could not generate persistent MAC address for veth79df0ad: No such file or directory
Sep 26 04:13:31 sentry-docker00.cs.umd.edu systemd-udevd[3977750]: Could not generate persistent MAC address for veth8a4c1ca: No such file or directory
Sep 26 04:13:31 sentry-docker00.cs.umd.edu systemd-udevd[3977751]: Could not generate persistent MAC address for veth808c3de: No such file or directory
Sep 26 04:13:31 sentry-docker00.cs.umd.edu systemd-udevd[3977756]: Could not generate persistent MAC address for vethbc165e3: No such file or directory
Sep 26 04:13:31 sentry-docker00.cs.umd.edu systemd-udevd[3977761]: Could not generate persistent MAC address for vetha0a9799: No such file or directory
Sep 26 04:13:31 sentry-docker00.cs.umd.edu systemd-udevd[3977815]: Could not generate persistent MAC address for vethf6d0c68: No such file or directory
Sep 26 04:13:31 sentry-docker00.cs.umd.edu systemd-udevd[3977822]: Could not generate persistent MAC address for vethdd8e5e1: No such file or directory
Sep 26 04:33:39 sentry-docker00.cs.umd.edu systemd-udevd[3987266]: link_config: could not get ethtool features for veth2ad4d22
Sep 26 04:33:39 sentry-docker00.cs.umd.edu systemd-udevd[3987266]: Could not set offload features of veth2ad4d22: No such device
Sep 26 04:33:39 sentry-docker00.cs.umd.edu systemd-udevd[3987303]: Could not generate persistent MAC address for veth7faf374: No such file or directory
Sep 26 04:33:39 sentry-docker00.cs.umd.edu systemd-udevd[3987304]: Could not generate persistent MAC address for veth0816bf3: No such file or directory
Sep 26 04:33:39 sentry-docker00.cs.umd.edu systemd-udevd[3987307]: Could not generate persistent MAC address for vethe338fa7: No such file or directory
Sep 26 04:33:39 sentry-docker00.cs.umd.edu systemd-udevd[3987309]: Could not generate persistent MAC address for veth1734fbd: No such file or directory
Sep 26 04:33:39 sentry-docker00.cs.umd.edu systemd-udevd[3987327]: Could not generate persistent MAC address for vethef91582: No such file or directory
Sep 26 04:33:39 sentry-docker00.cs.umd.edu systemd-udevd[3987304]: Could not generate persistent MAC address for veth7882a5a: No such file or directory
Sep 26 04:33:40 sentry-docker00.cs.umd.edu systemd-udevd[3987327]: Could not generate persistent MAC address for veth5d41cf6: No such file or directory
Sep 26 04:33:40 sentry-docker00.cs.umd.edu systemd-udevd[3987304]: Could not generate persistent MAC address for veth3db9e10: No such file or directory
Sep 26 04:33:40 sentry-docker00.cs.umd.edu systemd-udevd[3987327]: Could not generate persistent MAC address for veth1b08208: No such file or directory
Sep 26 04:33:40 sentry-docker00.cs.umd.edu systemd-udevd[3987310]: Could not generate persistent MAC address for vethccc0220: No such file or directory
Sep 26 04:53:48 sentry-docker00.cs.umd.edu systemd-udevd[3996682]: link_config: could not get ethtool features for veth1b08208
Sep 26 04:53:48 sentry-docker00.cs.umd.edu systemd-udevd[3996682]: Could not set offload features of veth1b08208: No such device
Sep 26 04:53:48 sentry-docker00.cs.umd.edu systemd-udevd[3996713]: Could not generate persistent MAC address for veth33e2c79: No such file or directory
Sep 26 04:53:48 sentry-docker00.cs.umd.edu systemd-udevd[3996714]: Could not generate persistent MAC address for veth1fe59f5: No such file or directory
Sep 26 04:53:48 sentry-docker00.cs.umd.edu systemd-udevd[3996717]: Could not generate persistent MAC address for veth424973b: No such file or directory
Sep 26 04:53:48 sentry-docker00.cs.umd.edu systemd-udevd[3996718]: Could not generate persistent MAC address for vethcda1d04: No such file or directory
Sep 26 04:53:48 sentry-docker00.cs.umd.edu systemd-udevd[3996717]: Could not generate persistent MAC address for veth7629960: No such file or directory
Sep 26 04:53:48 sentry-docker00.cs.umd.edu systemd-udevd[3996718]: Could not generate persistent MAC address for veth6bf4238: No such file or directory
... 4 more distinct messages not shown
== smokeping-slave (1 distinct, 1 total) ==
Sep 26 04:15:31 smokeping-slave nologin[2651977]: Attempted login by UNKNOWN (UID: 65534) on UNKNOWN
== strawberry (9 distinct, 40 total) ==
Sep 26 04: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 04: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 04:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 26 04: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 04: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 04:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 26 04:15:04 strawberry nologin[3653538]: Attempted login by UNKNOWN (UID: 65534) on UNKNOWN
Sep 26 04:15:04 strawberry pipewire[3653537]: mod.jackdbus-detect: Failed to receive jackdbus reply: org.freedesktop.DBus.Error.ServiceUnknown: The name org.jackaudio.service was not provided by any .service files
Sep 26 04:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-fclone (9 distinct, 9 total) ==
Sep 26 04:22:00 submit26-b9-fclone setroubleshoot[509329]: 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 04:22:00 submit26-b9-fclone setroubleshoot[509329]: 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 04:22:00 submit26-b9-fclone setroubleshoot[509329]: 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 04:22:00 submit26-b9-fclone setroubleshoot[509329]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.96afVs/repodata/repomd.xml. For complete SELinux messages run: sealert -l 03e2f521-0e7c-481f-8e92-0602c6adeedc
Sep 26 04:22:00 submit26-b9-fclone setroubleshoot[509329]: 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 04:22:00 submit26-b9-fclone setroubleshoot[509329]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.96afVs. For complete SELinux messages run: sealert -l 887adbf9-2bb9-4009-b800-36ddf9ba0db5
Sep 26 04:22:00 submit26-b9-fclone setroubleshoot[509329]: 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 04:22:00 submit26-b9-fclone setroubleshoot[509329]: 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 04:22:00 submit26-b9-fclone setroubleshoot[509329]: 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
== wraith (2 distinct, 2 total) ==
Sep 26 04:45:24 wraith kernel: workqueue: i915_hpd_poll_init_work [i915] hogged CPU for >10000us 2051 times, consider switching to WQ_UNBOUND
Sep 26 04:46:23 wraith kernel: workqueue: output_poll_execute hogged CPU for >10000us 2051 times, consider switching to WQ_UNBOUND
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 2.9329s
Status : exited 0
Output :
Syslog digest — 2026-09-26 04:05 EDT
Processed 47,685 lines, filtered 1,504 (3%). 46,181 unknown (177 distinct) from 17 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 26 04:01:01 b0b02.cs.umd.edu rustdesk[1201280]: cannot open display:
== biggulp.cs.umd.edu (6 distinct, 6 total) ==
Sep 26 03:57:15 biggulp.cs.umd.edu sshd-session[130985]: error: kex_protocol_error: type 20 seq 2 [preauth]
Sep 26 03:57:15 biggulp.cs.umd.edu sshd-session[130985]: error: kex_protocol_error: type 30 seq 3 [preauth]
Sep 26 03:57:17 biggulp.cs.umd.edu sshd-session[130985]: error: kex_protocol_error: type 20 seq 4 [preauth]
Sep 26 03:57:17 biggulp.cs.umd.edu sshd-session[130985]: error: kex_protocol_error: type 30 seq 5 [preauth]
Sep 26 03:57:19 biggulp.cs.umd.edu sshd-session[130985]: error: kex_protocol_error: type 20 seq 6 [preauth]
Sep 26 03:57:19 biggulp.cs.umd.edu sshd-session[130985]: error: kex_protocol_error: type 30 seq 7 [preauth]
== idm00 (1 distinct, 1 total) ==
Sep 26 03:54:08 idm00 named[4166701]: client @0x7f11a40662f8 10.73.240.42#56698: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 26 03:39:29 idmp0 named[1598691]: client @0x7f2d3001d0e8 10.73.240.43#51187: update '73.10.in-addr.arpa/IN' denied
== itmon02 (2 distinct, 4 total) ==
Sep 26 03:15:04 itmon02 (httpd)[2924071]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
Sep 26 03:17:56 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x3]
== kadath.cs.umd.edu (1 distinct, 1 total) ==
Sep 26 03:47:32 kadath.cs.umd.edu puppet-agent[2531433]: (Facter) invalid or malformed lldp data: MalformedDataError: no lldp interface data found
== krispykreme.cs.umd.edu (6 distinct, 6 total) ==
Sep 26 03:53:22 krispykreme.cs.umd.edu sshd-session[2694226]: error: kex_protocol_error: type 20 seq 2 [preauth]
Sep 26 03:53:22 krispykreme.cs.umd.edu sshd-session[2694226]: error: kex_protocol_error: type 30 seq 3 [preauth]
Sep 26 03:53:25 krispykreme.cs.umd.edu sshd-session[2694226]: error: kex_protocol_error: type 20 seq 4 [preauth]
Sep 26 03:53:25 krispykreme.cs.umd.edu sshd-session[2694226]: error: kex_protocol_error: type 30 seq 5 [preauth]
Sep 26 03:53:27 krispykreme.cs.umd.edu sshd-session[2694226]: error: kex_protocol_error: type 20 seq 6 [preauth]
Sep 26 03:53:27 krispykreme.cs.umd.edu sshd-session[2694226]: error: kex_protocol_error: type 30 seq 7 [preauth]
== librenms (1 distinct, 1 total) ==
Sep 26 03:47:03 librenms (httpd)[2565772]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
== munin (2 distinct, 8 total) ==
Sep 26 03:08:58 munin sudo[3727599]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x4]
Sep 26 03:08:58 munin sudo[3727599]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x4]
== netbox (1 distinct, 1 total) ==
Sep 26 03:08:03 netbox (httpd)[696074]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
== netman.cs.umd.edu (2 distinct, 3 total) ==
Sep 26 03:30:56 netman.cs.umd.edu krb5_child[847167]: No credentials cache found
Sep 26 03:39:04 netman.cs.umd.edu krb5_child[848836]: Preauthentication failed [x2]
== newhonors2 (1 distinct, 24 total) ==
Sep 26 03:13:02 newhonors2 dhcpcd[3167313]: dhcpcd is not running [x24]
== ntop00 (104 distinct, 46034 total) ==
Sep 26 03:05:01 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 ] [x21915]
Sep 26 03:05:01 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 ] [x20717]
Sep 26 03:05:01 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 ] [x3241]
Sep 26 03:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 467) ***
Sep 26 03:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 467, QN: 5502/5502, ET: 0) ***
Sep 26 03:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 467) ***
Sep 26 03:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 467, QN: 60/60, ET: 0) ***
Sep 26 03:10:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x12]
Sep 26 03:10:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x12]
Sep 26 03:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 468) ***
Sep 26 03:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 468, QN: 0/50, ET: 0) ***
Sep 26 03:10:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x12]
Sep 26 03:10:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x12]
Sep 26 03:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 468) ***
Sep 26 03:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 468, QN: 0/5384, ET: 0) ***
Sep 26 03:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 469) ***
Sep 26 03:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 469, QN: 4757/4757, ET: 0) ***
Sep 26 03:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 469) ***
Sep 26 03:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 469, QN: 66/66, ET: 0) ***
Sep 26 03:14:01 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 ] [x17]
Sep 26 03:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 470) ***
Sep 26 03:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 470, QN: 0/5006, ET: 0) ***
Sep 26 03:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 470) ***
Sep 26 03:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 470, QN: 0/82, ET: 0) ***
Sep 26 03:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 471) ***
Sep 26 03:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 471, QN: 5517/5517, ET: 0) ***
Sep 26 03:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 471) ***
Sep 26 03:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 471, QN: 59/59, ET: 0) ***
Sep 26 03:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 472) ***
Sep 26 03:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 472, QN: 0/5408, ET: 0) ***
... 74 more distinct messages not shown
== outbound00.cs.umd.edu (4 distinct, 10 total) ==
Sep 26 03:09:09 outbound00.cs.umd.edu python3[3971740]: ldapdb [x7]
Sep 26 03:24:10 outbound00.cs.umd.edu systemd[1]: Configuration file /usr/lib/systemd/system/authentication_milter.service is marked executable. Please remove executable permission bits. Proceeding anyway.
Sep 26 03:54:02 outbound00.cs.umd.edu krb5_child[3982439]: Preauthentication failed
Sep 26 03:57:38 outbound00.cs.umd.edu krb5_child[3983881]: Client 'admin(a)UMD.EDU' not found in Kerberos database
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 26 03:13:06 outbound01.cs.umd.edu python3[2037843]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 26 03:13:06 sentry-docker00.cs.umd.edu systemd-udevd[3949400]: link_config: could not get ethtool features for veth6d96a7a
Sep 26 03:13:06 sentry-docker00.cs.umd.edu systemd-udevd[3949400]: Could not set offload features of veth6d96a7a: No such device
Sep 26 03:13:06 sentry-docker00.cs.umd.edu systemd-udevd[3949422]: Could not generate persistent MAC address for vethffbf0bb: No such file or directory
Sep 26 03:13:06 sentry-docker00.cs.umd.edu systemd-udevd[3949423]: Could not generate persistent MAC address for vethc4cc12c: No such file or directory
Sep 26 03:13:06 sentry-docker00.cs.umd.edu systemd-udevd[3949486]: Could not generate persistent MAC address for veth8d74f40: No such file or directory
Sep 26 03:13:06 sentry-docker00.cs.umd.edu systemd-udevd[3949487]: Could not generate persistent MAC address for veth2cd7ba7: No such file or directory
Sep 26 03:13:06 sentry-docker00.cs.umd.edu systemd-udevd[3949508]: Could not generate persistent MAC address for vethc2aef29: No such file or directory
Sep 26 03:13:06 sentry-docker00.cs.umd.edu systemd-udevd[3949496]: Could not generate persistent MAC address for veth96dd921: No such file or directory
Sep 26 03:13:06 sentry-docker00.cs.umd.edu systemd-udevd[3949508]: Could not generate persistent MAC address for veth5a7b8fa: No such file or directory
Sep 26 03:13:06 sentry-docker00.cs.umd.edu systemd-udevd[3949496]: Could not generate persistent MAC address for veth2a8ae14: No such file or directory
Sep 26 03:13:06 sentry-docker00.cs.umd.edu systemd-udevd[3949545]: Could not generate persistent MAC address for vethd0f46d9: No such file or directory
Sep 26 03:13:06 sentry-docker00.cs.umd.edu systemd-udevd[3949544]: Could not generate persistent MAC address for veth99b9bfe: No such file or directory
Sep 26 03:33:14 sentry-docker00.cs.umd.edu systemd-udevd[3958907]: link_config: could not get ethtool features for vethc2aef29
Sep 26 03:33:14 sentry-docker00.cs.umd.edu systemd-udevd[3958907]: Could not set offload features of vethc2aef29: No such device
Sep 26 03:33:15 sentry-docker00.cs.umd.edu systemd-udevd[3958935]: Could not generate persistent MAC address for veth60ba9f9: No such file or directory
Sep 26 03:33:15 sentry-docker00.cs.umd.edu systemd-udevd[3958936]: Could not generate persistent MAC address for vethe778b04: No such file or directory
Sep 26 03:33:15 sentry-docker00.cs.umd.edu systemd-udevd[3958939]: Could not generate persistent MAC address for veth0703025: No such file or directory
Sep 26 03:33:15 sentry-docker00.cs.umd.edu systemd-udevd[3958940]: Could not generate persistent MAC address for vethb6cd06d: No such file or directory
Sep 26 03:33:15 sentry-docker00.cs.umd.edu systemd-udevd[3958967]: Could not generate persistent MAC address for veth58c0a7d: No such file or directory
Sep 26 03:33:15 sentry-docker00.cs.umd.edu systemd-udevd[3958972]: Could not generate persistent MAC address for vethcfcc77c: No such file or directory
Sep 26 03:33:15 sentry-docker00.cs.umd.edu systemd-udevd[3959028]: Could not generate persistent MAC address for veth41f95d2: No such file or directory
Sep 26 03:33:15 sentry-docker00.cs.umd.edu systemd-udevd[3959023]: Could not generate persistent MAC address for veth3f07833: No such file or directory
Sep 26 03:33:15 sentry-docker00.cs.umd.edu systemd-udevd[3959017]: Could not generate persistent MAC address for vethff88c5d: No such file or directory
Sep 26 03:33:15 sentry-docker00.cs.umd.edu systemd-udevd[3959029]: Could not generate persistent MAC address for vethf9e23c3: No such file or directory
Sep 26 03:53:23 sentry-docker00.cs.umd.edu systemd-udevd[3968264]: link_config: could not get ethtool features for veth60ba9f9
Sep 26 03:53:23 sentry-docker00.cs.umd.edu systemd-udevd[3968264]: Could not set offload features of veth60ba9f9: No such device
Sep 26 03:53:23 sentry-docker00.cs.umd.edu systemd-udevd[3968297]: Could not generate persistent MAC address for veth07b9bad: No such file or directory
Sep 26 03:53:23 sentry-docker00.cs.umd.edu systemd-udevd[3968298]: Could not generate persistent MAC address for vethdb476b0: No such file or directory
Sep 26 03:53:23 sentry-docker00.cs.umd.edu systemd-udevd[3968301]: Could not generate persistent MAC address for veth03612f0: No such file or directory
Sep 26 03:53:23 sentry-docker00.cs.umd.edu systemd-udevd[3968302]: Could not generate persistent MAC address for veth048d358: No such file or directory
... 6 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 26 03: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 03: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 03:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 26 03: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 03: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 03:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 26 03:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 2.9098s
Status : exited 0
Output :
Syslog digest — 2026-09-26 03:05 EDT
Processed 47,405 lines, filtered 1,692 (3%). 45,713 unknown (176 distinct) from 15 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 26 03:00:57 b0b02.cs.umd.edu rustdesk[1186180]: cannot open display:
== galax (1 distinct, 1 total) ==
Sep 26 02:31:54 galax kernel: workqueue: dm_irq_work_func [amdgpu] hogged CPU for >10000us 2051 times, consider switching to WQ_UNBOUND
== idm00 (1 distinct, 1 total) ==
Sep 26 02:54:08 idm00 named[4166701]: client @0x7f11980727c8 10.73.240.42#59670: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 26 02:39:29 idmp0 named[1598691]: client @0x7f2d1401bb98 10.73.240.43#64599: update '73.10.in-addr.arpa/IN' denied
== irb2156 (1 distinct, 1 total) ==
Sep 26 02:34:13 irb2156 systemd-resolved[3402]: Using degraded feature set UDP instead of UDP+EDNS0 for DNS server 128.8.74.3.
== itmon02 (1 distinct, 5 total) ==
Sep 26 02:07:57 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x5]
== munin (2 distinct, 38 total) ==
Sep 26 02:08:12 munin sudo[3706132]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x19]
Sep 26 02:08:12 munin sudo[3706132]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x19]
== newhonors2 (1 distinct, 24 total) ==
Sep 26 02:13:03 newhonors2 dhcpcd[3164870]: dhcpcd is not running [x24]
== ntop00 (104 distinct, 45535 total) ==
Sep 26 02:05:09 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 ] [x21651]
Sep 26 02:05:09 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 ] [x20424]
Sep 26 02: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 ] [x3298]
Sep 26 02:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 443) ***
Sep 26 02:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 443, QN: 4554/4554, ET: 0) ***
Sep 26 02:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 443) ***
Sep 26 02:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 443, QN: 59/59, ET: 0) ***
Sep 26 02:10:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x12]
Sep 26 02:10:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x12]
Sep 26 02:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 444) ***
Sep 26 02:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 444, QN: 0/5189, ET: 0) ***
Sep 26 02:10:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x12]
Sep 26 02:10:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x12]
Sep 26 02:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 444) ***
Sep 26 02:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 444, QN: 0/52, ET: 0) ***
Sep 26 02:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 445) ***
Sep 26 02:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 445, QN: 5354/5354, ET: 0) ***
Sep 26 02:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 445) ***
Sep 26 02:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 445, QN: 58/58, ET: 0) ***
Sep 26 02: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 ] [x18]
Sep 26 02:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 446) ***
Sep 26 02:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 446, QN: 0/5086, ET: 0) ***
Sep 26 02:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 446) ***
Sep 26 02:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 446, QN: 0/73, ET: 0) ***
Sep 26 02:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 447) ***
Sep 26 02:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 447, QN: 4873/4873, ET: 0) ***
Sep 26 02:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 447) ***
Sep 26 02:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 447, QN: 67/67, ET: 0) ***
Sep 26 02:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 448) ***
Sep 26 02:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 448, QN: 0/54, ET: 0) ***
... 74 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 26 02:09:09 outbound00.cs.umd.edu python3[3957606]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 26 02:13:06 outbound01.cs.umd.edu python3[2023905]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 26 02:12:41 sentry-docker00.cs.umd.edu systemd-udevd[3920662]: link_config: could not get ethtool features for veth6c50115
Sep 26 02:12:41 sentry-docker00.cs.umd.edu systemd-udevd[3920662]: Could not set offload features of veth6c50115: No such device
Sep 26 02:12:41 sentry-docker00.cs.umd.edu systemd-udevd[3920697]: Could not generate persistent MAC address for veth9e9f52d: No such file or directory
Sep 26 02:12:41 sentry-docker00.cs.umd.edu systemd-udevd[3920698]: Could not generate persistent MAC address for veth61c0f81: No such file or directory
Sep 26 02:12:41 sentry-docker00.cs.umd.edu systemd-udevd[3920701]: Could not generate persistent MAC address for veth52a02d3: No such file or directory
Sep 26 02:12:41 sentry-docker00.cs.umd.edu systemd-udevd[3920702]: Could not generate persistent MAC address for vethcad0d9b: No such file or directory
Sep 26 02:12:41 sentry-docker00.cs.umd.edu systemd-udevd[3920725]: Could not generate persistent MAC address for vethb67f011: No such file or directory
Sep 26 02:12:41 sentry-docker00.cs.umd.edu systemd-udevd[3920726]: Could not generate persistent MAC address for vethe91ce33: No such file or directory
Sep 26 02:12:41 sentry-docker00.cs.umd.edu systemd-udevd[3920744]: Could not generate persistent MAC address for veth142a5d8: No such file or directory
Sep 26 02:12:41 sentry-docker00.cs.umd.edu systemd-udevd[3920751]: Could not generate persistent MAC address for vethb511de4: No such file or directory
Sep 26 02:12:41 sentry-docker00.cs.umd.edu systemd-udevd[3920765]: Could not generate persistent MAC address for veth06f110b: No such file or directory
Sep 26 02:12:41 sentry-docker00.cs.umd.edu systemd-udevd[3920766]: Could not generate persistent MAC address for vethfae43f4: No such file or directory
Sep 26 02:32:49 sentry-docker00.cs.umd.edu systemd-udevd[3930139]: link_config: could not set ethtool features for vethb67f011
Sep 26 02:32:49 sentry-docker00.cs.umd.edu systemd-udevd[3930139]: Could not set offload features of vethb67f011: Operation not permitted
Sep 26 02:32:49 sentry-docker00.cs.umd.edu systemd-udevd[3930163]: Could not generate persistent MAC address for veth00fe2b0: No such file or directory
Sep 26 02:32:49 sentry-docker00.cs.umd.edu systemd-udevd[3930164]: Could not generate persistent MAC address for veth435a2bb: No such file or directory
Sep 26 02:32:49 sentry-docker00.cs.umd.edu systemd-udevd[3930182]: Could not generate persistent MAC address for veth1caa67a: No such file or directory
Sep 26 02:32:49 sentry-docker00.cs.umd.edu systemd-udevd[3930167]: Could not generate persistent MAC address for vethdbb67e1: No such file or directory
Sep 26 02:32:49 sentry-docker00.cs.umd.edu systemd-udevd[3930178]: Could not generate persistent MAC address for veth39aaf74: No such file or directory
Sep 26 02:32:49 sentry-docker00.cs.umd.edu systemd-udevd[3930177]: Could not generate persistent MAC address for veth3c143de: No such file or directory
Sep 26 02:32:49 sentry-docker00.cs.umd.edu systemd-udevd[3930178]: Could not generate persistent MAC address for veth5fdfdf4: No such file or directory
Sep 26 02:32:49 sentry-docker00.cs.umd.edu systemd-udevd[3930173]: Could not generate persistent MAC address for vethfe63d84: No such file or directory
Sep 26 02:32:49 sentry-docker00.cs.umd.edu systemd-udevd[3930225]: Could not generate persistent MAC address for vethd1b5418: No such file or directory
Sep 26 02:32:49 sentry-docker00.cs.umd.edu systemd-udevd[3930235]: Could not generate persistent MAC address for veth90adfcb: No such file or directory
Sep 26 02:52:58 sentry-docker00.cs.umd.edu systemd-udevd[3939957]: link_config: could not get ethtool features for veth1caa67a
Sep 26 02:52:58 sentry-docker00.cs.umd.edu systemd-udevd[3939957]: Could not set offload features of veth1caa67a: No such device
Sep 26 02:52:58 sentry-docker00.cs.umd.edu systemd-udevd[3939993]: Could not generate persistent MAC address for veth6d96a7a: No such file or directory
Sep 26 02:52:58 sentry-docker00.cs.umd.edu systemd-udevd[3939994]: Could not generate persistent MAC address for vethd4dd658: No such file or directory
Sep 26 02:52:58 sentry-docker00.cs.umd.edu systemd-udevd[3939997]: Could not generate persistent MAC address for veth1aecd51: No such file or directory
Sep 26 02:52:58 sentry-docker00.cs.umd.edu systemd-udevd[3939998]: Could not generate persistent MAC address for veth67b1fae: No such file or directory
... 6 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 26 02: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 02: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 02:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 26 02: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 02: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 02:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 26 02:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (9 distinct, 9 total) ==
Sep 26 02:25:56 submit26-b9-f1 setroubleshoot[3741822]: 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
Sep 26 02:25:56 submit26-b9-f1 setroubleshoot[3741822]: 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
Sep 26 02:25:56 submit26-b9-f1 setroubleshoot[3741822]: 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 02:25:56 submit26-b9-f1 setroubleshoot[3741822]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.vHW4zr/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d
Sep 26 02:25:56 submit26-b9-f1 setroubleshoot[3741822]: 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 02:25:56 submit26-b9-f1 setroubleshoot[3741822]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.vHW4zr. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8
Sep 26 02:25:57 submit26-b9-f1 setroubleshoot[3741822]: 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
Sep 26 02:25:57 submit26-b9-f1 setroubleshoot[3741822]: 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 02:25:57 submit26-b9-f1 setroubleshoot[3741822]: 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
== submit26-b9-f2 (9 distinct, 11 total) ==
Sep 26 02:06:51 submit26-b9-f2 setroubleshoot[2820289]: 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 [x2]
Sep 26 02:06:51 submit26-b9-f2 setroubleshoot[2820289]: 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 [x2]
Sep 26 02:06:51 submit26-b9-f2 setroubleshoot[2820289]: 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 02:06:51 submit26-b9-f2 setroubleshoot[2820289]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.GVkKZa/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876
Sep 26 02:06:51 submit26-b9-f2 setroubleshoot[2820289]: 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 02:06:51 submit26-b9-f2 setroubleshoot[2820289]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.GVkKZa. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8
Sep 26 02:06:51 submit26-b9-f2 setroubleshoot[2820289]: 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 02:06:51 submit26-b9-f2 setroubleshoot[2820289]: 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 02:06:51 submit26-b9-f2 setroubleshoot[2820289]: 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
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.8293s
Status : exited 0
Output :
Syslog digest — 2026-09-26 02:05 EDT
Processed 26,104 lines, filtered 1,326 (5%). 24,778 unknown (193 distinct) from 18 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 26 02:00:52 b0b02.cs.umd.edu rustdesk[1170561]: cannot open display:
== cheezit.cs.umd.edu (3 distinct, 4 total) ==
Sep 26 01:43:38 cheezit.cs.umd.edu sshd-session[3199959]: pam_access(sshd:auth): access denied for user `larry' from `71.191.93.172' [x2]
Sep 26 01:43:40 cheezit.cs.umd.edu sshd-session[3199959]: Error in Duo login for 'larry' from 71.191.93.172
Sep 26 01:43:40 cheezit.cs.umd.edu sshd-session[3199957]: error: PAM: Authentication failure for larry from 71.191.93.172
== helmsdeep (1 distinct, 1 total) ==
Sep 26 01:05:47 helmsdeep kernel: clocksource: timekeeping watchdog on CPU0: kvm-clock retried 1 times before success
== idm00 (1 distinct, 1 total) ==
Sep 26 01:54:08 idm00 named[4166701]: client @0x7f11a945b458 10.73.240.42#62715: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 26 01:39:29 idmp0 named[1598691]: client @0x7f2d200241d8 10.73.240.43#50625: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 6 total) ==
Sep 26 01:07:58 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x6]
== munin (2 distinct, 4 total) ==
Sep 26 01:53:22 munin sudo[3700488]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x2]
Sep 26 01:53:22 munin sudo[3700488]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x2]
== netman.cs.umd.edu (3 distinct, 3 total) ==
Sep 26 02:00:44 netman.cs.umd.edu setroubleshoot[821850]: Deleting alert 49825fae-e786-4ccd-8ab4-15b21ec01b20, it is allowed in current policy
Sep 26 02:00:44 netman.cs.umd.edu setroubleshoot[821850]: Deleting alert 3339e8ec-2a3c-445e-9160-e54349c55e12, it is allowed in current policy
Sep 26 02:00:47 netman.cs.umd.edu setroubleshoot[821850]: SELinux is preventing /usr/sbin/vsftpd from name_connect access on the tcp_socket port 49191. For complete SELinux messages run: sealert -l 13cab75a-d208-4d9a-93ef-61c98f995ae3
== newhonors2 (1 distinct, 24 total) ==
Sep 26 01:13:03 newhonors2 dhcpcd[3163026]: dhcpcd is not running [x24]
== ntop00 (115 distinct, 24625 total) ==
Sep 26 01:05:13 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 418, QN: 6909/6909, ET: 12) ***
Sep 26 01:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 419) ***
Sep 26 01:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 419, QN: 7332/7332, ET: 0) ***
Sep 26 01:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 419) ***
Sep 26 01:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 419, QN: 55/55, ET: 0) ***
Sep 26 01:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 420) ***
Sep 26 01:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 420) ***
Sep 26 01:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 420, QN: 67/67, ET: 0) ***
Sep 26 01:10:11 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 420, QN: 6593/6593, ET: 10) ***
Sep 26 01:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 421) ***
Sep 26 01:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 421, QN: 5698/5698, ET: 0) ***
Sep 26 01:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 421) ***
Sep 26 01:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 421, QN: 53/53, ET: 0) ***
Sep 26 01:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 422) ***
Sep 26 01:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 422) ***
Sep 26 01:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 422, QN: 46/46, ET: 0) ***
Sep 26 01:15:09 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 422, QN: 5629/5629, ET: 8) ***
Sep 26 01:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 423) ***
Sep 26 01:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 423, QN: 5671/5671, ET: 0) ***
Sep 26 01:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 423) ***
Sep 26 01:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 423, QN: 44/44, ET: 0) ***
Sep 26 01:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 424) ***
Sep 26 01:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 424) ***
Sep 26 01:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 424, QN: 42/42, ET: 0) ***
Sep 26 01:20:09 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 424, QN: 5771/5771, ET: 8) ***
Sep 26 01:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 425) ***
Sep 26 01:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 425, QN: 5401/5401, ET: 0) ***
Sep 26 01:23:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 425) ***
Sep 26 01:23:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 425, QN: 53/53, ET: 0) ***
Sep 26 01:25:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 426) ***
... 85 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 26 01:09:09 outbound00.cs.umd.edu python3[3943681]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 26 01:13:07 outbound01.cs.umd.edu python3[2009776]: ldapdb [x6]
== sebatinsky.cs.umd.edu (1 distinct, 1 total) ==
Sep 26 01:09:42 sebatinsky.cs.umd.edu kernel: hpet1: lost 1 rtc interrupts
== sentry-docker00.cs.umd.edu (34 distinct, 34 total) ==
Sep 26 01:12:16 sentry-docker00.cs.umd.edu systemd-udevd[3892057]: Could not generate persistent MAC address for vethd9029a7: No such file or directory
Sep 26 01:12:16 sentry-docker00.cs.umd.edu systemd-udevd[3892058]: Could not generate persistent MAC address for veth8810242: No such file or directory
Sep 26 01:12:16 sentry-docker00.cs.umd.edu systemd-udevd[3892061]: Could not generate persistent MAC address for veth6d028b9: No such file or directory
Sep 26 01:12:16 sentry-docker00.cs.umd.edu systemd-udevd[3892062]: Could not generate persistent MAC address for vethcc1ad8e: No such file or directory
Sep 26 01:12:16 sentry-docker00.cs.umd.edu systemd-udevd[3892082]: Could not generate persistent MAC address for vetha69eeaf: No such file or directory
Sep 26 01:12:16 sentry-docker00.cs.umd.edu systemd-udevd[3892070]: Could not generate persistent MAC address for veth1d6271a: No such file or directory
Sep 26 01:12:16 sentry-docker00.cs.umd.edu systemd-udevd[3892073]: Could not generate persistent MAC address for veth8adddd7: No such file or directory
Sep 26 01:12:16 sentry-docker00.cs.umd.edu systemd-udevd[3892066]: Could not generate persistent MAC address for vethbbc963f: No such file or directory
Sep 26 01:12:16 sentry-docker00.cs.umd.edu systemd-udevd[3892070]: Could not generate persistent MAC address for veth9c9fb40: No such file or directory
Sep 26 01:12:16 sentry-docker00.cs.umd.edu systemd-udevd[3892073]: Could not generate persistent MAC address for vethb94b71a: No such file or directory
Sep 26 01:32:24 sentry-docker00.cs.umd.edu systemd-udevd[3901683]: Could not generate persistent MAC address for veth15b51e9: No such file or directory
Sep 26 01:32:24 sentry-docker00.cs.umd.edu systemd-udevd[3901684]: Could not generate persistent MAC address for vethfd7a83c: No such file or directory
Sep 26 01:32:24 sentry-docker00.cs.umd.edu systemd-udevd[3901687]: Could not generate persistent MAC address for vetha06c282: No such file or directory
Sep 26 01:32:24 sentry-docker00.cs.umd.edu systemd-udevd[3901688]: Could not generate persistent MAC address for veth88bdac0: No such file or directory
Sep 26 01:32:24 sentry-docker00.cs.umd.edu systemd-udevd[3901711]: Could not generate persistent MAC address for veth318a7c2: No such file or directory
Sep 26 01:32:24 sentry-docker00.cs.umd.edu systemd-udevd[3901712]: Could not generate persistent MAC address for vetha07e683: No such file or directory
Sep 26 01:32:25 sentry-docker00.cs.umd.edu systemd-udevd[3901724]: Could not generate persistent MAC address for vetha6f3888: No such file or directory
Sep 26 01:32:25 sentry-docker00.cs.umd.edu systemd-udevd[3901720]: Could not generate persistent MAC address for vetha4686e0: No such file or directory
Sep 26 01:32:25 sentry-docker00.cs.umd.edu systemd-udevd[3901744]: Could not generate persistent MAC address for veth2b2bcd5: No such file or directory
Sep 26 01:32:25 sentry-docker00.cs.umd.edu systemd-udevd[3901740]: Could not generate persistent MAC address for vethbdab5c7: No such file or directory
Sep 26 01:52:33 sentry-docker00.cs.umd.edu systemd-udevd[3911103]: link_config: could not get ethtool features for veth15b51e9
Sep 26 01:52:33 sentry-docker00.cs.umd.edu systemd-udevd[3911103]: Could not set offload features of veth15b51e9: No such device
Sep 26 01:52:33 sentry-docker00.cs.umd.edu systemd-udevd[3911105]: link_config: could not get ethtool features for vetha06c282
Sep 26 01:52:33 sentry-docker00.cs.umd.edu systemd-udevd[3911105]: Could not set offload features of vetha06c282: No such device
Sep 26 01:52:33 sentry-docker00.cs.umd.edu systemd-udevd[3911142]: Could not generate persistent MAC address for veth3997e0a: No such file or directory
Sep 26 01:52:33 sentry-docker00.cs.umd.edu systemd-udevd[3911143]: Could not generate persistent MAC address for veth15b7f76: No such file or directory
Sep 26 01:52:33 sentry-docker00.cs.umd.edu systemd-udevd[3911147]: Could not generate persistent MAC address for veth3531c67: No such file or directory
Sep 26 01:52:33 sentry-docker00.cs.umd.edu systemd-udevd[3911146]: Could not generate persistent MAC address for veth3920aa7: No such file or directory
Sep 26 01:52:33 sentry-docker00.cs.umd.edu systemd-udevd[3911171]: Could not generate persistent MAC address for veth61db956: No such file or directory
Sep 26 01:52:33 sentry-docker00.cs.umd.edu systemd-udevd[3911170]: Could not generate persistent MAC address for veth6c50115: No such file or directory
... 4 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 26 01: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 01: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 01:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 26 01: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 01: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 01:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 26 01:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f3 (10 distinct, 13 total) ==
Sep 26 01:06:45 submit26-b9-f3 setroubleshoot[3499410]: 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 01:06:45 submit26-b9-f3 setroubleshoot[3499410]: 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 01:06:45 submit26-b9-f3 setroubleshoot[3499410]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 580b20e4-ec2c-433d-905c-5bd417fba033 [x2]
Sep 26 01:06:45 submit26-b9-f3 setroubleshoot[3499410]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.tbTNn9/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f
Sep 26 01:06:45 submit26-b9-f3 setroubleshoot[3499410]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l bff72452-d40a-430b-9060-dd0a48f5b6ba [x2]
Sep 26 01:06:45 submit26-b9-f3 setroubleshoot[3499410]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.tbTNn9. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd
Sep 26 01:06:45 submit26-b9-f3 setroubleshoot[3499410]: 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 01:06:45 submit26-b9-f3 setroubleshoot[3499410]: 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 [x2]
Sep 26 01:06:45 submit26-b9-f3 setroubleshoot[3499410]: 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 01:06:45 submit26-b9-f3 setroubleshoot[3499410]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.DSBIbI/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f
== submit26-b9-f4 (9 distinct, 9 total) ==
Sep 26 01:24:48 submit26-b9-f4 setroubleshoot[2560023]: 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 01:24:48 submit26-b9-f4 setroubleshoot[2560023]: 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 01:24:48 submit26-b9-f4 setroubleshoot[2560023]: 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 01:24:48 submit26-b9-f4 setroubleshoot[2560023]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.gj1MMJ/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0
Sep 26 01:24:48 submit26-b9-f4 setroubleshoot[2560023]: 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 01:24:48 submit26-b9-f4 setroubleshoot[2560023]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.gj1MMJ. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c
Sep 26 01:24:48 submit26-b9-f4 setroubleshoot[2560023]: 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 01:24:48 submit26-b9-f4 setroubleshoot[2560023]: 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 01:24:48 submit26-b9-f4 setroubleshoot[2560023]: 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
== wraith (1 distinct, 1 total) ==
Sep 26 01:31:30 wraith kernel: set_capacity_and_notify: 28 callbacks suppressed
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.0493s
Status : exited 0
Output :
Syslog digest — 2026-09-26 01:05 EDT
Processed 1,843 lines, filtered 1,345 (72%). 498 unknown (248 distinct) from 30 host(s).
== abuse (3 distinct, 4 total) ==
Sep 26 00:10:14 abuse systemd[1]: New main PID 11062 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 26 00:10:32 abuse systemd[1]: Daemon never wrote its PID file. Failing.
Sep 26 00:10:42 abuse systemd[1]: pmlogger.service: Supervising process 18439 which is not our child. We'll most likely not notice when it exits.
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 26 01:00:48 b0b02.cs.umd.edu rustdesk[1155740]: cannot open display:
== galax (3 distinct, 3 total) ==
Sep 26 00:17:02 galax kernel: xhci_hcd 0000:70:00.0: WARN: xHC CMD_RUN timeout
Sep 26 00:17:02 galax kernel: xhci_hcd 0000:70:00.0: PM: suspend_common(): xhci_pci_suspend returns -110
Sep 26 00:17:02 galax kernel: xhci_hcd 0000:70:00.0: can't suspend (hcd_pci_runtime_suspend returned -110)
== grades01.cs.umd.edu (3 distinct, 4 total) ==
Sep 26 00:10:13 grades01.cs.umd.edu systemd[1]: New main PID 2878 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 26 00:10:37 grades01.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 26 00:10:52 grades01.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 10565 which is not our child. We'll most likely not notice when it exits.
== hazfs.cs.umd.edu (11 distinct, 66 total) ==
Sep 26 00:53:09 hazfs.cs.umd.edu snmpd[1431]: send response: Failure in sendto [x6]
Sep 26 00:53:09 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userweb" [x6]
Sep 26 00:53:09 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."zfslist" [x6]
Sep 26 00:53:09 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userhome" [x6]
Sep 26 00:53:09 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userweb" [x6]
Sep 26 00:53:09 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."zfslist" [x6]
Sep 26 00:53:09 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userhome" [x6]
Sep 26 00:53:09 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userweb" [x6]
Sep 26 00:53:09 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."zfslist" [x6]
Sep 26 00:53:09 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userhome" [x6]
Sep 26 00:53:09 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutNumLines."userweb" [x6]
== idm00 (1 distinct, 1 total) ==
Sep 26 00:54:08 idm00 named[4166701]: client @0x7f11a94233e8 10.73.240.42#53320: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 26 00:39:29 idmp0 named[1598691]: client @0x7f2d200241d8 10.73.240.43#53225: update '73.10.in-addr.arpa/IN' denied
== inbound01.cs.umd.edu (23 distinct, 51 total) ==
Sep 26 00:37:35 inbound01.cs.umd.edu sshd-session[2104459]: error: maximum authentication attempts exceeded for root from 84.47.79.252 port 42127 ssh2 [preauth]
Sep 26 00:37:57 inbound01.cs.umd.edu sshd-session[2104473]: error: maximum authentication attempts exceeded for root from 84.47.79.252 port 43803 ssh2 [preauth]
Sep 26 00:38:18 inbound01.cs.umd.edu sshd-session[2104577]: error: maximum authentication attempts exceeded for root from 84.47.79.252 port 45682 ssh2 [preauth]
Sep 26 00:38:26 inbound01.cs.umd.edu krb5_child[2104604]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x16]
Sep 26 00:38:47 inbound01.cs.umd.edu sshd-session[2104597]: error: maximum authentication attempts exceeded for admin from 84.47.79.252 port 47990 ssh2 [preauth]
Sep 26 00:39:10 inbound01.cs.umd.edu sshd-session[2104716]: error: maximum authentication attempts exceeded for admin from 84.47.79.252 port 49945 ssh2 [preauth]
Sep 26 00:39:46 inbound01.cs.umd.edu sshd-session[2104768]: error: maximum authentication attempts exceeded for invalid user oracle from 84.47.79.252 port 53229 ssh2 [preauth]
Sep 26 00:40:09 inbound01.cs.umd.edu sshd-session[2104868]: error: maximum authentication attempts exceeded for invalid user oracle from 84.47.79.252 port 54932 ssh2 [preauth]
Sep 26 00:40:37 inbound01.cs.umd.edu sshd-session[2105168]: error: maximum authentication attempts exceeded for invalid user usuario from 84.47.79.252 port 57425 ssh2 [preauth]
Sep 26 00:40:56 inbound01.cs.umd.edu sshd-session[2105177]: error: maximum authentication attempts exceeded for invalid user usuario from 84.47.79.252 port 59064 ssh2 [preauth]
Sep 26 00:41:25 inbound01.cs.umd.edu sshd-session[2105282]: error: maximum authentication attempts exceeded for invalid user test from 84.47.79.252 port 33105 ssh2 [preauth]
Sep 26 00:41:47 inbound01.cs.umd.edu sshd-session[2105304]: error: maximum authentication attempts exceeded for invalid user test from 84.47.79.252 port 34787 ssh2 [preauth]
Sep 26 00:42:13 inbound01.cs.umd.edu sshd-session[2105431]: error: maximum authentication attempts exceeded for invalid user user from 84.47.79.252 port 37318 ssh2 [preauth]
Sep 26 00:42:32 inbound01.cs.umd.edu sshd-session[2105692]: error: maximum authentication attempts exceeded for invalid user user from 84.47.79.252 port 38823 ssh2 [preauth]
Sep 26 00:43:06 inbound01.cs.umd.edu sshd-session[2105801]: error: maximum authentication attempts exceeded for invalid user ftpuser from 84.47.79.252 port 41502 ssh2 [preauth]
Sep 26 00:43:27 inbound01.cs.umd.edu sshd-session[2105808]: error: maximum authentication attempts exceeded for invalid user ftpuser from 84.47.79.252 port 43293 ssh2 [preauth]
Sep 26 00:43:44 inbound01.cs.umd.edu krb5_child[2105922]: Client 'test1(a)UMD.EDU' not found in Kerberos database [x14]
Sep 26 00:44:03 inbound01.cs.umd.edu sshd-session[2105894]: error: maximum authentication attempts exceeded for test1 from 84.47.79.252 port 46295 ssh2 [preauth]
Sep 26 00:44:26 inbound01.cs.umd.edu sshd-session[2105939]: error: maximum authentication attempts exceeded for test1 from 84.47.79.252 port 48034 ssh2 [preauth]
Sep 26 00:44:58 inbound01.cs.umd.edu sshd-session[2105983]: error: maximum authentication attempts exceeded for invalid user test2 from 84.47.79.252 port 50805 ssh2 [preauth]
Sep 26 00:45:18 inbound01.cs.umd.edu sshd-session[2106081]: error: maximum authentication attempts exceeded for invalid user test2 from 84.47.79.252 port 52645 ssh2 [preauth]
Sep 26 00:45:48 inbound01.cs.umd.edu sshd-session[2106381]: error: maximum authentication attempts exceeded for invalid user ubuntu from 84.47.79.252 port 54975 ssh2 [preauth]
Sep 26 00:46:11 inbound01.cs.umd.edu sshd-session[2106479]: error: maximum authentication attempts exceeded for invalid user ubuntu from 84.47.79.252 port 56873 ssh2 [preauth]
== itmon02 (1 distinct, 3 total) ==
Sep 26 00:18:38 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x3]
== jubjub.cs.umd.edu (3 distinct, 4 total) ==
Sep 26 00:10:13 jubjub.cs.umd.edu systemd[1]: New main PID 1275163 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 26 00:10:33 jubjub.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 26 00:10:41 jubjub.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 1282702 which is not our child. We'll most likely not notice when it exits.
== librenms (1 distinct, 1 total) ==
Sep 26 00:59:40 librenms (httpd)[2410760]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
== mirrors.cs.umd.edu (4 distinct, 6 total) ==
Sep 26 00:10:34 mirrors.cs.umd.edu root[17069]: pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily-K.log
Sep 26 00:10:34 mirrors.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing. [x2]
Sep 26 00:10:38 mirrors.cs.umd.edu systemd[1]: New main PID 15998 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 26 00:12:17 mirrors.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 32569 which is not our child. We'll most likely not notice when it exits.
== misty.cs.umd.edu (3 distinct, 4 total) ==
Sep 26 00:10:15 misty.cs.umd.edu systemd[1]: New main PID 33188 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 26 00:10:35 misty.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 26 00:10:50 misty.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 40388 which is not our child. We'll most likely not notice when it exits.
== munin (2 distinct, 72 total) ==
Sep 26 00:13:39 munin sudo[3663404]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x36]
Sep 26 00:13:39 munin sudo[3663404]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x36]
== newhonors2 (1 distinct, 24 total) ==
Sep 26 00:13:03 newhonors2 dhcpcd[3161181]: dhcpcd is not running [x24]
== ntop00 (100 distinct, 100 total) ==
Sep 26 00:05:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 394) ***
Sep 26 00:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 394) ***
Sep 26 00:05:02 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 394, QN: 52/52, ET: 1) ***
Sep 26 00:05:07 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 394, QN: 4445/4445, ET: 6) ***
Sep 26 00:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 395) ***
Sep 26 00:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 395, QN: 4584/4584, ET: 0) ***
Sep 26 00:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 395) ***
Sep 26 00:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 395, QN: 53/53, ET: 0) ***
Sep 26 00:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 396) ***
Sep 26 00:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 396, QN: 59/59, ET: 0) ***
Sep 26 00:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 396) ***
Sep 26 00:10:07 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 396, QN: 4232/4232, ET: 6) ***
Sep 26 00:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 397) ***
Sep 26 00:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 397, QN: 4276/4276, ET: 0) ***
Sep 26 00:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 397) ***
Sep 26 00:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 397, QN: 55/55, ET: 0) ***
Sep 26 00:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 398) ***
Sep 26 00:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 398) ***
Sep 26 00:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 398, QN: 57/57, ET: 0) ***
Sep 26 00:15:08 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 398, QN: 4604/4604, ET: 7) ***
Sep 26 00:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 399) ***
Sep 26 00:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 399, QN: 4696/4696, ET: 0) ***
Sep 26 00:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 399) ***
Sep 26 00:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 399, QN: 73/73, ET: 0) ***
Sep 26 00:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 400) ***
Sep 26 00:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 400) ***
Sep 26 00:20:02 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 400, QN: 50/50, ET: 1) ***
Sep 26 00:20:08 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 400, QN: 4376/4376, ET: 7) ***
Sep 26 00:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 401) ***
Sep 26 00:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 401, QN: 4545/4545, ET: 0) ***
... 70 more distinct messages not shown
== outbound00.cs.umd.edu (16 distinct, 34 total) ==
Sep 26 00:05:29 outbound00.cs.umd.edu sshd-session[3927908]: error: maximum authentication attempts exceeded for invalid user usuario from 84.47.79.252 port 54709 ssh2 [preauth]
Sep 26 00:05:52 outbound00.cs.umd.edu sshd-session[3927997]: error: maximum authentication attempts exceeded for invalid user usuario from 84.47.79.252 port 56586 ssh2 [preauth]
Sep 26 00:06:23 outbound00.cs.umd.edu sshd-session[3928084]: error: maximum authentication attempts exceeded for invalid user test from 84.47.79.252 port 59124 ssh2 [preauth]
Sep 26 00:06:46 outbound00.cs.umd.edu sshd-session[3928402]: error: maximum authentication attempts exceeded for invalid user test from 84.47.79.252 port 32844 ssh2 [preauth]
Sep 26 00:07:18 outbound00.cs.umd.edu sshd-session[3928442]: error: maximum authentication attempts exceeded for invalid user user from 84.47.79.252 port 35623 ssh2 [preauth]
Sep 26 00:07:39 outbound00.cs.umd.edu sshd-session[3928515]: error: maximum authentication attempts exceeded for invalid user user from 84.47.79.252 port 37410 ssh2 [preauth]
Sep 26 00:08:15 outbound00.cs.umd.edu sshd-session[3928530]: error: maximum authentication attempts exceeded for invalid user ftpuser from 84.47.79.252 port 40306 ssh2 [preauth]
Sep 26 00:08:34 outbound00.cs.umd.edu sshd-session[3928859]: error: maximum authentication attempts exceeded for invalid user ftpuser from 84.47.79.252 port 42006 ssh2 [preauth]
Sep 26 00:08:51 outbound00.cs.umd.edu krb5_child[3928873]: Client 'test1(a)UMD.EDU' not found in Kerberos database [x14]
Sep 26 00:09:09 outbound00.cs.umd.edu python3[3929107]: ldapdb [x6]
Sep 26 00:09:14 outbound00.cs.umd.edu sshd-session[3928870]: error: maximum authentication attempts exceeded for test1 from 84.47.79.252 port 44829 ssh2 [preauth]
Sep 26 00:09:40 outbound00.cs.umd.edu sshd-session[3929220]: error: maximum authentication attempts exceeded for test1 from 84.47.79.252 port 46872 ssh2 [preauth]
Sep 26 00:10:05 outbound00.cs.umd.edu sshd-session[3929268]: error: maximum authentication attempts exceeded for invalid user test2 from 84.47.79.252 port 49797 ssh2 [preauth]
Sep 26 00:10:22 outbound00.cs.umd.edu sshd-session[3929638]: error: maximum authentication attempts exceeded for invalid user test2 from 84.47.79.252 port 51150 ssh2 [preauth]
Sep 26 00:10:49 outbound00.cs.umd.edu sshd-session[3930104]: error: maximum authentication attempts exceeded for invalid user ubuntu from 84.47.79.252 port 53199 ssh2 [preauth]
Sep 26 00:11:12 outbound00.cs.umd.edu sshd-session[3930214]: error: maximum authentication attempts exceeded for invalid user ubuntu from 84.47.79.252 port 54908 ssh2 [preauth]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 26 00:13:07 outbound01.cs.umd.edu python3[1995760]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (34 distinct, 34 total) ==
Sep 26 00:11:51 sentry-docker00.cs.umd.edu systemd-udevd[3863682]: link_config: could not get ethtool features for vetheaa695a
Sep 26 00:11:51 sentry-docker00.cs.umd.edu systemd-udevd[3863682]: Could not set offload features of vetheaa695a: No such device
Sep 26 00:11:51 sentry-docker00.cs.umd.edu systemd-udevd[3863729]: Could not generate persistent MAC address for veth5cf3419: No such file or directory
Sep 26 00:11:51 sentry-docker00.cs.umd.edu systemd-udevd[3863730]: Could not generate persistent MAC address for veth9afe979: No such file or directory
Sep 26 00:11:51 sentry-docker00.cs.umd.edu systemd-udevd[3863748]: Could not generate persistent MAC address for veth97966c7: No such file or directory
Sep 26 00:11:51 sentry-docker00.cs.umd.edu systemd-udevd[3863755]: Could not generate persistent MAC address for veth6979c49: No such file or directory
Sep 26 00:11:51 sentry-docker00.cs.umd.edu systemd-udevd[3863748]: Could not generate persistent MAC address for veth61d2740: No such file or directory
Sep 26 00:11:51 sentry-docker00.cs.umd.edu systemd-udevd[3863733]: Could not generate persistent MAC address for vethd28a935: No such file or directory
Sep 26 00:11:51 sentry-docker00.cs.umd.edu systemd-udevd[3863759]: Could not generate persistent MAC address for veth0397654: No such file or directory
Sep 26 00:11:51 sentry-docker00.cs.umd.edu systemd-udevd[3863760]: Could not generate persistent MAC address for vetha04f271: No such file or directory
Sep 26 00:11:51 sentry-docker00.cs.umd.edu systemd-udevd[3863828]: Could not generate persistent MAC address for veth3a80a21: No such file or directory
Sep 26 00:11:51 sentry-docker00.cs.umd.edu systemd-udevd[3863826]: Could not generate persistent MAC address for vethb157636: No such file or directory
Sep 26 00:32:00 sentry-docker00.cs.umd.edu systemd-udevd[3873209]: Could not generate persistent MAC address for vethbd5596b: No such file or directory
Sep 26 00:32:00 sentry-docker00.cs.umd.edu systemd-udevd[3873208]: Could not generate persistent MAC address for veth6c5df28: No such file or directory
Sep 26 00:32:00 sentry-docker00.cs.umd.edu systemd-udevd[3873212]: Could not generate persistent MAC address for veth4170895: No such file or directory
Sep 26 00:32:00 sentry-docker00.cs.umd.edu systemd-udevd[3873215]: Could not generate persistent MAC address for veth26795f0: No such file or directory
Sep 26 00:32:00 sentry-docker00.cs.umd.edu systemd-udevd[3873236]: Could not generate persistent MAC address for veth63477e3: No such file or directory
Sep 26 00:32:00 sentry-docker00.cs.umd.edu systemd-udevd[3873237]: Could not generate persistent MAC address for vethfdbc491: No such file or directory
Sep 26 00:32:00 sentry-docker00.cs.umd.edu systemd-udevd[3873255]: Could not generate persistent MAC address for veth6ac028d: No such file or directory
Sep 26 00:32:00 sentry-docker00.cs.umd.edu systemd-udevd[3873240]: Could not generate persistent MAC address for vethc4d7fea: No such file or directory
Sep 26 00:32:00 sentry-docker00.cs.umd.edu systemd-udevd[3873288]: Could not generate persistent MAC address for veth8bbf032: No such file or directory
Sep 26 00:32:00 sentry-docker00.cs.umd.edu systemd-udevd[3873289]: Could not generate persistent MAC address for veth716f072: No such file or directory
Sep 26 00:52:08 sentry-docker00.cs.umd.edu systemd-udevd[3882616]: link_config: could not get ethtool features for veth63477e3
Sep 26 00:52:08 sentry-docker00.cs.umd.edu systemd-udevd[3882616]: Could not set offload features of veth63477e3: No such device
Sep 26 00:52:08 sentry-docker00.cs.umd.edu systemd-udevd[3882650]: Could not generate persistent MAC address for veth0a48827: No such file or directory
Sep 26 00:52:08 sentry-docker00.cs.umd.edu systemd-udevd[3882651]: Could not generate persistent MAC address for veth2363e02: No such file or directory
Sep 26 00:52:08 sentry-docker00.cs.umd.edu systemd-udevd[3882669]: Could not generate persistent MAC address for vethe5bb244: No such file or directory
Sep 26 00:52:08 sentry-docker00.cs.umd.edu systemd-udevd[3882657]: Could not generate persistent MAC address for veth92519b2: No such file or directory
Sep 26 00:52:08 sentry-docker00.cs.umd.edu systemd-udevd[3882657]: Could not generate persistent MAC address for veth1fc5f83: No such file or directory
Sep 26 00:52:08 sentry-docker00.cs.umd.edu systemd-udevd[3882659]: Could not generate persistent MAC address for vetha48336a: No such file or directory
... 4 more distinct messages not shown
== strawberry (8 distinct, 39 total) ==
Sep 26 00: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 00: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 00:07:04 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 26 00: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 00: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 00:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 26 00:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
Sep 26 01:04:42 strawberry smartd[5314]: Device: /dev/sda [SAT], not capable of Offline or Self-Testing.
== submit10-cln25 (3 distinct, 4 total) ==
Sep 26 00:10:11 submit10-cln25 systemd: New main PID 31978 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 26 00:10:30 submit10-cln25 systemd: Daemon never wrote its PID file. Failing.
Sep 26 00:10:35 submit10-cln25 systemd: pmlogger.service: Supervising process 6513 which is not our child. We'll most likely not notice when it exits.
== submit26-b9-f1 (1 distinct, 3 total) ==
Sep 26 00:13:08 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x3]
== submit26-b9-f2 (1 distinct, 1 total) ==
Sep 26 00:09:02 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
== submit26-b9-f3 (1 distinct, 1 total) ==
Sep 26 00:08:06 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
== submit26-b9-f4 (1 distinct, 3 total) ==
Sep 26 00:08:11 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x3]
== submit26-b9-fclone (9 distinct, 12 total) ==
Sep 26 00:21:59 submit26-b9-fclone setroubleshoot[499511]: 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 00:21:59 submit26-b9-fclone setroubleshoot[499511]: 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 00:21:59 submit26-b9-fclone setroubleshoot[499511]: 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 [x2]
Sep 26 00:21:59 submit26-b9-fclone setroubleshoot[499511]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.Q57Af9/repodata/repomd.xml. For complete SELinux messages run: sealert -l 03e2f521-0e7c-481f-8e92-0602c6adeedc [x2]
Sep 26 00:21:59 submit26-b9-fclone setroubleshoot[499511]: 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 [x2]
Sep 26 00:21:59 submit26-b9-fclone setroubleshoot[499511]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.Q57Af9. For complete SELinux messages run: sealert -l 887adbf9-2bb9-4009-b800-36ddf9ba0db5
Sep 26 00:21:59 submit26-b9-fclone setroubleshoot[499511]: 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 00:21:59 submit26-b9-fclone setroubleshoot[499511]: 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 00:21:59 submit26-b9-fclone setroubleshoot[499511]: 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
== tma-0 (3 distinct, 4 total) ==
Sep 26 00:10:13 tma-0 systemd[1]: New main PID 30375 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 26 00:10:30 tma-0 systemd[1]: Daemon never wrote its PID file. Failing.
Sep 26 00:10:38 tma-0 systemd[1]: pmlogger.service: Supervising process 5657 which is not our child. We'll most likely not notice when it exits.
== uffish.cs.umd.edu (3 distinct, 4 total) ==
Sep 26 00:10:13 uffish.cs.umd.edu systemd[1]: New main PID 3768032 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 26 00:10:39 uffish.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 26 00:11:00 uffish.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 3775644 which is not our child. We'll most likely not notice when it exits.
== vacuum.cs.umd.edu (3 distinct, 4 total) ==
Sep 26 00:10:14 vacuum.cs.umd.edu systemd[1]: New main PID 30705 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 26 00:10:33 vacuum.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 26 00:10:44 vacuum.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 6050 which is not our child. We'll most likely not notice when it exits.
== whiffle.cs.umd.edu (3 distinct, 4 total) ==
Sep 26 00:10:13 whiffle.cs.umd.edu systemd[1]: New main PID 3301159 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 26 00:10:38 whiffle.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 26 00:10:52 whiffle.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 3308446 which is not our child. We'll most likely not notice when it exits.
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.0469s
Status : exited 0
Output :
Syslog digest — 2026-09-26 00:05 EDT
Processed 2,437 lines, filtered 2,075 (85%). 362 unknown (262 distinct) from 60 host(s).
== abadi-computer (3 distinct, 3 total) ==
Sep 25 23:24:09 abadi-computer falcon-sensor[553]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225
Sep 25 23:24:09 abadi-computer falcon-sensor[553]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225
Sep 26 00:00:00 abadi-computer systemctl[946252]: Warning: The unit file, source configuration file or drop-ins of cups.service changed on disk. Run 'systemctl daemon-reload' to reload units.
== ai-course (2 distinct, 2 total) ==
Sep 25 23:28:37 ai-course falcon-sensor-bpf[725219]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225
Sep 25 23:28:37 ai-course falcon-sensor-bpf[725219]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 26 00:00:47 b0b02.cs.umd.edu rustdesk[1139614]: cannot open display:
== biggulp.cs.umd.edu (2 distinct, 2 total) ==
Sep 25 23:22:57 biggulp.cs.umd.edu falcon-sensor-bpf[834]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225
Sep 25 23:22:57 biggulp.cs.umd.edu falcon-sensor-bpf[834]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225
== bigtuna (2 distinct, 2 total) ==
Sep 25 23:33:30 bigtuna falcon-sensor-bpf[876]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225
Sep 25 23:33:30 bigtuna falcon-sensor-bpf[876]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225
== borealis (2 distinct, 2 total) ==
Sep 25 23:34:16 borealis falcon-sensor-bpf[921]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225
Sep 25 23:34:16 borealis falcon-sensor-bpf[921]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225
== borogove.cs.umd.edu (2 distinct, 2 total) ==
Sep 25 23:30:39 borogove.cs.umd.edu falcon-sensor-bpf[1404]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225
Sep 25 23:30:39 borogove.cs.umd.edu falcon-sensor-bpf[1404]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225
== cheezit.cs.umd.edu (2 distinct, 2 total) ==
Sep 25 23:33:42 cheezit.cs.umd.edu falcon-sensor-bpf[1347]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225
Sep 25 23:33:42 cheezit.cs.umd.edu falcon-sensor-bpf[1347]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225
== cskayako (2 distinct, 2 total) ==
Sep 25 23:34:14 cskayako falcon-sensor-bpf[746]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225
Sep 25 23:34:14 cskayako falcon-sensor-bpf[746]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225
== defer (2 distinct, 2 total) ==
Sep 25 23:28:13 defer falcon-sensor-bpf[811]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225
Sep 25 23:28:13 defer falcon-sensor-bpf[811]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225
== emaar (2 distinct, 2 total) ==
Sep 25 23:25:29 emaar falcon-sensor-bpf[971]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225
Sep 25 23:25:29 emaar falcon-sensor-bpf[971]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225
== frozone (2 distinct, 2 total) ==
Sep 25 23:30:48 frozone falcon-sensor-bpf[1052]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225
Sep 25 23:30:48 frozone falcon-sensor-bpf[1052]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225
== galahad.cs.umd.edu (2 distinct, 2 total) ==
Sep 25 23:37:15 galahad.cs.umd.edu falcon-sensor-bpf[970]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225
Sep 25 23:37:15 galahad.cs.umd.edu falcon-sensor-bpf[970]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225
== galax (3 distinct, 3 total) ==
Sep 25 23:27:15 galax kernel: workqueue: dm_irq_work_func [amdgpu] hogged CPU for >10000us 1027 times, consider switching to WQ_UNBOUND
Sep 25 23:47:26 galax falcon-sensor[1499]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225
Sep 25 23:47:26 galax falcon-sensor[1499]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225
== gle-dind02.cs.umd.edu (7 distinct, 7 total) ==
Sep 25 23:43:37 gle-dind02.cs.umd.edu systemd-udevd[2799439]: link_config: could not get ethtool features for veth4d847f5
Sep 25 23:43:37 gle-dind02.cs.umd.edu systemd-udevd[2799439]: Could not set offload features of veth4d847f5: No such device
Sep 25 23:43:37 gle-dind02.cs.umd.edu systemd-udevd[2799457]: Could not generate persistent MAC address for veth5198d5f: No such file or directory
Sep 25 23:43:37 gle-dind02.cs.umd.edu systemd-udevd[2799458]: Could not generate persistent MAC address for veth3e9e93d: No such file or directory
Sep 25 23:43:39 gle-dind02.cs.umd.edu systemd-udevd[2799579]: Could not generate persistent MAC address for veth6f25791: No such file or directory
Sep 25 23:43:39 gle-dind02.cs.umd.edu systemd-udevd[2799580]: Could not generate persistent MAC address for vethc629276: No such file or directory
Sep 25 23:43:42 gle-dind02.cs.umd.edu lldpd[973]: unable to send packet on real device for veth95e1048: No such device or address
== gle-dind04 (2 distinct, 2 total) ==
Sep 25 23:32:48 gle-dind04 falcon-sensor-bpf[1017]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225
Sep 25 23:32:48 gle-dind04 falcon-sensor-bpf[1017]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225
== gle-omnibus00.cs.umd.edu (2 distinct, 2 total) ==
Sep 25 23:45:02 gle-omnibus00.cs.umd.edu falcon-sensor-bpf[935]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225
Sep 25 23:45:02 gle-omnibus00.cs.umd.edu falcon-sensor-bpf[935]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225
== grosh (2 distinct, 2 total) ==
Sep 25 23:48:13 grosh falcon-sensor-bpf[3220]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225
Sep 25 23:48:13 grosh falcon-sensor-bpf[3220]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225
== hackerman (2 distinct, 2 total) ==
Sep 25 23:44:25 hackerman falcon-sensor-bpf[896]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225
Sep 25 23:44:25 hackerman falcon-sensor-bpf[896]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225
== haproxy02.cs.umd.edu (2 distinct, 2 total) ==
Sep 25 23:44:55 haproxy02.cs.umd.edu falcon-sensor-bpf[990]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225
Sep 25 23:44:55 haproxy02.cs.umd.edu falcon-sensor-bpf[990]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225
== haproxy03.cs.umd.edu (2 distinct, 2 total) ==
Sep 25 23:32:48 haproxy03.cs.umd.edu falcon-sensor-bpf[1401]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225
Sep 25 23:32:48 haproxy03.cs.umd.edu falcon-sensor-bpf[1401]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225
== hasaraumd (2 distinct, 2 total) ==
Sep 25 23:31:14 hasaraumd falcon-sensor-bpf[730]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225
Sep 25 23:31:14 hasaraumd falcon-sensor-bpf[730]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225
== hspc (3 distinct, 3 total) ==
Sep 25 23:34:48 hspc falcon-sensor-bpf[1008]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225
Sep 25 23:34:48 hspc falcon-sensor-bpf[1008]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225
Sep 26 00:00:03 hspc kernel: kauditd_printk_skb: 2 callbacks suppressed
== idm00 (1 distinct, 1 total) ==
Sep 25 23:54:08 idm00 named[4166701]: client @0x7f11a403a7a8 10.73.240.42#54941: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 25 23:39:29 idmp0 named[1598691]: client @0x7f2d4c02e298 10.73.240.43#49511: update '73.10.in-addr.arpa/IN' denied
== irb2156 (2 distinct, 2 total) ==
Sep 25 23:32:41 irb2156 falcon-sensor-bpf[3728]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225
Sep 25 23:32:41 irb2156 falcon-sensor-bpf[3728]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225
== jaws.cs.umd.edu (2 distinct, 2 total) ==
Sep 25 23:30:10 jaws.cs.umd.edu falcon-sensor-bpf[1192]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225
Sep 25 23:30:10 jaws.cs.umd.edu falcon-sensor-bpf[1192]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225
== kadath.cs.umd.edu (2 distinct, 2 total) ==
Sep 25 23:32:02 kadath.cs.umd.edu falcon-sensor-bpf[938]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225
Sep 25 23:32:02 kadath.cs.umd.edu falcon-sensor-bpf[938]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225
== krispykreme.cs.umd.edu (3 distinct, 3 total) ==
Sep 25 23:09:32 krispykreme.cs.umd.edu sshd-session[2616560]: pam_access(sshd:auth): access denied for user `bahar' from `173.66.227.191'
Sep 25 23:28:18 krispykreme.cs.umd.edu falcon-sensor-bpf[1298]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225
Sep 25 23:28:18 krispykreme.cs.umd.edu falcon-sensor-bpf[1298]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225
== lifepix (2 distinct, 2 total) ==
Sep 25 23:37:57 lifepix falcon-sensor-bpf[875]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225
Sep 25 23:37:57 lifepix falcon-sensor-bpf[875]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225
== mashie (2 distinct, 2 total) ==
Sep 25 23:26:59 mashie falcon-sensor-bpf[786]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225
Sep 25 23:26:59 mashie falcon-sensor-bpf[786]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225
== matrix (1 distinct, 1 total) ==
Sep 26 00:00:06 matrix (nin-node)[3552621]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
== neo-gizmonic (1 distinct, 1 total) ==
Sep 26 00:00:01 neo-gizmonic (nin-node)[2480752]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
== neoavion (1 distinct, 1 total) ==
Sep 26 00:00:25 neoavion (nin-node)[592067]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
== neodontcare.cs.umd.edu (2 distinct, 2 total) ==
Sep 25 23:32:57 neodontcare.cs.umd.edu falcon-sensor-bpf[951]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225
Sep 25 23:32:57 neodontcare.cs.umd.edu falcon-sensor-bpf[951]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225
== neograd (2 distinct, 2 total) ==
Sep 25 23:40:46 neograd falcon-sensor-bpf[697]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225
Sep 25 23:40:46 neograd falcon-sensor-bpf[697]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225
== netman.cs.umd.edu (2 distinct, 2 total) ==
Sep 25 23:28:06 netman.cs.umd.edu falcon-sensor-bpf[1129]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225
Sep 25 23:28:06 netman.cs.umd.edu falcon-sensor-bpf[1129]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225
== newhonors2 (2 distinct, 25 total) ==
Sep 25 23:13:02 newhonors2 dhcpcd[3159136]: dhcpcd is not running [x24]
Sep 26 00:00:14 newhonors2 (nin-node)[3160651]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
== nightingale (2 distinct, 2 total) ==
Sep 25 23:23:25 nightingale falcon-sensor-bpf[870]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225
Sep 25 23:23:25 nightingale falcon-sensor-bpf[870]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225
== ntop00 (96 distinct, 96 total) ==
Sep 25 23:05:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 370) ***
Sep 25 23:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 370) ***
Sep 25 23:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 370, QN: 67/67, ET: 0) ***
Sep 25 23:05:06 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 370, QN: 3772/3772, ET: 5) ***
Sep 25 23:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 371) ***
Sep 25 23:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 371, QN: 4035/4035, ET: 0) ***
Sep 25 23:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 371) ***
Sep 25 23:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 371, QN: 47/47, ET: 0) ***
Sep 25 23:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 372) ***
Sep 25 23:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 372) ***
Sep 25 23:10:02 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 372, QN: 59/59, ET: 1) ***
Sep 25 23:10:06 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 372, QN: 4124/4124, ET: 5) ***
Sep 25 23:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 373) ***
Sep 25 23:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 373, QN: 4968/4968, ET: 0) ***
Sep 25 23:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 373) ***
Sep 25 23:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 373, QN: 55/55, ET: 0) ***
Sep 25 23:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 374) ***
Sep 25 23:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 374) ***
Sep 25 23:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 374, QN: 44/44, ET: 0) ***
Sep 25 23:15:08 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 374, QN: 5481/5481, ET: 7) ***
Sep 25 23:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 375) ***
Sep 25 23:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 375, QN: 4421/4421, ET: 0) ***
Sep 25 23:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 375) ***
Sep 25 23:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 375, QN: 46/46, ET: 0) ***
Sep 25 23:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 376) ***
Sep 25 23:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 376) ***
Sep 25 23:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 376, QN: 49/49, ET: 0) ***
Sep 25 23:20:06 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 376, QN: 3932/3932, ET: 5) ***
Sep 25 23:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 377) ***
Sep 25 23:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 377, QN: 3924/3924, ET: 0) ***
... 66 more distinct messages not shown
== openrepo (1 distinct, 1 total) ==
Sep 26 00:00:47 openrepo (nin-node)[3886635]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
== orchids (2 distinct, 2 total) ==
Sep 25 23:23:23 orchids falcon-sensor-bpf[1099]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225
Sep 25 23:23:23 orchids falcon-sensor-bpf[1099]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225
== outbound00.cs.umd.edu (9 distinct, 29 total) ==
Sep 25 23:09:09 outbound00.cs.umd.edu python3[3914784]: ldapdb [x6]
Sep 26 00:02:40 outbound00.cs.umd.edu sshd-session[3927546]: error: maximum authentication attempts exceeded for root from 84.47.79.252 port 40876 ssh2 [preauth]
Sep 26 00:03:04 outbound00.cs.umd.edu sshd-session[3927560]: error: maximum authentication attempts exceeded for root from 84.47.79.252 port 42640 ssh2 [preauth]
Sep 26 00:03:23 outbound00.cs.umd.edu sshd-session[3927619]: error: maximum authentication attempts exceeded for root from 84.47.79.252 port 44587 ssh2 [preauth]
Sep 26 00:03:29 outbound00.cs.umd.edu krb5_child[3927709]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x16]
Sep 26 00:03:46 outbound00.cs.umd.edu sshd-session[3927705]: error: maximum authentication attempts exceeded for admin from 84.47.79.252 port 46450 ssh2 [preauth]
Sep 26 00:04:02 outbound00.cs.umd.edu sshd-session[3927725]: error: maximum authentication attempts exceeded for admin from 84.47.79.252 port 48062 ssh2 [preauth]
Sep 26 00:04:39 outbound00.cs.umd.edu sshd-session[3927849]: error: maximum authentication attempts exceeded for invalid user oracle from 84.47.79.252 port 50353 ssh2 [preauth]
Sep 26 00:04:58 outbound00.cs.umd.edu sshd-session[3927858]: error: maximum authentication attempts exceeded for invalid user oracle from 84.47.79.252 port 52391 ssh2 [preauth]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 25 23:13:06 outbound01.cs.umd.edu python3[1980995]: ldapdb [x6]
== portal (2 distinct, 2 total) ==
Sep 25 23:25:04 portal falcon-sensor-bpf[7590]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225
Sep 25 23:25:04 portal falcon-sensor-bpf[7590]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225
== quiss (2 distinct, 2 total) ==
Sep 25 23:34:25 quiss falcon-sensor-bpf[1301]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225
Sep 25 23:34:25 quiss falcon-sensor-bpf[1301]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 25 23:11:26 sentry-docker00.cs.umd.edu systemd-udevd[3835440]: Could not generate persistent MAC address for veth58a59c7: No such file or directory
Sep 25 23:11:26 sentry-docker00.cs.umd.edu systemd-udevd[3835439]: Could not generate persistent MAC address for veth4083453: No such file or directory
Sep 25 23:11:26 sentry-docker00.cs.umd.edu systemd-udevd[3835443]: Could not generate persistent MAC address for vethcc2f907: No such file or directory
Sep 25 23:11:26 sentry-docker00.cs.umd.edu systemd-udevd[3835460]: Could not generate persistent MAC address for veth9ada4d3: No such file or directory
Sep 25 23:11:26 sentry-docker00.cs.umd.edu systemd-udevd[3835467]: Could not generate persistent MAC address for veth30e1b21: No such file or directory
Sep 25 23:11:26 sentry-docker00.cs.umd.edu systemd-udevd[3835468]: Could not generate persistent MAC address for veth7a2d0d2: No such file or directory
Sep 25 23:11:26 sentry-docker00.cs.umd.edu systemd-udevd[3835486]: Could not generate persistent MAC address for veth85d1093: No such file or directory
Sep 25 23:11:26 sentry-docker00.cs.umd.edu systemd-udevd[3835493]: Could not generate persistent MAC address for vethe62953f: No such file or directory
Sep 25 23:11:26 sentry-docker00.cs.umd.edu systemd-udevd[3835493]: Could not generate persistent MAC address for veth3e99861: No such file or directory
Sep 25 23:11:26 sentry-docker00.cs.umd.edu systemd-udevd[3835480]: Could not generate persistent MAC address for veth1c5b5fa: No such file or directory
Sep 25 23:31:34 sentry-docker00.cs.umd.edu systemd-udevd[3844759]: link_config: could not get ethtool features for veth3e99861
Sep 25 23:31:34 sentry-docker00.cs.umd.edu systemd-udevd[3844759]: Could not set offload features of veth3e99861: No such device
Sep 25 23:31:34 sentry-docker00.cs.umd.edu systemd-udevd[3844799]: link_config: could not get ethtool features for vethcc2f907
Sep 25 23:31:34 sentry-docker00.cs.umd.edu systemd-udevd[3844799]: Could not set offload features of vethcc2f907: No such device
Sep 25 23:31:35 sentry-docker00.cs.umd.edu systemd-udevd[3844881]: Could not generate persistent MAC address for vethf3193b7: No such file or directory
Sep 25 23:31:35 sentry-docker00.cs.umd.edu systemd-udevd[3844882]: Could not generate persistent MAC address for vethf6ea11b: No such file or directory
Sep 25 23:31:35 sentry-docker00.cs.umd.edu systemd-udevd[3844885]: Could not generate persistent MAC address for veth8c1e4e8: No such file or directory
Sep 25 23:31:35 sentry-docker00.cs.umd.edu systemd-udevd[3844886]: Could not generate persistent MAC address for veth45de23f: No such file or directory
Sep 25 23:31:35 sentry-docker00.cs.umd.edu systemd-udevd[3844909]: Could not generate persistent MAC address for veth8516b60: No such file or directory
Sep 25 23:31:35 sentry-docker00.cs.umd.edu systemd-udevd[3844910]: Could not generate persistent MAC address for veth2fd11e5: No such file or directory
Sep 25 23:31:35 sentry-docker00.cs.umd.edu systemd-udevd[3844932]: Could not generate persistent MAC address for vethd258174: No such file or directory
Sep 25 23:31:35 sentry-docker00.cs.umd.edu systemd-udevd[3844924]: Could not generate persistent MAC address for veth998b4eb: No such file or directory
Sep 25 23:31:35 sentry-docker00.cs.umd.edu systemd-udevd[3844909]: Could not generate persistent MAC address for veth8239bbf: No such file or directory
Sep 25 23:31:35 sentry-docker00.cs.umd.edu systemd-udevd[3844934]: Could not generate persistent MAC address for veth2681827: No such file or directory
Sep 25 23:51:43 sentry-docker00.cs.umd.edu systemd-udevd[3854272]: link_config: could not get ethtool features for veth2681827
Sep 25 23:51:43 sentry-docker00.cs.umd.edu systemd-udevd[3854272]: Could not set offload features of veth2681827: No such device
Sep 25 23:51:43 sentry-docker00.cs.umd.edu systemd-udevd[3854301]: Could not generate persistent MAC address for veth60dad2c: No such file or directory
Sep 25 23:51:43 sentry-docker00.cs.umd.edu systemd-udevd[3854302]: Could not generate persistent MAC address for vethadaa8e8: No such file or directory
Sep 25 23:51:43 sentry-docker00.cs.umd.edu systemd-udevd[3854305]: Could not generate persistent MAC address for vetha04fa3b: No such file or directory
Sep 25 23:51:43 sentry-docker00.cs.umd.edu systemd-udevd[3854306]: Could not generate persistent MAC address for veth1332036: No such file or directory
... 6 more distinct messages not shown
== strawberry (10 distinct, 41 total) ==
Sep 25 23:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 25 23:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 25 23:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 25 23:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 25 23:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 25 23:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 25 23:31:07 strawberry falcon-sensor-bpf[808]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225
Sep 25 23:31:07 strawberry falcon-sensor-bpf[808]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225
Sep 25 23:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
Sep 26 00:00:03 strawberry kernel: kauditd_printk_skb: 2 callbacks suppressed
== stuckeys (2 distinct, 2 total) ==
Sep 25 23:25:39 stuckeys falcon-sensor-bpf[1493]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225
Sep 25 23:25:39 stuckeys falcon-sensor-bpf[1493]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225
== submit26-b9-f1 (1 distinct, 5 total) ==
Sep 25 23:08:34 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x5]
== submit26-b9-f2 (1 distinct, 4 total) ==
Sep 25 23:18:08 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x4]
== submit26-b9-f3 (1 distinct, 7 total) ==
Sep 25 23:05:06 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x7]
== submit26-b9-f4 (1 distinct, 9 total) ==
Sep 25 23:08:11 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x9]
== talkhosts9 (2 distinct, 2 total) ==
Sep 25 23:32:42 talkhosts9 falcon-sensor-bpf[714]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225
Sep 25 23:32:42 talkhosts9 falcon-sensor-bpf[714]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225
== teaching-awards (2 distinct, 2 total) ==
Sep 25 23:30:59 teaching-awards falcon-sensor-bpf[782]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225
Sep 25 23:30:59 teaching-awards falcon-sensor-bpf[782]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225
== tulgey.cs.umd.edu (2 distinct, 2 total) ==
Sep 25 23:30:36 tulgey.cs.umd.edu falcon-sensor-bpf[1526]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225
Sep 25 23:30:36 tulgey.cs.umd.edu falcon-sensor-bpf[1526]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225
== tumtum.cs.umd.edu (2 distinct, 2 total) ==
Sep 25 23:31:46 tumtum.cs.umd.edu falcon-sensor-bpf[1360]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225
Sep 25 23:31:46 tumtum.cs.umd.edu falcon-sensor-bpf[1360]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225
== wraith (3 distinct, 3 total) ==
Sep 25 23:36:56 wraith falcon-sensor[946]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225
Sep 25 23:36:56 wraith falcon-sensor[946]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225
Sep 26 00:00:43 wraith (nin-node)[35562]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
== yogurt (2 distinct, 2 total) ==
Sep 25 23:30:37 yogurt falcon-sensor-bpf[947]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225
Sep 25 23:30:37 yogurt falcon-sensor-bpf[947]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225
== zwicker-computer (3 distinct, 3 total) ==
Sep 25 23:27:38 zwicker-computer falcon-sensor-bpf[718]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225
Sep 25 23:27:38 zwicker-computer falcon-sensor-bpf[718]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225
Sep 26 00:00:10 zwicker-computer kernel: kauditd_printk_skb: 2 callbacks suppressed
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.0463s
Status : exited 0
Output :
Syslog digest — 2026-09-25 23:05 EDT
Processed 1,990 lines, filtered 1,641 (82%). 349 unknown (247 distinct) from 19 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 25 23:00:42 b0b02.cs.umd.edu rustdesk[1124381]: cannot open display:
== gle-dind00.cs.umd.edu (40 distinct, 40 total) ==
Sep 25 22:46:45 gle-dind00.cs.umd.edu systemd-udevd[3388134]: Could not generate persistent MAC address for vethee0b49f: No such file or directory
Sep 25 22:46:45 gle-dind00.cs.umd.edu systemd-udevd[3388132]: Could not generate persistent MAC address for vethda966a8: No such file or directory
Sep 25 22:46:45 gle-dind00.cs.umd.edu systemd-udevd[3388233]: Could not generate persistent MAC address for vethefcd3e1: No such file or directory
Sep 25 22:46:45 gle-dind00.cs.umd.edu systemd-udevd[3388234]: Could not generate persistent MAC address for veth845a7af: No such file or directory
Sep 25 22:46:46 gle-dind00.cs.umd.edu systemd-udevd[3388332]: Could not generate persistent MAC address for veth04ae93d: No such file or directory
Sep 25 22:46:46 gle-dind00.cs.umd.edu systemd-udevd[3388333]: Could not generate persistent MAC address for veth16c39e4: No such file or directory
Sep 25 22:46:48 gle-dind00.cs.umd.edu systemd-udevd[3388432]: Could not generate persistent MAC address for vethf855c9a: No such file or directory
Sep 25 22:46:48 gle-dind00.cs.umd.edu systemd-udevd[3388433]: Could not generate persistent MAC address for veth3888e3a: No such file or directory
Sep 25 22:46:49 gle-dind00.cs.umd.edu systemd-udevd[3388529]: Could not generate persistent MAC address for vethd87f607: No such file or directory
Sep 25 22:46:49 gle-dind00.cs.umd.edu systemd-udevd[3388530]: Could not generate persistent MAC address for veth957bd24: No such file or directory
Sep 25 22:46:50 gle-dind00.cs.umd.edu systemd-udevd[3388701]: Could not generate persistent MAC address for vethc6e54cd: No such file or directory
Sep 25 22:46:50 gle-dind00.cs.umd.edu systemd-udevd[3388702]: Could not generate persistent MAC address for veth30ece1d: No such file or directory
Sep 25 22:46:51 gle-dind00.cs.umd.edu systemd-udevd[3388814]: Could not generate persistent MAC address for veth6f1f1a8: No such file or directory
Sep 25 22:46:51 gle-dind00.cs.umd.edu systemd-udevd[3388813]: Could not generate persistent MAC address for vethcf2e5a4: No such file or directory
Sep 25 22:46:54 gle-dind00.cs.umd.edu systemd-udevd[3388938]: Could not generate persistent MAC address for veth77e7b2e: No such file or directory
Sep 25 22:46:54 gle-dind00.cs.umd.edu systemd-udevd[3388939]: Could not generate persistent MAC address for veth67bef02: No such file or directory
Sep 25 22:46:55 gle-dind00.cs.umd.edu systemd-udevd[3389056]: Could not generate persistent MAC address for veth75e6029: No such file or directory
Sep 25 22:46:55 gle-dind00.cs.umd.edu systemd-udevd[3389055]: Could not generate persistent MAC address for veth464c8f8: No such file or directory
Sep 25 22:47:20 gle-dind00.cs.umd.edu systemd-udevd[3389672]: Could not generate persistent MAC address for vethdf3c3b9: No such file or directory
Sep 25 22:47:20 gle-dind00.cs.umd.edu systemd-udevd[3389673]: Could not generate persistent MAC address for vethf387efe: No such file or directory
Sep 25 22:47:21 gle-dind00.cs.umd.edu systemd-udevd[3389773]: Could not generate persistent MAC address for vethb03c1e8: No such file or directory
Sep 25 22:47:21 gle-dind00.cs.umd.edu systemd-udevd[3389774]: Could not generate persistent MAC address for veth6b0202b: No such file or directory
Sep 25 22:47:22 gle-dind00.cs.umd.edu systemd-udevd[3389873]: Could not generate persistent MAC address for vethbe8b333: No such file or directory
Sep 25 22:47:22 gle-dind00.cs.umd.edu systemd-udevd[3389874]: Could not generate persistent MAC address for veth0edb72c: No such file or directory
Sep 25 22:47:23 gle-dind00.cs.umd.edu systemd-udevd[3389970]: Could not generate persistent MAC address for veth774d443: No such file or directory
Sep 25 22:47:23 gle-dind00.cs.umd.edu systemd-udevd[3389971]: Could not generate persistent MAC address for veth8ebba01: No such file or directory
Sep 25 22:47:24 gle-dind00.cs.umd.edu systemd-udevd[3390067]: Could not generate persistent MAC address for veth31fa132: No such file or directory
Sep 25 22:47:24 gle-dind00.cs.umd.edu systemd-udevd[3390068]: Could not generate persistent MAC address for veth37cb210: No such file or directory
Sep 25 22:47:25 gle-dind00.cs.umd.edu systemd-udevd[3390243]: Could not generate persistent MAC address for veth29d1018: No such file or directory
Sep 25 22:47:25 gle-dind00.cs.umd.edu systemd-udevd[3390242]: Could not generate persistent MAC address for vethe5b2104: No such file or directory
... 10 more distinct messages not shown
== gle-dind02.cs.umd.edu (34 distinct, 34 total) ==
Sep 25 22:46:57 gle-dind02.cs.umd.edu systemd-udevd[2786745]: Could not generate persistent MAC address for veth3b48da5: No such file or directory
Sep 25 22:46:57 gle-dind02.cs.umd.edu systemd-udevd[2786746]: Could not generate persistent MAC address for vethf49e838: No such file or directory
Sep 25 22:46:58 gle-dind02.cs.umd.edu systemd-udevd[2786847]: Could not generate persistent MAC address for veth1465524: No such file or directory
Sep 25 22:46:58 gle-dind02.cs.umd.edu systemd-udevd[2786848]: Could not generate persistent MAC address for veth538a019: No such file or directory
Sep 25 22:46:59 gle-dind02.cs.umd.edu systemd-udevd[2786946]: Could not generate persistent MAC address for veth1e92207: No such file or directory
Sep 25 22:46:59 gle-dind02.cs.umd.edu systemd-udevd[2786945]: Could not generate persistent MAC address for veth384db07: No such file or directory
Sep 25 22:47:00 gle-dind02.cs.umd.edu systemd-udevd[2787042]: Could not generate persistent MAC address for vethec1ddff: No such file or directory
Sep 25 22:47:00 gle-dind02.cs.umd.edu systemd-udevd[2787043]: Could not generate persistent MAC address for veth59a299d: No such file or directory
Sep 25 22:47:01 gle-dind02.cs.umd.edu systemd-udevd[2787141]: Could not generate persistent MAC address for veth521ef62: No such file or directory
Sep 25 22:47:01 gle-dind02.cs.umd.edu systemd-udevd[2787140]: Could not generate persistent MAC address for vethad563d6: No such file or directory
Sep 25 22:47:03 gle-dind02.cs.umd.edu systemd-udevd[2787343]: Could not generate persistent MAC address for veth5be2eb6: No such file or directory
Sep 25 22:47:03 gle-dind02.cs.umd.edu systemd-udevd[2787342]: Could not generate persistent MAC address for veth9ca1ad6: No such file or directory
Sep 25 22:47:04 gle-dind02.cs.umd.edu systemd-udevd[2787540]: Could not generate persistent MAC address for veth7f4d187: No such file or directory
Sep 25 22:47:04 gle-dind02.cs.umd.edu systemd-udevd[2787541]: Could not generate persistent MAC address for veth91e837c: No such file or directory
Sep 25 22:47:15 gle-dind02.cs.umd.edu systemd-udevd[2787999]: Could not generate persistent MAC address for vethf311d8a: No such file or directory
Sep 25 22:47:15 gle-dind02.cs.umd.edu systemd-udevd[2787998]: Could not generate persistent MAC address for veth33127dc: No such file or directory
Sep 25 22:47:16 gle-dind02.cs.umd.edu systemd-udevd[2788101]: Could not generate persistent MAC address for veth3f8bda0: No such file or directory
Sep 25 22:47:16 gle-dind02.cs.umd.edu systemd-udevd[2788102]: Could not generate persistent MAC address for vethb3ce501: No such file or directory
Sep 25 22:47:17 gle-dind02.cs.umd.edu systemd-udevd[2788213]: Could not generate persistent MAC address for vethd69bfd4: No such file or directory
Sep 25 22:47:17 gle-dind02.cs.umd.edu systemd-udevd[2788214]: Could not generate persistent MAC address for vethdb6dcdd: No such file or directory
Sep 25 22:47:19 gle-dind02.cs.umd.edu systemd-udevd[2788328]: Could not generate persistent MAC address for veth1560b4c: No such file or directory
Sep 25 22:47:19 gle-dind02.cs.umd.edu systemd-udevd[2788327]: Could not generate persistent MAC address for veth574c0e4: No such file or directory
Sep 25 22:47:35 gle-dind02.cs.umd.edu systemd-udevd[2788541]: Could not generate persistent MAC address for vetha863195: No such file or directory
Sep 25 22:47:35 gle-dind02.cs.umd.edu systemd-udevd[2788542]: Could not generate persistent MAC address for veth130cc86: No such file or directory
Sep 25 22:47:36 gle-dind02.cs.umd.edu systemd-udevd[2788641]: Could not generate persistent MAC address for veth5fa065e: No such file or directory
Sep 25 22:47:36 gle-dind02.cs.umd.edu systemd-udevd[2788640]: Could not generate persistent MAC address for veth4479a25: No such file or directory
Sep 25 22:47:37 gle-dind02.cs.umd.edu systemd-udevd[2788738]: Could not generate persistent MAC address for veth03a32c1: No such file or directory
Sep 25 22:47:37 gle-dind02.cs.umd.edu systemd-udevd[2788739]: Could not generate persistent MAC address for veth2b29ced: No such file or directory
Sep 25 22:47:38 gle-dind02.cs.umd.edu systemd-udevd[2788837]: Could not generate persistent MAC address for veth3ec6900: No such file or directory
Sep 25 22:47:38 gle-dind02.cs.umd.edu systemd-udevd[2788836]: Could not generate persistent MAC address for veth7555851: No such file or directory
... 4 more distinct messages not shown
== idm00 (1 distinct, 1 total) ==
Sep 25 22:54:08 idm00 named[4166701]: client @0x7f11a93f2098 10.73.240.42#51795: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 25 22:39:29 idmp0 named[1598691]: client @0x7f2d4001be78 10.73.240.43#61675: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 4 total) ==
Sep 25 22:18:49 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x4]
== munin (2 distinct, 2 total) ==
Sep 25 22:08:49 munin sudo[3618107]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory
Sep 25 22:08:49 munin sudo[3618107]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order.
== newhonors.cs.umd.edu (1 distinct, 1 total) ==
Sep 25 23:03:21 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 25 22:13:03 newhonors2 dhcpcd[3157294]: dhcpcd is not running [x24]
== ntop00 (94 distinct, 94 total) ==
Sep 25 22:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 346, QN: 81/81, ET: 0) ***
Sep 25 22:05:10 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 346, QN: 5853/5853, ET: 9) ***
Sep 25 22:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 347) ***
Sep 25 22:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 347, QN: 70/70, ET: 0) ***
Sep 25 22:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 347) ***
Sep 25 22:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 347, QN: 4659/4659, ET: 0) ***
Sep 25 22:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 348) ***
Sep 25 22:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 348) ***
Sep 25 22:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 348, QN: 57/57, ET: 0) ***
Sep 25 22:10:09 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 348, QN: 4647/4647, ET: 8) ***
Sep 25 22:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 349) ***
Sep 25 22:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 349, QN: 60/60, ET: 0) ***
Sep 25 22:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 349) ***
Sep 25 22:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 349, QN: 5445/5445, ET: 0) ***
Sep 25 22:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 350) ***
Sep 25 22:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 350) ***
Sep 25 22:15:02 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 350, QN: 54/54, ET: 1) ***
Sep 25 22:15:11 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 350, QN: 5979/5979, ET: 10) ***
Sep 25 22:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 351) ***
Sep 25 22:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 351, QN: 5973/5973, ET: 0) ***
Sep 25 22:18:02 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 351) ***
Sep 25 22:18:02 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 351, QN: 71/71, ET: 0) ***
Sep 25 22:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 352) ***
Sep 25 22:20:02 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 352) ***
Sep 25 22:20:02 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 352, QN: 82/82, ET: 0) ***
Sep 25 22:20:09 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 352, QN: 5766/5766, ET: 8) ***
Sep 25 22:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 353) ***
Sep 25 22:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 353, QN: 4480/4480, ET: 0) ***
Sep 25 22:23:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 353) ***
Sep 25 22:23:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 353, QN: 60/60, ET: 0) ***
... 64 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 25 22:09:09 outbound00.cs.umd.edu python3[3900675]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 25 22:13:06 outbound01.cs.umd.edu python3[1967018]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 25 22:11:01 sentry-docker00.cs.umd.edu systemd-udevd[3806907]: link_config: could not get ethtool features for veth9579a78
Sep 25 22:11:01 sentry-docker00.cs.umd.edu systemd-udevd[3806907]: Could not set offload features of veth9579a78: No such device
Sep 25 22:11:01 sentry-docker00.cs.umd.edu systemd-udevd[3806976]: Could not generate persistent MAC address for vetheee19a9: No such file or directory
Sep 25 22:11:01 sentry-docker00.cs.umd.edu systemd-udevd[3806977]: Could not generate persistent MAC address for veth0455d53: No such file or directory
Sep 25 22:11:01 sentry-docker00.cs.umd.edu systemd-udevd[3806995]: Could not generate persistent MAC address for vethfb773e0: No such file or directory
Sep 25 22:11:01 sentry-docker00.cs.umd.edu systemd-udevd[3806989]: Could not generate persistent MAC address for vethbac10fd: No such file or directory
Sep 25 22:11:01 sentry-docker00.cs.umd.edu systemd-udevd[3806977]: Could not generate persistent MAC address for veth1f9aa12: No such file or directory
Sep 25 22:11:01 sentry-docker00.cs.umd.edu systemd-udevd[3806997]: Could not generate persistent MAC address for veth67c495d: No such file or directory
Sep 25 22:11:01 sentry-docker00.cs.umd.edu systemd-udevd[3807034]: Could not generate persistent MAC address for veth08793b4: No such file or directory
Sep 25 22:11:01 sentry-docker00.cs.umd.edu systemd-udevd[3807035]: Could not generate persistent MAC address for veth0e0bfc6: No such file or directory
Sep 25 22:11:01 sentry-docker00.cs.umd.edu systemd-udevd[3807040]: Could not generate persistent MAC address for vethcd49dfc: No such file or directory
Sep 25 22:11:01 sentry-docker00.cs.umd.edu systemd-udevd[3807042]: Could not generate persistent MAC address for vethc1b575f: No such file or directory
Sep 25 22:31:09 sentry-docker00.cs.umd.edu systemd-udevd[3816570]: link_config: could not get ethtool features for vetheee19a9
Sep 25 22:31:09 sentry-docker00.cs.umd.edu systemd-udevd[3816570]: Could not set offload features of vetheee19a9: No such device
Sep 25 22:31:10 sentry-docker00.cs.umd.edu systemd-udevd[3816606]: Could not generate persistent MAC address for veth64b49d1: No such file or directory
Sep 25 22:31:10 sentry-docker00.cs.umd.edu systemd-udevd[3816607]: Could not generate persistent MAC address for veth56b338d: No such file or directory
Sep 25 22:31:10 sentry-docker00.cs.umd.edu systemd-udevd[3816610]: Could not generate persistent MAC address for veth8e647bc: No such file or directory
Sep 25 22:31:10 sentry-docker00.cs.umd.edu systemd-udevd[3816611]: Could not generate persistent MAC address for veth35ad7ea: No such file or directory
Sep 25 22:31:10 sentry-docker00.cs.umd.edu systemd-udevd[3816634]: Could not generate persistent MAC address for veth221ed68: No such file or directory
Sep 25 22:31:10 sentry-docker00.cs.umd.edu systemd-udevd[3816635]: Could not generate persistent MAC address for vethd94e303: No such file or directory
Sep 25 22:31:10 sentry-docker00.cs.umd.edu systemd-udevd[3816638]: Could not generate persistent MAC address for vethb5ab971: No such file or directory
Sep 25 22:31:10 sentry-docker00.cs.umd.edu systemd-udevd[3816640]: Could not generate persistent MAC address for veth3374adb: No such file or directory
Sep 25 22:31:10 sentry-docker00.cs.umd.edu systemd-udevd[3816646]: Could not generate persistent MAC address for veth826538d: No such file or directory
Sep 25 22:31:10 sentry-docker00.cs.umd.edu systemd-udevd[3816649]: Could not generate persistent MAC address for vethfa0c6f7: No such file or directory
Sep 25 22:51:18 sentry-docker00.cs.umd.edu systemd-udevd[3826005]: link_config: could not get ethtool features for veth64b49d1
Sep 25 22:51:18 sentry-docker00.cs.umd.edu systemd-udevd[3826005]: Could not set offload features of veth64b49d1: No such device
Sep 25 22:51:18 sentry-docker00.cs.umd.edu systemd-udevd[3826064]: Could not generate persistent MAC address for veth3a48aaa: No such file or directory
Sep 25 22:51:18 sentry-docker00.cs.umd.edu systemd-udevd[3826065]: Could not generate persistent MAC address for veth7709cde: No such file or directory
Sep 25 22:51:18 sentry-docker00.cs.umd.edu systemd-udevd[3826068]: Could not generate persistent MAC address for veth525bf61: No such file or directory
Sep 25 22:51:18 sentry-docker00.cs.umd.edu systemd-udevd[3826076]: Could not generate persistent MAC address for veth95a247d: No such file or directory
... 6 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 25 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 25 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 25 22:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 25 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 25 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 25 22:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 25 22:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (10 distinct, 22 total) ==
Sep 25 22:07:18 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x10]
Sep 25 22:25:56 submit26-b9-f1 setroubleshoot[3712375]: 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
Sep 25 22:25:56 submit26-b9-f1 setroubleshoot[3712375]: 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
Sep 25 22:25:56 submit26-b9-f1 setroubleshoot[3712375]: 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 [x2]
Sep 25 22:25:56 submit26-b9-f1 setroubleshoot[3712375]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.ITNU8P/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d [x2]
Sep 25 22:25:56 submit26-b9-f1 setroubleshoot[3712375]: 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 [x2]
Sep 25 22:25:56 submit26-b9-f1 setroubleshoot[3712375]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.ITNU8P. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8
Sep 25 22:25:56 submit26-b9-f1 setroubleshoot[3712375]: 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
Sep 25 22:25:56 submit26-b9-f1 setroubleshoot[3712375]: 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 25 22:25:56 submit26-b9-f1 setroubleshoot[3712375]: 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
== submit26-b9-f2 (10 distinct, 17 total) ==
Sep 25 22:06:51 submit26-b9-f2 setroubleshoot[2796099]: 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 25 22:06:51 submit26-b9-f2 setroubleshoot[2796099]: 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 25 22:06:51 submit26-b9-f2 setroubleshoot[2796099]: 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 25 22:06:51 submit26-b9-f2 setroubleshoot[2796099]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.7AQV12/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876
Sep 25 22:06:51 submit26-b9-f2 setroubleshoot[2796099]: 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 25 22:06:51 submit26-b9-f2 setroubleshoot[2796099]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.7AQV12. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8
Sep 25 22:06:51 submit26-b9-f2 setroubleshoot[2796099]: 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 25 22:06:51 submit26-b9-f2 setroubleshoot[2796099]: 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 25 22:06:51 submit26-b9-f2 setroubleshoot[2796099]: 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 25 22:15:07 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x8]
== submit26-b9-f3 (1 distinct, 12 total) ==
Sep 25 22:06:46 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x12]
== submit26-b9-f4 (1 distinct, 6 total) ==
Sep 25 22:07:58 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x6]
== vacuum.cs.umd.edu (4 distinct, 4 total) ==
Sep 25 22:11:58 vacuum.cs.umd.edu abrt-hook-ccpp[32455]: Process 28037 (driver) of user 33 killed by SIGSEGV - dumping core
Sep 25 22:11:58 vacuum.cs.umd.edu abrt-server[32457]: Package 'amanda-backup_server' isn't signed with proper key
Sep 25 22:11:58 vacuum.cs.umd.edu abrt-server[32457]: 'post-create' on '/var/spool/abrt/ccpp-2026-09-25-22:11:58-28037' exited with 1
Sep 25 22:11:58 vacuum.cs.umd.edu abrt-server[32457]: Deleting problem directory '/var/spool/abrt/ccpp-2026-09-25-22:11:58-28037'
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.0424s
Status : exited 0
Output :
Syslog digest — 2026-09-25 22:05 EDT
Processed 1,686 lines, filtered 1,409 (83%). 277 unknown (174 distinct) from 17 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 25 22:00:38 b0b02.cs.umd.edu rustdesk[1109223]: cannot open display:
== biggulp.cs.umd.edu (1 distinct, 1 total) ==
Sep 25 21:27:16 biggulp.cs.umd.edu sshd-session[64386]: error: send_error: write: Connection reset by peer
== galax (2 distinct, 2 total) ==
Sep 25 21:08:45 galax kernel: workqueue: dm_irq_work_func [amdgpu] hogged CPU for >10000us 259 times, consider switching to WQ_UNBOUND
Sep 25 21:54:55 galax kernel: workqueue: dm_irq_work_func [amdgpu] hogged CPU for >10000us 515 times, consider switching to WQ_UNBOUND
== idm00 (1 distinct, 1 total) ==
Sep 25 21:54:07 idm00 named[4166701]: client @0x7f11980104c8 10.73.240.42#55055: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 25 21:39:29 idmp0 named[1598691]: client @0x7f2d4c01bf08 10.73.240.43#61505: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 1 total) ==
Sep 25 21:58:49 itmon02 sshd[1483508]: error: beginning MaxStartups throttling
== munin (2 distinct, 14 total) ==
Sep 25 21:08:28 munin sudo[3596321]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x7]
Sep 25 21:08:28 munin sudo[3596321]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x7]
== newhonors2 (1 distinct, 24 total) ==
Sep 25 21:13:03 newhonors2 dhcpcd[3155452]: dhcpcd is not running [x24]
== ntop00 (97 distinct, 97 total) ==
Sep 25 21:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 322) ***
Sep 25 21:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 322, QN: 58/58, ET: 0) ***
Sep 25 21:05:16 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 322, QN: 10783/10783, ET: 15) ***
Sep 25 21:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 323) ***
Sep 25 21:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 323, QN: 6829/6829, ET: 0) ***
Sep 25 21:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 323) ***
Sep 25 21:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 323, QN: 54/54, ET: 0) ***
Sep 25 21:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 324) ***
Sep 25 21:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 324) ***
Sep 25 21:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 324, QN: 42/42, ET: 0) ***
Sep 25 21:10:08 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 324, QN: 4318/4318, ET: 7) ***
Sep 25 21:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 325) ***
Sep 25 21:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 325, QN: 4779/4779, ET: 0) ***
Sep 25 21:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 325) ***
Sep 25 21:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 325, QN: 47/47, ET: 0) ***
Sep 25 21:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 326) ***
Sep 25 21:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 326, QN: 61/61, ET: 0) ***
Sep 25 21:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 326) ***
Sep 25 21:15:08 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 326, QN: 4926/4926, ET: 7) ***
Sep 25 21:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 327) ***
Sep 25 21:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 327, QN: 5294/5294, ET: 0) ***
Sep 25 21:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 327) ***
Sep 25 21:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 327, QN: 59/59, ET: 0) ***
Sep 25 21:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 328) ***
Sep 25 21:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 328) ***
Sep 25 21:20:02 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 328, QN: 61/61, ET: 1) ***
Sep 25 21:20:07 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 328, QN: 4805/4805, ET: 6) ***
Sep 25 21:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 329) ***
Sep 25 21:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 329, QN: 3997/3997, ET: 0) ***
Sep 25 21:23:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 329) ***
... 67 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 25 21:09:09 outbound00.cs.umd.edu python3[3886689]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 25 21:13:06 outbound01.cs.umd.edu python3[1952861]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 25 21:10:36 sentry-docker00.cs.umd.edu systemd-udevd[3778388]: link_config: could not get ethtool features for vethaff3c50
Sep 25 21:10:36 sentry-docker00.cs.umd.edu systemd-udevd[3778388]: Could not set offload features of vethaff3c50: No such device
Sep 25 21:10:36 sentry-docker00.cs.umd.edu systemd-udevd[3778554]: Could not generate persistent MAC address for vethfc33202: No such file or directory
Sep 25 21:10:36 sentry-docker00.cs.umd.edu systemd-udevd[3778555]: Could not generate persistent MAC address for veth6100919: No such file or directory
Sep 25 21:10:36 sentry-docker00.cs.umd.edu systemd-udevd[3778580]: Could not generate persistent MAC address for vethe9b11d7: No such file or directory
Sep 25 21:10:36 sentry-docker00.cs.umd.edu systemd-udevd[3778581]: Could not generate persistent MAC address for veth45db6f0: No such file or directory
Sep 25 21:10:36 sentry-docker00.cs.umd.edu systemd-udevd[3778584]: Could not generate persistent MAC address for veth271b1b2: No such file or directory
Sep 25 21:10:36 sentry-docker00.cs.umd.edu systemd-udevd[3778585]: Could not generate persistent MAC address for veth5c63b37: No such file or directory
Sep 25 21:10:36 sentry-docker00.cs.umd.edu systemd-udevd[3778614]: Could not generate persistent MAC address for vethb63cba4: No such file or directory
Sep 25 21:10:36 sentry-docker00.cs.umd.edu systemd-udevd[3778613]: Could not generate persistent MAC address for vethd28dca3: No such file or directory
Sep 25 21:10:36 sentry-docker00.cs.umd.edu systemd-udevd[3778617]: Could not generate persistent MAC address for veth8e55669: No such file or directory
Sep 25 21:10:36 sentry-docker00.cs.umd.edu systemd-udevd[3778614]: Could not generate persistent MAC address for vethe6eab97: No such file or directory
Sep 25 21:30:44 sentry-docker00.cs.umd.edu systemd-udevd[3788408]: link_config: could not get ethtool features for vethe9b11d7
Sep 25 21:30:44 sentry-docker00.cs.umd.edu systemd-udevd[3788408]: Could not set offload features of vethe9b11d7: No such device
Sep 25 21:30:45 sentry-docker00.cs.umd.edu systemd-udevd[3788437]: Could not generate persistent MAC address for vethc276090: No such file or directory
Sep 25 21:30:45 sentry-docker00.cs.umd.edu systemd-udevd[3788438]: Could not generate persistent MAC address for veth17731a4: No such file or directory
Sep 25 21:30:45 sentry-docker00.cs.umd.edu systemd-udevd[3788441]: Could not generate persistent MAC address for vethcf03cee: No such file or directory
Sep 25 21:30:45 sentry-docker00.cs.umd.edu systemd-udevd[3788442]: Could not generate persistent MAC address for veth4e5003d: No such file or directory
Sep 25 21:30:45 sentry-docker00.cs.umd.edu systemd-udevd[3788447]: Could not generate persistent MAC address for vethad9f0b0: No such file or directory
Sep 25 21:30:45 sentry-docker00.cs.umd.edu systemd-udevd[3788460]: Could not generate persistent MAC address for veth1481b88: No such file or directory
Sep 25 21:30:45 sentry-docker00.cs.umd.edu systemd-udevd[3788460]: Could not generate persistent MAC address for veth524f058: No such file or directory
Sep 25 21:30:45 sentry-docker00.cs.umd.edu systemd-udevd[3788447]: Could not generate persistent MAC address for veth1c243c5: No such file or directory
Sep 25 21:30:45 sentry-docker00.cs.umd.edu systemd-udevd[3788447]: Could not generate persistent MAC address for vethf67fc5a: No such file or directory
Sep 25 21:30:45 sentry-docker00.cs.umd.edu systemd-udevd[3788460]: Could not generate persistent MAC address for vethceed3c4: No such file or directory
Sep 25 21:50:53 sentry-docker00.cs.umd.edu systemd-udevd[3797757]: link_config: could not get ethtool features for vethc276090
Sep 25 21:50:53 sentry-docker00.cs.umd.edu systemd-udevd[3797757]: Could not set offload features of vethc276090: No such device
Sep 25 21:50:53 sentry-docker00.cs.umd.edu systemd-udevd[3797793]: Could not generate persistent MAC address for veth94cfe54: No such file or directory
Sep 25 21:50:53 sentry-docker00.cs.umd.edu systemd-udevd[3797794]: Could not generate persistent MAC address for veth3f4dbd3: No such file or directory
Sep 25 21:50:53 sentry-docker00.cs.umd.edu systemd-udevd[3797797]: Could not generate persistent MAC address for veth8c5fe41: No such file or directory
Sep 25 21:50:53 sentry-docker00.cs.umd.edu systemd-udevd[3797798]: Could not generate persistent MAC address for veth4604142: No such file or directory
... 6 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 25 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 25 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 25 21:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 25 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 25 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 25 21:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 25 21:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (1 distinct, 8 total) ==
Sep 25 21:19:50 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x8]
== submit26-b9-f2 (1 distinct, 5 total) ==
Sep 25 21:10:16 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x5]
== submit26-b9-f3 (10 distinct, 20 total) ==
Sep 25 21:06:45 submit26-b9-f3 setroubleshoot[3462154]: 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 25 21:06:45 submit26-b9-f3 setroubleshoot[3462154]: 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 25 21:06:45 submit26-b9-f3 setroubleshoot[3462154]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 580b20e4-ec2c-433d-905c-5bd417fba033 [x2]
Sep 25 21:06:45 submit26-b9-f3 setroubleshoot[3462154]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.f0iQKA/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f [x2]
Sep 25 21:06:45 submit26-b9-f3 setroubleshoot[3462154]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l bff72452-d40a-430b-9060-dd0a48f5b6ba [x2]
Sep 25 21:06:45 submit26-b9-f3 setroubleshoot[3462154]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.f0iQKA. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd
Sep 25 21:06:45 submit26-b9-f3 setroubleshoot[3462154]: 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 25 21:06:45 submit26-b9-f3 setroubleshoot[3462154]: 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 25 21:06:45 submit26-b9-f3 setroubleshoot[3462154]: 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 25 21:13:07 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x8]
== submit26-b9-f4 (10 distinct, 16 total) ==
Sep 25 21:08:13 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x4]
Sep 25 21:24:48 submit26-b9-f4 setroubleshoot[2528623]: 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 25 21:24:49 submit26-b9-f4 setroubleshoot[2528623]: 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 25 21:24:49 submit26-b9-f4 setroubleshoot[2528623]: 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 25 21:24:49 submit26-b9-f4 setroubleshoot[2528623]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.5CWXGp/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 [x2]
Sep 25 21:24:49 submit26-b9-f4 setroubleshoot[2528623]: 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 25 21:24:49 submit26-b9-f4 setroubleshoot[2528623]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.5CWXGp. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c
Sep 25 21:24:49 submit26-b9-f4 setroubleshoot[2528623]: 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 25 21:24:49 submit26-b9-f4 setroubleshoot[2528623]: 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 25 21:24:49 submit26-b9-f4 setroubleshoot[2528623]: 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
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.0420s
Status : exited 0
Output :
Syslog digest — 2026-09-25 21:05 EDT
Processed 1,829 lines, filtered 1,564 (85%). 265 unknown (173 distinct) from 19 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 25 21:00:34 b0b02.cs.umd.edu rustdesk[1093638]: cannot open display:
== galax (11 distinct, 11 total) ==
Sep 25 20:17:25 galax falcon-sensor[1499]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225
Sep 25 20:17:25 galax falcon-sensor[1499]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225
Sep 25 20:22:46 galax kernel: workqueue: dm_irq_work_func [amdgpu] hogged CPU for >10000us 4 times, consider switching to WQ_UNBOUND
Sep 25 20:22:57 galax kernel: workqueue: dm_irq_work_func [amdgpu] hogged CPU for >10000us 5 times, consider switching to WQ_UNBOUND
Sep 25 20:23:19 galax kernel: workqueue: dm_irq_work_func [amdgpu] hogged CPU for >10000us 7 times, consider switching to WQ_UNBOUND
Sep 25 20:24:02 galax kernel: workqueue: dm_irq_work_func [amdgpu] hogged CPU for >10000us 11 times, consider switching to WQ_UNBOUND
Sep 25 20:24:44 galax kernel: hrtimer: interrupt took 14898 ns
Sep 25 20:25:29 galax kernel: workqueue: dm_irq_work_func [amdgpu] hogged CPU for >10000us 19 times, consider switching to WQ_UNBOUND
Sep 25 20:28:22 galax kernel: workqueue: dm_irq_work_func [amdgpu] hogged CPU for >10000us 35 times, consider switching to WQ_UNBOUND
Sep 25 20:34:08 galax kernel: workqueue: dm_irq_work_func [amdgpu] hogged CPU for >10000us 67 times, consider switching to WQ_UNBOUND
Sep 25 20:45:40 galax kernel: workqueue: dm_irq_work_func [amdgpu] hogged CPU for >10000us 131 times, consider switching to WQ_UNBOUND
== idm00 (1 distinct, 1 total) ==
Sep 25 20:54:07 idm00 named[4166701]: client @0x7f11a006da58 10.73.240.42#51175: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 25 20:39:29 idmp0 named[1598691]: client @0x7f2d2c050c58 10.73.240.43#56676: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 1 total) ==
Sep 25 21:03:02 itmon02 sshd[1483508]: error: beginning MaxStartups throttling
== krispykreme.cs.umd.edu (1 distinct, 1 total) ==
Sep 25 20:06:30 krispykreme.cs.umd.edu sshd-session[2567687]: error: send_error: write: Connection reset by peer
== munin (2 distinct, 10 total) ==
Sep 25 20:13:02 munin sudo[3576076]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x5]
Sep 25 20:13:02 munin sudo[3576076]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x5]
== newhonors2 (1 distinct, 24 total) ==
Sep 25 20:13:02 newhonors2 dhcpcd[3153580]: dhcpcd is not running [x24]
== ntop00 (94 distinct, 94 total) ==
Sep 25 20:05:15 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 298, QN: 8849/8849, ET: 14) ***
Sep 25 20:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 299) ***
Sep 25 20:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 299, QN: 7000/7000, ET: 0) ***
Sep 25 20:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 299) ***
Sep 25 20:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 299, QN: 53/53, ET: 0) ***
Sep 25 20:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 300) ***
Sep 25 20:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 300) ***
Sep 25 20:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 300, QN: 50/50, ET: 0) ***
Sep 25 20:10:11 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 300, QN: 6544/6544, ET: 10) ***
Sep 25 20:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 301) ***
Sep 25 20:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 301, QN: 7373/7373, ET: 0) ***
Sep 25 20:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 301) ***
Sep 25 20:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 301, QN: 47/47, ET: 0) ***
Sep 25 20:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 302) ***
Sep 25 20:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 302) ***
Sep 25 20:15:02 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 302, QN: 45/45, ET: 1) ***
Sep 25 20:15:13 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 302, QN: 7575/7575, ET: 12) ***
Sep 25 20:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 303) ***
Sep 25 20:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 303, QN: 8145/8145, ET: 0) ***
Sep 25 20:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 303) ***
Sep 25 20:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 303, QN: 51/51, ET: 0) ***
Sep 25 20:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 304) ***
Sep 25 20:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 304) ***
Sep 25 20:20:02 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 304, QN: 54/54, ET: 1) ***
Sep 25 20:20:13 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 304, QN: 8691/8691, ET: 12) ***
Sep 25 20:23:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 305) ***
Sep 25 20:23:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 305, QN: 51/51, ET: 0) ***
Sep 25 20:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 305) ***
Sep 25 20:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 305, QN: 8183/8183, ET: 0) ***
Sep 25 20:25:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 306) ***
... 64 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 25 20:09:09 outbound00.cs.umd.edu python3[3872732]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 25 20:13:06 outbound01.cs.umd.edu python3[1938836]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 25 20:10:11 sentry-docker00.cs.umd.edu systemd-udevd[3750148]: link_config: could not get ethtool features for vethe4df8c2
Sep 25 20:10:11 sentry-docker00.cs.umd.edu systemd-udevd[3750148]: Could not set offload features of vethe4df8c2: No such device
Sep 25 20:10:11 sentry-docker00.cs.umd.edu systemd-udevd[3750181]: Could not generate persistent MAC address for veth0c49789: No such file or directory
Sep 25 20:10:11 sentry-docker00.cs.umd.edu systemd-udevd[3750182]: Could not generate persistent MAC address for veth877b6b4: No such file or directory
Sep 25 20:10:11 sentry-docker00.cs.umd.edu systemd-udevd[3750186]: Could not generate persistent MAC address for veth920bd81: No such file or directory
Sep 25 20:10:11 sentry-docker00.cs.umd.edu systemd-udevd[3750185]: Could not generate persistent MAC address for veth40239b5: No such file or directory
Sep 25 20:10:11 sentry-docker00.cs.umd.edu systemd-udevd[3750209]: Could not generate persistent MAC address for vethb94fb08: No such file or directory
Sep 25 20:10:11 sentry-docker00.cs.umd.edu systemd-udevd[3750211]: Could not generate persistent MAC address for veth523d594: No such file or directory
Sep 25 20:10:11 sentry-docker00.cs.umd.edu systemd-udevd[3750224]: Could not generate persistent MAC address for veth39e15f2: No such file or directory
Sep 25 20:10:11 sentry-docker00.cs.umd.edu systemd-udevd[3750233]: Could not generate persistent MAC address for vethf430779: No such file or directory
Sep 25 20:10:12 sentry-docker00.cs.umd.edu systemd-udevd[3750213]: Could not generate persistent MAC address for veth60f78bc: No such file or directory
Sep 25 20:10:12 sentry-docker00.cs.umd.edu systemd-udevd[3750219]: Could not generate persistent MAC address for veth120539b: No such file or directory
Sep 25 20:30:20 sentry-docker00.cs.umd.edu systemd-udevd[3759546]: link_config: could not get ethtool features for vethf430779
Sep 25 20:30:20 sentry-docker00.cs.umd.edu systemd-udevd[3759546]: Could not set offload features of vethf430779: No such device
Sep 25 20:30:20 sentry-docker00.cs.umd.edu systemd-udevd[3759582]: Could not generate persistent MAC address for veth04ee7f7: No such file or directory
Sep 25 20:30:20 sentry-docker00.cs.umd.edu systemd-udevd[3759583]: Could not generate persistent MAC address for veth9459b11: No such file or directory
Sep 25 20:30:20 sentry-docker00.cs.umd.edu systemd-udevd[3759586]: Could not generate persistent MAC address for vethb2ac74a: No such file or directory
Sep 25 20:30:20 sentry-docker00.cs.umd.edu systemd-udevd[3759593]: Could not generate persistent MAC address for vethe2ad52b: No such file or directory
Sep 25 20:30:20 sentry-docker00.cs.umd.edu systemd-udevd[3759597]: Could not generate persistent MAC address for veth036d91e: No such file or directory
Sep 25 20:30:20 sentry-docker00.cs.umd.edu systemd-udevd[3759600]: Could not generate persistent MAC address for veth85711f3: No such file or directory
Sep 25 20:30:20 sentry-docker00.cs.umd.edu systemd-udevd[3759612]: Could not generate persistent MAC address for vethdcff478: No such file or directory
Sep 25 20:30:20 sentry-docker00.cs.umd.edu systemd-udevd[3759613]: Could not generate persistent MAC address for vethdb776db: No such file or directory
Sep 25 20:30:20 sentry-docker00.cs.umd.edu systemd-udevd[3759632]: Could not generate persistent MAC address for vethafeb730: No such file or directory
Sep 25 20:30:20 sentry-docker00.cs.umd.edu systemd-udevd[3759635]: Could not generate persistent MAC address for veth46a6a9b: No such file or directory
Sep 25 20:50:28 sentry-docker00.cs.umd.edu systemd-udevd[3768959]: link_config: could not get ethtool features for veth036d91e
Sep 25 20:50:28 sentry-docker00.cs.umd.edu systemd-udevd[3768959]: Could not set offload features of veth036d91e: No such device
Sep 25 20:50:28 sentry-docker00.cs.umd.edu systemd-udevd[3769011]: Could not generate persistent MAC address for vethed4b7cc: No such file or directory
Sep 25 20:50:28 sentry-docker00.cs.umd.edu systemd-udevd[3769012]: Could not generate persistent MAC address for veth311e471: No such file or directory
Sep 25 20:50:28 sentry-docker00.cs.umd.edu systemd-udevd[3769015]: Could not generate persistent MAC address for vethb832d1a: No such file or directory
Sep 25 20:50:28 sentry-docker00.cs.umd.edu systemd-udevd[3769016]: Could not generate persistent MAC address for veth335ba90: No such file or directory
... 6 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 25 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 25 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 25 20:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 25 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 25 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 25 20:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 25 20:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (1 distinct, 2 total) ==
Sep 25 20:35:07 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x2]
== submit26-b9-f2 (1 distinct, 6 total) ==
Sep 25 20:08:08 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x6]
== submit26-b9-f3 (1 distinct, 11 total) ==
Sep 25 20:05:31 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x11]
== submit26-b9-f4 (1 distinct, 5 total) ==
Sep 25 20:14:18 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x5]
== submit26-b9-fclone (9 distinct, 9 total) ==
Sep 25 20:21:59 submit26-b9-fclone setroubleshoot[489792]: 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 25 20:21:59 submit26-b9-fclone setroubleshoot[489792]: 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 25 20:21:59 submit26-b9-fclone setroubleshoot[489792]: 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 25 20:21:59 submit26-b9-fclone setroubleshoot[489792]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.Ijs7YL/repodata/repomd.xml. For complete SELinux messages run: sealert -l 03e2f521-0e7c-481f-8e92-0602c6adeedc
Sep 25 20:21:59 submit26-b9-fclone setroubleshoot[489792]: 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 25 20:21:59 submit26-b9-fclone setroubleshoot[489792]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.Ijs7YL. For complete SELinux messages run: sealert -l 887adbf9-2bb9-4009-b800-36ddf9ba0db5
Sep 25 20:21:59 submit26-b9-fclone setroubleshoot[489792]: 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 25 20:21:59 submit26-b9-fclone setroubleshoot[489792]: 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 25 20:21:59 submit26-b9-fclone setroubleshoot[489792]: 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
== wraith (2 distinct, 2 total) ==
Sep 25 20:13:23 wraith kernel: workqueue: i915_hpd_poll_init_work [i915] hogged CPU for >10000us 1027 times, consider switching to WQ_UNBOUND
Sep 25 20:14:22 wraith kernel: workqueue: output_poll_execute hogged CPU for >10000us 1027 times, consider switching to WQ_UNBOUND
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.0446s
Status : exited 0
Output :
Syslog digest — 2026-09-25 20:05 EDT
Processed 1,685 lines, filtered 1,318 (78%). 367 unknown (229 distinct) from 22 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 25 20:00:33 b0b02.cs.umd.edu rustdesk[1078610]: cannot open display:
== gle-dind02.cs.umd.edu (67 distinct, 67 total) ==
Sep 25 19:24:29 gle-dind02.cs.umd.edu kernel: systemd invoked oom-killer: gfp_mask=0x6200ca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0
Sep 25 19:24:30 gle-dind02.cs.umd.edu kernel: CPU: 1 PID: 1 Comm: systemd Kdump: loaded Tainted: G X -------- - - 4.18.0-553.162.1.el8_10.x86_64 #1
Sep 25 19:24:30 gle-dind02.cs.umd.edu kernel: Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.17.0-0-gb52ca86e094d-prebuilt.qemu.org 04/01/2014
Sep 25 19:24:30 gle-dind02.cs.umd.edu kernel: Call Trace:
Sep 25 19:24:30 gle-dind02.cs.umd.edu kernel: dump_stack+0x41/0x60
Sep 25 19:24:30 gle-dind02.cs.umd.edu kernel: dump_header+0x4a/0x1df
Sep 25 19:24:30 gle-dind02.cs.umd.edu kernel: oom_kill_process.cold.33+0xb/0x10
Sep 25 19:24:30 gle-dind02.cs.umd.edu kernel: out_of_memory+0x1bd/0x4e0
Sep 25 19:24:30 gle-dind02.cs.umd.edu kernel: __alloc_pages_slowpath+0xbf0/0xcd0
Sep 25 19:24:30 gle-dind02.cs.umd.edu kernel: __alloc_pages_nodemask+0x2e2/0x330
Sep 25 19:24:30 gle-dind02.cs.umd.edu kernel: pagecache_get_page+0xe7/0x330
Sep 25 19:24:30 gle-dind02.cs.umd.edu kernel: filemap_fault+0x6c8/0xa30
Sep 25 19:24:30 gle-dind02.cs.umd.edu kernel: ? __mod_memcg_lruvec_state+0x4a/0xd0
Sep 25 19:24:30 gle-dind02.cs.umd.edu kernel: ? __mod_lruvec_page_state+0x5e/0x80
Sep 25 19:24:30 gle-dind02.cs.umd.edu kernel: ? page_add_file_rmap+0x99/0x150
Sep 25 19:24:30 gle-dind02.cs.umd.edu kernel: ? alloc_set_pte+0xb6/0x420
Sep 25 19:24:30 gle-dind02.cs.umd.edu kernel: ? xas_load+0x8/0x80
Sep 25 19:24:30 gle-dind02.cs.umd.edu kernel: ? _cond_resched+0x15/0x30
Sep 25 19:24:30 gle-dind02.cs.umd.edu kernel: __xfs_filemap_fault+0x6d/0x200 [xfs]
Sep 25 19:24:30 gle-dind02.cs.umd.edu kernel: __do_fault+0x38/0xc0
Sep 25 19:24:30 gle-dind02.cs.umd.edu kernel: handle_pte_fault+0x55d/0x880
Sep 25 19:24:30 gle-dind02.cs.umd.edu kernel: ? ep_read_events_proc+0xe0/0xe0
Sep 25 19:24:30 gle-dind02.cs.umd.edu kernel: __handle_mm_fault+0x552/0x6d0
Sep 25 19:24:30 gle-dind02.cs.umd.edu kernel: handle_mm_fault+0xca/0x2a0
Sep 25 19:24:30 gle-dind02.cs.umd.edu kernel: __do_page_fault+0x1e4/0x440
Sep 25 19:24:30 gle-dind02.cs.umd.edu kernel: do_page_fault+0x37/0x12d
Sep 25 19:24:30 gle-dind02.cs.umd.edu kernel: ? page_fault+0x8/0x30
Sep 25 19:24:30 gle-dind02.cs.umd.edu kernel: page_fault+0x1e/0x30
Sep 25 19:24:30 gle-dind02.cs.umd.edu kernel: RIP: 0033:0x564336fc0e40
Sep 25 19:24:30 gle-dind02.cs.umd.edu kernel: Code: Unable to access opcode bytes at RIP 0x564336fc0e16.
... 37 more distinct messages not shown
== idm00 (1 distinct, 1 total) ==
Sep 25 19:54:07 idm00 named[4166701]: client @0x7f11a0045838 10.73.240.42#64510: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 25 19:39:29 idmp0 named[1598691]: client @0x7f2d400135d8 10.73.240.43#54455: update '73.10.in-addr.arpa/IN' denied
== inbound01.cs.umd.edu (1 distinct, 1 total) ==
Sep 25 19:44:20 inbound01.cs.umd.edu krb5_child[2034623]: Client 'admin(a)UMD.EDU' not found in Kerberos database
== itmon02 (1 distinct, 3 total) ==
Sep 25 19:18:11 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x3]
== mcstic (1 distinct, 4 total) ==
Sep 25 19:27:06 mcstic krb5_child[1119348]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x4]
== munin (2 distinct, 56 total) ==
Sep 25 19:13:53 munin sudo[3554529]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x28]
Sep 25 19:13:53 munin sudo[3554529]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x28]
== netman.cs.umd.edu (1 distinct, 2 total) ==
Sep 25 19:43:04 netman.cs.umd.edu krb5_child[716206]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x2]
== newhonors2 (1 distinct, 24 total) ==
Sep 25 19:13:03 newhonors2 dhcpcd[3151734]: dhcpcd is not running [x24]
== ntop00 (98 distinct, 98 total) ==
Sep 25 19:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 274) ***
Sep 25 19:05:02 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 274, QN: 67/67, ET: 1) ***
Sep 25 19:05:12 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 274, QN: 8448/8448, ET: 11) ***
Sep 25 19:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 275) ***
Sep 25 19:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 275, QN: 8354/8354, ET: 0) ***
Sep 25 19:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 275) ***
Sep 25 19:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 275, QN: 61/61, ET: 0) ***
Sep 25 19:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 276) ***
Sep 25 19:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 276) ***
Sep 25 19:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 276, QN: 53/53, ET: 0) ***
Sep 25 19:10:12 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 276, QN: 8101/8101, ET: 11) ***
Sep 25 19:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 277) ***
Sep 25 19:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 277, QN: 7556/7556, ET: 0) ***
Sep 25 19:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 277) ***
Sep 25 19:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 277, QN: 41/41, ET: 0) ***
Sep 25 19:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 278) ***
Sep 25 19:15:02 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 278) ***
Sep 25 19:15:02 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 278, QN: 60/60, ET: 0) ***
Sep 25 19:15:11 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 278, QN: 7435/7435, ET: 10) ***
Sep 25 19:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 279) ***
Sep 25 19:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 279, QN: 7778/7778, ET: 0) ***
Sep 25 19:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 279) ***
Sep 25 19:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 279, QN: 69/69, ET: 0) ***
Sep 25 19:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 280) ***
Sep 25 19:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 280) ***
Sep 25 19:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 280, QN: 53/53, ET: 0) ***
Sep 25 19:20:12 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 280, QN: 8355/8355, ET: 11) ***
Sep 25 19:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 281) ***
Sep 25 19:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 281, QN: 7779/7779, ET: 0) ***
Sep 25 19:23:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 281) ***
... 68 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 25 19:09:09 outbound00.cs.umd.edu python3[3858773]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 25 19:13:06 outbound01.cs.umd.edu python3[1924865]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (38 distinct, 38 total) ==
Sep 25 19:09:46 sentry-docker00.cs.umd.edu systemd-udevd[3721935]: link_config: could not get ethtool features for veth07902a0
Sep 25 19:09:46 sentry-docker00.cs.umd.edu systemd-udevd[3721935]: Could not set offload features of veth07902a0: No such device
Sep 25 19:09:46 sentry-docker00.cs.umd.edu systemd-udevd[3721964]: Could not generate persistent MAC address for veth0f39963: No such file or directory
Sep 25 19:09:46 sentry-docker00.cs.umd.edu systemd-udevd[3721965]: Could not generate persistent MAC address for vethdd0552f: No such file or directory
Sep 25 19:09:46 sentry-docker00.cs.umd.edu systemd-udevd[3721968]: Could not generate persistent MAC address for veth17a0eac: No such file or directory
Sep 25 19:09:46 sentry-docker00.cs.umd.edu systemd-udevd[3721969]: Could not generate persistent MAC address for vethb124242: No such file or directory
Sep 25 19:09:46 sentry-docker00.cs.umd.edu systemd-udevd[3721970]: Could not generate persistent MAC address for veth45d29d2: No such file or directory
Sep 25 19:09:46 sentry-docker00.cs.umd.edu systemd-udevd[3721981]: Could not generate persistent MAC address for vethea8d31e: No such file or directory
Sep 25 19:09:46 sentry-docker00.cs.umd.edu systemd-udevd[3722001]: Could not generate persistent MAC address for veth1105677: No such file or directory
Sep 25 19:09:46 sentry-docker00.cs.umd.edu systemd-udevd[3722003]: Could not generate persistent MAC address for veth9e8c186: No such file or directory
Sep 25 19:09:46 sentry-docker00.cs.umd.edu systemd-udevd[3722039]: Could not generate persistent MAC address for veth10b5b8a: No such file or directory
Sep 25 19:09:46 sentry-docker00.cs.umd.edu systemd-udevd[3722032]: Could not generate persistent MAC address for vethe5a45dd: No such file or directory
Sep 25 19:29:55 sentry-docker00.cs.umd.edu systemd-udevd[3731399]: link_config: could not get ethtool features for veth45d29d2
Sep 25 19:29:55 sentry-docker00.cs.umd.edu systemd-udevd[3731399]: Could not set offload features of veth45d29d2: No such device
Sep 25 19:29:55 sentry-docker00.cs.umd.edu systemd-udevd[3731400]: link_config: could not get ethtool features for veth17a0eac
Sep 25 19:29:55 sentry-docker00.cs.umd.edu systemd-udevd[3731400]: Could not set offload features of veth17a0eac: No such device
Sep 25 19:29:55 sentry-docker00.cs.umd.edu systemd-udevd[3731435]: Could not generate persistent MAC address for vethdf8aa4e: No such file or directory
Sep 25 19:29:55 sentry-docker00.cs.umd.edu systemd-udevd[3731436]: Could not generate persistent MAC address for vethf9fa459: No such file or directory
Sep 25 19:29:55 sentry-docker00.cs.umd.edu systemd-udevd[3731439]: Could not generate persistent MAC address for vethbdb27a5: No such file or directory
Sep 25 19:29:55 sentry-docker00.cs.umd.edu systemd-udevd[3731441]: Could not generate persistent MAC address for vethcb417bc: No such file or directory
Sep 25 19:29:55 sentry-docker00.cs.umd.edu systemd-udevd[3731459]: Could not generate persistent MAC address for veth44c0aa1: No such file or directory
Sep 25 19:29:55 sentry-docker00.cs.umd.edu systemd-udevd[3731455]: Could not generate persistent MAC address for vethb43ff4e: No such file or directory
Sep 25 19:29:55 sentry-docker00.cs.umd.edu systemd-udevd[3731448]: Could not generate persistent MAC address for veth04cd01b: No such file or directory
Sep 25 19:29:55 sentry-docker00.cs.umd.edu systemd-udevd[3731459]: Could not generate persistent MAC address for vethbadf8a7: No such file or directory
Sep 25 19:29:55 sentry-docker00.cs.umd.edu systemd-udevd[3731509]: Could not generate persistent MAC address for vethf4070f2: No such file or directory
Sep 25 19:29:55 sentry-docker00.cs.umd.edu systemd-udevd[3731511]: Could not generate persistent MAC address for veth5d1669d: No such file or directory
Sep 25 19:50:03 sentry-docker00.cs.umd.edu systemd-udevd[3740777]: link_config: could not get ethtool features for vethdf8aa4e
Sep 25 19:50:03 sentry-docker00.cs.umd.edu systemd-udevd[3740777]: Could not set offload features of vethdf8aa4e: No such device
Sep 25 19:50:03 sentry-docker00.cs.umd.edu systemd-udevd[3740810]: Could not generate persistent MAC address for veth5070ee3: No such file or directory
Sep 25 19:50:03 sentry-docker00.cs.umd.edu systemd-udevd[3740811]: Could not generate persistent MAC address for vethfc788c8: No such file or directory
... 8 more distinct messages not shown
== soul (1 distinct, 2 total) ==
Sep 25 19:25:30 soul krb5_child[792526]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x2]
== strawberry (7 distinct, 38 total) ==
Sep 25 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 25 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 25 19:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 25 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 25 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 25 19:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 25 19:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (1 distinct, 6 total) ==
Sep 25 19:07:03 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x6]
== submit26-b9-f2 (1 distinct, 2 total) ==
Sep 25 19:53:47 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x2]
== submit26-b9-f3 (1 distinct, 4 total) ==
Sep 25 19:14:59 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x4]
== submit26-b9-f4 (1 distinct, 4 total) ==
Sep 25 19:15:39 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x4]
== teaching-awards (1 distinct, 1 total) ==
Sep 25 19:31:11 teaching-awards krb5_child[1656201]: Client 'admin(a)UMD.EDU' not found in Kerberos database
== yogurt (1 distinct, 2 total) ==
Sep 25 19:24:17 yogurt kernel: [drm:radeon_gem_va_update_vm [radeon]] *ERROR* Couldn't update BO_VA (-4) [x2]
1
0