Command: /usr/local/sbin/syslog-digest.py
Time : 0.5089s
Status : exited 0
Output :
Syslog digest — 2026-08-03 03:05 EDT
Processed 4,688 lines, filtered 3,900 (83%). 788 unknown (74 distinct) from 19 host(s).
== abuse (1 distinct, 347 total) ==
Aug 3 02:05:06 abuse rsyslogd[21745]: imjournal: open() failed for path: '/var/lib/rsyslog/imjournal.state.tmp': Input/output error [v8.2404.0 try https://www.rsyslog.com/e/2433 ] [x347]
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Aug 3 02:42:55 b0b02.cs.umd.edu rustdesk[2337047]: cannot open display:
== biggulp.cs.umd.edu (5 distinct, 5 total) ==
Aug 3 02:42:51 biggulp.cs.umd.edu sshd-session[2500438]: error: maximum authentication attempts exceeded for root from 109.63.133.236 port 37974 ssh2 [preauth]
Aug 3 02:42:57 biggulp.cs.umd.edu sshd-session[2500473]: error: maximum authentication attempts exceeded for root from 109.63.133.236 port 38264 ssh2 [preauth]
Aug 3 02:43:03 biggulp.cs.umd.edu sshd-session[2500506]: error: maximum authentication attempts exceeded for root from 109.63.133.236 port 38546 ssh2 [preauth]
Aug 3 02:43:16 biggulp.cs.umd.edu sshd-session[2500515]: error: maximum authentication attempts exceeded for admin from 109.63.133.236 port 39198 ssh2 [preauth]
Aug 3 02:43:22 biggulp.cs.umd.edu sshd-session[2500523]: error: maximum authentication attempts exceeded for admin from 109.63.133.236 port 39530 ssh2 [preauth]
== cheezit.cs.umd.edu (11 distinct, 13 total) ==
Aug 3 02:36:50 cheezit.cs.umd.edu setroubleshoot[494006]: failed to retrieve rpm info for path '/var/log/falconctl.log':
Aug 3 02:36:51 cheezit.cs.umd.edu setroubleshoot[494006]: SELinux is preventing /opt/CrowdStrike/falconctl18708 from append access on the file /var/log/falconctl.log. For complete SELinux messages run: sealert -l 63f66d53-fcfc-44da-a79e-c789b1ce2ce8
Aug 3 02:36:53 cheezit.cs.umd.edu setroubleshoot[494006]: SELinux is preventing /opt/CrowdStrike/falconctl18708 from write access on the file falconstore. For complete SELinux messages run: sealert -l 386506af-597f-4357-89de-bc382f369a6e
Aug 3 02:37:04 cheezit.cs.umd.edu setroubleshoot[494408]: failed to retrieve rpm info for path '/var/lib/sss/pipes/nss': [x2]
Aug 3 02:37:05 cheezit.cs.umd.edu setroubleshoot[494408]: SELinux is preventing /usr/bin/lsof from write access on the sock_file /var/lib/sss/pipes/nss. For complete SELinux messages run: sealert -l f570494d-54d2-4dac-97e2-28395659abf1 [x2]
Aug 3 02:37:05 cheezit.cs.umd.edu setroubleshoot[494408]: SELinux is preventing /usr/bin/lsof from write access on the sock_file socket. For complete SELinux messages run: sealert -l 9ff2383b-9e1d-44ff-b8ae-af91637450ae
Aug 3 02:37:45 cheezit.cs.umd.edu setroubleshoot[494832]: SELinux is preventing /usr/bin/python3.9 from read access on the file /etc/selinux/targeted/contexts/files/file_contexts.subs_dist. For complete SELinux messages run: sealert -l 679eb260-cf5d-4783-99f4-ce308edb3295
Aug 3 02:37:45 cheezit.cs.umd.edu setroubleshoot[494832]: SELinux is preventing /usr/bin/python3.9 from open access on the file /etc/selinux/targeted/contexts/files/file_contexts.subs_dist. For complete SELinux messages run: sealert -l 77caba8a-5cd0-4e18-b188-6e35c461772d
Aug 3 02:37:45 cheezit.cs.umd.edu setroubleshoot[494832]: SELinux is preventing /usr/bin/python3.9 from read access on the file /etc/selinux/targeted/contexts/files/file_contexts.subs. For complete SELinux messages run: sealert -l d9c6dd0d-0a34-4430-a5ff-e985c55cb064
Aug 3 02:37:45 cheezit.cs.umd.edu setroubleshoot[494832]: SELinux is preventing /usr/bin/python3.9 from open access on the file /etc/selinux/targeted/contexts/files/file_contexts.subs. For complete SELinux messages run: sealert -l 8edbce57-8212-4ac8-af50-3fe403231eda
Aug 3 02:37:45 cheezit.cs.umd.edu setroubleshoot[494832]: SELinux is preventing /usr/bin/python3.9 from map access on the file /etc/selinux/targeted/contexts/files/file_contexts.bin. For complete SELinux messages run: sealert -l 4a0cbe3b-6f49-4c7e-95c6-380f7aef806e
== cmsc436-0101-redis (2 distinct, 2 total) ==
Aug 3 02:07:26 cmsc436-0101-redis krb5_child[726385]: Client 'admin(a)UMD.EDU' not found in Kerberos database
Aug 3 02:07:28 cmsc436-0101-redis sshd-session[726381]: error: PAM: Authentication failure for admin from 34.140.33.144
== contest (1 distinct, 34 total) ==
Aug 3 02:06:00 contest goferd[1007]: [ERROR][worker-0] gofer.messaging.adapter.connect:33 - connect: proton+amqps://satellite8.cs.umd.edu:5647, failed: Connection amqps://satellite8.cs.umd.edu:5647 disconnected: Condition('proton.pythonio', 'Connection refused to all addresses') [x34]
== csfw00a (1 distinct, 246 total) ==
Aug 3 02:04:24 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x246]
== idm00 (1 distinct, 1 total) ==
Aug 3 02:51:15 idm00 named[1455]: client @0x7f330ca369a8 10.73.240.42#64227: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Aug 3 02:36:01 idmp0 named[5198]: client @0x7f992400e068 10.73.240.43#56928: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 35 total) ==
Aug 3 02:08:04 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x35]
== krispykreme.cs.umd.edu (3 distinct, 3 total) ==
Aug 3 03:00:05 krispykreme.cs.umd.edu sshd-session[2651416]: pam_access(sshd:auth): access denied for user `admin' from `34.22.121.160'
Aug 3 03:00:06 krispykreme.cs.umd.edu krb5_child[2651418]: Client 'admin(a)UMD.EDU' not found in Kerberos database
Aug 3 03:00:06 krispykreme.cs.umd.edu sshd-session[2651414]: error: PAM: System error for admin from 34.22.121.160
== munin (2 distinct, 4 total) ==
Aug 3 02:52:53 munin sudo[924533]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x2]
Aug 3 02:52:53 munin sudo[924533]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x2]
== newhonors2 (1 distinct, 24 total) ==
Aug 3 02:13:02 newhonors2 dhcpcd[660521]: dhcpcd is not running [x24]
== outbound00.cs.umd.edu (2 distinct, 7 total) ==
Aug 3 02:09:09 outbound00.cs.umd.edu python3[2338043]: ldapdb [x6]
Aug 3 02:49:45 outbound00.cs.umd.edu krb5_child[2347405]: Client 'admin(a)UMD.EDU' not found in Kerberos database
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Aug 3 02:13:06 outbound01.cs.umd.edu python3[370885]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Aug 3 02:16:32 sentry-docker00.cs.umd.edu systemd-udevd[772410]: link_config: could not get ethtool features for veth8033bb8
Aug 3 02:16:32 sentry-docker00.cs.umd.edu systemd-udevd[772410]: Could not set offload features of veth8033bb8: No such device
Aug 3 02:16:32 sentry-docker00.cs.umd.edu systemd-udevd[772435]: Could not generate persistent MAC address for veth087465b: No such file or directory
Aug 3 02:16:32 sentry-docker00.cs.umd.edu systemd-udevd[772436]: Could not generate persistent MAC address for veth56faf7d: No such file or directory
Aug 3 02:16:33 sentry-docker00.cs.umd.edu systemd-udevd[772439]: Could not generate persistent MAC address for veth49d24fb: No such file or directory
Aug 3 02:16:33 sentry-docker00.cs.umd.edu systemd-udevd[772440]: Could not generate persistent MAC address for veth8477eda: No such file or directory
Aug 3 02:16:33 sentry-docker00.cs.umd.edu systemd-udevd[772463]: Could not generate persistent MAC address for veth7167671: No such file or directory
Aug 3 02:16:33 sentry-docker00.cs.umd.edu systemd-udevd[772464]: Could not generate persistent MAC address for veth927cbb4: No such file or directory
Aug 3 02:16:33 sentry-docker00.cs.umd.edu systemd-udevd[772482]: Could not generate persistent MAC address for veth3711874: No such file or directory
Aug 3 02:16:33 sentry-docker00.cs.umd.edu systemd-udevd[772463]: Could not generate persistent MAC address for veth7b34f73: No such file or directory
Aug 3 02:17:54 sentry-docker00.cs.umd.edu systemd-udevd[773231]: Could not generate persistent MAC address for veth08ad5e4: No such file or directory
Aug 3 02:17:54 sentry-docker00.cs.umd.edu systemd-udevd[773232]: Could not generate persistent MAC address for vethab1f1f7: No such file or directory
Aug 3 02:36:41 sentry-docker00.cs.umd.edu systemd-udevd[782171]: link_config: could not set ethtool features for veth7167671
Aug 3 02:36:41 sentry-docker00.cs.umd.edu systemd-udevd[782171]: Could not set offload features of veth7167671: Operation not permitted
Aug 3 02:36:41 sentry-docker00.cs.umd.edu systemd-udevd[782193]: Could not generate persistent MAC address for veth6ba931f: No such file or directory
Aug 3 02:36:41 sentry-docker00.cs.umd.edu systemd-udevd[782194]: Could not generate persistent MAC address for vethe6714b1: No such file or directory
Aug 3 02:36:41 sentry-docker00.cs.umd.edu systemd-udevd[782197]: Could not generate persistent MAC address for vethd73de87: No such file or directory
Aug 3 02:36:41 sentry-docker00.cs.umd.edu systemd-udevd[782198]: Could not generate persistent MAC address for vethcd9c6ba: No such file or directory
Aug 3 02:36:41 sentry-docker00.cs.umd.edu systemd-udevd[782221]: Could not generate persistent MAC address for veth87e6598: No such file or directory
Aug 3 02:36:41 sentry-docker00.cs.umd.edu systemd-udevd[782222]: Could not generate persistent MAC address for vethb98579a: No such file or directory
Aug 3 02:36:41 sentry-docker00.cs.umd.edu systemd-udevd[782246]: Could not generate persistent MAC address for veth347b6f1: No such file or directory
Aug 3 02:36:41 sentry-docker00.cs.umd.edu systemd-udevd[782248]: Could not generate persistent MAC address for veth813d17a: No such file or directory
Aug 3 02:37:59 sentry-docker00.cs.umd.edu systemd-udevd[782928]: Could not generate persistent MAC address for vethda8feb5: No such file or directory
Aug 3 02:37:59 sentry-docker00.cs.umd.edu systemd-udevd[782929]: Could not generate persistent MAC address for veth58b6d43: No such file or directory
Aug 3 02:56:49 sentry-docker00.cs.umd.edu systemd-udevd[791842]: link_config: could not get ethtool features for veth347b6f1
Aug 3 02:56:49 sentry-docker00.cs.umd.edu systemd-udevd[791842]: Could not set offload features of veth347b6f1: No such device
Aug 3 02:56:49 sentry-docker00.cs.umd.edu systemd-udevd[791865]: Could not generate persistent MAC address for vethd1b6719: No such file or directory
Aug 3 02:56:49 sentry-docker00.cs.umd.edu systemd-udevd[791866]: Could not generate persistent MAC address for veth2132ee7: No such file or directory
Aug 3 02:56:49 sentry-docker00.cs.umd.edu systemd-udevd[791869]: Could not generate persistent MAC address for vethe49b80f: No such file or directory
Aug 3 02:56:49 sentry-docker00.cs.umd.edu systemd-udevd[791887]: Could not generate persistent MAC address for vethd9660ac: No such file or directory
... 6 more distinct messages not shown
== strawberry (2 distinct, 8 total) ==
Aug 3 02:09:44 strawberry udisksd[1067]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/ST2000DM001_1CH164_W1E8J5KJ: Error updating SMART data: Error sending ATA command CHECK POWER MODE: Unexpected sense data returned:#0120000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................#0120010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................#012 (g-io-error-quark, 0) [x6]
Aug 3 02:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-2 (1 distinct, 8 total) ==
Aug 3 02:05:05 submit26-b9-2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x8]
== submit26-b9-4 (1 distinct, 7 total) ==
Aug 3 02:05:05 submit26-b9-4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x7]
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.5162s
Status : exited 0
Output :
Syslog digest — 2026-08-03 02:05 EDT
Processed 4,352 lines, filtered 3,464 (79%). 888 unknown (108 distinct) from 21 host(s).
== abuse (1 distinct, 346 total) ==
Aug 3 01:05:06 abuse rsyslogd[21745]: imjournal: open() failed for path: '/var/lib/rsyslog/imjournal.state.tmp': Input/output error [v8.2404.0 try https://www.rsyslog.com/e/2433 ] [x346]
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Aug 3 01:42:51 b0b02.cs.umd.edu rustdesk[2321972]: cannot open display:
== contest (10 distinct, 47 total) ==
Aug 3 01:05:18 contest goferd[1007]: [ERROR][worker-0] gofer.messaging.adapter.connect:33 - connect: proton+amqps://satellite8.cs.umd.edu:5647, failed: Connection amqps://satellite8.cs.umd.edu:5647 disconnected: Condition('proton.pythonio', 'Connection refused to all addresses') [x34]
Aug 3 01:48:17 contest setroubleshoot[536120]: SELinux is preventing /usr/libexec/platform-python3.6 from create access on the directory libdnf.Cx6w9V. For complete SELinux messages run: sealert -l cb6b25c6-4765-4cf2-88a0-9b3b508e94e9
Aug 3 01:48:17 contest setroubleshoot[536120]: SELinux is preventing /usr/bin/gpgconf from add_name access on the directory repodata. For complete SELinux messages run: sealert -l 41cf7b1b-0f34-4609-98f2-b66e7825fef7 [x2]
Aug 3 01:48:17 contest setroubleshoot[536120]: SELinux is preventing /usr/libexec/platform-python3.6 from create access on the file mirrorlist. For complete SELinux messages run: sealert -l fc20ff92-ea83-4f38-a24b-ddfd737a3141
Aug 3 01:48:17 contest setroubleshoot[536120]: SELinux is preventing /usr/libexec/platform-python3.6 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l ac675631-fa35-4e93-adc9-b692b18e53e5
Aug 3 01:48:17 contest setroubleshoot[536120]: SELinux is preventing /usr/libexec/platform-python3.6 from read access on the directory libdnf.Cx6w9V. For complete SELinux messages run: sealert -l 45d103b6-0810-4890-a705-990118577ce8
Aug 3 01:48:17 contest setroubleshoot[536120]: SELinux is preventing /usr/libexec/platform-python3.6 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 7e499113-2fd7-4f67-bec6-3521efbe3637 [x3]
Aug 3 01:48:18 contest setroubleshoot[536120]: SELinux is preventing /usr/libexec/platform-python3.6 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 3928930b-a1ed-448d-950b-0665ac2adef8 [x2]
Aug 3 01:48:18 contest setroubleshoot[536120]: SELinux is preventing /usr/libexec/platform-python3.6 from create access on the directory libdnf.zQjTat. For complete SELinux messages run: sealert -l cb6b25c6-4765-4cf2-88a0-9b3b508e94e9
Aug 3 01:48:25 contest setroubleshoot[536120]: SELinux is preventing /usr/libexec/platform-python3.6 from read access on the directory libdnf.zQjTat. For complete SELinux messages run: sealert -l 45d103b6-0810-4890-a705-990118577ce8
== csfw00a (2 distinct, 258 total) ==
Aug 3 01:05:06 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x246]
Aug 3 01:33:49 csfw00a ospf6d[1477]: [EC 100663307] Could not send entire message [x12]
== hackerman (1 distinct, 1 total) ==
Aug 3 01:19:01 hackerman gnome-software[2060381]: failed to commit changes to dconf: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dfile_2derror_2dquark.Code2: Failed to create file “/adminhomes/sajith/.config/dconf/user.SQCYT3”: Permission denied
== hazfs.cs.umd.edu (11 distinct, 66 total) ==
Aug 3 01:50:54 hazfs.cs.umd.edu snmpd[1431]: send response: Failure in sendto [x6]
Aug 3 01:50:54 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userweb" [x6]
Aug 3 01:50:54 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."zfslist" [x6]
Aug 3 01:50:54 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userhome" [x6]
Aug 3 01:50:54 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userweb" [x6]
Aug 3 01:50:54 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."zfslist" [x6]
Aug 3 01:50:54 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userhome" [x6]
Aug 3 01:50:54 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userweb" [x6]
Aug 3 01:50:54 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."zfslist" [x6]
Aug 3 01:50:54 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userhome" [x6]
Aug 3 01:50:54 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutNumLines."userweb" [x6]
== idm00 (2 distinct, 2 total) ==
Aug 3 01:24:05 idm00 named[1455]: client @0x7f3304247948 10.73.245.12#53809: update '73.10.in-addr.arpa/IN' denied
Aug 3 01:51:15 idm00 named[1455]: client @0x7f3310a9be68 10.73.240.42#64781: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Aug 3 01:36:01 idmp0 named[5198]: client @0x7f98fc0059e8 10.73.240.43#64507: update '73.10.in-addr.arpa/IN' denied
== inbound00.cs.umd.edu (1 distinct, 1 total) ==
Aug 3 01:52:48 inbound00.cs.umd.edu krb5_child[2370506]: Client 'admin(a)UMD.EDU' not found in Kerberos database
== itmon02 (1 distinct, 35 total) ==
Aug 3 01:07:50 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x35]
== mcstic (2 distinct, 5 total) ==
Aug 3 01:13:34 mcstic krb5_child[2038451]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x4]
Aug 3 01:13:40 mcstic sshd[2038446]: error: PAM: Authentication failure for admin from 34.78.35.91
== newhonors2 (1 distinct, 24 total) ==
Aug 3 01:13:03 newhonors2 dhcpcd[658656]: dhcpcd is not running [x24]
== outbound00.cs.umd.edu (3 distinct, 8 total) ==
Aug 3 01:09:09 outbound00.cs.umd.edu python3[2324162]: ldapdb [x6]
Aug 3 01:46:42 outbound00.cs.umd.edu krb5_child[2332693]: Preauthentication failed
Aug 3 01:55:20 outbound00.cs.umd.edu krb5_child[2335142]: Client 'admin(a)UMD.EDU' not found in Kerberos database
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Aug 3 01:13:06 outbound01.cs.umd.edu python3[356863]: ldapdb [x6]
== sebatinsky.cs.umd.edu (1 distinct, 2 total) ==
Aug 3 01:50:32 sebatinsky.cs.umd.edu setroubleshoot[1173928]: SELinux is preventing /usr/libexec/platform-python3.6 from add_name access on the directory .dbenv.lock. For complete SELinux messages run: sealert -l 26d5bc02-bfff-4827-a9f2-b991fef962b5 [x2]
== sentry-docker00.cs.umd.edu (38 distinct, 38 total) ==
Aug 3 01:16:07 sentry-docker00.cs.umd.edu systemd-udevd[743841]: link_config: could not get ethtool features for veth80c2fa7
Aug 3 01:16:07 sentry-docker00.cs.umd.edu systemd-udevd[743841]: Could not set offload features of veth80c2fa7: No such device
Aug 3 01:16:08 sentry-docker00.cs.umd.edu systemd-udevd[743862]: Could not generate persistent MAC address for veth69e8293: No such file or directory
Aug 3 01:16:08 sentry-docker00.cs.umd.edu systemd-udevd[743863]: Could not generate persistent MAC address for vethbfae673: No such file or directory
Aug 3 01:16:08 sentry-docker00.cs.umd.edu systemd-udevd[743881]: Could not generate persistent MAC address for veth55e32df: No such file or directory
Aug 3 01:16:08 sentry-docker00.cs.umd.edu systemd-udevd[743875]: Could not generate persistent MAC address for vethf9c3d14: No such file or directory
Aug 3 01:16:08 sentry-docker00.cs.umd.edu systemd-udevd[743890]: Could not generate persistent MAC address for veth026f297: No such file or directory
Aug 3 01:16:08 sentry-docker00.cs.umd.edu systemd-udevd[743891]: Could not generate persistent MAC address for veth527ab39: No such file or directory
Aug 3 01:16:08 sentry-docker00.cs.umd.edu systemd-udevd[743927]: Could not generate persistent MAC address for veth00a6ba0: No such file or directory
Aug 3 01:16:08 sentry-docker00.cs.umd.edu systemd-udevd[743905]: Could not generate persistent MAC address for veth50c9fff: No such file or directory
Aug 3 01:17:37 sentry-docker00.cs.umd.edu systemd-udevd[744693]: link_config: could not get ethtool features for veth210cd0a
Aug 3 01:17:37 sentry-docker00.cs.umd.edu systemd-udevd[744693]: Could not set offload features of veth210cd0a: No such device
Aug 3 01:17:37 sentry-docker00.cs.umd.edu systemd-udevd[744710]: Could not generate persistent MAC address for vethb650166: No such file or directory
Aug 3 01:17:37 sentry-docker00.cs.umd.edu systemd-udevd[744711]: Could not generate persistent MAC address for veth14a0f70: No such file or directory
Aug 3 01:36:16 sentry-docker00.cs.umd.edu systemd-udevd[753548]: link_config: could not set ethtool features for veth69e8293
Aug 3 01:36:16 sentry-docker00.cs.umd.edu systemd-udevd[753548]: Could not set offload features of veth69e8293: Operation not permitted
Aug 3 01:36:16 sentry-docker00.cs.umd.edu systemd-udevd[753578]: Could not generate persistent MAC address for veth7430586: No such file or directory
Aug 3 01:36:16 sentry-docker00.cs.umd.edu systemd-udevd[753579]: Could not generate persistent MAC address for veth7a9c48c: No such file or directory
Aug 3 01:36:16 sentry-docker00.cs.umd.edu systemd-udevd[753582]: Could not generate persistent MAC address for veth0f3f89b: No such file or directory
Aug 3 01:36:16 sentry-docker00.cs.umd.edu systemd-udevd[753583]: Could not generate persistent MAC address for veth2de3d8c: No such file or directory
Aug 3 01:36:16 sentry-docker00.cs.umd.edu systemd-udevd[753606]: Could not generate persistent MAC address for vetha63f6bd: No such file or directory
Aug 3 01:36:16 sentry-docker00.cs.umd.edu systemd-udevd[753607]: Could not generate persistent MAC address for vetha2b3493: No such file or directory
Aug 3 01:36:16 sentry-docker00.cs.umd.edu systemd-udevd[753625]: Could not generate persistent MAC address for veth42817cb: No such file or directory
Aug 3 01:36:16 sentry-docker00.cs.umd.edu systemd-udevd[753627]: Could not generate persistent MAC address for vethdb24c6e: No such file or directory
Aug 3 01:37:42 sentry-docker00.cs.umd.edu systemd-udevd[754380]: Could not generate persistent MAC address for veth31b248b: No such file or directory
Aug 3 01:37:42 sentry-docker00.cs.umd.edu systemd-udevd[754381]: Could not generate persistent MAC address for vethbd3fd33: No such file or directory
Aug 3 01:56:24 sentry-docker00.cs.umd.edu systemd-udevd[762975]: link_config: could not get ethtool features for veth7430586
Aug 3 01:56:24 sentry-docker00.cs.umd.edu systemd-udevd[762975]: Could not set offload features of veth7430586: No such device
Aug 3 01:56:24 sentry-docker00.cs.umd.edu systemd-udevd[763007]: Could not generate persistent MAC address for vethc5a4247: No such file or directory
Aug 3 01:56:24 sentry-docker00.cs.umd.edu systemd-udevd[763008]: Could not generate persistent MAC address for veth019f2a4: No such file or directory
... 8 more distinct messages not shown
== strawberry (2 distinct, 8 total) ==
Aug 3 01:09:44 strawberry udisksd[1067]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/ST2000DM001_1CH164_W1E8J5KJ: Error updating SMART data: Error sending ATA command CHECK POWER MODE: Unexpected sense data returned:#0120000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................#0120010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................#012 (g-io-error-quark, 0) [x6]
Aug 3 01:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-2 (10 distinct, 14 total) ==
Aug 3 01:12:52 submit26-b9-2 setroubleshoot[911587]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l d506243c-d61e-48f3-b42a-4592c913deb0
Aug 3 01:12:52 submit26-b9-2 setroubleshoot[911587]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 3b4752ac-1b9a-4af9-a05b-32e4c2eb13ab
Aug 3 01:12:52 submit26-b9-2 setroubleshoot[911587]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 29e5adbd-4381-4467-b40d-a2219101e096
Aug 3 01:12:52 submit26-b9-2 setroubleshoot[911587]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.vu2BXu/repodata/repomd.xml. For complete SELinux messages run: sealert -l 1b38f2ec-01ce-4343-8059-ba7494ecc5c4
Aug 3 01:12:52 submit26-b9-2 setroubleshoot[911587]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l e5f9af40-1f63-4924-b012-27ab2a7b2266
Aug 3 01:12:52 submit26-b9-2 setroubleshoot[911587]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.vu2BXu. For complete SELinux messages run: sealert -l 5c54db87-54a3-4a7c-97b4-b5c48d6c3543
Aug 3 01:12:52 submit26-b9-2 setroubleshoot[911587]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 63cd60e1-1e61-4276-afea-dd8526ffe8b2
Aug 3 01:12:52 submit26-b9-2 setroubleshoot[911587]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 81c7e9ec-e023-4c6d-b1ad-c02a242e655e
Aug 3 01:12:52 submit26-b9-2 setroubleshoot[911587]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 6ae9a597-e123-4d74-8eec-a8ebe0f5e4d0
Aug 3 01:18:07 submit26-b9-2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x5]
== submit26-b9-3 (9 distinct, 9 total) ==
Aug 3 01:20:38 submit26-b9-3 setroubleshoot[793724]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 5b912a44-22fd-4560-b201-2a4e289b73f5
Aug 3 01:20:38 submit26-b9-3 setroubleshoot[793724]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 7f1df1e4-725e-4953-98eb-1079f908f543
Aug 3 01:20:38 submit26-b9-3 setroubleshoot[793724]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 40b8852a-f77b-44b4-affe-5f11fa33de43
Aug 3 01:20:38 submit26-b9-3 setroubleshoot[793724]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.3UbMf8/repodata/repomd.xml. For complete SELinux messages run: sealert -l 45a8019e-f6b5-4baa-92c1-862594b40d46
Aug 3 01:20:38 submit26-b9-3 setroubleshoot[793724]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l e9f0bfff-7784-4126-baa4-2bb06da56591
Aug 3 01:20:38 submit26-b9-3 setroubleshoot[793724]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.3UbMf8. For complete SELinux messages run: sealert -l 0b17cc3d-cdc6-4fe2-a11f-3892e7c41dc7
Aug 3 01:20:38 submit26-b9-3 setroubleshoot[793724]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 10e38c64-b65f-4cdd-901e-4375652d9a42
Aug 3 01:20:38 submit26-b9-3 setroubleshoot[793724]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 7fd9cf72-ef38-48e1-b6aa-b571b26a7b22
Aug 3 01:20:38 submit26-b9-3 setroubleshoot[793724]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l b9b11116-89bd-4a3c-980c-1d422c5dcee4
== submit26-b9-4 (1 distinct, 7 total) ==
Aug 3 01:10:05 submit26-b9-4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x7]
== submit26-clnb9 (9 distinct, 9 total) ==
Aug 3 01:31:56 submit26-clnb9 setroubleshoot[1712440]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 6783ed2b-5ae4-42b5-975a-4bf50eec4658
Aug 3 01:31:56 submit26-clnb9 setroubleshoot[1712440]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 9e7fa955-cc30-4804-ac8c-e1779e85946c
Aug 3 01:31:56 submit26-clnb9 setroubleshoot[1712440]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 69bfa6e3-089c-40ff-9563-fd30787d0774
Aug 3 01:31:56 submit26-clnb9 setroubleshoot[1712440]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.QTQsKl/repodata/repomd.xml. For complete SELinux messages run: sealert -l 001acdb5-31ef-4e52-b10b-90f467a89ddc
Aug 3 01:31:56 submit26-clnb9 setroubleshoot[1712440]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l edacddcf-16ed-4dc3-8d82-7c597d5dee23
Aug 3 01:31:56 submit26-clnb9 setroubleshoot[1712440]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.QTQsKl. For complete SELinux messages run: sealert -l 62b3782e-4730-4488-8178-94dafe9b552c
Aug 3 01:31:56 submit26-clnb9 setroubleshoot[1712440]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 81cb3698-78f8-440a-8e3c-e5d1041e6b78
Aug 3 01:31:57 submit26-clnb9 setroubleshoot[1712440]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 792b472a-115c-4799-9805-fc7436f916b9
Aug 3 01:31:57 submit26-clnb9 setroubleshoot[1712440]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 15c83a86-837b-41e2-b662-b39cd4e361cb
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.5084s
Status : exited 0
Output :
Syslog digest — 2026-08-03 01:05 EDT
Processed 4,325 lines, filtered 3,504 (81%). 821 unknown (113 distinct) from 29 host(s).
== abuse (1 distinct, 347 total) ==
Aug 3 00:05:06 abuse rsyslogd[21745]: imjournal: open() failed for path: '/var/lib/rsyslog/imjournal.state.tmp': Input/output error [v8.2404.0 try https://www.rsyslog.com/e/2433 ] [x347]
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Aug 3 00:42:47 b0b02.cs.umd.edu rustdesk[2306917]: cannot open display:
== contest (1 distinct, 33 total) ==
Aug 3 00:06:24 contest goferd[1007]: [ERROR][worker-0] gofer.messaging.adapter.connect:33 - connect: proton+amqps://satellite8.cs.umd.edu:5647, failed: Connection amqps://satellite8.cs.umd.edu:5647 disconnected: Condition('proton.pythonio', 'Connection refused to all addresses') [x33]
== csfw00a (2 distinct, 238 total) ==
Aug 3 00:04:33 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x230]
Aug 3 00:50:01 csfw00a ospf6d[1477]: [EC 100663307] Could not send entire message [x8]
== cskayako (2 distinct, 2 total) ==
Aug 3 00:06:40 cskayako setroubleshoot[1855218]: SELinux is preventing /usr/bin/php from add_name access on the directory /var/www/html/(null). For complete SELinux messages run: sealert -l 5239c113-abc1-4953-a9c0-21d695a0d1bb
Aug 3 00:06:40 cskayako setroubleshoot[1855218]: SELinux is preventing /usr/bin/php from create access on the file /var/www/html/(null). For complete SELinux messages run: sealert -l cacf8f36-45b0-4374-9a33-d15de767aae7
== grades01.cs.umd.edu (3 distinct, 4 total) ==
Aug 3 00:10:14 grades01.cs.umd.edu systemd[1]: New main PID 28327 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Aug 3 00:10:37 grades01.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Aug 3 00:10:53 grades01.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 3737 which is not our child. We'll most likely not notice when it exits.
== idm00 (1 distinct, 1 total) ==
Aug 3 00:51:15 idm00 named[1455]: client @0x7f33041f95f8 10.73.240.42#62269: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Aug 3 00:36:01 idmp0 named[5198]: client @0x7f98fc0059e8 10.73.240.43#62342: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 30 total) ==
Aug 3 00:08:16 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x30]
== jubjub.cs.umd.edu (3 distinct, 4 total) ==
Aug 3 00:10:13 jubjub.cs.umd.edu systemd[1]: New main PID 1380598 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Aug 3 00:10:32 jubjub.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Aug 3 00:10:41 jubjub.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 1388106 which is not our child. We'll most likely not notice when it exits.
== mirrors.cs.umd.edu (3 distinct, 4 total) ==
Aug 3 00:10:12 mirrors.cs.umd.edu systemd[1]: New main PID 27204 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Aug 3 00:10:30 mirrors.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Aug 3 00:10:44 mirrors.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 1901 which is not our child. We'll most likely not notice when it exits.
== misty.cs.umd.edu (3 distinct, 4 total) ==
Aug 3 00:10:14 misty.cs.umd.edu systemd[1]: New main PID 21671 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Aug 3 00:10:34 misty.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Aug 3 00:10:50 misty.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 29369 which is not our child. We'll most likely not notice when it exits.
== netman.cs.umd.edu (6 distinct, 9 total) ==
Aug 3 00:08:40 netman.cs.umd.edu krb5_child[101731]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x4]
Aug 3 00:08:44 netman.cs.umd.edu sshd[101728]: error: PAM: Authentication failure for admin from 34.53.184.22
Aug 3 00:09:30 netman.cs.umd.edu sshd[101766]: error: Protocol major versions differ: 2 vs. 1
Aug 3 00:29:59 netman.cs.umd.edu setroubleshoot[107820]: SELinux is preventing /usr/bin/gpg from read access on the file gpg.conf. For complete SELinux messages run: sealert -l 019ad1da-a874-4814-8037-3b3e5f413ad2
Aug 3 00:30:00 netman.cs.umd.edu setroubleshoot[107820]: SELinux is preventing /usr/bin/gpg from open access on the file /root/.gnupg/gpg.conf. For complete SELinux messages run: sealert -l cb54177e-d44c-46a1-b246-5c0bbb8343be
Aug 3 00:30:03 netman.cs.umd.edu setroubleshoot[107820]: SELinux is preventing /usr/bin/gpg from getattr access on the file /root/.gnupg/gpg.conf. For complete SELinux messages run: sealert -l fbba2e30-b7ab-491c-9ec6-f553e9ef72af
== networkvm01.cs.umd.edu (10 distinct, 12 total) ==
Aug 3 00:48:40 networkvm01.cs.umd.edu setroubleshoot[3720626]: SELinux is preventing /usr/bin/gpg from write access on the directory /(null). For complete SELinux messages run: sealert -l 8ead1354-ae8a-4a17-bb3f-146ebf6c892c
Aug 3 00:48:40 networkvm01.cs.umd.edu setroubleshoot[3720626]: SELinux is preventing /usr/bin/gpg from add_name access on the directory /(null). For complete SELinux messages run: sealert -l f9b51e91-5dbc-455f-88c2-f0746a2f0f4c
Aug 3 00:48:40 networkvm01.cs.umd.edu setroubleshoot[3720626]: SELinux is preventing /usr/bin/gpg from create access on the file /(null). For complete SELinux messages run: sealert -l af0a60e6-c449-4bdd-bfb8-c69b58472884 [x2]
Aug 3 00:48:40 networkvm01.cs.umd.edu setroubleshoot[3720626]: SELinux is preventing /usr/bin/gpg from link access on the file /(null). For complete SELinux messages run: sealert -l 3df452f6-4d9e-4e38-946b-ea8e1edd356c [x2]
Aug 3 00:48:40 networkvm01.cs.umd.edu setroubleshoot[3720626]: SELinux is preventing /usr/bin/gpg from remove_name access on the directory .#lk0x00005572abe56ed0.networkvm01.cs.umd.edu.3720625x. For complete SELinux messages run: sealert -l fcac71c9-c7c0-45a9-9dc2-a8dcbeccfc75
Aug 3 00:48:40 networkvm01.cs.umd.edu setroubleshoot[3720626]: SELinux is preventing /usr/bin/gpg from unlink access on the file .#lk0x00005572abe56ed0.networkvm01.cs.umd.edu.3720625x. For complete SELinux messages run: sealert -l a672ebb7-fa69-419c-b1f0-fb386b8b48a6
Aug 3 00:48:40 networkvm01.cs.umd.edu setroubleshoot[3720626]: SELinux is preventing /usr/bin/gpg from write access on the directory /(null). For complete SELinux messages run: sealert -l fec9104e-d27a-4fd4-9872-6b17088c2951
Aug 3 00:48:40 networkvm01.cs.umd.edu setroubleshoot[3720626]: SELinux is preventing /usr/bin/gpg from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 26718b2a-493d-457d-818c-244bd8d4ec9d
Aug 3 00:48:40 networkvm01.cs.umd.edu setroubleshoot[3720626]: SELinux is preventing /usr/bin/gpg from remove_name access on the directory .#lk0x000055a87f760ee0.networkvm01.cs.umd.edu.3720673x. For complete SELinux messages run: sealert -l 80e6efe4-93f3-4219-8132-b2b52db1f517
Aug 3 00:48:40 networkvm01.cs.umd.edu setroubleshoot[3720626]: SELinux is preventing /usr/bin/gpg from unlink access on the file .#lk0x000055a87f760ee0.networkvm01.cs.umd.edu.3720673x. For complete SELinux messages run: sealert -l a672ebb7-fa69-419c-b1f0-fb386b8b48a6
== newhonors2 (1 distinct, 24 total) ==
Aug 3 00:13:03 newhonors2 dhcpcd[656804]: dhcpcd is not running [x24]
== openrepo (1 distinct, 1 total) ==
Aug 3 00:41:53 openrepo (nin-node)[1013822]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Aug 3 00:09:09 outbound00.cs.umd.edu python3[2309721]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Aug 3 00:13:06 outbound01.cs.umd.edu python3[342927]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (34 distinct, 34 total) ==
Aug 3 00:15:43 sentry-docker00.cs.umd.edu systemd-udevd[715535]: Could not generate persistent MAC address for veth68614a9: No such file or directory
Aug 3 00:15:43 sentry-docker00.cs.umd.edu systemd-udevd[715536]: Could not generate persistent MAC address for veth30806ff: No such file or directory
Aug 3 00:15:43 sentry-docker00.cs.umd.edu systemd-udevd[715539]: Could not generate persistent MAC address for veth126a2a4: No such file or directory
Aug 3 00:15:43 sentry-docker00.cs.umd.edu systemd-udevd[715540]: Could not generate persistent MAC address for vethacef841: No such file or directory
Aug 3 00:15:43 sentry-docker00.cs.umd.edu systemd-udevd[715535]: Could not generate persistent MAC address for veth8446906: No such file or directory
Aug 3 00:15:43 sentry-docker00.cs.umd.edu systemd-udevd[715548]: Could not generate persistent MAC address for vetha7b861d: No such file or directory
Aug 3 00:15:43 sentry-docker00.cs.umd.edu systemd-udevd[715565]: Could not generate persistent MAC address for veth7bbb21e: No such file or directory
Aug 3 00:15:43 sentry-docker00.cs.umd.edu systemd-udevd[715566]: Could not generate persistent MAC address for veth1b29e05: No such file or directory
Aug 3 00:17:13 sentry-docker00.cs.umd.edu systemd-udevd[716354]: Could not generate persistent MAC address for veth9aeeb54: No such file or directory
Aug 3 00:17:13 sentry-docker00.cs.umd.edu systemd-udevd[716355]: Could not generate persistent MAC address for veth8276c9d: No such file or directory
Aug 3 00:35:51 sentry-docker00.cs.umd.edu systemd-udevd[724997]: Could not generate persistent MAC address for vetha6216c5: No such file or directory
Aug 3 00:35:51 sentry-docker00.cs.umd.edu systemd-udevd[724998]: Could not generate persistent MAC address for vethbe5de8b: No such file or directory
Aug 3 00:35:51 sentry-docker00.cs.umd.edu systemd-udevd[725001]: Could not generate persistent MAC address for vethf85b066: No such file or directory
Aug 3 00:35:51 sentry-docker00.cs.umd.edu systemd-udevd[725002]: Could not generate persistent MAC address for vethd80fae6: No such file or directory
Aug 3 00:35:51 sentry-docker00.cs.umd.edu systemd-udevd[725013]: Could not generate persistent MAC address for veth77b1ba2: No such file or directory
Aug 3 00:35:51 sentry-docker00.cs.umd.edu systemd-udevd[725003]: Could not generate persistent MAC address for veth7907498: No such file or directory
Aug 3 00:35:51 sentry-docker00.cs.umd.edu systemd-udevd[725027]: Could not generate persistent MAC address for veth18631fe: No such file or directory
Aug 3 00:35:51 sentry-docker00.cs.umd.edu systemd-udevd[725028]: Could not generate persistent MAC address for vethfec1efc: No such file or directory
Aug 3 00:37:21 sentry-docker00.cs.umd.edu systemd-udevd[725826]: Could not generate persistent MAC address for veth1acd6d7: No such file or directory
Aug 3 00:37:21 sentry-docker00.cs.umd.edu systemd-udevd[725827]: Could not generate persistent MAC address for veth444609e: No such file or directory
Aug 3 00:55:59 sentry-docker00.cs.umd.edu systemd-udevd[734293]: link_config: could not get ethtool features for veth77b1ba2
Aug 3 00:55:59 sentry-docker00.cs.umd.edu systemd-udevd[734293]: Could not set offload features of veth77b1ba2: No such device
Aug 3 00:55:59 sentry-docker00.cs.umd.edu systemd-udevd[734317]: link_config: could not get ethtool features for vetha6216c5
Aug 3 00:55:59 sentry-docker00.cs.umd.edu systemd-udevd[734317]: Could not set offload features of vetha6216c5: No such device
Aug 3 00:55:59 sentry-docker00.cs.umd.edu systemd-udevd[734391]: Could not generate persistent MAC address for veth8e1edee: No such file or directory
Aug 3 00:55:59 sentry-docker00.cs.umd.edu systemd-udevd[734392]: Could not generate persistent MAC address for vethb4d9f82: No such file or directory
Aug 3 00:55:59 sentry-docker00.cs.umd.edu systemd-udevd[734410]: Could not generate persistent MAC address for veth541170d: No such file or directory
Aug 3 00:55:59 sentry-docker00.cs.umd.edu systemd-udevd[734416]: Could not generate persistent MAC address for veth72fbff0: No such file or directory
Aug 3 00:55:59 sentry-docker00.cs.umd.edu systemd-udevd[734419]: Could not generate persistent MAC address for veth3b2525c: No such file or directory
Aug 3 00:55:59 sentry-docker00.cs.umd.edu systemd-udevd[734421]: Could not generate persistent MAC address for veth8c2b943: No such file or directory
... 4 more distinct messages not shown
== strawberry (3 distinct, 9 total) ==
Aug 3 00:09:44 strawberry udisksd[1067]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/ST2000DM001_1CH164_W1E8J5KJ: Error updating SMART data: Error sending ATA command CHECK POWER MODE: Unexpected sense data returned:#0120000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................#0120010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................#012 (g-io-error-quark, 0) [x6]
Aug 3 00:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
Aug 3 01:04:42 strawberry smartd[5314]: Device: /dev/sda [SAT], not capable of Offline or Self-Testing.
== submit10-cln25 (3 distinct, 4 total) ==
Aug 3 00:10:11 submit10-cln25 systemd: New main PID 27361 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Aug 3 00:10:30 submit10-cln25 systemd: Daemon never wrote its PID file. Failing.
Aug 3 00:10:36 submit10-cln25 systemd: pmlogger.service: Supervising process 1893 which is not our child. We'll most likely not notice when it exits.
== submit26-b9-2 (1 distinct, 3 total) ==
Aug 3 00:20:18 submit26-b9-2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x3]
== submit26-b9-4 (11 distinct, 20 total) ==
Aug 3 00:06:23 submit26-b9-4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x6]
Aug 3 00:15:28 submit26-b9-4 setroubleshoot[908945]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l a4e66030-8621-4da9-bd27-5988bb1bf8ad [x2]
Aug 3 00:15:28 submit26-b9-4 setroubleshoot[908945]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l c055e37d-bbf5-4800-9083-d606f792c8c1 [x2]
Aug 3 00:15:28 submit26-b9-4 setroubleshoot[908945]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l e5bc3a56-6d6f-4776-954f-ddde1579648f
Aug 3 00:15:28 submit26-b9-4 setroubleshoot[908945]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.7Rb8rz/repodata/repomd.xml. For complete SELinux messages run: sealert -l a8ec5e1b-49f9-4fbc-a8ae-22e800f7abf2
Aug 3 00:15:28 submit26-b9-4 setroubleshoot[908945]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 945db714-d0c0-4402-911e-932978b8b036
Aug 3 00:15:28 submit26-b9-4 setroubleshoot[908945]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.7Rb8rz. For complete SELinux messages run: sealert -l 463998a0-fb0d-463c-82b1-471135710a14
Aug 3 00:15:28 submit26-b9-4 setroubleshoot[908945]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 473d2e21-15d8-407a-a9ee-2b842607fa00 [x2]
Aug 3 00:15:28 submit26-b9-4 setroubleshoot[908945]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 80c54d4f-bf4b-4501-addb-1627383587d0
Aug 3 00:15:28 submit26-b9-4 setroubleshoot[908945]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l c63d3890-151e-49a0-83f0-3dfb69d051e5 [x2]
Aug 3 00:15:29 submit26-b9-4 setroubleshoot[908945]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.3HEze2. For complete SELinux messages run: sealert -l 463998a0-fb0d-463c-82b1-471135710a14
== tma-0 (4 distinct, 5 total) ==
Aug 3 00:10:13 tma-0 systemd[1]: New main PID 6726 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Aug 3 00:10:30 tma-0 systemd[1]: Daemon never wrote its PID file. Failing.
Aug 3 00:10:38 tma-0 systemd[1]: pmlogger.service: Supervising process 14365 which is not our child. We'll most likely not notice when it exits.
Aug 3 00:30:25 tma-0 sshd[19119]: error: PAM: Authentication failure for admin from 91.35.78.34.bc.googleusercontent.com
== uffish.cs.umd.edu (3 distinct, 4 total) ==
Aug 3 00:10:12 uffish.cs.umd.edu systemd[1]: New main PID 735477 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Aug 3 00:10:34 uffish.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Aug 3 00:10:51 uffish.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 743076 which is not our child. We'll most likely not notice when it exits.
== updates00.cs.umd.edu (3 distinct, 4 total) ==
Aug 3 00:10:12 updates00.cs.umd.edu systemd[1]: New main PID 12088 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Aug 3 00:10:30 updates00.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Aug 3 00:10:36 updates00.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 19046 which is not our child. We'll most likely not notice when it exits.
== vacuum.cs.umd.edu (3 distinct, 4 total) ==
Aug 3 00:10:14 vacuum.cs.umd.edu systemd[1]: New main PID 21641 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Aug 3 00:10:32 vacuum.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Aug 3 00:10:44 vacuum.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 29042 which is not our child. We'll most likely not notice when it exits.
== whiffle.cs.umd.edu (3 distinct, 4 total) ==
Aug 3 00:10:14 whiffle.cs.umd.edu systemd[1]: New main PID 540736 does not belong to service, and PID file is not owned by root. Refusing. [x2]
Aug 3 00:10:40 whiffle.cs.umd.edu systemd[1]: Daemon never wrote its PID file. Failing.
Aug 3 00:10:53 whiffle.cs.umd.edu systemd[1]: pmlogger.service: Supervising process 548402 which is not our child. We'll most likely not notice when it exits.
== wraith (3 distinct, 3 total) ==
Aug 3 00:54:53 wraith kernel: nvme 10000:e1:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Aug 3 00:54:53 wraith kernel: nvme 10000:e1:00.0: device [15b7:5015] error status/mask=00000001/0000e000
Aug 3 00:54:53 wraith kernel: nvme 10000:e1:00.0: [ 0] RxErr (First)
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.4805s
Status : exited 0
Output :
Syslog digest — 2026-08-03 00:05 EDT
Processed 4,184 lines, filtered 3,439 (82%). 745 unknown (81 distinct) from 23 host(s).
== abuse (1 distinct, 346 total) ==
Aug 2 23:05:06 abuse rsyslogd[21745]: imjournal: open() failed for path: '/var/lib/rsyslog/imjournal.state.tmp': Input/output error [v8.2404.0 try https://www.rsyslog.com/e/2433 ] [x346]
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Aug 2 23:42:44 b0b02.cs.umd.edu rustdesk[2290931]: cannot open display:
== biggulp.cs.umd.edu (3 distinct, 3 total) ==
Aug 2 23:49:17 biggulp.cs.umd.edu sshd-session[2468157]: pam_access(sshd:auth): access denied for user `admin' from `34.156.44.197'
Aug 2 23:49:17 biggulp.cs.umd.edu krb5_child[2468159]: Client 'admin(a)UMD.EDU' not found in Kerberos database
Aug 2 23:49:17 biggulp.cs.umd.edu sshd-session[2468155]: error: PAM: System error for admin from 34.156.44.197
== cheezit.cs.umd.edu (6 distinct, 7 total) ==
Aug 2 23:47:38 cheezit.cs.umd.edu sshd-session[452567]: pam_access(sshd:auth): access denied for user `admin' from `34.79.156.231'
Aug 2 23:47:38 cheezit.cs.umd.edu krb5_child[452569]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x2]
Aug 2 23:47:38 cheezit.cs.umd.edu sshd-session[452565]: error: PAM: System error for admin from 34.79.156.231
Aug 2 23:48:27 cheezit.cs.umd.edu sshd-session[452625]: error: Protocol major versions differ: 2 vs. 1
Aug 2 23:56:35 cheezit.cs.umd.edu sshd-session[455162]: pam_access(sshd:auth): access denied for user `admin' from `34.38.81.163'
Aug 2 23:56:35 cheezit.cs.umd.edu sshd-session[455160]: error: PAM: System error for admin from 34.38.81.163
== contest (1 distinct, 34 total) ==
Aug 2 23:05:42 contest goferd[1007]: [ERROR][worker-0] gofer.messaging.adapter.connect:33 - connect: proton+amqps://satellite8.cs.umd.edu:5647, failed: Connection amqps://satellite8.cs.umd.edu:5647 disconnected: Condition('proton.pythonio', 'Connection refused to all addresses') [x34]
== csfw00a (1 distinct, 206 total) ==
Aug 2 23:05:32 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x206]
== hackerman (7 distinct, 12 total) ==
Aug 2 23:19:01 hackerman gnome-software[2060381]: failed to commit changes to dconf: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dfile_2derror_2dquark.Code2: Failed to create file “/adminhomes/sajith/.config/dconf/user.KF5XT3”: Permission denied
Aug 2 23:20:04 hackerman gnome-software[2060381]: can't reliably fixup error code 4 in domain g-io-error-quark: Not a directory [x4]
Aug 2 23:20:12 hackerman gnome-software[2060381]: Only 0 apps for recent list, hiding
Aug 2 23:20:28 hackerman packagekitd[3287650]: Failed to get cache filename for libreoffice [x2]
Aug 2 23:20:28 hackerman packagekitd[3287650]: Failed to get cache filename for kernel [x2]
Aug 2 23:20:36 hackerman gnome-software[2060381]: failed to commit changes to dconf: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dfile_2derror_2dquark.Code2: Failed to create file “/adminhomes/sajith/.config/dconf/user.R87HT3”: Permission denied
Aug 2 23:20:39 hackerman packagekitd[3287650]: failed to parse public key for /etc/pki/rpm-gpg/RPM-GPG-KEY-PQC-redhat-release
== idm00 (1 distinct, 1 total) ==
Aug 2 23:51:15 idm00 named[1455]: client @0x7f3304b3d148 10.73.240.42#52914: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Aug 2 23:36:01 idmp0 named[5198]: client @0x7f98f4021ea8 10.73.240.43#63507: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 33 total) ==
Aug 2 23:07:51 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x33]
== krispykreme.cs.umd.edu (2 distinct, 4 total) ==
Aug 2 23:08:28 krispykreme.cs.umd.edu sshd-session[2585507]: pam_access(sshd:auth): access denied for user `root' from `193.24.211.204' [x2]
Aug 2 23:08:30 krispykreme.cs.umd.edu sshd-session[2585505]: error: PAM: Authentication failure for root from 193.24.211.204 [x2]
== matrix (1 distinct, 1 total) ==
Aug 3 00:00:17 matrix (nin-node)[618768]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
== neo-gizmonic (1 distinct, 1 total) ==
Aug 3 00:00:27 neo-gizmonic (nin-node)[405331]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
== neoavion (1 distinct, 1 total) ==
Aug 3 00:00:25 neoavion (nin-node)[3149735]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
== newhonors2 (2 distinct, 25 total) ==
Aug 2 23:13:02 newhonors2 dhcpcd[654618]: dhcpcd is not running [x24]
Aug 3 00:00:43 newhonors2 (nin-node)[656265]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Aug 2 23:09:09 outbound00.cs.umd.edu python3[2295702]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Aug 2 23:13:06 outbound01.cs.umd.edu python3[328338]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (40 distinct, 40 total) ==
Aug 2 23:15:17 sentry-docker00.cs.umd.edu systemd-udevd[687068]: link_config: could not get ethtool features for veth9807a09
Aug 2 23:15:17 sentry-docker00.cs.umd.edu systemd-udevd[687068]: Could not set offload features of veth9807a09: No such device
Aug 2 23:15:17 sentry-docker00.cs.umd.edu systemd-udevd[687137]: link_config: could not get ethtool features for vetha39a432
Aug 2 23:15:17 sentry-docker00.cs.umd.edu systemd-udevd[687137]: Could not set offload features of vetha39a432: No such device
Aug 2 23:15:18 sentry-docker00.cs.umd.edu systemd-udevd[687159]: Could not generate persistent MAC address for vetha3e84d9: No such file or directory
Aug 2 23:15:18 sentry-docker00.cs.umd.edu systemd-udevd[687160]: Could not generate persistent MAC address for veth41feff8: No such file or directory
Aug 2 23:15:18 sentry-docker00.cs.umd.edu systemd-udevd[687163]: Could not generate persistent MAC address for vethe540a2b: No such file or directory
Aug 2 23:15:18 sentry-docker00.cs.umd.edu systemd-udevd[687164]: Could not generate persistent MAC address for vethf446d4a: No such file or directory
Aug 2 23:15:18 sentry-docker00.cs.umd.edu systemd-udevd[687177]: Could not generate persistent MAC address for veth1843926: No such file or directory
Aug 2 23:15:18 sentry-docker00.cs.umd.edu systemd-udevd[687167]: Could not generate persistent MAC address for veth64a4ff6: No such file or directory
Aug 2 23:15:18 sentry-docker00.cs.umd.edu systemd-udevd[687238]: Could not generate persistent MAC address for veth6d7a013: No such file or directory
Aug 2 23:15:18 sentry-docker00.cs.umd.edu systemd-udevd[687241]: Could not generate persistent MAC address for veth57b6971: No such file or directory
Aug 2 23:16:56 sentry-docker00.cs.umd.edu systemd-udevd[688026]: Could not generate persistent MAC address for vethecba1c2: No such file or directory
Aug 2 23:16:56 sentry-docker00.cs.umd.edu systemd-udevd[688027]: Could not generate persistent MAC address for vethf5d3beb: No such file or directory
Aug 2 23:35:26 sentry-docker00.cs.umd.edu systemd-udevd[696608]: link_config: could not get ethtool features for vetha3e84d9
Aug 2 23:35:26 sentry-docker00.cs.umd.edu systemd-udevd[696608]: Could not set offload features of vetha3e84d9: No such device
Aug 2 23:35:26 sentry-docker00.cs.umd.edu systemd-udevd[696615]: link_config: could not get ethtool features for veth6d7a013
Aug 2 23:35:26 sentry-docker00.cs.umd.edu systemd-udevd[696615]: Could not set offload features of veth6d7a013: No such device
Aug 2 23:35:26 sentry-docker00.cs.umd.edu systemd-udevd[696645]: Could not generate persistent MAC address for vethcdec746: No such file or directory
Aug 2 23:35:26 sentry-docker00.cs.umd.edu systemd-udevd[696646]: Could not generate persistent MAC address for vethef8dbdb: No such file or directory
Aug 2 23:35:26 sentry-docker00.cs.umd.edu systemd-udevd[696664]: Could not generate persistent MAC address for veth236f4e1: No such file or directory
Aug 2 23:35:26 sentry-docker00.cs.umd.edu systemd-udevd[696665]: Could not generate persistent MAC address for veth103767e: No such file or directory
Aug 2 23:35:26 sentry-docker00.cs.umd.edu systemd-udevd[696690]: Could not generate persistent MAC address for vethfc26379: No such file or directory
Aug 2 23:35:26 sentry-docker00.cs.umd.edu systemd-udevd[696691]: Could not generate persistent MAC address for veth47463c2: No such file or directory
Aug 2 23:35:26 sentry-docker00.cs.umd.edu systemd-udevd[696748]: Could not generate persistent MAC address for veth65c4e90: No such file or directory
Aug 2 23:35:26 sentry-docker00.cs.umd.edu systemd-udevd[696750]: Could not generate persistent MAC address for veth115d486: No such file or directory
Aug 2 23:37:00 sentry-docker00.cs.umd.edu systemd-udevd[697514]: Could not generate persistent MAC address for vethe9f02c3: No such file or directory
Aug 2 23:37:00 sentry-docker00.cs.umd.edu systemd-udevd[697515]: Could not generate persistent MAC address for veth77f98e6: No such file or directory
Aug 2 23:55:34 sentry-docker00.cs.umd.edu systemd-udevd[706073]: link_config: could not get ethtool features for veth236f4e1
Aug 2 23:55:34 sentry-docker00.cs.umd.edu systemd-udevd[706073]: Could not set offload features of veth236f4e1: No such device
... 10 more distinct messages not shown
== soul (2 distinct, 2 total) ==
Aug 2 23:08:27 soul krb5_child[3281129]: Client 'admin(a)UMD.EDU' not found in Kerberos database
Aug 2 23:59:31 soul krb5_child[3287507]: Preauthentication failed
== strawberry (3 distinct, 9 total) ==
Aug 2 23:09:44 strawberry udisksd[1067]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/ST2000DM001_1CH164_W1E8J5KJ: Error updating SMART data: Error sending ATA command CHECK POWER MODE: Unexpected sense data returned:#0120000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................#0120010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................#012 (g-io-error-quark, 0) [x6]
Aug 2 23:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
Aug 3 00:00:03 strawberry kernel: kauditd_printk_skb: 4 callbacks suppressed
== submit26-b9-4 (1 distinct, 2 total) ==
Aug 2 23:30:56 submit26-b9-4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x2]
== talkhosts9 (1 distinct, 2 total) ==
Aug 2 23:07:03 talkhosts9 setroubleshoot[918323]: SELinux is preventing /usr/bin/lsof from getattr access on the unix_stream_socket unix_stream_socket. For complete SELinux messages run: sealert -l a6df89b3-c497-469c-8232-c4fde0508abf [x2]
== wraith (2 distinct, 2 total) ==
Aug 3 00:00:05 wraith kernel: kauditd_printk_skb: 26 callbacks suppressed
Aug 3 00:00:05 wraith (nin-node)[1076764]: 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 : 0.4765s
Status : exited 0
Output :
Syslog digest — 2026-08-02 23:05 EDT
Processed 4,125 lines, filtered 3,387 (82%). 738 unknown (73 distinct) from 20 host(s).
== abuse (1 distinct, 346 total) ==
Aug 2 22:05:06 abuse rsyslogd[21745]: imjournal: open() failed for path: '/var/lib/rsyslog/imjournal.state.tmp': Input/output error [v8.2404.0 try https://www.rsyslog.com/e/2433 ] [x346]
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Aug 2 22:42:40 b0b02.cs.umd.edu rustdesk[2275837]: cannot open display:
== bale (1 distinct, 1 total) ==
Aug 2 22:05:40 bale setroubleshoot[3729407]: SELinux is preventing /usr/bin/tar from using the fowner capability. For complete SELinux messages run: sealert -l 8f58859c-1c63-4aee-afff-7c8e1dd95f45
== contest (1 distinct, 33 total) ==
Aug 2 22:06:47 contest goferd[1007]: [ERROR][worker-0] gofer.messaging.adapter.connect:33 - connect: proton+amqps://satellite8.cs.umd.edu:5647, failed: Connection amqps://satellite8.cs.umd.edu:5647 disconnected: Condition('proton.pythonio', 'Connection refused to all addresses') [x33]
== csfw00a (1 distinct, 218 total) ==
Aug 2 22:04:57 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x218]
== hackerman (6 distinct, 11 total) ==
Aug 2 22:20:04 hackerman gnome-software[2060381]: can't reliably fixup error code 4 in domain g-io-error-quark: Not a directory [x4]
Aug 2 22:20:12 hackerman gnome-software[2060381]: Only 0 apps for recent list, hiding
Aug 2 22:20:28 hackerman gnome-software[2060381]: failed to commit changes to dconf: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dfile_2derror_2dquark.Code2: Failed to create file “/adminhomes/sajith/.config/dconf/user.4N63S3”: Permission denied
Aug 2 22:20:29 hackerman packagekitd[3274319]: Failed to get cache filename for libreoffice [x2]
Aug 2 22:20:29 hackerman packagekitd[3274319]: Failed to get cache filename for kernel [x2]
Aug 2 22:20:38 hackerman packagekitd[3274319]: failed to parse public key for /etc/pki/rpm-gpg/RPM-GPG-KEY-PQC-redhat-release
== idm00 (1 distinct, 1 total) ==
Aug 2 22:51:15 idm00 named[1455]: client @0x7f330c467a48 10.73.240.42#52818: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Aug 2 22:36:01 idmp0 named[5198]: client @0x7f9918084e38 10.73.240.43#57973: update '73.10.in-addr.arpa/IN' denied
== inbound01.cs.umd.edu (2 distinct, 2 total) ==
Aug 2 23:01:56 inbound01.cs.umd.edu krb5_child[346341]: Client 'admin(a)UMD.EDU' not found in Kerberos database
Aug 2 23:02:42 inbound01.cs.umd.edu sshd-session[346680]: error: Protocol major versions differ: 2 vs. 1
== itmon02 (1 distinct, 27 total) ==
Aug 2 22:13:11 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x27]
== krispykreme.cs.umd.edu (6 distinct, 6 total) ==
Aug 2 22:35:13 krispykreme.cs.umd.edu sshd-session[2576427]: pam_access(sshd:auth): access denied for user `root' from `193.24.211.204'
Aug 2 22:35:14 krispykreme.cs.umd.edu sshd-session[2576425]: error: PAM: Authentication failure for root from 193.24.211.204
Aug 2 22:45:59 krispykreme.cs.umd.edu sshd-session[2579015]: pam_access(sshd:auth): access denied for user `admin' from `34.53.149.193'
Aug 2 22:46:00 krispykreme.cs.umd.edu krb5_child[2579017]: Client 'admin(a)UMD.EDU' not found in Kerberos database
Aug 2 22:46:00 krispykreme.cs.umd.edu sshd-session[2579013]: error: PAM: System error for admin from 34.53.149.193
Aug 2 22:46:48 krispykreme.cs.umd.edu sshd-session[2579137]: error: Protocol major versions differ: 2 vs. 1
== matrix (2 distinct, 3 total) ==
Aug 2 22:20:39 matrix krb5_child[562154]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x2]
Aug 2 22:20:41 matrix sshd[562147]: error: PAM: Authentication failure for admin from 34.53.184.22
== newhonors2 (1 distinct, 24 total) ==
Aug 2 22:13:03 newhonors2 dhcpcd[652776]: dhcpcd is not running [x24]
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Aug 2 22:09:09 outbound00.cs.umd.edu python3[2281626]: ldapdb [x6]
== outbound01.cs.umd.edu (3 distinct, 8 total) ==
Aug 2 22:13:06 outbound01.cs.umd.edu python3[314504]: ldapdb [x6]
Aug 2 23:02:46 outbound01.cs.umd.edu krb5_child[326018]: Client 'admin(a)UMD.EDU' not found in Kerberos database
Aug 2 23:02:59 outbound01.cs.umd.edu sshd-session[326105]: error: Protocol major versions differ: 2 vs. 1
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Aug 2 22:14:53 sentry-docker00.cs.umd.edu systemd-udevd[658440]: Could not generate persistent MAC address for vethb51682c: No such file or directory
Aug 2 22:14:53 sentry-docker00.cs.umd.edu systemd-udevd[658441]: Could not generate persistent MAC address for veth3a910ff: No such file or directory
Aug 2 22:14:53 sentry-docker00.cs.umd.edu systemd-udevd[658466]: Could not generate persistent MAC address for veth19f1e05: No such file or directory
Aug 2 22:14:53 sentry-docker00.cs.umd.edu systemd-udevd[658467]: Could not generate persistent MAC address for veth88a0dfc: No such file or directory
Aug 2 22:14:53 sentry-docker00.cs.umd.edu systemd-udevd[658474]: Could not generate persistent MAC address for veth4ede3e8: No such file or directory
Aug 2 22:14:53 sentry-docker00.cs.umd.edu systemd-udevd[658511]: Could not generate persistent MAC address for vethef3804e: No such file or directory
Aug 2 22:14:53 sentry-docker00.cs.umd.edu systemd-udevd[658514]: Could not generate persistent MAC address for veth87818ac: No such file or directory
Aug 2 22:14:53 sentry-docker00.cs.umd.edu systemd-udevd[658493]: Could not generate persistent MAC address for veth9235c6f: No such file or directory
Aug 2 22:16:35 sentry-docker00.cs.umd.edu systemd-udevd[659625]: Could not generate persistent MAC address for vethd4aa0ba: No such file or directory
Aug 2 22:16:35 sentry-docker00.cs.umd.edu systemd-udevd[659626]: Could not generate persistent MAC address for veth4e088bc: No such file or directory
Aug 2 22:35:01 sentry-docker00.cs.umd.edu systemd-udevd[667920]: link_config: could not get ethtool features for vethb51682c
Aug 2 22:35:01 sentry-docker00.cs.umd.edu systemd-udevd[667920]: Could not set offload features of vethb51682c: No such device
Aug 2 22:35:01 sentry-docker00.cs.umd.edu systemd-udevd[667922]: link_config: could not get ethtool features for veth9235c6f
Aug 2 22:35:01 sentry-docker00.cs.umd.edu systemd-udevd[667922]: Could not set offload features of veth9235c6f: No such device
Aug 2 22:35:01 sentry-docker00.cs.umd.edu systemd-udevd[667956]: Could not generate persistent MAC address for veth0c2441e: No such file or directory
Aug 2 22:35:01 sentry-docker00.cs.umd.edu systemd-udevd[667957]: Could not generate persistent MAC address for vethf16c70b: No such file or directory
Aug 2 22:35:01 sentry-docker00.cs.umd.edu systemd-udevd[667960]: Could not generate persistent MAC address for vethba10370: No such file or directory
Aug 2 22:35:01 sentry-docker00.cs.umd.edu systemd-udevd[667961]: Could not generate persistent MAC address for veth15f2eb2: No such file or directory
Aug 2 22:35:01 sentry-docker00.cs.umd.edu systemd-udevd[667984]: Could not generate persistent MAC address for veth438c396: No such file or directory
Aug 2 22:35:01 sentry-docker00.cs.umd.edu systemd-udevd[667985]: Could not generate persistent MAC address for vethccdb965: No such file or directory
Aug 2 22:35:01 sentry-docker00.cs.umd.edu systemd-udevd[668010]: Could not generate persistent MAC address for veth927bede: No such file or directory
Aug 2 22:35:01 sentry-docker00.cs.umd.edu systemd-udevd[668011]: Could not generate persistent MAC address for veth4aac7c6: No such file or directory
Aug 2 22:36:43 sentry-docker00.cs.umd.edu systemd-udevd[669149]: Could not generate persistent MAC address for vethe212144: No such file or directory
Aug 2 22:36:43 sentry-docker00.cs.umd.edu systemd-udevd[669150]: Could not generate persistent MAC address for veth099786d: No such file or directory
Aug 2 22:55:09 sentry-docker00.cs.umd.edu systemd-udevd[677410]: link_config: could not get ethtool features for veth0c2441e
Aug 2 22:55:09 sentry-docker00.cs.umd.edu systemd-udevd[677410]: Could not set offload features of veth0c2441e: No such device
Aug 2 22:55:09 sentry-docker00.cs.umd.edu systemd-udevd[677452]: Could not generate persistent MAC address for vethca7906d: No such file or directory
Aug 2 22:55:09 sentry-docker00.cs.umd.edu systemd-udevd[677453]: Could not generate persistent MAC address for veth57a00d3: No such file or directory
Aug 2 22:55:09 sentry-docker00.cs.umd.edu systemd-udevd[677456]: Could not generate persistent MAC address for vetha39a432: No such file or directory
Aug 2 22:55:09 sentry-docker00.cs.umd.edu systemd-udevd[677457]: Could not generate persistent MAC address for veth88b0dac: No such file or directory
... 6 more distinct messages not shown
== strawberry (2 distinct, 8 total) ==
Aug 2 22:09:44 strawberry udisksd[1067]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/ST2000DM001_1CH164_W1E8J5KJ: Error updating SMART data: Error sending ATA command CHECK POWER MODE: Unexpected sense data returned:#0120000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................#0120010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................#012 (g-io-error-quark, 0) [x6]
Aug 2 22:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-2 (1 distinct, 1 total) ==
Aug 2 22:15:06 submit26-b9-2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
== submit26-b9-4 (1 distinct, 1 total) ==
Aug 2 22:15:05 submit26-b9-4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
== vacuum.cs.umd.edu (4 distinct, 4 total) ==
Aug 2 22:11:58 vacuum.cs.umd.edu abrt-hook-ccpp[23188]: Process 18749 (driver) of user 33 killed by SIGABRT - dumping core
Aug 2 22:11:58 vacuum.cs.umd.edu abrt-server[23190]: Package 'amanda-backup_server' isn't signed with proper key
Aug 2 22:11:58 vacuum.cs.umd.edu abrt-server[23190]: 'post-create' on '/var/spool/abrt/ccpp-2026-08-02-22:11:58-18749' exited with 1
Aug 2 22:11:58 vacuum.cs.umd.edu abrt-server[23190]: Deleting problem directory '/var/spool/abrt/ccpp-2026-08-02-22:11:58-18749'
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.4876s
Status : exited 0
Output :
Syslog digest — 2026-08-02 22:05 EDT
Processed 3,940 lines, filtered 3,129 (79%). 811 unknown (98 distinct) from 17 host(s).
== abuse (1 distinct, 346 total) ==
Aug 2 21:05:06 abuse rsyslogd[21745]: imjournal: open() failed for path: '/var/lib/rsyslog/imjournal.state.tmp': Input/output error [v8.2404.0 try https://www.rsyslog.com/e/2433 ] [x346]
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Aug 2 21:42:36 b0b02.cs.umd.edu rustdesk[2260796]: cannot open display:
== contest (10 distinct, 47 total) ==
Aug 2 21:06:05 contest goferd[1007]: [ERROR][worker-0] gofer.messaging.adapter.connect:33 - connect: proton+amqps://satellite8.cs.umd.edu:5647, failed: Connection amqps://satellite8.cs.umd.edu:5647 disconnected: Condition('proton.pythonio', 'Connection refused to all addresses') [x34]
Aug 2 21:48:17 contest setroubleshoot[526903]: SELinux is preventing /usr/libexec/platform-python3.6 from create access on the directory libdnf.a75lAD. For complete SELinux messages run: sealert -l cb6b25c6-4765-4cf2-88a0-9b3b508e94e9
Aug 2 21:48:17 contest setroubleshoot[526903]: SELinux is preventing /usr/bin/gpgconf from add_name access on the directory repodata. For complete SELinux messages run: sealert -l 41cf7b1b-0f34-4609-98f2-b66e7825fef7 [x2]
Aug 2 21:48:17 contest setroubleshoot[526903]: SELinux is preventing /usr/libexec/platform-python3.6 from create access on the file mirrorlist. For complete SELinux messages run: sealert -l fc20ff92-ea83-4f38-a24b-ddfd737a3141
Aug 2 21:48:17 contest setroubleshoot[526903]: SELinux is preventing /usr/libexec/platform-python3.6 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l ac675631-fa35-4e93-adc9-b692b18e53e5
Aug 2 21:48:17 contest setroubleshoot[526903]: SELinux is preventing /usr/libexec/platform-python3.6 from read access on the directory libdnf.a75lAD. For complete SELinux messages run: sealert -l 45d103b6-0810-4890-a705-990118577ce8
Aug 2 21:48:17 contest setroubleshoot[526903]: SELinux is preventing /usr/libexec/platform-python3.6 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 7e499113-2fd7-4f67-bec6-3521efbe3637 [x3]
Aug 2 21:48:17 contest setroubleshoot[526903]: SELinux is preventing /usr/libexec/platform-python3.6 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 3928930b-a1ed-448d-950b-0665ac2adef8 [x2]
Aug 2 21:48:18 contest setroubleshoot[526903]: SELinux is preventing /usr/libexec/platform-python3.6 from create access on the directory libdnf.6WtPWn. For complete SELinux messages run: sealert -l cb6b25c6-4765-4cf2-88a0-9b3b508e94e9
Aug 2 21:48:18 contest setroubleshoot[526903]: SELinux is preventing /usr/libexec/platform-python3.6 from read access on the directory libdnf.6WtPWn. For complete SELinux messages run: sealert -l 45d103b6-0810-4890-a705-990118577ce8
== csfw00a (1 distinct, 242 total) ==
Aug 2 21:05:12 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x242]
== hackerman (7 distinct, 12 total) ==
Aug 2 21:19:01 hackerman gnome-software[2060381]: failed to commit changes to dconf: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dfile_2derror_2dquark.Code2: Failed to create file “/adminhomes/sajith/.config/dconf/user.7KXVS3”: Permission denied
Aug 2 21:20:04 hackerman gnome-software[2060381]: can't reliably fixup error code 4 in domain g-io-error-quark: Not a directory [x4]
Aug 2 21:20:12 hackerman gnome-software[2060381]: Only 0 apps for recent list, hiding
Aug 2 21:20:28 hackerman gnome-software[2060381]: failed to commit changes to dconf: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dfile_2derror_2dquark.Code2: Failed to create file “/adminhomes/sajith/.config/dconf/user.B461S3”: Permission denied
Aug 2 21:20:29 hackerman packagekitd[3260503]: Failed to get cache filename for libreoffice [x2]
Aug 2 21:20:29 hackerman packagekitd[3260503]: Failed to get cache filename for kernel [x2]
Aug 2 21:20:38 hackerman packagekitd[3260503]: failed to parse public key for /etc/pki/rpm-gpg/RPM-GPG-KEY-PQC-redhat-release
== idm00 (1 distinct, 1 total) ==
Aug 2 21:51:15 idm00 named[1455]: client @0x7f33157df218 10.73.240.42#51331: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Aug 2 21:36:01 idmp0 named[5198]: client @0x7f98f400ddc8 10.73.240.43#57556: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 41 total) ==
Aug 2 21:07:58 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x41]
== newhonors2 (1 distinct, 24 total) ==
Aug 2 21:13:03 newhonors2 dhcpcd[650911]: dhcpcd is not running [x24]
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Aug 2 21:09:09 outbound00.cs.umd.edu python3[2267784]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Aug 2 21:13:07 outbound01.cs.umd.edu python3[300479]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (40 distinct, 40 total) ==
Aug 2 21:14:28 sentry-docker00.cs.umd.edu systemd-udevd[629738]: link_config: could not get ethtool features for veth6038891
Aug 2 21:14:28 sentry-docker00.cs.umd.edu systemd-udevd[629738]: Could not set offload features of veth6038891: No such device
Aug 2 21:14:28 sentry-docker00.cs.umd.edu systemd-udevd[629774]: Could not generate persistent MAC address for vethf392d9d: No such file or directory
Aug 2 21:14:28 sentry-docker00.cs.umd.edu systemd-udevd[629775]: Could not generate persistent MAC address for veth6ce7562: No such file or directory
Aug 2 21:14:28 sentry-docker00.cs.umd.edu systemd-udevd[629778]: Could not generate persistent MAC address for veth1370191: No such file or directory
Aug 2 21:14:28 sentry-docker00.cs.umd.edu systemd-udevd[629779]: Could not generate persistent MAC address for veth80a71a6: No such file or directory
Aug 2 21:14:28 sentry-docker00.cs.umd.edu systemd-udevd[629802]: Could not generate persistent MAC address for vethd7bd3d5: No such file or directory
Aug 2 21:14:28 sentry-docker00.cs.umd.edu systemd-udevd[629803]: Could not generate persistent MAC address for vethab3f28b: No such file or directory
Aug 2 21:14:28 sentry-docker00.cs.umd.edu systemd-udevd[629821]: Could not generate persistent MAC address for veth855f05b: No such file or directory
Aug 2 21:14:28 sentry-docker00.cs.umd.edu systemd-udevd[629826]: Could not generate persistent MAC address for veth1a8c1a3: No such file or directory
Aug 2 21:16:22 sentry-docker00.cs.umd.edu systemd-udevd[631012]: link_config: could not get ethtool features for vethc85c90c
Aug 2 21:16:22 sentry-docker00.cs.umd.edu systemd-udevd[631012]: Could not set offload features of vethc85c90c: No such device
Aug 2 21:16:22 sentry-docker00.cs.umd.edu systemd-udevd[631030]: Could not generate persistent MAC address for veth132dfd9: No such file or directory
Aug 2 21:16:22 sentry-docker00.cs.umd.edu systemd-udevd[631031]: Could not generate persistent MAC address for veth3f96d10: No such file or directory
Aug 2 21:34:36 sentry-docker00.cs.umd.edu systemd-udevd[639451]: link_config: could not get ethtool features for veth855f05b
Aug 2 21:34:36 sentry-docker00.cs.umd.edu systemd-udevd[639451]: Could not set offload features of veth855f05b: No such device
Aug 2 21:34:36 sentry-docker00.cs.umd.edu systemd-udevd[639480]: Could not generate persistent MAC address for veth891fdd7: No such file or directory
Aug 2 21:34:36 sentry-docker00.cs.umd.edu systemd-udevd[639481]: Could not generate persistent MAC address for vetha5f2a9f: No such file or directory
Aug 2 21:34:36 sentry-docker00.cs.umd.edu systemd-udevd[639484]: Could not generate persistent MAC address for vethe315b04: No such file or directory
Aug 2 21:34:36 sentry-docker00.cs.umd.edu systemd-udevd[639485]: Could not generate persistent MAC address for veth904bc46: No such file or directory
Aug 2 21:34:36 sentry-docker00.cs.umd.edu systemd-udevd[639508]: Could not generate persistent MAC address for veth1a7a302: No such file or directory
Aug 2 21:34:36 sentry-docker00.cs.umd.edu systemd-udevd[639509]: Could not generate persistent MAC address for veth4af09b5: No such file or directory
Aug 2 21:34:36 sentry-docker00.cs.umd.edu systemd-udevd[639521]: Could not generate persistent MAC address for vethd993e75: No such file or directory
Aug 2 21:34:36 sentry-docker00.cs.umd.edu systemd-udevd[639525]: Could not generate persistent MAC address for veth1f0a775: No such file or directory
Aug 2 21:36:26 sentry-docker00.cs.umd.edu systemd-udevd[640681]: link_config: could not get ethtool features for veth132dfd9
Aug 2 21:36:26 sentry-docker00.cs.umd.edu systemd-udevd[640681]: Could not set offload features of veth132dfd9: No such device
Aug 2 21:36:27 sentry-docker00.cs.umd.edu systemd-udevd[640699]: Could not generate persistent MAC address for vethecdcb18: No such file or directory
Aug 2 21:36:27 sentry-docker00.cs.umd.edu systemd-udevd[640700]: Could not generate persistent MAC address for veth1bcb227: No such file or directory
Aug 2 21:54:44 sentry-docker00.cs.umd.edu systemd-udevd[648920]: link_config: could not get ethtool features for veth891fdd7
Aug 2 21:54:44 sentry-docker00.cs.umd.edu systemd-udevd[648920]: Could not set offload features of veth891fdd7: No such device
... 10 more distinct messages not shown
== strawberry (2 distinct, 8 total) ==
Aug 2 21:09:44 strawberry udisksd[1067]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/ST2000DM001_1CH164_W1E8J5KJ: Error updating SMART data: Error sending ATA command CHECK POWER MODE: Unexpected sense data returned:#0120000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................#0120010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................#012 (g-io-error-quark, 0) [x6]
Aug 2 21:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-2 (10 distinct, 11 total) ==
Aug 2 21:12:52 submit26-b9-2 setroubleshoot[899791]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l d506243c-d61e-48f3-b42a-4592c913deb0
Aug 2 21:12:52 submit26-b9-2 setroubleshoot[899791]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 3b4752ac-1b9a-4af9-a05b-32e4c2eb13ab
Aug 2 21:12:52 submit26-b9-2 setroubleshoot[899791]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 29e5adbd-4381-4467-b40d-a2219101e096
Aug 2 21:12:52 submit26-b9-2 setroubleshoot[899791]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.p6QtDY/repodata/repomd.xml. For complete SELinux messages run: sealert -l 1b38f2ec-01ce-4343-8059-ba7494ecc5c4
Aug 2 21:12:52 submit26-b9-2 setroubleshoot[899791]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l e5f9af40-1f63-4924-b012-27ab2a7b2266
Aug 2 21:12:52 submit26-b9-2 setroubleshoot[899791]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.p6QtDY. For complete SELinux messages run: sealert -l 5c54db87-54a3-4a7c-97b4-b5c48d6c3543
Aug 2 21:12:52 submit26-b9-2 setroubleshoot[899791]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 63cd60e1-1e61-4276-afea-dd8526ffe8b2
Aug 2 21:12:52 submit26-b9-2 setroubleshoot[899791]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 81c7e9ec-e023-4c6d-b1ad-c02a242e655e
Aug 2 21:12:52 submit26-b9-2 setroubleshoot[899791]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 6ae9a597-e123-4d74-8eec-a8ebe0f5e4d0
Aug 2 21:34:22 submit26-b9-2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x2]
== submit26-b9-3 (9 distinct, 9 total) ==
Aug 2 21:20:38 submit26-b9-3 setroubleshoot[789648]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 5b912a44-22fd-4560-b201-2a4e289b73f5
Aug 2 21:20:38 submit26-b9-3 setroubleshoot[789648]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 7f1df1e4-725e-4953-98eb-1079f908f543
Aug 2 21:20:38 submit26-b9-3 setroubleshoot[789648]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 40b8852a-f77b-44b4-affe-5f11fa33de43
Aug 2 21:20:38 submit26-b9-3 setroubleshoot[789648]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.9TsF1H/repodata/repomd.xml. For complete SELinux messages run: sealert -l 45a8019e-f6b5-4baa-92c1-862594b40d46
Aug 2 21:20:38 submit26-b9-3 setroubleshoot[789648]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l e9f0bfff-7784-4126-baa4-2bb06da56591
Aug 2 21:20:38 submit26-b9-3 setroubleshoot[789648]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.9TsF1H. For complete SELinux messages run: sealert -l 0b17cc3d-cdc6-4fe2-a11f-3892e7c41dc7
Aug 2 21:20:38 submit26-b9-3 setroubleshoot[789648]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 10e38c64-b65f-4cdd-901e-4375652d9a42
Aug 2 21:20:38 submit26-b9-3 setroubleshoot[789648]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 7fd9cf72-ef38-48e1-b6aa-b571b26a7b22
Aug 2 21:20:38 submit26-b9-3 setroubleshoot[789648]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l b9b11116-89bd-4a3c-980c-1d422c5dcee4
== submit26-b9-4 (1 distinct, 2 total) ==
Aug 2 21:31:15 submit26-b9-4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x2]
== submit26-clnb9 (10 distinct, 14 total) ==
Aug 2 21:31:56 submit26-clnb9 setroubleshoot[1704279]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 6783ed2b-5ae4-42b5-975a-4bf50eec4658 [x2]
Aug 2 21:31:56 submit26-clnb9 setroubleshoot[1704279]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 9e7fa955-cc30-4804-ac8c-e1779e85946c [x2]
Aug 2 21:31:56 submit26-clnb9 setroubleshoot[1704279]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 69bfa6e3-089c-40ff-9563-fd30787d0774
Aug 2 21:31:56 submit26-clnb9 setroubleshoot[1704279]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.xZsEqZ/repodata/repomd.xml. For complete SELinux messages run: sealert -l 001acdb5-31ef-4e52-b10b-90f467a89ddc
Aug 2 21:31:56 submit26-clnb9 setroubleshoot[1704279]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l edacddcf-16ed-4dc3-8d82-7c597d5dee23
Aug 2 21:31:56 submit26-clnb9 setroubleshoot[1704279]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.xZsEqZ. For complete SELinux messages run: sealert -l 62b3782e-4730-4488-8178-94dafe9b552c
Aug 2 21:31:56 submit26-clnb9 setroubleshoot[1704279]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 81cb3698-78f8-440a-8e3c-e5d1041e6b78 [x2]
Aug 2 21:31:56 submit26-clnb9 setroubleshoot[1704279]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 792b472a-115c-4799-9805-fc7436f916b9
Aug 2 21:31:56 submit26-clnb9 setroubleshoot[1704279]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 15c83a86-837b-41e2-b662-b39cd4e361cb [x2]
Aug 2 21:31:57 submit26-clnb9 setroubleshoot[1704279]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.K9ARFo. For complete SELinux messages run: sealert -l 62b3782e-4730-4488-8178-94dafe9b552c
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.4881s
Status : exited 0
Output :
Syslog digest — 2026-08-02 21:05 EDT
Processed 4,005 lines, filtered 3,218 (80%). 787 unknown (83 distinct) from 20 host(s).
== abuse (1 distinct, 348 total) ==
Aug 2 20:05:06 abuse rsyslogd[21745]: imjournal: open() failed for path: '/var/lib/rsyslog/imjournal.state.tmp': Input/output error [v8.2404.0 try https://www.rsyslog.com/e/2433 ] [x348]
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Aug 2 20:42:33 b0b02.cs.umd.edu rustdesk[2245756]: cannot open display:
== cheezit.cs.umd.edu (11 distinct, 24 total) ==
Aug 2 20:14:16 cheezit.cs.umd.edu sshd-session[401060]: pam_access(sshd:auth): access denied for user `admin' from `171.231.198.232' [x4]
Aug 2 20:14:17 cheezit.cs.umd.edu krb5_child[401064]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x6]
Aug 2 20:14:17 cheezit.cs.umd.edu sshd-session[401046]: error: PAM: System error for admin from 171.231.198.232 [x4]
Aug 2 20:17:18 cheezit.cs.umd.edu sshd-session[401944]: pam_access(sshd:auth): access denied for user `root' from `171.231.198.232'
Aug 2 20:17:22 cheezit.cs.umd.edu sshd-session[401930]: error: PAM: Authentication failure for root from 171.231.198.232
Aug 2 20:32:42 cheezit.cs.umd.edu sshd-session[405939]: pam_access(sshd:auth): access denied for user `admin' from `171.231.180.28' [x2]
Aug 2 20:32:45 cheezit.cs.umd.edu sshd-session[405879]: error: PAM: System error for admin from 171.231.180.28 [x2]
Aug 2 20:40:55 cheezit.cs.umd.edu sshd-session[407919]: pam_access(sshd:auth): access denied for user `operator' from `171.231.198.232'
Aug 2 20:40:55 cheezit.cs.umd.edu sshd-session[407920]: pam_access(sshd:auth): access denied for user `ftp' from `171.231.180.28'
Aug 2 20:40:56 cheezit.cs.umd.edu sshd-session[407889]: error: PAM: Authentication failure for operator from 171.231.198.232
Aug 2 20:40:56 cheezit.cs.umd.edu sshd-session[407878]: error: PAM: Authentication failure for ftp from 171.231.180.28
== contest (1 distinct, 34 total) ==
Aug 2 20:05:23 contest goferd[1007]: [ERROR][worker-0] gofer.messaging.adapter.connect:33 - connect: proton+amqps://satellite8.cs.umd.edu:5647, failed: Connection amqps://satellite8.cs.umd.edu:5647 disconnected: Condition('proton.pythonio', 'Connection refused to all addresses') [x34]
== csfw00a (1 distinct, 230 total) ==
Aug 2 20:05:00 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x230]
== dojo (2 distinct, 2 total) ==
Aug 2 20:13:09 dojo sshd[937225]: error: PAM: Authentication failure for root from 171.231.198.232
Aug 2 20:16:25 dojo sshd[937584]: error: PAM: Authentication failure for root from 171.231.180.28
== hackerman (6 distinct, 11 total) ==
Aug 2 20:20:04 hackerman gnome-software[2060381]: can't reliably fixup error code 4 in domain g-io-error-quark: Not a directory [x4]
Aug 2 20:20:12 hackerman gnome-software[2060381]: Only 0 apps for recent list, hiding
Aug 2 20:20:28 hackerman gnome-software[2060381]: failed to commit changes to dconf: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dfile_2derror_2dquark.Code2: Failed to create file “/adminhomes/sajith/.config/dconf/user.8WDET3”: Permission denied
Aug 2 20:20:28 hackerman packagekitd[3246987]: Failed to get cache filename for libreoffice [x2]
Aug 2 20:20:28 hackerman packagekitd[3246987]: Failed to get cache filename for kernel [x2]
Aug 2 20:20:38 hackerman packagekitd[3246987]: failed to parse public key for /etc/pki/rpm-gpg/RPM-GPG-KEY-PQC-redhat-release
== idm00 (1 distinct, 1 total) ==
Aug 2 20:51:14 idm00 named[1455]: client @0x7f33153cee88 10.73.240.42#61991: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Aug 2 20:36:01 idmp0 named[5198]: client @0x7f991403c8e8 10.73.240.43#62355: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 28 total) ==
Aug 2 20:12:50 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x28]
== krispykreme.cs.umd.edu (2 distinct, 2 total) ==
Aug 2 20:30:15 krispykreme.cs.umd.edu sshd-session[2541217]: pam_access(sshd:auth): access denied for user `root' from `193.24.211.204'
Aug 2 20:30:18 krispykreme.cs.umd.edu sshd-session[2541215]: error: PAM: Authentication failure for root from 193.24.211.204
== netman.cs.umd.edu (3 distinct, 3 total) ==
Aug 2 20:30:01 netman.cs.umd.edu setroubleshoot[41122]: SELinux is preventing /usr/bin/gpg from read access on the file gpg.conf. For complete SELinux messages run: sealert -l 019ad1da-a874-4814-8037-3b3e5f413ad2
Aug 2 20:30:02 netman.cs.umd.edu setroubleshoot[41122]: SELinux is preventing /usr/bin/gpg from open access on the file /root/.gnupg/gpg.conf. For complete SELinux messages run: sealert -l cb54177e-d44c-46a1-b246-5c0bbb8343be
Aug 2 20:30:02 netman.cs.umd.edu setroubleshoot[41122]: SELinux is preventing /usr/bin/gpg from getattr access on the file /root/.gnupg/gpg.conf. For complete SELinux messages run: sealert -l fbba2e30-b7ab-491c-9ec6-f553e9ef72af
== newhonors2 (1 distinct, 24 total) ==
Aug 2 20:13:03 newhonors2 dhcpcd[649070]: dhcpcd is not running [x24]
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Aug 2 20:09:09 outbound00.cs.umd.edu python3[2253973]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Aug 2 20:13:06 outbound01.cs.umd.edu python3[286649]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Aug 2 20:14:03 sentry-docker00.cs.umd.edu systemd-udevd[601441]: link_config: could not get ethtool features for vethcd860a6
Aug 2 20:14:03 sentry-docker00.cs.umd.edu systemd-udevd[601441]: Could not set offload features of vethcd860a6: No such device
Aug 2 20:14:03 sentry-docker00.cs.umd.edu systemd-udevd[601470]: Could not generate persistent MAC address for vethe930b40: No such file or directory
Aug 2 20:14:03 sentry-docker00.cs.umd.edu systemd-udevd[601471]: Could not generate persistent MAC address for veth05a0e10: No such file or directory
Aug 2 20:14:03 sentry-docker00.cs.umd.edu systemd-udevd[601474]: Could not generate persistent MAC address for veth3cb1e64: No such file or directory
Aug 2 20:14:03 sentry-docker00.cs.umd.edu systemd-udevd[601475]: Could not generate persistent MAC address for veth1080fba: No such file or directory
Aug 2 20:14:03 sentry-docker00.cs.umd.edu systemd-udevd[601474]: Could not generate persistent MAC address for vethb748c8a: No such file or directory
Aug 2 20:14:03 sentry-docker00.cs.umd.edu systemd-udevd[601490]: Could not generate persistent MAC address for veth2ba9cb4: No such file or directory
Aug 2 20:14:03 sentry-docker00.cs.umd.edu systemd-udevd[601474]: Could not generate persistent MAC address for vethc7272e2: No such file or directory
Aug 2 20:14:03 sentry-docker00.cs.umd.edu systemd-udevd[601490]: Could not generate persistent MAC address for vetha4ae3a9: No such file or directory
Aug 2 20:16:01 sentry-docker00.cs.umd.edu systemd-udevd[602683]: Could not generate persistent MAC address for veth4cb59f4: No such file or directory
Aug 2 20:16:01 sentry-docker00.cs.umd.edu systemd-udevd[602684]: Could not generate persistent MAC address for veth19f96ae: No such file or directory
Aug 2 20:34:11 sentry-docker00.cs.umd.edu systemd-udevd[610825]: link_config: could not get ethtool features for veth3cb1e64
Aug 2 20:34:11 sentry-docker00.cs.umd.edu systemd-udevd[610825]: Could not set offload features of veth3cb1e64: No such device
Aug 2 20:34:11 sentry-docker00.cs.umd.edu systemd-udevd[610894]: link_config: could not get ethtool features for vethe930b40
Aug 2 20:34:11 sentry-docker00.cs.umd.edu systemd-udevd[610894]: Could not set offload features of vethe930b40: No such device
Aug 2 20:34:11 sentry-docker00.cs.umd.edu systemd-udevd[610913]: Could not generate persistent MAC address for veth43f8bc5: No such file or directory
Aug 2 20:34:11 sentry-docker00.cs.umd.edu systemd-udevd[610914]: Could not generate persistent MAC address for vethf2efbc8: No such file or directory
Aug 2 20:34:11 sentry-docker00.cs.umd.edu systemd-udevd[610925]: Could not generate persistent MAC address for vethe4fff99: No such file or directory
Aug 2 20:34:11 sentry-docker00.cs.umd.edu systemd-udevd[610927]: Could not generate persistent MAC address for vetha0aef91: No such file or directory
Aug 2 20:34:11 sentry-docker00.cs.umd.edu systemd-udevd[610936]: Could not generate persistent MAC address for veth70fc2c1: No such file or directory
Aug 2 20:34:11 sentry-docker00.cs.umd.edu systemd-udevd[610934]: Could not generate persistent MAC address for veth877f530: No such file or directory
Aug 2 20:34:11 sentry-docker00.cs.umd.edu systemd-udevd[610970]: Could not generate persistent MAC address for vethfb36e85: No such file or directory
Aug 2 20:34:11 sentry-docker00.cs.umd.edu systemd-udevd[610971]: Could not generate persistent MAC address for veth2f3f4b6: No such file or directory
Aug 2 20:36:06 sentry-docker00.cs.umd.edu systemd-udevd[612110]: Could not generate persistent MAC address for vethed7b841: No such file or directory
Aug 2 20:36:06 sentry-docker00.cs.umd.edu systemd-udevd[612111]: Could not generate persistent MAC address for veth94ea943: No such file or directory
Aug 2 20:54:19 sentry-docker00.cs.umd.edu systemd-udevd[620362]: Could not generate persistent MAC address for veth6038891: No such file or directory
Aug 2 20:54:19 sentry-docker00.cs.umd.edu systemd-udevd[620363]: Could not generate persistent MAC address for veth74a6430: No such file or directory
Aug 2 20:54:19 sentry-docker00.cs.umd.edu systemd-udevd[620408]: Could not generate persistent MAC address for veth96a115c: No such file or directory
Aug 2 20:54:19 sentry-docker00.cs.umd.edu systemd-udevd[620407]: Could not generate persistent MAC address for vethaf8fb45: No such file or directory
... 6 more distinct messages not shown
== soul (1 distinct, 6 total) ==
Aug 2 20:22:26 soul krb5_child[3260923]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x6]
== strawberry (2 distinct, 8 total) ==
Aug 2 20:09:44 strawberry udisksd[1067]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/ST2000DM001_1CH164_W1E8J5KJ: Error updating SMART data: Error sending ATA command CHECK POWER MODE: Unexpected sense data returned:#0120000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................#0120010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................#012 (g-io-error-quark, 0) [x6]
Aug 2 20:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-4 (9 distinct, 9 total) ==
Aug 2 20:15:28 submit26-b9-4 setroubleshoot[897183]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l a4e66030-8621-4da9-bd27-5988bb1bf8ad
Aug 2 20:15:28 submit26-b9-4 setroubleshoot[897183]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l c055e37d-bbf5-4800-9083-d606f792c8c1
Aug 2 20:15:28 submit26-b9-4 setroubleshoot[897183]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l e5bc3a56-6d6f-4776-954f-ddde1579648f
Aug 2 20:15:28 submit26-b9-4 setroubleshoot[897183]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.JCkt5Q/repodata/repomd.xml. For complete SELinux messages run: sealert -l a8ec5e1b-49f9-4fbc-a8ae-22e800f7abf2
Aug 2 20:15:28 submit26-b9-4 setroubleshoot[897183]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 945db714-d0c0-4402-911e-932978b8b036
Aug 2 20:15:28 submit26-b9-4 setroubleshoot[897183]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.JCkt5Q. For complete SELinux messages run: sealert -l 463998a0-fb0d-463c-82b1-471135710a14
Aug 2 20:15:28 submit26-b9-4 setroubleshoot[897183]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 473d2e21-15d8-407a-a9ee-2b842607fa00
Aug 2 20:15:28 submit26-b9-4 setroubleshoot[897183]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 80c54d4f-bf4b-4501-addb-1627383587d0
Aug 2 20:15:28 submit26-b9-4 setroubleshoot[897183]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l c63d3890-151e-49a0-83f0-3dfb69d051e5
== teaching-awards (1 distinct, 7 total) ==
Aug 2 20:16:30 teaching-awards krb5_child[1778885]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x7]
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.4883s
Status : exited 0
Output :
Syslog digest — 2026-08-02 20:05 EDT
Processed 4,060 lines, filtered 3,228 (79%). 832 unknown (73 distinct) from 18 host(s).
== abuse (1 distinct, 349 total) ==
Aug 2 19:05:06 abuse rsyslogd[21745]: imjournal: open() failed for path: '/var/lib/rsyslog/imjournal.state.tmp': Input/output error [v8.2404.0 try https://www.rsyslog.com/e/2433 ] [x349]
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Aug 2 19:42:30 b0b02.cs.umd.edu rustdesk[2230543]: cannot open display:
== cheezit.cs.umd.edu (5 distinct, 5 total) ==
Aug 2 19:52:06 cheezit.cs.umd.edu sshd-session[395871]: pam_access(sshd:auth): access denied for user `admin' from `171.231.198.232'
Aug 2 19:52:07 cheezit.cs.umd.edu krb5_child[395873]: Client 'admin(a)UMD.EDU' not found in Kerberos database
Aug 2 19:52:07 cheezit.cs.umd.edu sshd-session[395869]: error: PAM: System error for admin from 171.231.198.232
Aug 2 19:56:39 cheezit.cs.umd.edu sshd-session[397557]: pam_access(sshd:auth): access denied for user `root' from `171.231.198.232'
Aug 2 19:56:41 cheezit.cs.umd.edu sshd-session[397554]: error: PAM: Authentication failure for root from 171.231.198.232
== contest (1 distinct, 33 total) ==
Aug 2 19:06:28 contest goferd[1007]: [ERROR][worker-0] gofer.messaging.adapter.connect:33 - connect: proton+amqps://satellite8.cs.umd.edu:5647, failed: Connection amqps://satellite8.cs.umd.edu:5647 disconnected: Condition('proton.pythonio', 'Connection refused to all addresses') [x33]
== csfw00a (2 distinct, 248 total) ==
Aug 2 19:04:47 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x236]
Aug 2 19:29:38 csfw00a ospf6d[1477]: [EC 100663307] Could not send entire message [x12]
== dojo (1 distinct, 1 total) ==
Aug 2 19:55:11 dojo sshd[936340]: error: PAM: Authentication failure for root from 171.231.180.28
== hackerman (7 distinct, 12 total) ==
Aug 2 19:19:01 hackerman gnome-software[2060381]: failed to commit changes to dconf: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dfile_2derror_2dquark.Code2: Failed to create file “/adminhomes/sajith/.config/dconf/user.1I0YS3”: Permission denied
Aug 2 19:20:04 hackerman gnome-software[2060381]: can't reliably fixup error code 4 in domain g-io-error-quark: Not a directory [x4]
Aug 2 19:20:12 hackerman gnome-software[2060381]: Only 0 apps for recent list, hiding
Aug 2 19:20:28 hackerman gnome-software[2060381]: failed to commit changes to dconf: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dfile_2derror_2dquark.Code2: Failed to create file “/adminhomes/sajith/.config/dconf/user.0HDWS3”: Permission denied
Aug 2 19:20:28 hackerman packagekitd[3234057]: Failed to get cache filename for libreoffice [x2]
Aug 2 19:20:28 hackerman packagekitd[3234057]: Failed to get cache filename for kernel [x2]
Aug 2 19:20:37 hackerman packagekitd[3234057]: failed to parse public key for /etc/pki/rpm-gpg/RPM-GPG-KEY-PQC-redhat-release
== hazfs.cs.umd.edu (11 distinct, 66 total) ==
Aug 2 19:52:49 hazfs.cs.umd.edu snmpd[1431]: send response: Failure in sendto [x6]
Aug 2 19:52:49 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userweb" [x6]
Aug 2 19:52:49 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."zfslist" [x6]
Aug 2 19:52:49 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userhome" [x6]
Aug 2 19:52:49 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userweb" [x6]
Aug 2 19:52:49 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."zfslist" [x6]
Aug 2 19:52:49 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userhome" [x6]
Aug 2 19:52:49 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userweb" [x6]
Aug 2 19:52:49 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."zfslist" [x6]
Aug 2 19:52:49 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userhome" [x6]
Aug 2 19:52:49 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutNumLines."userweb" [x6]
== idm00 (1 distinct, 1 total) ==
Aug 2 19:51:14 idm00 named[1455]: client @0x7f33153cee88 10.73.240.42#61004: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Aug 2 19:36:01 idmp0 named[5198]: client @0x7f99145a70c8 10.73.240.43#64678: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 35 total) ==
Aug 2 19:08:02 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x35]
== newhonors2 (1 distinct, 24 total) ==
Aug 2 19:13:02 newhonors2 dhcpcd[647227]: dhcpcd is not running [x24]
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Aug 2 19:09:08 outbound00.cs.umd.edu python3[2240172]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Aug 2 19:13:06 outbound01.cs.umd.edu python3[272829]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (34 distinct, 34 total) ==
Aug 2 19:13:38 sentry-docker00.cs.umd.edu systemd-udevd[573177]: Could not generate persistent MAC address for vethb17d868: No such file or directory
Aug 2 19:13:38 sentry-docker00.cs.umd.edu systemd-udevd[573178]: Could not generate persistent MAC address for veth891926b: No such file or directory
Aug 2 19:13:38 sentry-docker00.cs.umd.edu systemd-udevd[573196]: Could not generate persistent MAC address for vethca2d120: No such file or directory
Aug 2 19:13:38 sentry-docker00.cs.umd.edu systemd-udevd[573181]: Could not generate persistent MAC address for veth9696fb4: No such file or directory
Aug 2 19:13:38 sentry-docker00.cs.umd.edu systemd-udevd[573191]: Could not generate persistent MAC address for veth02ea539: No such file or directory
Aug 2 19:13:38 sentry-docker00.cs.umd.edu systemd-udevd[573186]: Could not generate persistent MAC address for vethb24fe3e: No such file or directory
Aug 2 19:13:38 sentry-docker00.cs.umd.edu systemd-udevd[573186]: Could not generate persistent MAC address for veth7c5a7e2: No such file or directory
Aug 2 19:13:38 sentry-docker00.cs.umd.edu systemd-udevd[573191]: Could not generate persistent MAC address for vethf71af8f: No such file or directory
Aug 2 19:15:45 sentry-docker00.cs.umd.edu systemd-udevd[574435]: Could not generate persistent MAC address for veth464db77: No such file or directory
Aug 2 19:15:45 sentry-docker00.cs.umd.edu systemd-udevd[574436]: Could not generate persistent MAC address for veth6bff3eb: No such file or directory
Aug 2 19:33:46 sentry-docker00.cs.umd.edu systemd-udevd[582554]: link_config: could not get ethtool features for vethb17d868
Aug 2 19:33:46 sentry-docker00.cs.umd.edu systemd-udevd[582554]: Could not set offload features of vethb17d868: No such device
Aug 2 19:33:46 sentry-docker00.cs.umd.edu systemd-udevd[582584]: Could not generate persistent MAC address for veth4add0e2: No such file or directory
Aug 2 19:33:46 sentry-docker00.cs.umd.edu systemd-udevd[582585]: Could not generate persistent MAC address for vethc1e6e73: No such file or directory
Aug 2 19:33:46 sentry-docker00.cs.umd.edu systemd-udevd[582588]: Could not generate persistent MAC address for vethe82475f: No such file or directory
Aug 2 19:33:46 sentry-docker00.cs.umd.edu systemd-udevd[582589]: Could not generate persistent MAC address for veth5b305d9: No such file or directory
Aug 2 19:33:46 sentry-docker00.cs.umd.edu systemd-udevd[582612]: Could not generate persistent MAC address for veth2ec2c70: No such file or directory
Aug 2 19:33:46 sentry-docker00.cs.umd.edu systemd-udevd[582613]: Could not generate persistent MAC address for veth5f3cfe7: No such file or directory
Aug 2 19:33:46 sentry-docker00.cs.umd.edu systemd-udevd[582622]: Could not generate persistent MAC address for vethb2aceaf: No such file or directory
Aug 2 19:33:46 sentry-docker00.cs.umd.edu systemd-udevd[582623]: Could not generate persistent MAC address for veth208c732: No such file or directory
Aug 2 19:35:53 sentry-docker00.cs.umd.edu systemd-udevd[583812]: Could not generate persistent MAC address for vetha5138c7: No such file or directory
Aug 2 19:35:53 sentry-docker00.cs.umd.edu systemd-udevd[583813]: Could not generate persistent MAC address for veth6128784: No such file or directory
Aug 2 19:53:54 sentry-docker00.cs.umd.edu systemd-udevd[592003]: link_config: could not get ethtool features for vethe82475f
Aug 2 19:53:54 sentry-docker00.cs.umd.edu systemd-udevd[592003]: Could not set offload features of vethe82475f: No such device
Aug 2 19:53:54 sentry-docker00.cs.umd.edu systemd-udevd[592032]: Could not generate persistent MAC address for vethcd860a6: No such file or directory
Aug 2 19:53:54 sentry-docker00.cs.umd.edu systemd-udevd[592033]: Could not generate persistent MAC address for vethabeb712: No such file or directory
Aug 2 19:53:54 sentry-docker00.cs.umd.edu systemd-udevd[592037]: Could not generate persistent MAC address for veth1745637: No such file or directory
Aug 2 19:53:54 sentry-docker00.cs.umd.edu systemd-udevd[592036]: Could not generate persistent MAC address for vethe29c807: No such file or directory
Aug 2 19:53:54 sentry-docker00.cs.umd.edu systemd-udevd[592047]: Could not generate persistent MAC address for veth2715359: No such file or directory
Aug 2 19:53:54 sentry-docker00.cs.umd.edu systemd-udevd[592050]: Could not generate persistent MAC address for veth40e4114: No such file or directory
... 4 more distinct messages not shown
== soul (1 distinct, 1 total) ==
Aug 2 19:52:18 soul krb5_child[3257013]: Client 'admin(a)UMD.EDU' not found in Kerberos database
== strawberry (2 distinct, 8 total) ==
Aug 2 19:09:44 strawberry udisksd[1067]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/ST2000DM001_1CH164_W1E8J5KJ: Error updating SMART data: Error sending ATA command CHECK POWER MODE: Unexpected sense data returned:#0120000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................#0120010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................#012 (g-io-error-quark, 0) [x6]
Aug 2 19:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== teaching-awards (1 distinct, 1 total) ==
Aug 2 19:54:47 teaching-awards krb5_child[1778141]: Client 'admin(a)UMD.EDU' not found in Kerberos database
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.4900s
Status : exited 0
Output :
Syslog digest — 2026-08-02 19:05 EDT
Processed 4,285 lines, filtered 3,502 (81%). 783 unknown (67 distinct) from 17 host(s).
== abuse (1 distinct, 346 total) ==
Aug 2 18:05:06 abuse rsyslogd[21745]: imjournal: open() failed for path: '/var/lib/rsyslog/imjournal.state.tmp': Input/output error [v8.2404.0 try https://www.rsyslog.com/e/2433 ] [x346]
== b0b02.cs.umd.edu (4 distinct, 4 total) ==
Aug 2 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-08-02T22:10:59.390893641Z" level=info msg="PurgeUploads starting: olderThan=2026-07-26 22:10:59.390810567 +0000 UTC m=-84179.849261135, actuallyDelete=true"
Aug 2 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-08-02T22:10:59.391332701Z" level=info msg="Purge uploads finished. Num deleted=0, num errors=1"
Aug 2 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-08-02T22:10:59.39135282Z" level=info msg="Starting upload purge in 24h0m0s" go.version=go1.11.2 instance.id=68469aa4-7857-4a69-bf12-c2190b4f96d8 service=registry version=v2.7.1
Aug 2 18:42:26 b0b02.cs.umd.edu rustdesk[2215435]: cannot open display:
== contest (1 distinct, 34 total) ==
Aug 2 18:05:47 contest goferd[1007]: [ERROR][worker-0] gofer.messaging.adapter.connect:33 - connect: proton+amqps://satellite8.cs.umd.edu:5647, failed: Connection amqps://satellite8.cs.umd.edu:5647 disconnected: Condition('proton.pythonio', 'Connection refused to all addresses') [x34]
== csfw00a (2 distinct, 264 total) ==
Aug 2 18:04:28 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x256]
Aug 2 18:56:33 csfw00a ospf6d[1477]: [EC 100663307] Could not send entire message [x8]
== hackerman (6 distinct, 11 total) ==
Aug 2 18:20:04 hackerman gnome-software[2060381]: can't reliably fixup error code 4 in domain g-io-error-quark: Not a directory [x4]
Aug 2 18:20:12 hackerman gnome-software[2060381]: Only 0 apps for recent list, hiding
Aug 2 18:20:27 hackerman gnome-software[2060381]: failed to commit changes to dconf: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dfile_2derror_2dquark.Code2: Failed to create file “/adminhomes/sajith/.config/dconf/user.HS4ZS3”: Permission denied
Aug 2 18:20:28 hackerman packagekitd[3221173]: Failed to get cache filename for libreoffice [x2]
Aug 2 18:20:28 hackerman packagekitd[3221173]: Failed to get cache filename for kernel [x2]
Aug 2 18:20:37 hackerman packagekitd[3221173]: failed to parse public key for /etc/pki/rpm-gpg/RPM-GPG-KEY-PQC-redhat-release
== idm00 (1 distinct, 1 total) ==
Aug 2 18:51:14 idm00 named[1455]: client @0x7f330c465cd8 10.73.240.42#53367: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Aug 2 18:36:01 idmp0 named[5198]: client @0x7f98fc03bf48 10.73.240.43#57144: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 29 total) ==
Aug 2 18:08:08 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x29]
== krispykreme.cs.umd.edu (3 distinct, 3 total) ==
Aug 2 18:50:52 krispykreme.cs.umd.edu sshd-session[2512561]: pam_access(sshd:auth): access denied for user `admin' from `193.24.211.204'
Aug 2 18:50:52 krispykreme.cs.umd.edu krb5_child[2512563]: Client 'admin(a)UMD.EDU' not found in Kerberos database
Aug 2 18:50:52 krispykreme.cs.umd.edu sshd-session[2512559]: error: PAM: System error for admin from 193.24.211.204
== newhonors2 (1 distinct, 24 total) ==
Aug 2 18:13:03 newhonors2 dhcpcd[645383]: dhcpcd is not running [x24]
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Aug 2 18:09:08 outbound00.cs.umd.edu python3[2226183]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Aug 2 18:13:06 outbound01.cs.umd.edu python3[259004]: ldapdb [x6]
== peach.cs.umd.edu (2 distinct, 2 total) ==
Aug 2 18:32:10 peach.cs.umd.edu setroubleshoot[664906]: SELinux is preventing /usr/bin/qemu-ga from search access on the directory /var/lib/containers/storage/overlay. For complete SELinux messages run: sealert -l 007f2494-1b82-4ff6-bd59-5f449ab9de99
Aug 2 18:32:10 peach.cs.umd.edu setroubleshoot[664906]: SELinux is preventing /usr/bin/qemu-ga from search access on the directory /var/lib/containers/storage/overlay. For complete SELinux messages run: sealert -l a801d9aa-5cee-4f5c-b9a9-bd22e572596b
== sentry-docker00.cs.umd.edu (38 distinct, 38 total) ==
Aug 2 18:13:13 sentry-docker00.cs.umd.edu systemd-udevd[544664]: link_config: could not get ethtool features for veth8690fc4
Aug 2 18:13:13 sentry-docker00.cs.umd.edu systemd-udevd[544664]: Could not set offload features of veth8690fc4: No such device
Aug 2 18:13:13 sentry-docker00.cs.umd.edu systemd-udevd[544716]: Could not generate persistent MAC address for veth9b524fa: No such file or directory
Aug 2 18:13:13 sentry-docker00.cs.umd.edu systemd-udevd[544717]: Could not generate persistent MAC address for vetha51a357: No such file or directory
Aug 2 18:13:13 sentry-docker00.cs.umd.edu systemd-udevd[544720]: Could not generate persistent MAC address for vethb0c9f94: No such file or directory
Aug 2 18:13:13 sentry-docker00.cs.umd.edu systemd-udevd[544721]: Could not generate persistent MAC address for veth3da3606: No such file or directory
Aug 2 18:13:13 sentry-docker00.cs.umd.edu systemd-udevd[544743]: Could not generate persistent MAC address for vethe1b12d6: No such file or directory
Aug 2 18:13:13 sentry-docker00.cs.umd.edu systemd-udevd[544723]: Could not generate persistent MAC address for veth68d71be: No such file or directory
Aug 2 18:13:13 sentry-docker00.cs.umd.edu systemd-udevd[544746]: Could not generate persistent MAC address for veth5a70248: No such file or directory
Aug 2 18:13:13 sentry-docker00.cs.umd.edu systemd-udevd[544747]: Could not generate persistent MAC address for vethe1c7aa8: No such file or directory
Aug 2 18:15:24 sentry-docker00.cs.umd.edu systemd-udevd[545778]: Could not generate persistent MAC address for vethee51029: No such file or directory
Aug 2 18:15:24 sentry-docker00.cs.umd.edu systemd-udevd[545779]: Could not generate persistent MAC address for veth1b27276: No such file or directory
Aug 2 18:33:21 sentry-docker00.cs.umd.edu systemd-udevd[554143]: link_config: could not get ethtool features for vethb0c9f94
Aug 2 18:33:21 sentry-docker00.cs.umd.edu systemd-udevd[554143]: Could not set offload features of vethb0c9f94: No such device
Aug 2 18:33:21 sentry-docker00.cs.umd.edu systemd-udevd[554174]: Could not generate persistent MAC address for veth992c3b7: No such file or directory
Aug 2 18:33:21 sentry-docker00.cs.umd.edu systemd-udevd[554175]: Could not generate persistent MAC address for veth6bfacb0: No such file or directory
Aug 2 18:33:21 sentry-docker00.cs.umd.edu systemd-udevd[554178]: Could not generate persistent MAC address for veth7aa16e1: No such file or directory
Aug 2 18:33:21 sentry-docker00.cs.umd.edu systemd-udevd[554179]: Could not generate persistent MAC address for veth38809b6: No such file or directory
Aug 2 18:33:21 sentry-docker00.cs.umd.edu systemd-udevd[554182]: Could not generate persistent MAC address for vethe068bf0: No such file or directory
Aug 2 18:33:21 sentry-docker00.cs.umd.edu systemd-udevd[554186]: Could not generate persistent MAC address for vethf15d3f0: No such file or directory
Aug 2 18:33:21 sentry-docker00.cs.umd.edu systemd-udevd[554206]: Could not generate persistent MAC address for veth2baa684: No such file or directory
Aug 2 18:33:21 sentry-docker00.cs.umd.edu systemd-udevd[554208]: Could not generate persistent MAC address for vethd0be7d6: No such file or directory
Aug 2 18:35:32 sentry-docker00.cs.umd.edu systemd-udevd[555465]: link_config: could not get ethtool features for vethee51029
Aug 2 18:35:32 sentry-docker00.cs.umd.edu systemd-udevd[555465]: Could not set offload features of vethee51029: No such device
Aug 2 18:35:32 sentry-docker00.cs.umd.edu systemd-udevd[555481]: Could not generate persistent MAC address for veth1d9787d: No such file or directory
Aug 2 18:35:32 sentry-docker00.cs.umd.edu systemd-udevd[555482]: Could not generate persistent MAC address for veth188f804: No such file or directory
Aug 2 18:53:29 sentry-docker00.cs.umd.edu systemd-udevd[563646]: Could not generate persistent MAC address for veth145efc6: No such file or directory
Aug 2 18:53:29 sentry-docker00.cs.umd.edu systemd-udevd[563647]: Could not generate persistent MAC address for veth5992843: No such file or directory
Aug 2 18:53:29 sentry-docker00.cs.umd.edu systemd-udevd[563681]: Could not generate persistent MAC address for vethacf5012: No such file or directory
Aug 2 18:53:29 sentry-docker00.cs.umd.edu systemd-udevd[563682]: Could not generate persistent MAC address for vethc7d8d30: No such file or directory
... 8 more distinct messages not shown
== strawberry (2 distinct, 8 total) ==
Aug 2 18:09:44 strawberry udisksd[1067]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/ST2000DM001_1CH164_W1E8J5KJ: Error updating SMART data: Error sending ATA command CHECK POWER MODE: Unexpected sense data returned:#0120000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................#0120010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................#012 (g-io-error-quark, 0) [x6]
Aug 2 18:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-2 (1 distinct, 2 total) ==
Aug 2 18:05:06 submit26-b9-2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x2]
== submit26-b9-4 (1 distinct, 4 total) ==
Aug 2 18:05:04 submit26-b9-4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x4]
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 0.5014s
Status : exited 0
Output :
Syslog digest — 2026-08-02 18:05 EDT
Processed 4,299 lines, filtered 3,470 (80%). 829 unknown (97 distinct) from 21 host(s).
== abuse (1 distinct, 347 total) ==
Aug 2 17:05:06 abuse rsyslogd[21745]: imjournal: open() failed for path: '/var/lib/rsyslog/imjournal.state.tmp': Input/output error [v8.2404.0 try https://www.rsyslog.com/e/2433 ] [x347]
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Aug 2 17:42:23 b0b02.cs.umd.edu rustdesk[2200365]: cannot open display:
== cheezit.cs.umd.edu (1 distinct, 1 total) ==
Aug 2 17:28:02 cheezit.cs.umd.edu sshd-session[362206]: error: send_error: write: Broken pipe
== contest (9 distinct, 44 total) ==
Aug 2 17:05:05 contest goferd[1007]: [ERROR][worker-0] gofer.messaging.adapter.connect:33 - connect: proton+amqps://satellite8.cs.umd.edu:5647, failed: Connection amqps://satellite8.cs.umd.edu:5647 disconnected: Condition('proton.pythonio', 'Connection refused to all addresses') [x34]
Aug 2 17:48:17 contest setroubleshoot[517639]: SELinux is preventing /usr/libexec/platform-python3.6 from create access on the directory libdnf.ApNGSS. For complete SELinux messages run: sealert -l cb6b25c6-4765-4cf2-88a0-9b3b508e94e9
Aug 2 17:48:17 contest setroubleshoot[517639]: SELinux is preventing /usr/bin/gpgconf from add_name access on the directory repodata. For complete SELinux messages run: sealert -l 41cf7b1b-0f34-4609-98f2-b66e7825fef7
Aug 2 17:48:17 contest setroubleshoot[517639]: SELinux is preventing /usr/libexec/platform-python3.6 from create access on the file mirrorlist. For complete SELinux messages run: sealert -l fc20ff92-ea83-4f38-a24b-ddfd737a3141
Aug 2 17:48:17 contest setroubleshoot[517639]: SELinux is preventing /usr/libexec/platform-python3.6 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l ac675631-fa35-4e93-adc9-b692b18e53e5 [x2]
Aug 2 17:48:17 contest setroubleshoot[517639]: SELinux is preventing /usr/libexec/platform-python3.6 from create access on the file repomd.xml.asc. For complete SELinux messages run: sealert -l fc20ff92-ea83-4f38-a24b-ddfd737a3141
Aug 2 17:48:17 contest setroubleshoot[517639]: SELinux is preventing /usr/libexec/platform-python3.6 from read access on the directory libdnf.ApNGSS. For complete SELinux messages run: sealert -l 45d103b6-0810-4890-a705-990118577ce8
Aug 2 17:48:18 contest setroubleshoot[517639]: SELinux is preventing /usr/libexec/platform-python3.6 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 7e499113-2fd7-4f67-bec6-3521efbe3637 [x2]
Aug 2 17:48:20 contest setroubleshoot[517639]: SELinux is preventing /usr/libexec/platform-python3.6 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 3928930b-a1ed-448d-950b-0665ac2adef8
== csfw00a (2 distinct, 276 total) ==
Aug 2 17:04:30 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x268]
Aug 2 17:42:20 csfw00a ospf6d[1477]: [EC 100663307] Could not send entire message [x8]
== frabjous (1 distinct, 2 total) ==
Aug 2 17:39:19 frabjous sshd-session[2752179]: error: Protocol major versions differ: 2 vs. 1 [x2]
== frozone (1 distinct, 1 total) ==
Aug 2 17:34:47 frozone systemd-tmpfiles[1266243]: Failed to remove "/var/tmp/test.log", ignoring: Operation not permitted
== hackerman (7 distinct, 12 total) ==
Aug 2 17:19:01 hackerman gnome-software[2060381]: failed to commit changes to dconf: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dfile_2derror_2dquark.Code2: Failed to create file “/adminhomes/sajith/.config/dconf/user.G7ZZS3”: Permission denied
Aug 2 17:20:04 hackerman gnome-software[2060381]: can't reliably fixup error code 4 in domain g-io-error-quark: Not a directory [x4]
Aug 2 17:20:12 hackerman gnome-software[2060381]: Only 0 apps for recent list, hiding
Aug 2 17:20:28 hackerman gnome-software[2060381]: failed to commit changes to dconf: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dfile_2derror_2dquark.Code2: Failed to create file “/adminhomes/sajith/.config/dconf/user.BGYBT3”: Permission denied
Aug 2 17:20:28 hackerman packagekitd[3207782]: Failed to get cache filename for libreoffice [x2]
Aug 2 17:20:28 hackerman packagekitd[3207782]: Failed to get cache filename for kernel [x2]
Aug 2 17:20:38 hackerman packagekitd[3207782]: failed to parse public key for /etc/pki/rpm-gpg/RPM-GPG-KEY-PQC-redhat-release
== idm00 (1 distinct, 1 total) ==
Aug 2 17:51:14 idm00 named[1455]: client @0x7f3310548a48 10.73.240.42#52743: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Aug 2 17:36:00 idmp0 named[5198]: client @0x7f99000dfeb8 10.73.240.43#52277: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 25 total) ==
Aug 2 17:07:52 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x25]
== newhonors2 (1 distinct, 24 total) ==
Aug 2 17:13:03 newhonors2 dhcpcd[643539]: dhcpcd is not running [x24]
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Aug 2 17:09:09 outbound00.cs.umd.edu python3[2212384]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Aug 2 17:13:07 outbound01.cs.umd.edu python3[244957]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Aug 2 17:12:48 sentry-docker00.cs.umd.edu systemd-udevd[516085]: link_config: could not get ethtool features for veth798b8b3
Aug 2 17:12:48 sentry-docker00.cs.umd.edu systemd-udevd[516085]: Could not set offload features of veth798b8b3: No such device
Aug 2 17:12:48 sentry-docker00.cs.umd.edu systemd-udevd[516173]: Could not generate persistent MAC address for vethdf928fb: No such file or directory
Aug 2 17:12:48 sentry-docker00.cs.umd.edu systemd-udevd[516174]: Could not generate persistent MAC address for veth53afb86: No such file or directory
Aug 2 17:12:48 sentry-docker00.cs.umd.edu systemd-udevd[516177]: Could not generate persistent MAC address for veth8d78d4e: No such file or directory
Aug 2 17:12:48 sentry-docker00.cs.umd.edu systemd-udevd[516178]: Could not generate persistent MAC address for vethd19c53b: No such file or directory
Aug 2 17:12:48 sentry-docker00.cs.umd.edu systemd-udevd[516201]: Could not generate persistent MAC address for vethe44b7c9: No such file or directory
Aug 2 17:12:48 sentry-docker00.cs.umd.edu systemd-udevd[516202]: Could not generate persistent MAC address for veth24d193b: No such file or directory
Aug 2 17:12:48 sentry-docker00.cs.umd.edu systemd-udevd[516227]: Could not generate persistent MAC address for veth19302f9: No such file or directory
Aug 2 17:12:48 sentry-docker00.cs.umd.edu systemd-udevd[516229]: Could not generate persistent MAC address for veth2ff7ed0: No such file or directory
Aug 2 17:15:03 sentry-docker00.cs.umd.edu systemd-udevd[517236]: Could not generate persistent MAC address for veth8d10ce7: No such file or directory
Aug 2 17:15:03 sentry-docker00.cs.umd.edu systemd-udevd[517237]: Could not generate persistent MAC address for vethb2714c6: No such file or directory
Aug 2 17:32:56 sentry-docker00.cs.umd.edu systemd-udevd[525827]: link_config: could not get ethtool features for veth8d78d4e
Aug 2 17:32:56 sentry-docker00.cs.umd.edu systemd-udevd[525827]: Could not set offload features of veth8d78d4e: No such device
Aug 2 17:32:56 sentry-docker00.cs.umd.edu systemd-udevd[525852]: Could not generate persistent MAC address for vethadf2f77: No such file or directory
Aug 2 17:32:56 sentry-docker00.cs.umd.edu systemd-udevd[525853]: Could not generate persistent MAC address for veth5f38ea3: No such file or directory
Aug 2 17:32:56 sentry-docker00.cs.umd.edu systemd-udevd[525856]: Could not generate persistent MAC address for vetha42a1e3: No such file or directory
Aug 2 17:32:56 sentry-docker00.cs.umd.edu systemd-udevd[525856]: Could not generate persistent MAC address for veth4488165: No such file or directory
Aug 2 17:32:56 sentry-docker00.cs.umd.edu systemd-udevd[525880]: Could not generate persistent MAC address for veth92b0748: No such file or directory
Aug 2 17:32:56 sentry-docker00.cs.umd.edu systemd-udevd[525881]: Could not generate persistent MAC address for vethc06c55a: No such file or directory
Aug 2 17:32:56 sentry-docker00.cs.umd.edu systemd-udevd[525884]: Could not generate persistent MAC address for veth880a1e7: No such file or directory
Aug 2 17:32:56 sentry-docker00.cs.umd.edu systemd-udevd[525895]: Could not generate persistent MAC address for veth52803a1: No such file or directory
Aug 2 17:35:11 sentry-docker00.cs.umd.edu systemd-udevd[526883]: Could not generate persistent MAC address for vethf58624f: No such file or directory
Aug 2 17:35:11 sentry-docker00.cs.umd.edu systemd-udevd[526884]: Could not generate persistent MAC address for veth6198589: No such file or directory
Aug 2 17:53:04 sentry-docker00.cs.umd.edu systemd-udevd[535244]: link_config: could not get ethtool features for vetha42a1e3
Aug 2 17:53:04 sentry-docker00.cs.umd.edu systemd-udevd[535244]: Could not set offload features of vetha42a1e3: No such device
Aug 2 17:53:05 sentry-docker00.cs.umd.edu systemd-udevd[535273]: Could not generate persistent MAC address for veth75930e1: No such file or directory
Aug 2 17:53:05 sentry-docker00.cs.umd.edu systemd-udevd[535274]: Could not generate persistent MAC address for veth8ddd928: No such file or directory
Aug 2 17:53:05 sentry-docker00.cs.umd.edu systemd-udevd[535277]: Could not generate persistent MAC address for veth8690fc4: No such file or directory
Aug 2 17:53:05 sentry-docker00.cs.umd.edu systemd-udevd[535278]: Could not generate persistent MAC address for vethc6aea28: No such file or directory
... 6 more distinct messages not shown
== strawberry (2 distinct, 8 total) ==
Aug 2 17:09:44 strawberry udisksd[1067]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/ST2000DM001_1CH164_W1E8J5KJ: Error updating SMART data: Error sending ATA command CHECK POWER MODE: Unexpected sense data returned:#0120000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................#0120010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................#012 (g-io-error-quark, 0) [x6]
Aug 2 17:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-2 (10 distinct, 11 total) ==
Aug 2 17:12:52 submit26-b9-2 setroubleshoot[889078]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l d506243c-d61e-48f3-b42a-4592c913deb0
Aug 2 17:12:52 submit26-b9-2 setroubleshoot[889078]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 3b4752ac-1b9a-4af9-a05b-32e4c2eb13ab
Aug 2 17:12:52 submit26-b9-2 setroubleshoot[889078]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 29e5adbd-4381-4467-b40d-a2219101e096
Aug 2 17:12:52 submit26-b9-2 setroubleshoot[889078]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.9kw7XK/repodata/repomd.xml. For complete SELinux messages run: sealert -l 1b38f2ec-01ce-4343-8059-ba7494ecc5c4
Aug 2 17:12:52 submit26-b9-2 setroubleshoot[889078]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l e5f9af40-1f63-4924-b012-27ab2a7b2266
Aug 2 17:12:52 submit26-b9-2 setroubleshoot[889078]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.9kw7XK. For complete SELinux messages run: sealert -l 5c54db87-54a3-4a7c-97b4-b5c48d6c3543
Aug 2 17:12:52 submit26-b9-2 setroubleshoot[889078]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 63cd60e1-1e61-4276-afea-dd8526ffe8b2
Aug 2 17:12:52 submit26-b9-2 setroubleshoot[889078]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 81c7e9ec-e023-4c6d-b1ad-c02a242e655e
Aug 2 17:12:52 submit26-b9-2 setroubleshoot[889078]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 6ae9a597-e123-4d74-8eec-a8ebe0f5e4d0
Aug 2 17:40:08 submit26-b9-2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x2]
== submit26-b9-3 (9 distinct, 11 total) ==
Aug 2 17:20:38 submit26-b9-3 setroubleshoot[785563]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 5b912a44-22fd-4560-b201-2a4e289b73f5 [x2]
Aug 2 17:20:38 submit26-b9-3 setroubleshoot[785563]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 7f1df1e4-725e-4953-98eb-1079f908f543 [x2]
Aug 2 17:20:38 submit26-b9-3 setroubleshoot[785563]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 40b8852a-f77b-44b4-affe-5f11fa33de43
Aug 2 17:20:38 submit26-b9-3 setroubleshoot[785563]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.3O9CJ9/repodata/repomd.xml. For complete SELinux messages run: sealert -l 45a8019e-f6b5-4baa-92c1-862594b40d46
Aug 2 17:20:38 submit26-b9-3 setroubleshoot[785563]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l e9f0bfff-7784-4126-baa4-2bb06da56591
Aug 2 17:20:38 submit26-b9-3 setroubleshoot[785563]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.3O9CJ9. For complete SELinux messages run: sealert -l 0b17cc3d-cdc6-4fe2-a11f-3892e7c41dc7
Aug 2 17:20:38 submit26-b9-3 setroubleshoot[785563]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 10e38c64-b65f-4cdd-901e-4375652d9a42
Aug 2 17:20:38 submit26-b9-3 setroubleshoot[785563]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 7fd9cf72-ef38-48e1-b6aa-b571b26a7b22
Aug 2 17:20:38 submit26-b9-3 setroubleshoot[785563]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l b9b11116-89bd-4a3c-980c-1d422c5dcee4
== submit26-b9-4 (1 distinct, 5 total) ==
Aug 2 17:23:28 submit26-b9-4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x5]
== submit26-clnb9 (9 distinct, 9 total) ==
Aug 2 17:31:56 submit26-clnb9 setroubleshoot[1696142]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 6783ed2b-5ae4-42b5-975a-4bf50eec4658
Aug 2 17:31:56 submit26-clnb9 setroubleshoot[1696142]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 9e7fa955-cc30-4804-ac8c-e1779e85946c
Aug 2 17:31:56 submit26-clnb9 setroubleshoot[1696142]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 69bfa6e3-089c-40ff-9563-fd30787d0774
Aug 2 17:31:56 submit26-clnb9 setroubleshoot[1696142]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.KfAKsq/repodata/repomd.xml. For complete SELinux messages run: sealert -l 001acdb5-31ef-4e52-b10b-90f467a89ddc
Aug 2 17:31:56 submit26-clnb9 setroubleshoot[1696142]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l edacddcf-16ed-4dc3-8d82-7c597d5dee23
Aug 2 17:31:56 submit26-clnb9 setroubleshoot[1696142]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.KfAKsq. For complete SELinux messages run: sealert -l 62b3782e-4730-4488-8178-94dafe9b552c
Aug 2 17:31:56 submit26-clnb9 setroubleshoot[1696142]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 81cb3698-78f8-440a-8e3c-e5d1041e6b78
Aug 2 17:31:56 submit26-clnb9 setroubleshoot[1696142]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 792b472a-115c-4799-9805-fc7436f916b9
Aug 2 17:31:56 submit26-clnb9 setroubleshoot[1696142]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 15c83a86-837b-41e2-b662-b39cd4e361cb
== talkhosts9 (1 distinct, 2 total) ==
Aug 2 17:06:42 talkhosts9 setroubleshoot[865153]: SELinux is preventing /usr/bin/lsof from getattr access on the unix_stream_socket unix_stream_socket. For complete SELinux messages run: sealert -l a6df89b3-c497-469c-8232-c4fde0508abf [x2]
1
0