Command: /usr/local/sbin/syslog-digest.py
Time : 7.5247s
Status : exited 0
Output :
Syslog digest — 2026-09-27 06:05 EDT
Processed 120,326 lines, filtered 1,444 (1%). 118,882 unknown (134 distinct) from 15 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 27 06:02:36 b0b02.cs.umd.edu rustdesk[1599973]: cannot open display:
== grades01.cs.umd.edu (1 distinct, 1 total) ==
Sep 27 05:49:02 grades01.cs.umd.edu puppet-agent[8578]: The directory '/srv/grades' contains 2471 entries, which exceeds the default soft limit 1000 and may cause excessive resource consumption and degraded performance. To remove this warning set a value for `max_files` parameter or consider using an alternate method to manage large directory trees
== idm00 (1 distinct, 1 total) ==
Sep 27 05:54:09 idm00 named[4166701]: client @0x7f11a4042778 10.73.240.42#65343: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 27 05:39:28 idmp0 named[1598691]: client @0x7f2d200241d8 10.73.240.43#59923: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 5 total) ==
Sep 27 05:13:32 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x5]
== matrix (4 distinct, 5 total) ==
Sep 27 05:06:38 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 369032, but reception only permitted for main PID 720
Sep 27 05:06:38 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 369037, but reception only permitted for main PID 720
Sep 27 05:06:38 matrix networkctl[369050]: Interface "vethd12c30e" not found.
Sep 27 05:06:38 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 369050, but reception only permitted for main PID 720 [x2]
== munin (2 distinct, 8 total) ==
Sep 27 05:28:03 munin sudo[106952]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x4]
Sep 27 05:28:03 munin sudo[106952]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x4]
== newhonors2 (1 distinct, 24 total) ==
Sep 27 05:13:03 newhonors2 dhcpcd[3216409]: dhcpcd is not running [x24]
== ntop00 (57 distinct, 118726 total) ==
Sep 27 05:05:34 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 ] [x56628]
Sep 27 05:05:34 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 ] [x53947]
Sep 27 05:05:34 ntop00 rsyslogd[1208]: file '/var/log/maillog'[15] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x235]
Sep 27 05:05:34 ntop00 rsyslogd[1208]: action 'action-3-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x235]
Sep 27 05:05:34 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 ] [x7609]
Sep 27 05:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1091) ***
Sep 27 05:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 1091, QN: 4961/4961, ET: 0) ***
Sep 27 05:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 1091) ***
Sep 27 05:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 1091, QN: 52/52, ET: 0) ***
Sep 27 05:10:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6]
Sep 27 05:10:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x6]
Sep 27 05:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1092) ***
Sep 27 05:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1092, QN: 0/5226, ET: 0) ***
Sep 27 05:10:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6]
Sep 27 05:10:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x6]
Sep 27 05:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1092) ***
Sep 27 05:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1092, QN: 0/51, ET: 0) ***
Sep 27 05:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1095) ***
Sep 27 05:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 1095, QN: 4140/4140, ET: 0) ***
Sep 27 05:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 1095) ***
Sep 27 05:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 1095, QN: 45/45, ET: 0) ***
Sep 27 05:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1096) ***
Sep 27 05:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1096, QN: 0/4311, ET: 0) ***
Sep 27 05:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1096) ***
Sep 27 05:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1096, QN: 0/53, ET: 0) ***
Sep 27 05:28:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1099) ***
Sep 27 05:28:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 1099, QN: 4750/4750, ET: 0) ***
Sep 27 05:28:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 1099) ***
Sep 27 05:28:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 1099, QN: 47/47, ET: 0) ***
Sep 27 05:30:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1100) ***
... 27 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 27 05:09:09 outbound00.cs.umd.edu python3[145212]: ldapdb [x6]
== outbound01.cs.umd.edu (2 distinct, 8 total) ==
Sep 27 05:08:33 outbound01.cs.umd.edu python3[2405867]: ldapdb [x7]
Sep 27 05:09:40 outbound01.cs.umd.edu systemd[1]: Configuration file /usr/lib/systemd/system/authentication_milter.service is marked executable. Please remove executable permission bits. Proceeding anyway.
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 27 05:23:55 sentry-docker00.cs.umd.edu systemd-udevd[496555]: link_config: could not get ethtool features for veth0f0fdb4
Sep 27 05:23:55 sentry-docker00.cs.umd.edu systemd-udevd[496555]: Could not set offload features of veth0f0fdb4: No such device
Sep 27 05:23:55 sentry-docker00.cs.umd.edu systemd-udevd[496556]: link_config: could not get ethtool features for vethfa51150
Sep 27 05:23:55 sentry-docker00.cs.umd.edu systemd-udevd[496556]: Could not set offload features of vethfa51150: No such device
Sep 27 05:23:55 sentry-docker00.cs.umd.edu systemd-udevd[496590]: Could not generate persistent MAC address for vethf636bdb: No such file or directory
Sep 27 05:23:55 sentry-docker00.cs.umd.edu systemd-udevd[496591]: Could not generate persistent MAC address for vetheb21707: No such file or directory
Sep 27 05:23:55 sentry-docker00.cs.umd.edu systemd-udevd[496594]: Could not generate persistent MAC address for veth1135a1b: No such file or directory
Sep 27 05:23:55 sentry-docker00.cs.umd.edu systemd-udevd[496595]: Could not generate persistent MAC address for vethc17d69e: No such file or directory
Sep 27 05:23:55 sentry-docker00.cs.umd.edu systemd-udevd[496619]: Could not generate persistent MAC address for veth1fe5842: No such file or directory
Sep 27 05:23:55 sentry-docker00.cs.umd.edu systemd-udevd[496624]: Could not generate persistent MAC address for veth17bac38: No such file or directory
Sep 27 05:23:55 sentry-docker00.cs.umd.edu systemd-udevd[496698]: Could not generate persistent MAC address for veth9c3f013: No such file or directory
Sep 27 05:23:55 sentry-docker00.cs.umd.edu systemd-udevd[496699]: Could not generate persistent MAC address for veth3b02923: No such file or directory
Sep 27 05:23:55 sentry-docker00.cs.umd.edu systemd-udevd[496702]: Could not generate persistent MAC address for veth725fedd: No such file or directory
Sep 27 05:23:55 sentry-docker00.cs.umd.edu systemd-udevd[496717]: Could not generate persistent MAC address for veth172a34d: No such file or directory
Sep 27 05:44:03 sentry-docker00.cs.umd.edu systemd-udevd[505922]: link_config: could not get ethtool features for veth725fedd
Sep 27 05:44:03 sentry-docker00.cs.umd.edu systemd-udevd[505922]: Could not set offload features of veth725fedd: No such device
Sep 27 05:44:03 sentry-docker00.cs.umd.edu systemd-udevd[506009]: Could not generate persistent MAC address for veth2662a63: No such file or directory
Sep 27 05:44:03 sentry-docker00.cs.umd.edu systemd-udevd[506010]: Could not generate persistent MAC address for vethc9477ab: No such file or directory
Sep 27 05:44:03 sentry-docker00.cs.umd.edu systemd-udevd[506013]: Could not generate persistent MAC address for veth04310dc: No such file or directory
Sep 27 05:44:03 sentry-docker00.cs.umd.edu systemd-udevd[506015]: Could not generate persistent MAC address for veth139f8b7: No such file or directory
Sep 27 05:44:03 sentry-docker00.cs.umd.edu systemd-udevd[506016]: Could not generate persistent MAC address for veth66f235d: No such file or directory
Sep 27 05:44:03 sentry-docker00.cs.umd.edu systemd-udevd[506014]: Could not generate persistent MAC address for veth8ea4b0e: No such file or directory
Sep 27 05:44:03 sentry-docker00.cs.umd.edu systemd-udevd[506061]: Could not generate persistent MAC address for vethb46c07b: No such file or directory
Sep 27 05:44:03 sentry-docker00.cs.umd.edu systemd-udevd[506069]: Could not generate persistent MAC address for vethab533a1: No such file or directory
Sep 27 05:44:03 sentry-docker00.cs.umd.edu systemd-udevd[506115]: Could not generate persistent MAC address for veth63233ea: No such file or directory
Sep 27 05:44:03 sentry-docker00.cs.umd.edu systemd-udevd[506120]: Could not generate persistent MAC address for veth0b4d3bb: No such file or directory
Sep 27 06:04:12 sentry-docker00.cs.umd.edu systemd-udevd[515437]: Could not generate persistent MAC address for vethe13f1ff: No such file or directory
Sep 27 06:04:12 sentry-docker00.cs.umd.edu systemd-udevd[515438]: Could not generate persistent MAC address for veth24f9360: No such file or directory
Sep 27 06:04:12 sentry-docker00.cs.umd.edu systemd-udevd[515441]: Could not generate persistent MAC address for veth7df4a74: No such file or directory
Sep 27 06:04:12 sentry-docker00.cs.umd.edu systemd-udevd[515442]: Could not generate persistent MAC address for veth08ee2de: No such file or directory
... 6 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 27 05:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 27 05:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 27 05:07:04 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 27 05:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 27 05:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 27 05:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 27 05:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f3 (9 distinct, 9 total) ==
Sep 27 05:06:45 submit26-b9-f3 setroubleshoot[3670144]: 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 27 05:06:45 submit26-b9-f3 setroubleshoot[3670144]: 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 27 05:06:45 submit26-b9-f3 setroubleshoot[3670144]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 580b20e4-ec2c-433d-905c-5bd417fba033
Sep 27 05:06:45 submit26-b9-f3 setroubleshoot[3670144]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.w2ViRp/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f
Sep 27 05:06:45 submit26-b9-f3 setroubleshoot[3670144]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l bff72452-d40a-430b-9060-dd0a48f5b6ba
Sep 27 05:06:45 submit26-b9-f3 setroubleshoot[3670144]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.w2ViRp. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd
Sep 27 05:06:45 submit26-b9-f3 setroubleshoot[3670144]: 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 27 05:06:45 submit26-b9-f3 setroubleshoot[3670144]: 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 27 05:06:45 submit26-b9-f3 setroubleshoot[3670144]: 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
== submit26-b9-f4 (10 distinct, 13 total) ==
Sep 27 05:24:48 submit26-b9-f4 setroubleshoot[2683916]: 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 27 05:24:48 submit26-b9-f4 setroubleshoot[2683916]: 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 27 05:24:48 submit26-b9-f4 setroubleshoot[2683916]: 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 27 05:24:48 submit26-b9-f4 setroubleshoot[2683916]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.Wp4Z7D/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0
Sep 27 05:24:48 submit26-b9-f4 setroubleshoot[2683916]: 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 27 05:24:48 submit26-b9-f4 setroubleshoot[2683916]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.Wp4Z7D. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c
Sep 27 05:24:48 submit26-b9-f4 setroubleshoot[2683916]: 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 27 05:24:48 submit26-b9-f4 setroubleshoot[2683916]: 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 [x2]
Sep 27 05:24:48 submit26-b9-f4 setroubleshoot[2683916]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 3178d5f5-80e9-404b-92b7-9bef397a8915
Sep 27 05:24:48 submit26-b9-f4 setroubleshoot[2683916]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.zII8EE/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 7.5369s
Status : exited 0
Output :
Syslog digest — 2026-09-27 05:05 EDT
Processed 120,369 lines, filtered 1,385 (1%). 118,984 unknown (187 distinct) from 17 host(s).
== abadi-computer (2 distinct, 2 total) ==
Sep 27 04:15:00 abadi-computer nologin[1137423]: Attempted login by UNKNOWN (UID: 65534) on UNKNOWN
Sep 27 04:15:00 abadi-computer pipewire[1137422]: 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 27 05:02:32 b0b02.cs.umd.edu rustdesk[1584674]: cannot open display:
== forge00 (1 distinct, 1 total) ==
Sep 27 04:09:03 forge00 (httpd)[1369740]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
== galax (56 distinct, 57 total) ==
Sep 27 04:21:24 galax puppet-agent[406377]: 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 27 04:21:24 galax puppet-agent[406377]: E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. [x2]
Sep 27 04:21:24 galax puppet-agent[406377]: (/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 27 04:21:24 galax puppet-agent[406377]: (/Stage[main]/Choria::Install/Package[choria]/ensure) E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. (corrective)
Sep 27 04:21:24 galax puppet-agent[406377]: (/Stage[main]/Choria::Config/File[/etc/choria]) Skipping because of failed dependencies
Sep 27 04:21:24 galax puppet-agent[406377]: (/Stage[main]/Choria::Config/File[/etc/choria/policies]) Skipping because of failed dependencies
Sep 27 04:21:24 galax puppet-agent[406377]: (/Stage[main]/Choria::Config/File[/etc/choria/policies/rego]) Skipping because of failed dependencies
Sep 27 04:21:24 galax puppet-agent[406377]: (/Stage[main]/Choria::Config/File[/etc/choria/plugin.d]) Skipping because of failed dependencies
Sep 27 04:21:24 galax puppet-agent[406377]: (/Stage[main]/Choria::Config/File[/etc/choria/overrides.json]) Skipping because of failed dependencies
Sep 27 04:21:24 galax puppet-agent[406377]: (/Stage[main]/Choria::Config/File[/etc/choria/machine]) Skipping because of failed dependencies
Sep 27 04:21:24 galax puppet-agent[406377]: (/Stage[main]/Choria::Config/File[/usr/bin/choria_mcollective_agent_compat.rb]) Skipping because of failed dependencies
Sep 27 04:21:24 galax puppet-agent[406377]: (/Stage[main]/Choria::Config/File[/etc/choria/server.conf]) Skipping because of failed dependencies
Sep 27 04:21:24 galax puppet-agent[406377]: (/Stage[main]/Mcollective::Config/File[/etc/choria/server.cfg]) Skipping because of failed dependencies
Sep 27 04:21:24 galax puppet-agent[406377]: (/Stage[main]/Mcollective::Config/File[/etc/choria/client.cfg]) Skipping because of failed dependencies
Sep 27 04:21:24 galax puppet-agent[406377]: (/Stage[main]/Mcollective::Config/File[/etc/choria/policies/choria_util.policy]) Skipping because of failed dependencies
Sep 27 04:21:24 galax puppet-agent[406377]: (/Stage[main]/Mcollective::Config/File[/etc/choria/policies/rpcutil.policy]) Skipping because of failed dependencies
Sep 27 04:21:24 galax puppet-agent[406377]: (/Stage[main]/Mcollective::Config/File[/etc/choria/policies/scout.policy]) Skipping because of failed dependencies
Sep 27 04:21:24 galax puppet-agent[406377]: (/Stage[main]/Mcollective::Config/File[/etc/choria/policies/rego/default.rego]) Skipping because of failed dependencies
Sep 27 04:21:25 galax puppet-agent[406377]: 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 27 04:21:25 galax puppet-agent[406377]: (/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 27 04:21:25 galax puppet-agent[406377]: (/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 27 04:21:26 galax puppet-agent[406377]: (/Stage[main]/Choria::Config/Concat[/etc/choria/policies/groups]/Concat_file[/etc/choria/policies/groups]) Skipping because of failed dependencies
Sep 27 04:21:26 galax puppet-agent[406377]: (/Stage[main]/Choria::Config/Concat[/etc/choria/policies/groups]/File[/etc/choria/policies/groups]) Skipping because of failed dependencies
Sep 27 04:21:26 galax puppet-agent[406377]: (/Stage[main]/Mcollective::Config/Mcollective::Config_file[/etc/choria/client.conf]/File[/etc/choria/client.conf]) Skipping because of failed dependencies
Sep 27 04:21:26 galax puppet-agent[406377]: (/Stage[main]/Mcollective::Config/Mcollective::Config_file[/etc/choria/choria-shim.cfg]/File[/etc/choria/choria-shim.cfg]) Skipping because of failed dependencies
Sep 27 04:21:26 galax puppet-agent[406377]: (/Stage[main]/Mcollective::Facts/Exec[mcollective_facts_yaml_refresh]) Skipping because of failed dependencies
Sep 27 04:21:26 galax puppet-agent[406377]: (/Stage[main]/Mcollective_agent_puppet/Mcollective::Module_plugin[mcollective_agent_puppet]/File[/etc/choria/policies/puppet.policy]) Skipping because of failed dependencies
Sep 27 04:21:26 galax puppet-agent[406377]: (/Stage[main]/Mcollective_agent_service/Mcollective::Module_plugin[mcollective_agent_service]/File[/etc/choria/policies/service.policy]) Skipping because of failed dependencies
Sep 27 04:21:26 galax puppet-agent[406377]: (/Stage[main]/Mcollective_agent_package/Mcollective::Module_plugin[mcollective_agent_package]/File[/etc/choria/policies/package.policy]) Skipping because of failed dependencies
Sep 27 04:21:26 galax puppet-agent[406377]: (/Stage[main]/Mcollective_agent_filemgr/Mcollective::Module_plugin[mcollective_agent_filemgr]/File[/etc/choria/policies/filemgr.policy]) Skipping because of failed dependencies
... 26 more distinct messages not shown
== idm00 (1 distinct, 1 total) ==
Sep 27 04:54:09 idm00 named[4166701]: client @0x7f11a93e2ef8 10.73.240.42#58516: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 27 04:39:28 idmp0 named[1598691]: client @0x7f2d200357a8 10.73.240.43#55697: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 8 total) ==
Sep 27 04:08:41 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x8]
== matrix (9 distinct, 10 total) ==
Sep 27 05:02:59 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 366704, but reception only permitted for main PID 720
Sep 27 05:02:59 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 366715, but reception only permitted for main PID 720
Sep 27 05:03:08 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 366804, but reception only permitted for main PID 720
Sep 27 05:03:08 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 366809, but reception only permitted for main PID 720
Sep 27 05:03:08 matrix systemd-resolved[3892763]: veth847efe6: Failed to determine whether the interface is managed, ignoring: No such file or directory
Sep 27 05:03:08 matrix networkctl[366820]: Interface "veth847efe6" not found.
Sep 27 05:03:08 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 366820, but reception only permitted for main PID 720 [x2]
Sep 27 05:03:08 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 366880, but reception only permitted for main PID 720
Sep 27 05:03:08 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 366888, but reception only permitted for main PID 720
== munin (2 distinct, 48 total) ==
Sep 27 04:18:53 munin sudo[81320]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x24]
Sep 27 04:18:53 munin sudo[81320]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x24]
== newhonors2 (1 distinct, 24 total) ==
Sep 27 04:13:02 newhonors2 dhcpcd[3214542]: dhcpcd is not running [x24]
== ntop00 (57 distinct, 118732 total) ==
Sep 27 04:05:04 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 ] [x56665]
Sep 27 04:05:04 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 ] [x53891]
Sep 27 04:05:04 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 ] [x239]
Sep 27 04:05:04 ntop00 rsyslogd[1208]: action 'action-3-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x239]
Sep 27 04:05:05 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 ] [x7626]
Sep 27 04:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1067) ***
Sep 27 04:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 1067, QN: 4698/4698, ET: 0) ***
Sep 27 04:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 1067) ***
Sep 27 04:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 1067, QN: 60/60, ET: 0) ***
Sep 27 04:10:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6]
Sep 27 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) [x6]
Sep 27 04:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1068) ***
Sep 27 04:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1068, QN: 0/4561, ET: 0) ***
Sep 27 04:10:02 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6]
Sep 27 04:10:02 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x6]
Sep 27 04:10:02 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1068) ***
Sep 27 04:10:02 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1068, QN: 0/61, ET: 0) ***
Sep 27 04:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1071) ***
Sep 27 04:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 1071, QN: 5899/5899, ET: 0) ***
Sep 27 04:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 1071) ***
Sep 27 04:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 1071, QN: 55/55, ET: 0) ***
Sep 27 04:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1072) ***
Sep 27 04:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1072, QN: 0/6384, ET: 0) ***
Sep 27 04:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1072) ***
Sep 27 04:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1072, QN: 0/59, ET: 0) ***
Sep 27 04:28:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1075) ***
Sep 27 04:28:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 1075, QN: 4942/4942, ET: 0) ***
Sep 27 04:28:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 1075) ***
Sep 27 04:28:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 1075, QN: 56/56, ET: 0) ***
Sep 27 04:30:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1076) ***
... 27 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 27 04:09:09 outbound00.cs.umd.edu python3[131215]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 27 04:13:07 outbound01.cs.umd.edu python3[2392654]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (34 distinct, 34 total) ==
Sep 27 04:23:30 sentry-docker00.cs.umd.edu systemd-udevd[468139]: link_config: could not get ethtool features for veth928efaf
Sep 27 04:23:30 sentry-docker00.cs.umd.edu systemd-udevd[468139]: Could not set offload features of veth928efaf: No such device
Sep 27 04:23:30 sentry-docker00.cs.umd.edu systemd-udevd[468168]: Could not generate persistent MAC address for vethe2a8c74: No such file or directory
Sep 27 04:23:30 sentry-docker00.cs.umd.edu systemd-udevd[468169]: Could not generate persistent MAC address for veth55c5d76: No such file or directory
Sep 27 04:23:30 sentry-docker00.cs.umd.edu systemd-udevd[468172]: Could not generate persistent MAC address for veth75405e3: No such file or directory
Sep 27 04:23:30 sentry-docker00.cs.umd.edu systemd-udevd[468173]: Could not generate persistent MAC address for veth7eb7a28: No such file or directory
Sep 27 04:23:30 sentry-docker00.cs.umd.edu systemd-udevd[468196]: Could not generate persistent MAC address for veth1247093: No such file or directory
Sep 27 04:23:30 sentry-docker00.cs.umd.edu systemd-udevd[468197]: Could not generate persistent MAC address for veth9bafd34: No such file or directory
Sep 27 04:23:30 sentry-docker00.cs.umd.edu systemd-udevd[468219]: Could not generate persistent MAC address for vetha071794: No such file or directory
Sep 27 04:23:30 sentry-docker00.cs.umd.edu systemd-udevd[468196]: Could not generate persistent MAC address for veth008cce3: No such file or directory
Sep 27 04:23:30 sentry-docker00.cs.umd.edu systemd-udevd[468214]: Could not generate persistent MAC address for vetha2230a0: No such file or directory
Sep 27 04:23:30 sentry-docker00.cs.umd.edu systemd-udevd[468210]: Could not generate persistent MAC address for veth6741e3d: No such file or directory
Sep 27 04:43:38 sentry-docker00.cs.umd.edu systemd-udevd[477580]: link_config: could not get ethtool features for veth1247093
Sep 27 04:43:38 sentry-docker00.cs.umd.edu systemd-udevd[477580]: Could not set offload features of veth1247093: No such device
Sep 27 04:43:38 sentry-docker00.cs.umd.edu systemd-udevd[477614]: Could not generate persistent MAC address for veth14b7808: No such file or directory
Sep 27 04:43:38 sentry-docker00.cs.umd.edu systemd-udevd[477615]: Could not generate persistent MAC address for vetha3bccbd: No such file or directory
Sep 27 04:43:38 sentry-docker00.cs.umd.edu systemd-udevd[477618]: Could not generate persistent MAC address for veth44c2711: No such file or directory
Sep 27 04:43:38 sentry-docker00.cs.umd.edu systemd-udevd[477619]: Could not generate persistent MAC address for veth920674b: No such file or directory
Sep 27 04:43:38 sentry-docker00.cs.umd.edu systemd-udevd[477635]: Could not generate persistent MAC address for veth249dd8e: No such file or directory
Sep 27 04:43:38 sentry-docker00.cs.umd.edu systemd-udevd[477622]: Could not generate persistent MAC address for veth4a450e8: No such file or directory
Sep 27 04:43:38 sentry-docker00.cs.umd.edu systemd-udevd[477618]: Could not generate persistent MAC address for veth7fdb301: No such file or directory
Sep 27 04:43:39 sentry-docker00.cs.umd.edu systemd-udevd[477621]: Could not generate persistent MAC address for veth6988020: No such file or directory
Sep 27 04:43:39 sentry-docker00.cs.umd.edu systemd-udevd[477639]: Could not generate persistent MAC address for vethf839b04: No such file or directory
Sep 27 04:43:39 sentry-docker00.cs.umd.edu systemd-udevd[477622]: Could not generate persistent MAC address for veth7095131: No such file or directory
Sep 27 05:03:47 sentry-docker00.cs.umd.edu systemd-udevd[487015]: Could not generate persistent MAC address for veth5cf8eb8: No such file or directory
Sep 27 05:03:47 sentry-docker00.cs.umd.edu systemd-udevd[487016]: Could not generate persistent MAC address for veth777fcc2: No such file or directory
Sep 27 05:03:47 sentry-docker00.cs.umd.edu systemd-udevd[487019]: Could not generate persistent MAC address for vethfa51150: No such file or directory
Sep 27 05:03:47 sentry-docker00.cs.umd.edu systemd-udevd[487020]: Could not generate persistent MAC address for veth5feff11: No such file or directory
Sep 27 05:03:47 sentry-docker00.cs.umd.edu systemd-udevd[487043]: Could not generate persistent MAC address for veth0f0fdb4: No such file or directory
Sep 27 05:03:47 sentry-docker00.cs.umd.edu systemd-udevd[487044]: Could not generate persistent MAC address for vetha868110: No such file or directory
... 4 more distinct messages not shown
== smokeping-slave (1 distinct, 1 total) ==
Sep 27 04:15:31 smokeping-slave nologin[2767094]: Attempted login by UNKNOWN (UID: 65534) on UNKNOWN
== strawberry (9 distinct, 40 total) ==
Sep 27 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 27 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 27 04:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 27 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 27 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 27 04:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 27 04:15:04 strawberry nologin[3745996]: Attempted login by UNKNOWN (UID: 65534) on UNKNOWN
Sep 27 04:15:04 strawberry pipewire[3745995]: 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 27 04:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-fclone (9 distinct, 12 total) ==
Sep 27 04:22:01 submit26-b9-fclone setroubleshoot[567752]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 9355d9d9-a311-48d2-bd37-6c0f6947dfff
Sep 27 04:22:01 submit26-b9-fclone setroubleshoot[567752]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l cc4658d7-9db1-405d-9eee-de0ccee5857f
Sep 27 04:22:01 submit26-b9-fclone setroubleshoot[567752]: 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 27 04:22:01 submit26-b9-fclone setroubleshoot[567752]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.kQ75o6/repodata/repomd.xml. For complete SELinux messages run: sealert -l 03e2f521-0e7c-481f-8e92-0602c6adeedc [x2]
Sep 27 04:22:01 submit26-b9-fclone setroubleshoot[567752]: 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 27 04:22:01 submit26-b9-fclone setroubleshoot[567752]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.kQ75o6. For complete SELinux messages run: sealert -l 887adbf9-2bb9-4009-b800-36ddf9ba0db5
Sep 27 04:22:01 submit26-b9-fclone setroubleshoot[567752]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 092e0644-8373-4017-b77f-1afa6c6da4ac
Sep 27 04:22:01 submit26-b9-fclone setroubleshoot[567752]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l ce429a92-56de-4de1-b859-cbfb69ae123c
Sep 27 04:22:01 submit26-b9-fclone setroubleshoot[567752]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 99b886eb-497b-406d-8206-afe76a1086b4
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 7.4168s
Status : exited 0
Output :
Syslog digest — 2026-09-27 04:05 EDT
Processed 118,654 lines, filtered 1,281 (1%). 117,373 unknown (139 distinct) from 15 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 27 04:02:28 b0b02.cs.umd.edu rustdesk[1569184]: cannot open display:
== grosh (3 distinct, 6 total) ==
Sep 27 03:43:12 grosh packagekitd[237952]: Failed to get cache filename for cosmic-epoch [x2]
Sep 27 03:43:12 grosh packagekitd[237952]: Failed to get cache filename for kernel-modules-extra-matched [x2]
Sep 27 03:43:12 grosh packagekitd[237952]: Failed to get cache filename for kernel [x2]
== idm00 (1 distinct, 1 total) ==
Sep 27 03:54:09 idm00 named[4166701]: client @0x7f11a412e378 10.73.240.42#50147: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 27 03:39:28 idmp0 named[1598691]: client @0x7f2d3802f8f8 10.73.240.43#49773: update '73.10.in-addr.arpa/IN' denied
== itmon02 (2 distinct, 3 total) ==
Sep 27 03:15:04 itmon02 (httpd)[757611]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
Sep 27 03:28:12 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x2]
== kadath.cs.umd.edu (1 distinct, 1 total) ==
Sep 27 03:47:32 kadath.cs.umd.edu puppet-agent[2783267]: (Facter) invalid or malformed lldp data: MalformedDataError: no lldp interface data found
== librenms (1 distinct, 1 total) ==
Sep 27 03:47:03 librenms (httpd)[3190810]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
== munin (2 distinct, 16 total) ==
Sep 27 03:12:57 munin sudo[57610]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x8]
Sep 27 03:12:57 munin sudo[57610]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x8]
== netbox (1 distinct, 1 total) ==
Sep 27 03:08:03 netbox (httpd)[837653]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
== newhonors2 (1 distinct, 24 total) ==
Sep 27 03:13:03 newhonors2 dhcpcd[3212699]: dhcpcd is not running [x24]
== ntop00 (79 distinct, 117230 total) ==
Sep 27 03:05:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x11]
Sep 27 03:05:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x12]
Sep 27 03:05: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 27 03:05:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x11]
Sep 27 03:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1042) ***
Sep 27 03:05:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1042) ***
Sep 27 03:05:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1042, QN: 0/5065, ET: 0) ***
Sep 27 03:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1042, QN: 0/51, ET: 0) ***
Sep 27 03: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 ] [x55888]
Sep 27 03: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 ] [x52986]
Sep 27 03:05:09 ntop00 rsyslogd[1208]: file '/var/log/maillog'[15] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x235]
Sep 27 03:05:09 ntop00 rsyslogd[1208]: action 'action-3-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x235]
Sep 27 03: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 ] [x7770]
Sep 27 03:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1043) ***
Sep 27 03:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 1043, QN: 5730/5730, ET: 0) ***
Sep 27 03:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 1043) ***
Sep 27 03:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 1043, QN: 52/52, ET: 0) ***
Sep 27 03:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1044) ***
Sep 27 03:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1044, QN: 0/5230, ET: 0) ***
Sep 27 03:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1044) ***
Sep 27 03:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1044, QN: 0/65, ET: 0) ***
Sep 27 03:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1046) ***
Sep 27 03:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1046, QN: 0/4574, ET: 0) ***
Sep 27 03:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1046) ***
Sep 27 03:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1046, QN: 0/55, ET: 0) ***
Sep 27 03:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1047) ***
Sep 27 03:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 1047, QN: 4343/4343, ET: 0) ***
Sep 27 03:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 1047) ***
Sep 27 03:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 1047, QN: 54/54, ET: 0) ***
Sep 27 03:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1048) ***
... 49 more distinct messages not shown
== outbound00.cs.umd.edu (2 distinct, 8 total) ==
Sep 27 03:09:09 outbound00.cs.umd.edu python3[116497]: ldapdb [x7]
Sep 27 03:24:15 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.
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 27 03:13:06 outbound01.cs.umd.edu python3[2378669]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 27 03:23:05 sentry-docker00.cs.umd.edu systemd-udevd[439658]: link_config: could not get ethtool features for vethc3ea7bd
Sep 27 03:23:05 sentry-docker00.cs.umd.edu systemd-udevd[439658]: Could not set offload features of vethc3ea7bd: No such device
Sep 27 03:23:05 sentry-docker00.cs.umd.edu systemd-udevd[439658]: link_config: could not get ethtool features for veth3ebd151
Sep 27 03:23:05 sentry-docker00.cs.umd.edu systemd-udevd[439658]: Could not set offload features of veth3ebd151: No such device
Sep 27 03:23:05 sentry-docker00.cs.umd.edu systemd-udevd[439778]: Could not generate persistent MAC address for veth7d020f0: No such file or directory
Sep 27 03:23:05 sentry-docker00.cs.umd.edu systemd-udevd[439779]: Could not generate persistent MAC address for veth02ae893: No such file or directory
Sep 27 03:23:05 sentry-docker00.cs.umd.edu systemd-udevd[439797]: Could not generate persistent MAC address for vethb070907: No such file or directory
Sep 27 03:23:05 sentry-docker00.cs.umd.edu systemd-udevd[439802]: Could not generate persistent MAC address for vetha1a619c: No such file or directory
Sep 27 03:23:05 sentry-docker00.cs.umd.edu systemd-udevd[439806]: Could not generate persistent MAC address for veth8cebfac: No such file or directory
Sep 27 03:23:05 sentry-docker00.cs.umd.edu systemd-udevd[439807]: Could not generate persistent MAC address for veth4a84b8a: No such file or directory
Sep 27 03:23:05 sentry-docker00.cs.umd.edu systemd-udevd[439843]: Could not generate persistent MAC address for vetha6c1994: No such file or directory
Sep 27 03:23:05 sentry-docker00.cs.umd.edu systemd-udevd[439827]: Could not generate persistent MAC address for vethe8de0b6: No such file or directory
Sep 27 03:23:05 sentry-docker00.cs.umd.edu systemd-udevd[439923]: Could not generate persistent MAC address for vethcb1bb1d: No such file or directory
Sep 27 03:23:05 sentry-docker00.cs.umd.edu systemd-udevd[439924]: Could not generate persistent MAC address for veth72a0ae9: No such file or directory
Sep 27 03:43:13 sentry-docker00.cs.umd.edu systemd-udevd[449156]: link_config: could not get ethtool features for vethb070907
Sep 27 03:43:13 sentry-docker00.cs.umd.edu systemd-udevd[449156]: Could not set offload features of vethb070907: No such device
Sep 27 03:43:13 sentry-docker00.cs.umd.edu systemd-udevd[449191]: Could not generate persistent MAC address for veth5f39b42: No such file or directory
Sep 27 03:43:13 sentry-docker00.cs.umd.edu systemd-udevd[449192]: Could not generate persistent MAC address for vethe864263: No such file or directory
Sep 27 03:43:13 sentry-docker00.cs.umd.edu systemd-udevd[449195]: Could not generate persistent MAC address for vethf5a5bed: No such file or directory
Sep 27 03:43:13 sentry-docker00.cs.umd.edu systemd-udevd[449196]: Could not generate persistent MAC address for veth192dbee: No such file or directory
Sep 27 03:43:13 sentry-docker00.cs.umd.edu systemd-udevd[449192]: Could not generate persistent MAC address for vethd83fb6b: No such file or directory
Sep 27 03:43:13 sentry-docker00.cs.umd.edu systemd-udevd[449207]: Could not generate persistent MAC address for veth00041a4: No such file or directory
Sep 27 03:43:13 sentry-docker00.cs.umd.edu systemd-udevd[449222]: Could not generate persistent MAC address for vethcb20dd7: No such file or directory
Sep 27 03:43:13 sentry-docker00.cs.umd.edu systemd-udevd[449221]: Could not generate persistent MAC address for veth4695587: No such file or directory
Sep 27 03:43:14 sentry-docker00.cs.umd.edu systemd-udevd[449295]: Could not generate persistent MAC address for vethe72a64d: No such file or directory
Sep 27 03:43:14 sentry-docker00.cs.umd.edu systemd-udevd[449296]: Could not generate persistent MAC address for veth7aa5577: No such file or directory
Sep 27 04:03:22 sentry-docker00.cs.umd.edu systemd-udevd[458632]: Could not generate persistent MAC address for vethd8840d5: No such file or directory
Sep 27 04:03:22 sentry-docker00.cs.umd.edu systemd-udevd[458633]: Could not generate persistent MAC address for vethb4b444a: No such file or directory
Sep 27 04:03:22 sentry-docker00.cs.umd.edu systemd-udevd[458651]: Could not generate persistent MAC address for vethe228cf9: No such file or directory
Sep 27 04:03:22 sentry-docker00.cs.umd.edu systemd-udevd[458636]: Could not generate persistent MAC address for veth7119da7: No such file or directory
... 6 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 27 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 27 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 27 03:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 27 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 27 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 27 03:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 27 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 : 7.5328s
Status : exited 0
Output :
Syslog digest — 2026-09-27 03:05 EDT
Processed 119,686 lines, filtered 1,760 (1%). 117,926 unknown (150 distinct) from 16 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 27 03:02:27 b0b02.cs.umd.edu rustdesk[1554010]: cannot open display:
== biggulp.cs.umd.edu (1 distinct, 4 total) ==
Sep 27 02:15:31 biggulp.cs.umd.edu sshd-session[360004]: error: send_error: write: Connection reset by peer [x4]
== galax (1 distinct, 1 total) ==
Sep 27 02:12:30 galax kernel: rtw89_8922ae 0000:06:00.0: failed to wait RF DACK
== idm00 (1 distinct, 1 total) ==
Sep 27 02:54:09 idm00 named[4166701]: client @0x7f11a0045838 10.73.240.42#52169: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 27 02:39:28 idmp0 named[1598691]: client @0x7f2d3002f808 10.73.240.43#60745: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 4 total) ==
Sep 27 02:08:30 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x4]
== munin (2 distinct, 56 total) ==
Sep 27 02:23:26 munin sudo[40621]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x28]
Sep 27 02:23:26 munin sudo[40621]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x28]
== newhonors2 (1 distinct, 24 total) ==
Sep 27 02:13:03 newhonors2 dhcpcd[3210869]: dhcpcd is not running [x24]
== ntop00 (77 distinct, 117729 total) ==
Sep 27 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 ] [x56135]
Sep 27 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 ] [x53199]
Sep 27 02:05:09 ntop00 rsyslogd[1208]: file '/var/log/maillog'[15] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x235]
Sep 27 02:05:09 ntop00 rsyslogd[1208]: action 'action-3-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x235]
Sep 27 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 ] [x7813]
Sep 27 02:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1019) ***
Sep 27 02:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 1019, QN: 4862/4862, ET: 0) ***
Sep 27 02:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 1019) ***
Sep 27 02:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 1019, QN: 41/41, ET: 0) ***
Sep 27 02:10:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x11]
Sep 27 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) [x11]
Sep 27 02:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1020) ***
Sep 27 02:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1020, QN: 0/5337, ET: 0) ***
Sep 27 02:10:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x11]
Sep 27 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) [x11]
Sep 27 02:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1020) ***
Sep 27 02:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1020, QN: 0/39, ET: 0) ***
Sep 27 02:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1022) ***
Sep 27 02:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1022, QN: 0/5549, ET: 0) ***
Sep 27 02:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1022) ***
Sep 27 02:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1022, QN: 0/57, ET: 0) ***
Sep 27 02:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1023) ***
Sep 27 02:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 1023, QN: 5175/5175, ET: 0) ***
Sep 27 02:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 1023) ***
Sep 27 02:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 1023, QN: 57/57, ET: 0) ***
Sep 27 02:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1024) ***
Sep 27 02:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1024, QN: 0/4681, ET: 0) ***
Sep 27 02:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1024) ***
Sep 27 02:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1024, QN: 0/50, ET: 0) ***
Sep 27 02:25:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1026) ***
... 47 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 27 02:09:09 outbound00.cs.umd.edu python3[102401]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 27 02:13:06 outbound01.cs.umd.edu python3[2364735]: ldapdb [x6]
== sebatinsky.cs.umd.edu (1 distinct, 1 total) ==
Sep 27 03:00:43 sebatinsky.cs.umd.edu kernel: hpet1: lost 1 rtc interrupts
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 27 02:22:40 sentry-docker00.cs.umd.edu systemd-udevd[410862]: link_config: could not set ethtool features for veth6583660
Sep 27 02:22:40 sentry-docker00.cs.umd.edu systemd-udevd[410862]: Could not set offload features of veth6583660: Operation not permitted
Sep 27 02:22:40 sentry-docker00.cs.umd.edu systemd-udevd[410894]: Could not generate persistent MAC address for vethf8cc8a8: No such file or directory
Sep 27 02:22:40 sentry-docker00.cs.umd.edu systemd-udevd[410895]: Could not generate persistent MAC address for veth3dc6def: No such file or directory
Sep 27 02:22:40 sentry-docker00.cs.umd.edu systemd-udevd[410898]: Could not generate persistent MAC address for veth5fabf55: No such file or directory
Sep 27 02:22:40 sentry-docker00.cs.umd.edu systemd-udevd[410904]: Could not generate persistent MAC address for vethcc6ff29: No such file or directory
Sep 27 02:22:40 sentry-docker00.cs.umd.edu systemd-udevd[410899]: Could not generate persistent MAC address for veth2835219: No such file or directory
Sep 27 02:22:40 sentry-docker00.cs.umd.edu systemd-udevd[410912]: Could not generate persistent MAC address for veth2191e18: No such file or directory
Sep 27 02:22:40 sentry-docker00.cs.umd.edu systemd-udevd[410918]: Could not generate persistent MAC address for veth8a7fe98: No such file or directory
Sep 27 02:22:40 sentry-docker00.cs.umd.edu systemd-udevd[410909]: Could not generate persistent MAC address for veth9b51b71: No such file or directory
Sep 27 02:22:40 sentry-docker00.cs.umd.edu systemd-udevd[410904]: Could not generate persistent MAC address for veth07df455: No such file or directory
Sep 27 02:22:40 sentry-docker00.cs.umd.edu systemd-udevd[410912]: Could not generate persistent MAC address for veth9f817c0: No such file or directory
Sep 27 02:42:48 sentry-docker00.cs.umd.edu systemd-udevd[420487]: link_config: could not get ethtool features for veth9b51b71
Sep 27 02:42:48 sentry-docker00.cs.umd.edu systemd-udevd[420487]: Could not set offload features of veth9b51b71: No such device
Sep 27 02:42:49 sentry-docker00.cs.umd.edu systemd-udevd[420521]: Could not generate persistent MAC address for vethde4e2a5: No such file or directory
Sep 27 02:42:49 sentry-docker00.cs.umd.edu systemd-udevd[420522]: Could not generate persistent MAC address for vethfa8f274: No such file or directory
Sep 27 02:42:49 sentry-docker00.cs.umd.edu systemd-udevd[420525]: Could not generate persistent MAC address for veth8eb902b: No such file or directory
Sep 27 02:42:49 sentry-docker00.cs.umd.edu systemd-udevd[420526]: Could not generate persistent MAC address for veth7cc41f7: No such file or directory
Sep 27 02:42:49 sentry-docker00.cs.umd.edu systemd-udevd[420549]: Could not generate persistent MAC address for vethc2b118f: No such file or directory
Sep 27 02:42:49 sentry-docker00.cs.umd.edu systemd-udevd[420550]: Could not generate persistent MAC address for vethecec1ef: No such file or directory
Sep 27 02:42:49 sentry-docker00.cs.umd.edu systemd-udevd[420553]: Could not generate persistent MAC address for vethe873d9c: No such file or directory
Sep 27 02:42:49 sentry-docker00.cs.umd.edu systemd-udevd[420554]: Could not generate persistent MAC address for veth4d37c6e: No such file or directory
Sep 27 02:42:49 sentry-docker00.cs.umd.edu systemd-udevd[420577]: Could not generate persistent MAC address for veth49bb0f5: No such file or directory
Sep 27 02:42:49 sentry-docker00.cs.umd.edu systemd-udevd[420578]: Could not generate persistent MAC address for veth376191f: No such file or directory
Sep 27 03:02:57 sentry-docker00.cs.umd.edu systemd-udevd[430291]: link_config: could not get ethtool features for vethc2b118f
Sep 27 03:02:57 sentry-docker00.cs.umd.edu systemd-udevd[430291]: Could not set offload features of vethc2b118f: No such device
Sep 27 03:02:57 sentry-docker00.cs.umd.edu systemd-udevd[430321]: Could not generate persistent MAC address for vethd8a4158: No such file or directory
Sep 27 03:02:57 sentry-docker00.cs.umd.edu systemd-udevd[430322]: Could not generate persistent MAC address for veth0d1a7c8: No such file or directory
Sep 27 03:02:57 sentry-docker00.cs.umd.edu systemd-udevd[430347]: Could not generate persistent MAC address for veth9821412: No such file or directory
Sep 27 03:02:57 sentry-docker00.cs.umd.edu systemd-udevd[430348]: Could not generate persistent MAC address for vethfa6ce8e: No such file or directory
... 6 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 27 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 27 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 27 02:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 27 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 27 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 27 02:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 27 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 27 02:25:57 submit26-b9-f1 setroubleshoot[3881007]: 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 27 02:25:57 submit26-b9-f1 setroubleshoot[3881007]: 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 27 02:25:57 submit26-b9-f1 setroubleshoot[3881007]: 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 27 02:25:57 submit26-b9-f1 setroubleshoot[3881007]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.1CRSEU/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d
Sep 27 02:25:57 submit26-b9-f1 setroubleshoot[3881007]: 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 27 02:25:57 submit26-b9-f1 setroubleshoot[3881007]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.1CRSEU. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8
Sep 27 02:25:57 submit26-b9-f1 setroubleshoot[3881007]: 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 27 02:25:57 submit26-b9-f1 setroubleshoot[3881007]: 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 27 02:25:57 submit26-b9-f1 setroubleshoot[3881007]: 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, 9 total) ==
Sep 27 02:06:51 submit26-b9-f2 setroubleshoot[2946807]: 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 27 02:06:51 submit26-b9-f2 setroubleshoot[2946807]: 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 27 02:06:51 submit26-b9-f2 setroubleshoot[2946807]: 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 27 02:06:51 submit26-b9-f2 setroubleshoot[2946807]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.tLOEBD/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876
Sep 27 02:06:51 submit26-b9-f2 setroubleshoot[2946807]: 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 27 02:06:51 submit26-b9-f2 setroubleshoot[2946807]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.tLOEBD. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8
Sep 27 02:06:51 submit26-b9-f2 setroubleshoot[2946807]: 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 27 02:06:51 submit26-b9-f2 setroubleshoot[2946807]: 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 27 02:06:51 submit26-b9-f2 setroubleshoot[2946807]: 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 : 7.4737s
Status : exited 0
Output :
Syslog digest — 2026-09-27 02:05 EDT
Processed 119,333 lines, filtered 1,398 (1%). 117,935 unknown (171 distinct) from 15 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 27 02:02:22 b0b02.cs.umd.edu rustdesk[1538741]: cannot open display:
== biggulp.cs.umd.edu (4 distinct, 5 total) ==
Sep 27 01:39:27 biggulp.cs.umd.edu sshd-session[353897]: error: send_error: write: Connection reset by peer
Sep 27 01:52:20 biggulp.cs.umd.edu sshd-session[355808]: pam_access(sshd:auth): access denied for user `larry' from `71.191.93.172' [x2]
Sep 27 01:52:21 biggulp.cs.umd.edu sshd-session[355808]: Error in Duo login for 'larry' from 71.191.93.172
Sep 27 01:52:21 biggulp.cs.umd.edu sshd-session[355806]: error: PAM: Authentication failure for larry from 71.191.93.172
== hazfs.cs.umd.edu (11 distinct, 66 total) ==
Sep 27 01:33:47 hazfs.cs.umd.edu snmpd[1431]: send response: Failure in sendto [x6]
Sep 27 01:33:47 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userweb" [x6]
Sep 27 01:33:47 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."zfslist" [x6]
Sep 27 01:33:47 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userhome" [x6]
Sep 27 01:33:47 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userweb" [x6]
Sep 27 01:33:47 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."zfslist" [x6]
Sep 27 01:33:47 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userhome" [x6]
Sep 27 01:33:47 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userweb" [x6]
Sep 27 01:33:47 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."zfslist" [x6]
Sep 27 01:33:47 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userhome" [x6]
Sep 27 01:33:47 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutNumLines."userweb" [x6]
== idm00 (1 distinct, 1 total) ==
Sep 27 01:54:09 idm00 named[4166701]: client @0x7f119804e448 10.73.240.42#49232: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 27 01:39:28 idmp0 named[1598691]: client @0x7f2d2801dea8 10.73.240.43#60684: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 5 total) ==
Sep 27 01:37:56 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x5]
== newhonors2 (1 distinct, 24 total) ==
Sep 27 01:13:03 newhonors2 dhcpcd[3209007]: dhcpcd is not running [x24]
== ntop00 (84 distinct, 117721 total) ==
Sep 27 01:05:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x13]
Sep 27 01:05:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x13]
Sep 27 01:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 994) ***
Sep 27 01:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 994, QN: 0/59, ET: 0) ***
Sep 27 01: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 ] [x7660]
Sep 27 01: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 ] [x56138]
Sep 27 01: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 ] [x53326]
Sep 27 01:05:09 ntop00 rsyslogd[1208]: file '/var/log/maillog'[15] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x235]
Sep 27 01:05:09 ntop00 rsyslogd[1208]: action 'action-3-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x235]
Sep 27 01:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 995) ***
Sep 27 01:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 995, QN: 4982/4982, ET: 0) ***
Sep 27 01:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 995) ***
Sep 27 01:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 995, QN: 62/62, ET: 0) ***
Sep 27 01:10:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x12]
Sep 27 01: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 27 01:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 996) ***
Sep 27 01:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 996, QN: 0/5332, ET: 0) ***
Sep 27 01:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 996) ***
Sep 27 01:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 996, QN: 0/57, ET: 0) ***
Sep 27 01: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 ] [x3]
Sep 27 01:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 998) ***
Sep 27 01:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 998, QN: 0/4550, ET: 0) ***
Sep 27 01:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 998) ***
Sep 27 01:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 998, QN: 0/44, ET: 0) ***
Sep 27 01:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 999) ***
Sep 27 01:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 999, QN: 4181/4181, ET: 0) ***
Sep 27 01:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 999) ***
Sep 27 01:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 999, QN: 59/59, ET: 0) ***
Sep 27 01:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1000) ***
Sep 27 01:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1000, QN: 0/4835, ET: 0) ***
... 54 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 27 01:09:09 outbound00.cs.umd.edu python3[88452]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 27 01:13:06 outbound01.cs.umd.edu python3[2350588]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 27 01:22:15 sentry-docker00.cs.umd.edu systemd-udevd[382295]: link_config: could not get ethtool features for vethcc2a3ca
Sep 27 01:22:15 sentry-docker00.cs.umd.edu systemd-udevd[382295]: Could not set offload features of vethcc2a3ca: No such device
Sep 27 01:22:15 sentry-docker00.cs.umd.edu systemd-udevd[382335]: Could not generate persistent MAC address for veth2565a2d: No such file or directory
Sep 27 01:22:15 sentry-docker00.cs.umd.edu systemd-udevd[382336]: Could not generate persistent MAC address for veth7f3d35c: No such file or directory
Sep 27 01:22:15 sentry-docker00.cs.umd.edu systemd-udevd[382339]: Could not generate persistent MAC address for vethaef78cf: No such file or directory
Sep 27 01:22:15 sentry-docker00.cs.umd.edu systemd-udevd[382340]: Could not generate persistent MAC address for veth56ad423: No such file or directory
Sep 27 01:22:15 sentry-docker00.cs.umd.edu systemd-udevd[382355]: Could not generate persistent MAC address for vethbcef809: No such file or directory
Sep 27 01:22:15 sentry-docker00.cs.umd.edu systemd-udevd[382360]: Could not generate persistent MAC address for vethfe6192a: No such file or directory
Sep 27 01:22:15 sentry-docker00.cs.umd.edu systemd-udevd[382365]: Could not generate persistent MAC address for veth1b3d073: No such file or directory
Sep 27 01:22:15 sentry-docker00.cs.umd.edu systemd-udevd[382366]: Could not generate persistent MAC address for vethb7c6c03: No such file or directory
Sep 27 01:22:15 sentry-docker00.cs.umd.edu systemd-udevd[382416]: Could not generate persistent MAC address for vethe01ccb9: No such file or directory
Sep 27 01:22:15 sentry-docker00.cs.umd.edu systemd-udevd[382419]: Could not generate persistent MAC address for veth4da65f1: No such file or directory
Sep 27 01:42:23 sentry-docker00.cs.umd.edu systemd-udevd[391963]: link_config: could not get ethtool features for veth1b3d073
Sep 27 01:42:23 sentry-docker00.cs.umd.edu systemd-udevd[391963]: Could not set offload features of veth1b3d073: No such device
Sep 27 01:42:24 sentry-docker00.cs.umd.edu systemd-udevd[392035]: Could not generate persistent MAC address for vethe66ae91: No such file or directory
Sep 27 01:42:24 sentry-docker00.cs.umd.edu systemd-udevd[392036]: Could not generate persistent MAC address for vethe7d5825: No such file or directory
Sep 27 01:42:24 sentry-docker00.cs.umd.edu systemd-udevd[392039]: Could not generate persistent MAC address for vethb1d1906: No such file or directory
Sep 27 01:42:24 sentry-docker00.cs.umd.edu systemd-udevd[392040]: Could not generate persistent MAC address for veth58502ce: No such file or directory
Sep 27 01:42:24 sentry-docker00.cs.umd.edu systemd-udevd[392063]: Could not generate persistent MAC address for veth0ab8b6c: No such file or directory
Sep 27 01:42:24 sentry-docker00.cs.umd.edu systemd-udevd[392064]: Could not generate persistent MAC address for veth88bc1af: No such file or directory
Sep 27 01:42:24 sentry-docker00.cs.umd.edu systemd-udevd[392082]: Could not generate persistent MAC address for veth0a8d887: No such file or directory
Sep 27 01:42:24 sentry-docker00.cs.umd.edu systemd-udevd[392073]: Could not generate persistent MAC address for vethfb794bb: No such file or directory
Sep 27 01:42:24 sentry-docker00.cs.umd.edu systemd-udevd[392079]: Could not generate persistent MAC address for veth1e4876d: No such file or directory
Sep 27 01:42:24 sentry-docker00.cs.umd.edu systemd-udevd[392069]: Could not generate persistent MAC address for vethcaa04a4: No such file or directory
Sep 27 02:02:32 sentry-docker00.cs.umd.edu systemd-udevd[401421]: link_config: could not set ethtool features for veth0a8d887
Sep 27 02:02:32 sentry-docker00.cs.umd.edu systemd-udevd[401421]: Could not set offload features of veth0a8d887: Operation not permitted
Sep 27 02:02:32 sentry-docker00.cs.umd.edu systemd-udevd[401446]: Could not generate persistent MAC address for veth262900a: No such file or directory
Sep 27 02:02:32 sentry-docker00.cs.umd.edu systemd-udevd[401447]: Could not generate persistent MAC address for vethee7109a: No such file or directory
Sep 27 02:02:32 sentry-docker00.cs.umd.edu systemd-udevd[401465]: Could not generate persistent MAC address for vethc206693: No such file or directory
Sep 27 02:02:32 sentry-docker00.cs.umd.edu systemd-udevd[401450]: Could not generate persistent MAC address for veth874fa89: No such file or directory
... 6 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 27 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 27 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 27 01:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 27 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 27 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 27 01:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 27 01:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f2 (1 distinct, 1 total) ==
Sep 27 01:30:07 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
== submit26-b9-f3 (10 distinct, 10 total) ==
Sep 27 01:06:45 submit26-b9-f3 setroubleshoot[3649673]: 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 27 01:06:45 submit26-b9-f3 setroubleshoot[3649673]: 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 27 01:06:45 submit26-b9-f3 setroubleshoot[3649673]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 580b20e4-ec2c-433d-905c-5bd417fba033
Sep 27 01:06:45 submit26-b9-f3 setroubleshoot[3649673]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.oqoEim/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f
Sep 27 01:06:45 submit26-b9-f3 setroubleshoot[3649673]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l bff72452-d40a-430b-9060-dd0a48f5b6ba
Sep 27 01:06:45 submit26-b9-f3 setroubleshoot[3649673]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.oqoEim. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd
Sep 27 01:06:45 submit26-b9-f3 setroubleshoot[3649673]: 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 27 01:06:45 submit26-b9-f3 setroubleshoot[3649673]: 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 27 01:06:45 submit26-b9-f3 setroubleshoot[3649673]: 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 27 01:08:20 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
== submit26-b9-f4 (11 distinct, 14 total) ==
Sep 27 01:24:49 submit26-b9-f4 setroubleshoot[2669749]: 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 27 01:24:49 submit26-b9-f4 setroubleshoot[2669749]: 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 27 01:24:49 submit26-b9-f4 setroubleshoot[2669749]: 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 27 01:24:49 submit26-b9-f4 setroubleshoot[2669749]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.4WQs5e/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0
Sep 27 01:24:49 submit26-b9-f4 setroubleshoot[2669749]: 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 27 01:24:49 submit26-b9-f4 setroubleshoot[2669749]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.4WQs5e. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c
Sep 27 01:24:49 submit26-b9-f4 setroubleshoot[2669749]: 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 27 01:24:49 submit26-b9-f4 setroubleshoot[2669749]: 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 [x2]
Sep 27 01:24:49 submit26-b9-f4 setroubleshoot[2669749]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 3178d5f5-80e9-404b-92b7-9bef397a8915
Sep 27 01:24:49 submit26-b9-f4 setroubleshoot[2669749]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.EPY0OG/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0
Sep 27 01:50:10 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 7.4423s
Status : exited 0
Output :
Syslog digest — 2026-09-27 01:05 EDT
Processed 118,796 lines, filtered 1,362 (1%). 117,434 unknown (182 distinct) from 31 host(s).
== abuse (3 distinct, 4 total) ==
Sep 27 00:10:14 abuse systemd[1]: New main PID 1414 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 27 00:10:33 abuse systemd[1]: Daemon never wrote its PID file. Failing.
Sep 27 00:10:44 abuse systemd[1]: pmlogger.service: Supervising process 8889 which is not our child. We'll most likely not notice when it exits.
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 27 01:02:18 b0b02.cs.umd.edu rustdesk[1523543]: cannot open display:
== biggulp.cs.umd.edu (1 distinct, 3 total) ==
Sep 27 00:21:15 biggulp.cs.umd.edu sshd-session[340731]: error: send_error: write: Connection reset by peer [x3]
== forge00 (1 distinct, 1 total) ==
Sep 27 00:45:23 forge00 (httpd)[1350202]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
== galax (1 distinct, 1 total) ==
Sep 27 00:55:19 galax systemctl[363401]: Warning: The unit file, source configuration file or drop-ins of cups.service changed on disk. Run 'systemctl daemon-reload' to reload units.
== grades01.cs.umd.edu (3 distinct, 4 total) ==
Sep 27 00:10:13 grades01.cs.umd.edu systemd[1]: New main PID 466 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 27 00:10:34 grades01.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 27 00:10:49 grades01.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 7922 which is not our child. We'll most likely not notice when it exits.
== idm00 (1 distinct, 1 total) ==
Sep 27 00:54:09 idm00 named[4166701]: client @0x7f11a93f2098 10.73.240.42#53448: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 27 00:39:28 idmp0 named[1598691]: client @0x7f2d2000e0b8 10.73.240.43#59784: update '73.10.in-addr.arpa/IN' denied
== itmon02 (2 distinct, 9 total) ==
Sep 27 00:12:57 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x8]
Sep 27 00:16:40 itmon02 (httpd)[505799]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
== jubjub.cs.umd.edu (3 distinct, 4 total) ==
Sep 27 00:10:13 jubjub.cs.umd.edu systemd[1]: New main PID 1583415 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 27 00:10:33 jubjub.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 27 00:10:41 jubjub.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 1590694 which is not our child. We'll most likely not notice when it exits.
== librenms (1 distinct, 1 total) ==
Sep 27 00:39:34 librenms (httpd)[3017198]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
== lifepix (1 distinct, 1 total) ==
Sep 27 00:07:40 lifepix (httpd)[346712]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
== mirrors.cs.umd.edu (4 distinct, 6 total) ==
Sep 27 00:10:34 mirrors.cs.umd.edu root[5629]: pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily-K.log
Sep 27 00:10:34 mirrors.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing. [x2]
Sep 27 00:10:37 mirrors.cs.umd.edu systemd[1]: New main PID 4554 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 27 00:11:56 mirrors.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 21293 which is not our child. We'll most likely not notice when it exits.
== misty.cs.umd.edu (3 distinct, 4 total) ==
Sep 27 00:10:15 misty.cs.umd.edu systemd[1]: New main PID 20648 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 27 00:10:35 misty.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 27 00:10:50 misty.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 28276 which is not our child. We'll most likely not notice when it exits.
== munin (3 distinct, 51 total) ==
Sep 27 00:08:07 munin sudo[4185241]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x25]
Sep 27 00:08:07 munin sudo[4185241]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x25]
Sep 27 00:47:53 munin (httpd)[4840]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
== newhonors2 (1 distinct, 24 total) ==
Sep 27 00:13:02 newhonors2 dhcpcd[3207165]: dhcpcd is not running [x24]
== ntop00 (76 distinct, 117196 total) ==
Sep 27 00:05:08 ntop00 rsyslogd[1208]: file '/var/log/messages'[13] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x55862]
Sep 27 00:05:08 ntop00 rsyslogd[1208]: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x53214]
Sep 27 00:05:08 ntop00 rsyslogd[1208]: file '/var/log/maillog'[15] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x231]
Sep 27 00:05:08 ntop00 rsyslogd[1208]: action 'action-3-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x231]
Sep 27 00:05:09 ntop00 rsyslogd[1208]: imjournal: open() failed for path: '/var/lib/rsyslog/imjournal.state.tmp': No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2433 ] [x7546]
Sep 27 00:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 971) ***
Sep 27 00:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 971, QN: 4433/4433, ET: 0) ***
Sep 27 00:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 971) ***
Sep 27 00:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 971, QN: 46/46, ET: 0) ***
Sep 27 00:15:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x11]
Sep 27 00:15:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x11]
Sep 27 00:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 974) ***
Sep 27 00:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 974, QN: 0/4075, ET: 0) ***
Sep 27 00:15:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x10]
Sep 27 00:15:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x10]
Sep 27 00:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 974) ***
Sep 27 00:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 974, QN: 0/59, ET: 0) ***
Sep 27 00:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 975) ***
Sep 27 00:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 975, QN: 4016/4016, ET: 0) ***
Sep 27 00:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 975) ***
Sep 27 00:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 975, QN: 55/55, ET: 0) ***
Sep 27 00:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 976) ***
Sep 27 00:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 976, QN: 0/4174, ET: 0) ***
Sep 27 00:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 976) ***
Sep 27 00:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 976, QN: 0/56, ET: 0) ***
Sep 27 00:24:02 ntop00 rsyslogd[1208]: action 'action-1-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x4]
Sep 27 00:25:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 978) ***
Sep 27 00:25:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 978, QN: 0/4703, ET: 0) ***
Sep 27 00:25:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 978) ***
Sep 27 00:25:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 978, QN: 0/47, ET: 0) ***
... 46 more distinct messages not shown
== openrepo (1 distinct, 1 total) ==
Sep 27 00:32:53 openrepo (nin-node)[4020573]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
== openvox08-board (1 distinct, 1 total) ==
Sep 27 00:48:33 openvox08-board (httpd)[2013639]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 27 00:09:09 outbound00.cs.umd.edu python3[73876]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 27 00:13:06 outbound01.cs.umd.edu python3[2336538]: ldapdb [x6]
== portal (1 distinct, 1 total) ==
Sep 27 00:21:49 portal (httpd)[2878492]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
== sentry-docker00.cs.umd.edu (38 distinct, 38 total) ==
Sep 27 00:21:50 sentry-docker00.cs.umd.edu systemd-udevd[354073]: link_config: could not get ethtool features for veth496d50f
Sep 27 00:21:50 sentry-docker00.cs.umd.edu systemd-udevd[354073]: Could not set offload features of veth496d50f: No such device
Sep 27 00:21:50 sentry-docker00.cs.umd.edu systemd-udevd[354147]: Could not generate persistent MAC address for vethf211124: No such file or directory
Sep 27 00:21:50 sentry-docker00.cs.umd.edu systemd-udevd[354148]: Could not generate persistent MAC address for vethbe0a607: No such file or directory
Sep 27 00:21:50 sentry-docker00.cs.umd.edu systemd-udevd[354151]: Could not generate persistent MAC address for veth9d3fb8a: No such file or directory
Sep 27 00:21:50 sentry-docker00.cs.umd.edu systemd-udevd[354152]: Could not generate persistent MAC address for veth2226217: No such file or directory
Sep 27 00:21:50 sentry-docker00.cs.umd.edu systemd-udevd[354176]: Could not generate persistent MAC address for vethb2c546a: No such file or directory
Sep 27 00:21:50 sentry-docker00.cs.umd.edu systemd-udevd[354175]: Could not generate persistent MAC address for vethc16b0ed: No such file or directory
Sep 27 00:21:50 sentry-docker00.cs.umd.edu systemd-udevd[354204]: Could not generate persistent MAC address for veth80f9703: No such file or directory
Sep 27 00:21:50 sentry-docker00.cs.umd.edu systemd-udevd[354196]: Could not generate persistent MAC address for veth6709cff: No such file or directory
Sep 27 00:21:50 sentry-docker00.cs.umd.edu systemd-udevd[354197]: Could not generate persistent MAC address for vethcd74ccb: No such file or directory
Sep 27 00:21:50 sentry-docker00.cs.umd.edu systemd-udevd[354218]: Could not generate persistent MAC address for vetha208387: No such file or directory
Sep 27 00:41:58 sentry-docker00.cs.umd.edu systemd-udevd[363487]: link_config: could not get ethtool features for veth9d3fb8a
Sep 27 00:41:58 sentry-docker00.cs.umd.edu systemd-udevd[363487]: Could not set offload features of veth9d3fb8a: No such device
Sep 27 00:41:59 sentry-docker00.cs.umd.edu systemd-udevd[363534]: Could not generate persistent MAC address for veth4a6ce82: No such file or directory
Sep 27 00:41:59 sentry-docker00.cs.umd.edu systemd-udevd[363535]: Could not generate persistent MAC address for vetheed2974: No such file or directory
Sep 27 00:41:59 sentry-docker00.cs.umd.edu systemd-udevd[363538]: Could not generate persistent MAC address for vethe3c3859: No such file or directory
Sep 27 00:41:59 sentry-docker00.cs.umd.edu systemd-udevd[363539]: Could not generate persistent MAC address for vethf4f45fe: No such file or directory
Sep 27 00:41:59 sentry-docker00.cs.umd.edu systemd-udevd[363563]: Could not generate persistent MAC address for vethd64d534: No such file or directory
Sep 27 00:41:59 sentry-docker00.cs.umd.edu systemd-udevd[363562]: Could not generate persistent MAC address for vethb9ebac8: No such file or directory
Sep 27 00:41:59 sentry-docker00.cs.umd.edu systemd-udevd[363581]: Could not generate persistent MAC address for vethbc5595f: No such file or directory
Sep 27 00:41:59 sentry-docker00.cs.umd.edu systemd-udevd[363582]: Could not generate persistent MAC address for vethb44e5e7: No such file or directory
Sep 27 00:41:59 sentry-docker00.cs.umd.edu systemd-udevd[363567]: Could not generate persistent MAC address for veth1973eb1: No such file or directory
Sep 27 00:41:59 sentry-docker00.cs.umd.edu systemd-udevd[363584]: Could not generate persistent MAC address for veth238a5e4: No such file or directory
Sep 27 01:02:07 sentry-docker00.cs.umd.edu systemd-udevd[372904]: link_config: could not get ethtool features for veth238a5e4
Sep 27 01:02:07 sentry-docker00.cs.umd.edu systemd-udevd[372904]: Could not set offload features of veth238a5e4: No such device
Sep 27 01:02:07 sentry-docker00.cs.umd.edu systemd-udevd[372909]: link_config: could not get ethtool features for veth4a6ce82
Sep 27 01:02:07 sentry-docker00.cs.umd.edu systemd-udevd[372909]: Could not set offload features of veth4a6ce82: No such device
Sep 27 01:02:07 sentry-docker00.cs.umd.edu systemd-udevd[372955]: Could not generate persistent MAC address for veth88e107d: No such file or directory
Sep 27 01:02:07 sentry-docker00.cs.umd.edu systemd-udevd[372954]: Could not generate persistent MAC address for veth4a6d039: No such file or directory
... 8 more distinct messages not shown
== strawberry (8 distinct, 39 total) ==
Sep 27 00:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 27 00:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 27 00:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 27 00:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 27 00:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 27 00:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 27 00:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
Sep 27 01:04:42 strawberry smartd[5314]: Device: /dev/sda [SAT], not capable of Offline or Self-Testing.
== submit10-cln25 (3 distinct, 4 total) ==
Sep 27 00:10:11 submit10-cln25 systemd: New main PID 20126 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 27 00:10:30 submit10-cln25 systemd: Daemon never wrote its PID file. Failing.
Sep 27 00:10:36 submit10-cln25 systemd: pmlogger.service: Supervising process 27027 which is not our child. We'll most likely not notice when it exits.
== submit26-b9-fclone (9 distinct, 9 total) ==
Sep 27 00:22:00 submit26-b9-fclone setroubleshoot[557947]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 9355d9d9-a311-48d2-bd37-6c0f6947dfff
Sep 27 00:22:00 submit26-b9-fclone setroubleshoot[557947]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l cc4658d7-9db1-405d-9eee-de0ccee5857f
Sep 27 00:22:01 submit26-b9-fclone setroubleshoot[557947]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 568a2429-0b1b-49df-af41-49b5cd298ae8
Sep 27 00:22:01 submit26-b9-fclone setroubleshoot[557947]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.eZ1COU/repodata/repomd.xml. For complete SELinux messages run: sealert -l 03e2f521-0e7c-481f-8e92-0602c6adeedc
Sep 27 00:22:01 submit26-b9-fclone setroubleshoot[557947]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 0d6b7b1f-ebe3-4beb-915a-b06b63bf2566
Sep 27 00:22:01 submit26-b9-fclone setroubleshoot[557947]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.eZ1COU. For complete SELinux messages run: sealert -l 887adbf9-2bb9-4009-b800-36ddf9ba0db5
Sep 27 00:22:01 submit26-b9-fclone setroubleshoot[557947]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 092e0644-8373-4017-b77f-1afa6c6da4ac
Sep 27 00:22:01 submit26-b9-fclone setroubleshoot[557947]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l ce429a92-56de-4de1-b859-cbfb69ae123c
Sep 27 00:22:01 submit26-b9-fclone setroubleshoot[557947]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 99b886eb-497b-406d-8206-afe76a1086b4
== tlsrpt (1 distinct, 1 total) ==
Sep 27 00:46:28 tlsrpt (httpd)[3257055]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
== tma-0 (3 distinct, 4 total) ==
Sep 27 00:10:13 tma-0 systemd[1]: New main PID 12000 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 27 00:10:30 tma-0 systemd[1]: Daemon never wrote its PID file. Failing.
Sep 27 00:10:38 tma-0 systemd[1]: pmlogger.service: Supervising process 18961 which is not our child. We'll most likely not notice when it exits.
== uffish.cs.umd.edu (3 distinct, 4 total) ==
Sep 27 00:10:12 uffish.cs.umd.edu systemd[1]: New main PID 4056007 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 27 00:10:39 uffish.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 27 00:10:55 uffish.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 4063615 which is not our child. We'll most likely not notice when it exits.
== vacuum.cs.umd.edu (3 distinct, 4 total) ==
Sep 27 00:10:15 vacuum.cs.umd.edu systemd[1]: New main PID 19378 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 27 00:10:33 vacuum.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 27 00:10:45 vacuum.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 26477 which is not our child. We'll most likely not notice when it exits.
== whiffle.cs.umd.edu (3 distinct, 4 total) ==
Sep 27 00:10:14 whiffle.cs.umd.edu systemd[1]: New main PID 3584881 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Sep 27 00:10:33 whiffle.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Sep 27 00:10:46 whiffle.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 3592422 which is not our child. We'll most likely not notice when it exits.
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 7.4605s
Status : exited 0
Output :
Syslog digest — 2026-09-27 00:05 EDT
Processed 119,291 lines, filtered 1,419 (1%). 117,872 unknown (130 distinct) from 26 host(s).
== abadi-computer (1 distinct, 1 total) ==
Sep 27 00:00:00 abadi-computer systemctl[1121849]: Warning: The unit file, source configuration file or drop-ins of cups.service changed on disk. Run 'systemctl daemon-reload' to reload units.
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 27 00:02:14 b0b02.cs.umd.edu rustdesk[1507398]: cannot open display:
== borogove.cs.umd.edu (1 distinct, 1 total) ==
Sep 27 00:00:02 borogove.cs.umd.edu rsyslogd[1921]: imfile: internal error? inotify provided watch descriptor 442 which we could not find in our tables - ignored [v8.2510.0-2.el9 try https://www.rsyslog.com/e/2175 ]
== hspc (1 distinct, 1 total) ==
Sep 27 00:00:04 hspc kernel: kauditd_printk_skb: 2 callbacks suppressed
== idm00 (2 distinct, 5 total) ==
Sep 26 23:54:09 idm00 named[4166701]: client @0x7f11a9464788 10.73.240.42#62006: update '73.10.in-addr.arpa/IN' denied
Sep 27 00:00:00 idm00 named[4166701]: checkhints: unable to get root NS rrset from cache: not found [x4]
== idmh1 (1 distinct, 2 total) ==
Sep 27 00:00:00 idmh1 named[3565631]: checkhints: unable to get root NS rrset from cache: not found [x2]
== idmp0 (2 distinct, 4 total) ==
Sep 26 23:39:28 idmp0 named[1598691]: client @0x7f2d1403a698 10.73.240.43#51537: update '73.10.in-addr.arpa/IN' denied
Sep 27 00:00:05 idmp0 named[1598691]: checkhints: unable to get root NS rrset from cache: not found [x3]
== idmv0 (1 distinct, 2 total) ==
Sep 27 00:00:01 idmv0 named[3973338]: checkhints: unable to get root NS rrset from cache: not found [x2]
== inbound01.cs.umd.edu (1 distinct, 1 total) ==
Sep 26 23:06:44 inbound01.cs.umd.edu sshd-session[2423320]: fatal: userauth_pubkey: parse publickey packet: incomplete message [preauth]
== itmon02 (1 distinct, 4 total) ==
Sep 26 23:08:22 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x4]
== jaws.cs.umd.edu (1 distinct, 1 total) ==
Sep 27 00:00:02 jaws.cs.umd.edu rsyslogd[1739]: imfile: poll_tree cannot stat file '/var/log/httpd/helpdesk.cs.umd.edu-ssl-8413_error_ssl.log' - ignored: No such file or directory [v8.2510.0-2.el9]
== krispykreme.cs.umd.edu (1 distinct, 5 total) ==
Sep 26 23:13:17 krispykreme.cs.umd.edu sshd-session[3012206]: error: send_error: write: Connection reset by peer [x5]
== matrix (1 distinct, 1 total) ==
Sep 27 00:00:13 matrix (nin-node)[189836]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
== munin (2 distinct, 20 total) ==
Sep 26 23:08:27 munin sudo[4162770]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x10]
Sep 26 23:08:27 munin sudo[4162770]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x10]
== neo-gizmonic (1 distinct, 1 total) ==
Sep 27 00:00:01 neo-gizmonic (nin-node)[2596289]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
== neoavion (1 distinct, 1 total) ==
Sep 27 00:00:25 neoavion (nin-node)[777229]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
== netbox (1 distinct, 1 total) ==
Sep 27 00:05:01 netbox (httpd)[819363]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
== newhonors2 (2 distinct, 25 total) ==
Sep 26 23:13:03 newhonors2 dhcpcd[3204959]: dhcpcd is not running [x24]
Sep 27 00:00:16 newhonors2 (nin-node)[3206621]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
== ntop00 (58 distinct, 117704 total) ==
Sep 26 23:05:08 ntop00 rsyslogd[1208]: file '/var/log/messages'[13] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x56107]
Sep 26 23:05:08 ntop00 rsyslogd[1208]: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x53273]
Sep 26 23:05:08 ntop00 rsyslogd[1208]: file '/var/log/maillog'[15] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x235]
Sep 26 23:05:08 ntop00 rsyslogd[1208]: action 'action-3-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x235]
Sep 26 23:05:09 ntop00 rsyslogd[1208]: imjournal: open() failed for path: '/var/lib/rsyslog/imjournal.state.tmp': No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2433 ] [x7779]
Sep 26 23:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 947) ***
Sep 26 23:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 947, QN: 3814/3814, ET: 0) ***
Sep 26 23:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 947) ***
Sep 26 23:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 947, QN: 58/58, ET: 0) ***
Sep 26 23:15:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6]
Sep 26 23:15:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x6]
Sep 26 23:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 950) ***
Sep 26 23:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 950, QN: 0/4919, ET: 0) ***
Sep 26 23:15:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6]
Sep 26 23:15:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x6]
Sep 26 23:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 950) ***
Sep 26 23:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 950, QN: 0/65, ET: 0) ***
Sep 26 23:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 951) ***
Sep 26 23:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 951, QN: 5420/5420, ET: 0) ***
Sep 26 23:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 951) ***
Sep 26 23:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 951, QN: 58/58, ET: 0) ***
Sep 26 23:25:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 954) ***
Sep 26 23:25:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 954, QN: 0/4224, ET: 0) ***
Sep 26 23:25:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 954) ***
Sep 26 23:25:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 954, QN: 0/49, ET: 0) ***
Sep 26 23:28:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 955) ***
Sep 26 23:28:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 955, QN: 4614/4614, ET: 0) ***
Sep 26 23:28:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 955) ***
Sep 26 23:28:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 955, QN: 58/58, ET: 0) ***
Sep 26 23:35:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 958) ***
... 28 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 26 23:09:09 outbound00.cs.umd.edu python3[59649]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 26 23:13:06 outbound01.cs.umd.edu python3[2321762]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (34 distinct, 34 total) ==
Sep 26 23:21:25 sentry-docker00.cs.umd.edu systemd-udevd[325956]: Could not generate persistent MAC address for veth899fb62: No such file or directory
Sep 26 23:21:25 sentry-docker00.cs.umd.edu systemd-udevd[325957]: Could not generate persistent MAC address for vethd856b08: No such file or directory
Sep 26 23:21:25 sentry-docker00.cs.umd.edu systemd-udevd[325960]: Could not generate persistent MAC address for veth9f82678: No such file or directory
Sep 26 23:21:25 sentry-docker00.cs.umd.edu systemd-udevd[325961]: Could not generate persistent MAC address for veth87e918e: No such file or directory
Sep 26 23:21:25 sentry-docker00.cs.umd.edu systemd-udevd[325977]: Could not generate persistent MAC address for vethb9ca596: No such file or directory
Sep 26 23:21:25 sentry-docker00.cs.umd.edu systemd-udevd[325972]: Could not generate persistent MAC address for veth2f10a4f: No such file or directory
Sep 26 23:21:25 sentry-docker00.cs.umd.edu systemd-udevd[325976]: Could not generate persistent MAC address for vethd00bd7e: No such file or directory
Sep 26 23:21:25 sentry-docker00.cs.umd.edu systemd-udevd[325983]: Could not generate persistent MAC address for veth5c46ee1: No such file or directory
Sep 26 23:21:25 sentry-docker00.cs.umd.edu systemd-udevd[325977]: Could not generate persistent MAC address for veth0de1000: No such file or directory
Sep 26 23:21:25 sentry-docker00.cs.umd.edu systemd-udevd[325976]: Could not generate persistent MAC address for vethf9c0f30: No such file or directory
Sep 26 23:41:33 sentry-docker00.cs.umd.edu systemd-udevd[335311]: link_config: could not get ethtool features for veth5c46ee1
Sep 26 23:41:33 sentry-docker00.cs.umd.edu systemd-udevd[335311]: Could not set offload features of veth5c46ee1: No such device
Sep 26 23:41:34 sentry-docker00.cs.umd.edu systemd-udevd[335346]: Could not generate persistent MAC address for veth39cc5ef: No such file or directory
Sep 26 23:41:34 sentry-docker00.cs.umd.edu systemd-udevd[335347]: Could not generate persistent MAC address for veth8908d8f: No such file or directory
Sep 26 23:41:34 sentry-docker00.cs.umd.edu systemd-udevd[335365]: Could not generate persistent MAC address for veth2e61ba8: No such file or directory
Sep 26 23:41:34 sentry-docker00.cs.umd.edu systemd-udevd[335372]: Could not generate persistent MAC address for veth25346a9: No such file or directory
Sep 26 23:41:34 sentry-docker00.cs.umd.edu systemd-udevd[335359]: Could not generate persistent MAC address for veth815b9aa: No such file or directory
Sep 26 23:41:34 sentry-docker00.cs.umd.edu systemd-udevd[335363]: Could not generate persistent MAC address for veth39dff53: No such file or directory
Sep 26 23:41:34 sentry-docker00.cs.umd.edu systemd-udevd[335354]: Could not generate persistent MAC address for veth10b989c: No such file or directory
Sep 26 23:41:34 sentry-docker00.cs.umd.edu systemd-udevd[335361]: Could not generate persistent MAC address for veth78879aa: No such file or directory
Sep 26 23:41:34 sentry-docker00.cs.umd.edu systemd-udevd[335359]: Could not generate persistent MAC address for vethc24d6a9: No such file or directory
Sep 26 23:41:34 sentry-docker00.cs.umd.edu systemd-udevd[335363]: Could not generate persistent MAC address for vethd6c1bef: No such file or directory
Sep 27 00:01:42 sentry-docker00.cs.umd.edu systemd-udevd[344659]: link_config: could not get ethtool features for veth10b989c
Sep 27 00:01:42 sentry-docker00.cs.umd.edu systemd-udevd[344659]: Could not set offload features of veth10b989c: No such device
Sep 27 00:01:42 sentry-docker00.cs.umd.edu systemd-udevd[344694]: Could not generate persistent MAC address for veth59f9c3f: No such file or directory
Sep 27 00:01:42 sentry-docker00.cs.umd.edu systemd-udevd[344695]: Could not generate persistent MAC address for vethf9d3ef8: No such file or directory
Sep 27 00:01:42 sentry-docker00.cs.umd.edu systemd-udevd[344698]: Could not generate persistent MAC address for veth662baab: No such file or directory
Sep 27 00:01:42 sentry-docker00.cs.umd.edu systemd-udevd[344703]: Could not generate persistent MAC address for veth5388f8b: No such file or directory
Sep 27 00:01:42 sentry-docker00.cs.umd.edu systemd-udevd[344699]: Could not generate persistent MAC address for vethd711ca3: No such file or directory
Sep 27 00:01:42 sentry-docker00.cs.umd.edu systemd-udevd[344710]: Could not generate persistent MAC address for vethda79bf0: No such file or directory
... 4 more distinct messages not shown
== strawberry (9 distinct, 40 total) ==
Sep 26 23:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 26 23:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 26 23:07:04 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 26 23:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 26 23:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 26 23:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 26 23:21:27 strawberry kernel: kauditd_printk_skb: 2 callbacks suppressed
Sep 26 23:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
Sep 27 00:00:03 strawberry kernel: kauditd_printk_skb: 4 callbacks suppressed
== tma-0 (2 distinct, 2 total) ==
Sep 26 23:58:19 tma-0 sshd[8697]: error: maximum authentication attempts exceeded for root from 184.153.171.150 port 54408 ssh2 [preauth]
Sep 26 23:58:19 tma-0 sshd[8697]: PAM service(sshd) ignoring max retries; 6 > 3
== unknown (1 distinct, 1 total) ==
using-explainable-ai
== wraith (2 distinct, 2 total) ==
Sep 27 00:00:07 wraith kernel: kauditd_printk_skb: 29 callbacks suppressed
Sep 27 00:00:07 wraith (nin-node)[101056]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 7.4279s
Status : exited 0
Output :
Syslog digest — 2026-09-26 23:05 EDT
Processed 119,024 lines, filtered 1,658 (1%). 117,366 unknown (156 distinct) from 16 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 26 23:02:10 b0b02.cs.umd.edu rustdesk[1492210]: cannot open display:
== idm00 (1 distinct, 1 total) ==
Sep 26 22:54:08 idm00 named[4166701]: client @0x7f11a9468268 10.73.240.42#63308: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 26 22:39:28 idmp0 named[1598691]: client @0x7f2d38010098 10.73.240.43#53231: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 2 total) ==
Sep 26 22:28:31 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x2]
== munin (2 distinct, 8 total) ==
Sep 26 22:28:31 munin sudo[4147910]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x4]
Sep 26 22:28:31 munin sudo[4147910]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x4]
== newhonors.cs.umd.edu (1 distinct, 1 total) ==
Sep 26 23:03:41 newhonors.cs.umd.edu systemd-tmpfiles: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
== newhonors2 (1 distinct, 24 total) ==
Sep 26 22:13:03 newhonors2 dhcpcd[3203115]: dhcpcd is not running [x24]
== ntop00 (77 distinct, 117212 total) ==
Sep 26 22:05:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x7]
Sep 26 22:05:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x7]
Sep 26 22:05:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 922) ***
Sep 26 22:05:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 922, QN: 0/5081, ET: 0) ***
Sep 26 22:05:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x7]
Sep 26 22:05:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x7]
Sep 26 22:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 922) ***
Sep 26 22:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 922, QN: 0/54, ET: 0) ***
Sep 26 22:05:08 ntop00 rsyslogd[1208]: file '/var/log/messages'[13] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x55919]
Sep 26 22:05:08 ntop00 rsyslogd[1208]: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x53141]
Sep 26 22:05:08 ntop00 rsyslogd[1208]: file '/var/log/maillog'[15] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x233]
Sep 26 22:05:08 ntop00 rsyslogd[1208]: action 'action-3-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x233]
Sep 26 22:05:08 ntop00 rsyslogd[1208]: imjournal: open() failed for path: '/var/lib/rsyslog/imjournal.state.tmp': No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2433 ] [x7590]
Sep 26 22:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 923) ***
Sep 26 22:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 923, QN: 4760/4760, ET: 0) ***
Sep 26 22:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 923) ***
Sep 26 22:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 923, QN: 49/49, ET: 0) ***
Sep 26 22:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 925) ***
Sep 26 22:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 925, QN: 5849/5849, ET: 0) ***
Sep 26 22:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 925) ***
Sep 26 22:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 925, QN: 54/54, ET: 0) ***
Sep 26 22:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 926) ***
Sep 26 22:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 926, QN: 0/6362, ET: 0) ***
Sep 26 22:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 926) ***
Sep 26 22:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 926, QN: 0/55, ET: 0) ***
Sep 26 22:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 927) ***
Sep 26 22:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 927, QN: 6786/6786, ET: 0) ***
Sep 26 22:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 927) ***
Sep 26 22:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 927, QN: 55/55, ET: 0) ***
Sep 26 22:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 929) ***
... 47 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 26 22:09:09 outbound00.cs.umd.edu python3[45516]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 26 22:13:06 outbound01.cs.umd.edu python3[2307789]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 26 22:21:00 sentry-docker00.cs.umd.edu systemd-udevd[297664]: link_config: could not get ethtool features for veth2e1202a
Sep 26 22:21:00 sentry-docker00.cs.umd.edu systemd-udevd[297664]: Could not set offload features of veth2e1202a: No such device
Sep 26 22:21:00 sentry-docker00.cs.umd.edu systemd-udevd[297721]: Could not generate persistent MAC address for vethe21f61f: No such file or directory
Sep 26 22:21:00 sentry-docker00.cs.umd.edu systemd-udevd[297722]: Could not generate persistent MAC address for veth58dd69f: No such file or directory
Sep 26 22:21:00 sentry-docker00.cs.umd.edu systemd-udevd[297725]: Could not generate persistent MAC address for veth1db2bc8: No such file or directory
Sep 26 22:21:00 sentry-docker00.cs.umd.edu systemd-udevd[297747]: Could not generate persistent MAC address for veth47d75cf: No such file or directory
Sep 26 22:21:00 sentry-docker00.cs.umd.edu systemd-udevd[297736]: Could not generate persistent MAC address for veth3e16485: No such file or directory
Sep 26 22:21:00 sentry-docker00.cs.umd.edu systemd-udevd[297732]: Could not generate persistent MAC address for veth86ad1aa: No such file or directory
Sep 26 22:21:01 sentry-docker00.cs.umd.edu systemd-udevd[297758]: Could not generate persistent MAC address for veth5b84c0b: No such file or directory
Sep 26 22:21:01 sentry-docker00.cs.umd.edu systemd-udevd[297760]: Could not generate persistent MAC address for vetha51c2d9: No such file or directory
Sep 26 22:21:01 sentry-docker00.cs.umd.edu systemd-udevd[297817]: Could not generate persistent MAC address for veth28463b5: No such file or directory
Sep 26 22:21:01 sentry-docker00.cs.umd.edu systemd-udevd[297815]: Could not generate persistent MAC address for vethb1df683: No such file or directory
Sep 26 22:41:09 sentry-docker00.cs.umd.edu systemd-udevd[307103]: link_config: could not set ethtool features for vethe21f61f
Sep 26 22:41:09 sentry-docker00.cs.umd.edu systemd-udevd[307103]: Could not set offload features of vethe21f61f: Operation not permitted
Sep 26 22:41:09 sentry-docker00.cs.umd.edu systemd-udevd[307128]: Could not generate persistent MAC address for vethf6f7fd9: No such file or directory
Sep 26 22:41:09 sentry-docker00.cs.umd.edu systemd-udevd[307129]: Could not generate persistent MAC address for veth59eb317: No such file or directory
Sep 26 22:41:09 sentry-docker00.cs.umd.edu systemd-udevd[307177]: Could not generate persistent MAC address for vethd8f0375: No such file or directory
Sep 26 22:41:09 sentry-docker00.cs.umd.edu systemd-udevd[307178]: Could not generate persistent MAC address for veth49c13ea: No such file or directory
Sep 26 22:41:09 sentry-docker00.cs.umd.edu systemd-udevd[307184]: Could not generate persistent MAC address for vethf3e8ddc: No such file or directory
Sep 26 22:41:09 sentry-docker00.cs.umd.edu systemd-udevd[307203]: Could not generate persistent MAC address for veth6a8e398: No such file or directory
Sep 26 22:41:09 sentry-docker00.cs.umd.edu systemd-udevd[307204]: Could not generate persistent MAC address for vethf5a7b94: No such file or directory
Sep 26 22:41:09 sentry-docker00.cs.umd.edu systemd-udevd[307196]: Could not generate persistent MAC address for veth7d77425: No such file or directory
Sep 26 22:41:09 sentry-docker00.cs.umd.edu systemd-udevd[307224]: Could not generate persistent MAC address for veth6395a10: No such file or directory
Sep 26 22:41:09 sentry-docker00.cs.umd.edu systemd-udevd[307221]: Could not generate persistent MAC address for vethfae786d: No such file or directory
Sep 26 23:01:17 sentry-docker00.cs.umd.edu systemd-udevd[316523]: link_config: could not get ethtool features for vethf5a7b94
Sep 26 23:01:17 sentry-docker00.cs.umd.edu systemd-udevd[316523]: Could not set offload features of vethf5a7b94: No such device
Sep 26 23:01:17 sentry-docker00.cs.umd.edu systemd-udevd[316563]: Could not generate persistent MAC address for veth65e6ffe: No such file or directory
Sep 26 23:01:17 sentry-docker00.cs.umd.edu systemd-udevd[316564]: Could not generate persistent MAC address for vethefb9db5: No such file or directory
Sep 26 23:01:17 sentry-docker00.cs.umd.edu systemd-udevd[316567]: Could not generate persistent MAC address for vethe7ed892: No such file or directory
Sep 26 23:01:17 sentry-docker00.cs.umd.edu systemd-udevd[316568]: Could not generate persistent MAC address for veth31c184e: No such file or directory
... 6 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 26 22:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 26 22:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 26 22:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 26 22:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 26 22:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 26 22:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 26 22:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (11 distinct, 15 total) ==
Sep 26 22:25:57 submit26-b9-f1 setroubleshoot[3843149]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 3ef7d677-731f-46bf-9c34-c2c55fea665c [x2]
Sep 26 22:25:57 submit26-b9-f1 setroubleshoot[3843149]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l aa60e26f-72e1-45f1-bc12-aa8b3b669e36 [x2]
Sep 26 22:25:57 submit26-b9-f1 setroubleshoot[3843149]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l d088fb43-23ee-4ae8-ae6a-5d1c041ee2d6
Sep 26 22:25:57 submit26-b9-f1 setroubleshoot[3843149]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.EDBZpQ/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d
Sep 26 22:25:57 submit26-b9-f1 setroubleshoot[3843149]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 0fd3339f-3ef2-45f3-9e58-65a58b42f3ee
Sep 26 22:25:57 submit26-b9-f1 setroubleshoot[3843149]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.EDBZpQ. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8
Sep 26 22:25:57 submit26-b9-f1 setroubleshoot[3843149]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 405a8556-cf9f-4ef4-8525-0dca18d4259d [x2]
Sep 26 22:25:57 submit26-b9-f1 setroubleshoot[3843149]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 3c38e23e-3631-4cb5-81c7-992675c836d9
Sep 26 22:25:57 submit26-b9-f1 setroubleshoot[3843149]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l a070e9b5-2867-47d6-b2e3-3b7d99725848 [x2]
Sep 26 22:25:57 submit26-b9-f1 setroubleshoot[3843149]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.lGUl89. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8
Sep 26 22:30:07 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
== submit26-b9-f2 (10 distinct, 10 total) ==
Sep 26 22:06:51 submit26-b9-f2 setroubleshoot[2912230]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 0659d546-3107-4f75-b00f-008c85f41dc6
Sep 26 22:06:51 submit26-b9-f2 setroubleshoot[2912230]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 156d9270-3466-4356-b86f-1a128825961a
Sep 26 22:06:51 submit26-b9-f2 setroubleshoot[2912230]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l c8a40bf5-2fc4-46b3-b813-8592b3523339
Sep 26 22:06:51 submit26-b9-f2 setroubleshoot[2912230]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.WApS6Z/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876
Sep 26 22:06:51 submit26-b9-f2 setroubleshoot[2912230]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 988123da-b724-4e6a-900c-33a2723fdaf1
Sep 26 22:06:51 submit26-b9-f2 setroubleshoot[2912230]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.WApS6Z. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8
Sep 26 22:06:51 submit26-b9-f2 setroubleshoot[2912230]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 3a749560-1cec-40ca-a4dc-596841be3885
Sep 26 22:06:51 submit26-b9-f2 setroubleshoot[2912230]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 0aa52f08-94f8-474e-96d8-e818846941af
Sep 26 22:06:51 submit26-b9-f2 setroubleshoot[2912230]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l de019dc4-408f-439c-902a-676d18dfe8e7
Sep 26 22:50:07 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
== submit26-b9-f4 (1 distinct, 1 total) ==
Sep 26 22:09:57 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
== vacuum.cs.umd.edu (4 distinct, 4 total) ==
Sep 26 22:11:58 vacuum.cs.umd.edu abrt-hook-ccpp[21121]: Process 16701 (driver) of user 33 killed by SIGABRT - dumping core
Sep 26 22:11:58 vacuum.cs.umd.edu abrt-server[21123]: Package 'amanda-backup_server' isn't signed with proper key
Sep 26 22:11:58 vacuum.cs.umd.edu abrt-server[21123]: 'post-create' on '/var/spool/abrt/ccpp-2026-09-26-22:11:58-16701' exited with 1
Sep 26 22:11:58 vacuum.cs.umd.edu abrt-server[21123]: Deleting problem directory '/var/spool/abrt/ccpp-2026-09-26-22:11:58-16701'
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 7.4429s
Status : exited 0
Output :
Syslog digest — 2026-09-26 22:05 EDT
Processed 118,790 lines, filtered 1,429 (1%). 117,361 unknown (154 distinct) from 15 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 26 22:02:05 b0b02.cs.umd.edu rustdesk[1476984]: cannot open display:
== idm00 (1 distinct, 1 total) ==
Sep 26 21:54:08 idm00 named[4166701]: client @0x7f11a9464788 10.73.240.42#51606: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 26 21:39:28 idmp0 named[1598691]: client @0x7f2d440131e8 10.73.240.43#65192: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 3 total) ==
Sep 26 21:18:25 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x3]
== munin (2 distinct, 12 total) ==
Sep 26 21:13:18 munin sudo[4121178]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x6]
Sep 26 21:13:18 munin sudo[4121178]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x6]
== newhonors2 (1 distinct, 24 total) ==
Sep 26 21:13:02 newhonors2 dhcpcd[3201272]: dhcpcd is not running [x24]
== ntop00 (79 distinct, 117210 total) ==
Sep 26 21:05:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6]
Sep 26 21:05:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x6]
Sep 26 21:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 898) ***
Sep 26 21:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 898, QN: 0/73, ET: 0) ***
Sep 26 21:05:08 ntop00 rsyslogd[1208]: file '/var/log/messages'[13] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x55882]
Sep 26 21:05:08 ntop00 rsyslogd[1208]: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x52984]
Sep 26 21:05:08 ntop00 rsyslogd[1208]: file '/var/log/maillog'[15] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x234]
Sep 26 21:05:08 ntop00 rsyslogd[1208]: action 'action-3-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x234]
Sep 26 21:05:08 ntop00 rsyslogd[1208]: imjournal: open() failed for path: '/var/lib/rsyslog/imjournal.state.tmp': No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2433 ] [x7784]
Sep 26 21:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 899) ***
Sep 26 21:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 899, QN: 5328/5328, ET: 0) ***
Sep 26 21:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 899) ***
Sep 26 21:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 899, QN: 68/68, ET: 0) ***
Sep 26 21:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 901) ***
Sep 26 21:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 901, QN: 4647/4647, ET: 0) ***
Sep 26 21:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 901) ***
Sep 26 21:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 901, QN: 45/45, ET: 0) ***
Sep 26 21:15:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x5]
Sep 26 21:15:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x5]
Sep 26 21:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 902) ***
Sep 26 21:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 902, QN: 0/5272, ET: 0) ***
Sep 26 21:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 902) ***
Sep 26 21:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 902, QN: 0/44, ET: 0) ***
Sep 26 21:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 903) ***
Sep 26 21:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 903, QN: 5500/5500, ET: 0) ***
Sep 26 21:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 903) ***
Sep 26 21:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 903, QN: 58/58, ET: 0) ***
Sep 26 21:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 905) ***
Sep 26 21:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 905, QN: 5631/5631, ET: 0) ***
Sep 26 21:23:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 905) ***
... 49 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 26 21:09:08 outbound00.cs.umd.edu python3[31513]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 26 21:13:06 outbound01.cs.umd.edu python3[2293657]: ldapdb [x6]
== sebatinsky.cs.umd.edu (1 distinct, 1 total) ==
Sep 26 21:09:43 sebatinsky.cs.umd.edu kernel: hpet1: lost 1 rtc interrupts
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 26 21:20:35 sentry-docker00.cs.umd.edu systemd-udevd[268804]: link_config: could not get ethtool features for vetha3ad32c
Sep 26 21:20:35 sentry-docker00.cs.umd.edu systemd-udevd[268804]: Could not set offload features of vetha3ad32c: No such device
Sep 26 21:20:35 sentry-docker00.cs.umd.edu systemd-udevd[268875]: Could not generate persistent MAC address for veth10b8e87: No such file or directory
Sep 26 21:20:35 sentry-docker00.cs.umd.edu systemd-udevd[268876]: Could not generate persistent MAC address for vethb3a8ff2: No such file or directory
Sep 26 21:20:35 sentry-docker00.cs.umd.edu systemd-udevd[268894]: Could not generate persistent MAC address for veth2ee57b4: No such file or directory
Sep 26 21:20:35 sentry-docker00.cs.umd.edu systemd-udevd[268888]: Could not generate persistent MAC address for veth6daa879: No such file or directory
Sep 26 21:20:35 sentry-docker00.cs.umd.edu systemd-udevd[268903]: Could not generate persistent MAC address for vethe5e086b: No such file or directory
Sep 26 21:20:35 sentry-docker00.cs.umd.edu systemd-udevd[268904]: Could not generate persistent MAC address for vethedb7e54: No such file or directory
Sep 26 21:20:35 sentry-docker00.cs.umd.edu systemd-udevd[268929]: Could not generate persistent MAC address for veth4b684fc: No such file or directory
Sep 26 21:20:35 sentry-docker00.cs.umd.edu systemd-udevd[268930]: Could not generate persistent MAC address for veth2056814: No such file or directory
Sep 26 21:20:35 sentry-docker00.cs.umd.edu systemd-udevd[268955]: Could not generate persistent MAC address for veth3167755: No such file or directory
Sep 26 21:20:35 sentry-docker00.cs.umd.edu systemd-udevd[268956]: Could not generate persistent MAC address for veth12bad31: No such file or directory
Sep 26 21:40:44 sentry-docker00.cs.umd.edu systemd-udevd[278574]: link_config: could not get ethtool features for veth2ee57b4
Sep 26 21:40:44 sentry-docker00.cs.umd.edu systemd-udevd[278574]: Could not set offload features of veth2ee57b4: No such device
Sep 26 21:40:44 sentry-docker00.cs.umd.edu systemd-udevd[278608]: Could not generate persistent MAC address for veth3433dfc: No such file or directory
Sep 26 21:40:44 sentry-docker00.cs.umd.edu systemd-udevd[278609]: Could not generate persistent MAC address for vethc6b2c20: No such file or directory
Sep 26 21:40:44 sentry-docker00.cs.umd.edu systemd-udevd[278612]: Could not generate persistent MAC address for veth79afbe4: No such file or directory
Sep 26 21:40:44 sentry-docker00.cs.umd.edu systemd-udevd[278613]: Could not generate persistent MAC address for veth85a9632: No such file or directory
Sep 26 21:40:44 sentry-docker00.cs.umd.edu systemd-udevd[278624]: Could not generate persistent MAC address for veth82497ff: No such file or directory
Sep 26 21:40:44 sentry-docker00.cs.umd.edu systemd-udevd[278609]: Could not generate persistent MAC address for veth9dfd391: No such file or directory
Sep 26 21:40:44 sentry-docker00.cs.umd.edu systemd-udevd[278638]: Could not generate persistent MAC address for vethfdb77e7: No such file or directory
Sep 26 21:40:44 sentry-docker00.cs.umd.edu systemd-udevd[278639]: Could not generate persistent MAC address for veth57a07e2: No such file or directory
Sep 26 21:40:44 sentry-docker00.cs.umd.edu systemd-udevd[278657]: Could not generate persistent MAC address for veth7935464: No such file or directory
Sep 26 21:40:44 sentry-docker00.cs.umd.edu systemd-udevd[278651]: Could not generate persistent MAC address for veth0174e24: No such file or directory
Sep 26 22:00:52 sentry-docker00.cs.umd.edu systemd-udevd[288198]: link_config: could not get ethtool features for veth3433dfc
Sep 26 22:00:52 sentry-docker00.cs.umd.edu systemd-udevd[288198]: Could not set offload features of veth3433dfc: No such device
Sep 26 22:00:52 sentry-docker00.cs.umd.edu systemd-udevd[288252]: Could not generate persistent MAC address for veth2e641b5: No such file or directory
Sep 26 22:00:52 sentry-docker00.cs.umd.edu systemd-udevd[288253]: Could not generate persistent MAC address for veth054e8bc: No such file or directory
Sep 26 22:00:52 sentry-docker00.cs.umd.edu systemd-udevd[288256]: Could not generate persistent MAC address for veth2e1202a: No such file or directory
Sep 26 22:00:52 sentry-docker00.cs.umd.edu systemd-udevd[288257]: Could not generate persistent MAC address for veth67b719d: No such file or directory
... 6 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 26 21:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 26 21:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 26 21:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 26 21:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 26 21:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 26 21:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 26 21:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f3 (10 distinct, 10 total) ==
Sep 26 21:06:45 submit26-b9-f3 setroubleshoot[3597515]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l a653b772-cbcd-438b-bae5-23c3dc69b31b
Sep 26 21:06:45 submit26-b9-f3 setroubleshoot[3597515]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 3e904634-6caa-4202-8c92-f139db798859
Sep 26 21:06:45 submit26-b9-f3 setroubleshoot[3597515]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 580b20e4-ec2c-433d-905c-5bd417fba033
Sep 26 21:06:45 submit26-b9-f3 setroubleshoot[3597515]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.bCbZti/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f
Sep 26 21:06:45 submit26-b9-f3 setroubleshoot[3597515]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l bff72452-d40a-430b-9060-dd0a48f5b6ba
Sep 26 21:06:45 submit26-b9-f3 setroubleshoot[3597515]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.bCbZti. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd
Sep 26 21:06:45 submit26-b9-f3 setroubleshoot[3597515]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 6da64b94-7024-45a9-b8c2-3b9812517407
Sep 26 21:06:45 submit26-b9-f3 setroubleshoot[3597515]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 64cbe179-abf1-4d5a-bade-bb164897ee65
Sep 26 21:06:45 submit26-b9-f3 setroubleshoot[3597515]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l d2e35b1a-e27c-4f91-9217-2bb1204e1e68
Sep 26 21:10:06 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
== submit26-b9-f4 (10 distinct, 10 total) ==
Sep 26 21:24:48 submit26-b9-f4 setroubleshoot[2633888]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l ee160f23-b161-4f4a-9985-c4edfd3a5beb
Sep 26 21:24:48 submit26-b9-f4 setroubleshoot[2633888]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 89a83821-4b24-4081-9973-0a79ca6ed5b4
Sep 26 21:24:48 submit26-b9-f4 setroubleshoot[2633888]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l f73955d6-1416-45f9-bab6-ff1f3ea07e9d
Sep 26 21:24:48 submit26-b9-f4 setroubleshoot[2633888]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.ORXJ1O/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0
Sep 26 21:24:48 submit26-b9-f4 setroubleshoot[2633888]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 20293136-86a3-40ba-a651-cff48d36059e
Sep 26 21:24:49 submit26-b9-f4 setroubleshoot[2633888]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.ORXJ1O. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c
Sep 26 21:24:49 submit26-b9-f4 setroubleshoot[2633888]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l eec250fb-073f-456d-93bc-f98776fd476d
Sep 26 21:24:49 submit26-b9-f4 setroubleshoot[2633888]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l c9209e04-a349-43d5-8cb2-3e303e48df74
Sep 26 21:24:49 submit26-b9-f4 setroubleshoot[2633888]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 3178d5f5-80e9-404b-92b7-9bef397a8915
Sep 26 21:30:09 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
== wraith (2 distinct, 2 total) ==
Sep 26 21:48:47 wraith kernel: workqueue: i915_hpd_poll_init_work [i915] hogged CPU for >10000us 4099 times, consider switching to WQ_UNBOUND
Sep 26 21:50:22 wraith kernel: workqueue: output_poll_execute hogged CPU for >10000us 4099 times, consider switching to WQ_UNBOUND
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 7.4814s
Status : exited 0
Output :
Syslog digest — 2026-09-26 21:05 EDT
Processed 119,536 lines, filtered 1,708 (1%). 117,828 unknown (141 distinct) from 15 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 26 21:02:01 b0b02.cs.umd.edu rustdesk[1461804]: cannot open display:
== cheezit.cs.umd.edu (1 distinct, 3 total) ==
Sep 26 21:02:58 cheezit.cs.umd.edu sshd-session[3469736]: error: PAM: Authentication failure for adamnguy from 10.174.62.191 [x3]
== galax (1 distinct, 1 total) ==
Sep 26 20:59:49 galax kernel: workqueue: dm_irq_work_func [amdgpu] hogged CPU for >10000us 8195 times, consider switching to WQ_UNBOUND
== idm00 (1 distinct, 1 total) ==
Sep 26 20:54:08 idm00 named[4166701]: client @0x7f119807baf8 10.73.240.42#50435: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 26 20:39:28 idmp0 named[1598691]: client @0x7f2d280332b8 10.73.240.43#51139: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 3 total) ==
Sep 26 20:08:21 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x3]
== munin (2 distinct, 4 total) ==
Sep 26 20:23:19 munin sudo[4102400]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x2]
Sep 26 20:23:19 munin sudo[4102400]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x2]
== newhonors2 (1 distinct, 24 total) ==
Sep 26 20:13:03 newhonors2 dhcpcd[3199432]: dhcpcd is not running [x24]
== ntop00 (81 distinct, 117697 total) ==
Sep 26 20:05:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6]
Sep 26 20:05:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x6]
Sep 26 20:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 874) ***
Sep 26 20:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 874, QN: 0/61, ET: 0) ***
Sep 26 20:05:08 ntop00 rsyslogd[1208]: file '/var/log/messages'[13] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x56110]
Sep 26 20:05:08 ntop00 rsyslogd[1208]: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x53328]
Sep 26 20:05:08 ntop00 rsyslogd[1208]: file '/var/log/maillog'[15] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x237]
Sep 26 20:05:08 ntop00 rsyslogd[1208]: action 'action-3-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x237]
Sep 26 20:05:09 ntop00 rsyslogd[1208]: imjournal: open() failed for path: '/var/lib/rsyslog/imjournal.state.tmp': No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2433 ] [x7689]
Sep 26 20:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 875) ***
Sep 26 20:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 875, QN: 7964/7964, ET: 0) ***
Sep 26 20:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 875) ***
Sep 26 20:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 875, QN: 61/61, ET: 0) ***
Sep 26 20:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 877) ***
Sep 26 20:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 877, QN: 65/65, ET: 0) ***
Sep 26 20:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 877) ***
Sep 26 20:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 877, QN: 8920/8920, ET: 0) ***
Sep 26 20:15:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6]
Sep 26 20:15:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x6]
Sep 26 20:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 878) ***
Sep 26 20:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 878, QN: 0/9655, ET: 0) ***
Sep 26 20:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 878) ***
Sep 26 20:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 878, QN: 0/59, ET: 0) ***
Sep 26 20:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 879) ***
Sep 26 20:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 879, QN: 9156/9156, ET: 0) ***
Sep 26 20:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 879) ***
Sep 26 20:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 879, QN: 57/57, ET: 0) ***
Sep 26 20:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 881) ***
Sep 26 20:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 881, QN: 9975/9975, ET: 0) ***
Sep 26 20:23:02 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 881) ***
... 51 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 26 20:09:09 outbound00.cs.umd.edu python3[17585]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 26 20:13:06 outbound01.cs.umd.edu python3[2279605]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (32 distinct, 32 total) ==
Sep 26 20:20:10 sentry-docker00.cs.umd.edu systemd-udevd[240674]: Could not generate persistent MAC address for veth0cb3890: No such file or directory
Sep 26 20:20:10 sentry-docker00.cs.umd.edu systemd-udevd[240675]: Could not generate persistent MAC address for veth3c2d252: No such file or directory
Sep 26 20:20:10 sentry-docker00.cs.umd.edu systemd-udevd[240678]: Could not generate persistent MAC address for veth3c2a590: No such file or directory
Sep 26 20:20:10 sentry-docker00.cs.umd.edu systemd-udevd[240690]: Could not generate persistent MAC address for vethcd3686e: No such file or directory
Sep 26 20:20:10 sentry-docker00.cs.umd.edu systemd-udevd[240698]: Could not generate persistent MAC address for vethdbd59d4: No such file or directory
Sep 26 20:20:10 sentry-docker00.cs.umd.edu systemd-udevd[240687]: Could not generate persistent MAC address for veth13de5de: No such file or directory
Sep 26 20:20:10 sentry-docker00.cs.umd.edu systemd-udevd[240706]: Could not generate persistent MAC address for veth8ade4f6: No such file or directory
Sep 26 20:20:10 sentry-docker00.cs.umd.edu systemd-udevd[240707]: Could not generate persistent MAC address for veth9bd96c7: No such file or directory
Sep 26 20:20:10 sentry-docker00.cs.umd.edu systemd-udevd[240718]: Could not generate persistent MAC address for veth38522ca: No such file or directory
Sep 26 20:20:10 sentry-docker00.cs.umd.edu systemd-udevd[240722]: Could not generate persistent MAC address for veth5ef6cbb: No such file or directory
Sep 26 20:40:19 sentry-docker00.cs.umd.edu systemd-udevd[249991]: link_config: could not get ethtool features for veth0cb3890
Sep 26 20:40:19 sentry-docker00.cs.umd.edu systemd-udevd[249991]: Could not set offload features of veth0cb3890: No such device
Sep 26 20:40:19 sentry-docker00.cs.umd.edu systemd-udevd[250071]: Could not generate persistent MAC address for veth4b44127: No such file or directory
Sep 26 20:40:19 sentry-docker00.cs.umd.edu systemd-udevd[250072]: Could not generate persistent MAC address for veth93ed0c0: No such file or directory
Sep 26 20:40:19 sentry-docker00.cs.umd.edu systemd-udevd[250075]: Could not generate persistent MAC address for veth96a6062: No such file or directory
Sep 26 20:40:19 sentry-docker00.cs.umd.edu systemd-udevd[250089]: Could not generate persistent MAC address for vethe1f95bc: No such file or directory
Sep 26 20:40:19 sentry-docker00.cs.umd.edu systemd-udevd[250099]: Could not generate persistent MAC address for veth82dd944: No such file or directory
Sep 26 20:40:19 sentry-docker00.cs.umd.edu systemd-udevd[250100]: Could not generate persistent MAC address for veth48266a2: No such file or directory
Sep 26 20:40:19 sentry-docker00.cs.umd.edu systemd-udevd[250118]: Could not generate persistent MAC address for vethe005dc8: No such file or directory
Sep 26 20:40:19 sentry-docker00.cs.umd.edu systemd-udevd[250116]: Could not generate persistent MAC address for veth6039b8b: No such file or directory
Sep 26 20:40:19 sentry-docker00.cs.umd.edu systemd-udevd[250171]: Could not generate persistent MAC address for veth7bf394a: No such file or directory
Sep 26 20:40:19 sentry-docker00.cs.umd.edu systemd-udevd[250173]: Could not generate persistent MAC address for veth019b195: No such file or directory
Sep 26 21:00:27 sentry-docker00.cs.umd.edu systemd-udevd[259751]: Could not generate persistent MAC address for veth55cccb1: No such file or directory
Sep 26 21:00:27 sentry-docker00.cs.umd.edu systemd-udevd[259752]: Could not generate persistent MAC address for veth650c18d: No such file or directory
Sep 26 21:00:27 sentry-docker00.cs.umd.edu systemd-udevd[259755]: Could not generate persistent MAC address for vethd85018c: No such file or directory
Sep 26 21:00:27 sentry-docker00.cs.umd.edu systemd-udevd[259756]: Could not generate persistent MAC address for vethd726dcb: No such file or directory
Sep 26 21:00:27 sentry-docker00.cs.umd.edu systemd-udevd[259762]: Could not generate persistent MAC address for vethf0e3b71: No such file or directory
Sep 26 21:00:27 sentry-docker00.cs.umd.edu systemd-udevd[259776]: Could not generate persistent MAC address for veth4f93a12: No such file or directory
Sep 26 21:00:27 sentry-docker00.cs.umd.edu systemd-udevd[259776]: Could not generate persistent MAC address for veth3eaba64: No such file or directory
Sep 26 21:00:27 sentry-docker00.cs.umd.edu systemd-udevd[259760]: Could not generate persistent MAC address for vethfa12872: No such file or directory
... 2 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 26 20:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 26 20:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 26 20:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 26 20:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 26 20:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 26 20:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 26 20:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f4 (1 distinct, 1 total) ==
Sep 26 20:48:59 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
== submit26-b9-fclone (9 distinct, 10 total) ==
Sep 26 20:22:01 submit26-b9-fclone setroubleshoot[548203]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 9355d9d9-a311-48d2-bd37-6c0f6947dfff [x2]
Sep 26 20:22:01 submit26-b9-fclone setroubleshoot[548203]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l cc4658d7-9db1-405d-9eee-de0ccee5857f
Sep 26 20:22:01 submit26-b9-fclone setroubleshoot[548203]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 568a2429-0b1b-49df-af41-49b5cd298ae8
Sep 26 20:22:01 submit26-b9-fclone setroubleshoot[548203]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.3PkJow/repodata/repomd.xml. For complete SELinux messages run: sealert -l 03e2f521-0e7c-481f-8e92-0602c6adeedc
Sep 26 20:22:01 submit26-b9-fclone setroubleshoot[548203]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 0d6b7b1f-ebe3-4beb-915a-b06b63bf2566
Sep 26 20:22:01 submit26-b9-fclone setroubleshoot[548203]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.3PkJow. For complete SELinux messages run: sealert -l 887adbf9-2bb9-4009-b800-36ddf9ba0db5
Sep 26 20:22:01 submit26-b9-fclone setroubleshoot[548203]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 092e0644-8373-4017-b77f-1afa6c6da4ac
Sep 26 20:22:02 submit26-b9-fclone setroubleshoot[548203]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l ce429a92-56de-4de1-b859-cbfb69ae123c
Sep 26 20:22:02 submit26-b9-fclone setroubleshoot[548203]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 99b886eb-497b-406d-8206-afe76a1086b4
1
0