Command: /usr/local/sbin/syslog-digest.py Time : 0.5460s Status : exited 0 Output : Syslog digest — 2026-07-28 02:05 EDT Processed 4,301 lines, filtered 3,318 (77%). 983 unknown (157 distinct) from 24 host(s). == abuse (1 distinct, 347 total) == Jul 28 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 ] [x347] == alec.cs.umd.edu (3 distinct, 60 total) == Jul 28 01:05:13 alec.cs.umd.edu setroubleshoot[3835478]: failed to retrieve rpm info for path '/run/netns/netns-9dfd0347-71eb-5698-085c-c769043aa5c3': [x12] Jul 28 01:05:14 alec.cs.umd.edu sedispatch[1526]: AVC Message regarding setroubleshoot, ignoring message [x24] Jul 28 01:05:14 alec.cs.umd.edu setroubleshoot[3835478]: SELinux is preventing /usr/bin/df from getattr access on the file /run/netns/netns-9dfd0347-71eb-5698-085c-c769043aa5c3. For complete SELinux messages run: sealert -l 23f93208-3063-4aac-b78a-bb0fcb40740c [x24] == ar102 (39 distinct, 39 total) == Jul 21 14:28:12 ar102 cosmic-session[67961]: [2026-07-21T18:28:12Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) Jul 21 14:28:15 ar102 cosmic-session[67961]: [2026-07-21T18:28:15Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) Jul 21 14:28:18 ar102 cosmic-session[67961]: [2026-07-21T18:28:18Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) Jul 21 14:28:21 ar102 cosmic-session[67961]: [2026-07-21T18:28:21Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) Jul 21 14:28:24 ar102 cosmic-session[67961]: [2026-07-21T18:28:24Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) Jul 21 14:28:27 ar102 cosmic-session[67961]: [2026-07-21T18:28:27Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) Jul 21 14:28:30 ar102 cosmic-session[67961]: [2026-07-21T18:28:30Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) Jul 21 14:28:33 ar102 cosmic-session[67961]: [2026-07-21T18:28:33Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) Jul 21 14:28:36 ar102 cosmic-session[67961]: [2026-07-21T18:28:36Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) Jul 21 14:28:39 ar102 cosmic-session[67961]: [2026-07-21T18:28:39Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) Jul 21 14:28:42 ar102 cosmic-session[67961]: [2026-07-21T18:28:42Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) Jul 21 14:28:45 ar102 cosmic-session[67961]: [2026-07-21T18:28:45Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) Jul 21 14:28:48 ar102 cosmic-session[67961]: [2026-07-21T18:28:48Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) Jul 21 14:28:51 ar102 cosmic-session[67961]: [2026-07-21T18:28:51Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) Jul 21 14:28:54 ar102 cosmic-session[67961]: [2026-07-21T18:28:54Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) Jul 21 14:28:57 ar102 cosmic-session[67961]: [2026-07-21T18:28:57Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) Jul 21 14:29:00 ar102 cosmic-session[67961]: [2026-07-21T18:29:00Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) Jul 21 14:29:03 ar102 cosmic-session[67961]: [2026-07-21T18:29:03Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) Jul 21 14:29:06 ar102 cosmic-session[67961]: [2026-07-21T18:29:06Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) Jul 21 14:29:09 ar102 cosmic-session[67961]: [2026-07-21T18:29:09Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) Jul 21 14:29:12 ar102 cosmic-session[67961]: [2026-07-21T18:29:12Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) Jul 21 14:29:15 ar102 cosmic-session[67961]: [2026-07-21T18:29:15Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) Jul 21 14:29:18 ar102 cosmic-session[67961]: [2026-07-21T18:29:18Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) Jul 21 14:29:21 ar102 cosmic-session[67961]: [2026-07-21T18:29:21Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) Jul 21 14:29:24 ar102 cosmic-session[67961]: [2026-07-21T18:29:24Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) Jul 21 14:29:27 ar102 cosmic-session[67961]: [2026-07-21T18:29:27Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) Jul 21 14:29:30 ar102 cosmic-session[67961]: [2026-07-21T18:29:30Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) Jul 21 14:29:33 ar102 cosmic-session[67961]: [2026-07-21T18:29:33Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) Jul 21 14:29:36 ar102 cosmic-session[67961]: [2026-07-21T18:29:36Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) Jul 21 14:29:39 ar102 cosmic-session[67961]: [2026-07-21T18:29:39Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) ... 9 more distinct messages not shown == b0b02.cs.umd.edu (1 distinct, 1 total) == Jul 28 01:34:26 b0b02.cs.umd.edu rustdesk[132558]: cannot open display: == bachata (1 distinct, 2 total) == Jul 28 01:46:59 bachata setroubleshoot[2032164]: SELinux is preventing /usr/sbin/smbd from name_bind access on the udp_socket port 956. For complete SELinux messages run: sealert -l 8f7247f1-69a5-4a62-a4f0-88a324bfd75c [x2] == cheezit.cs.umd.edu (14 distinct, 16 total) == Jul 28 01:19:17 cheezit.cs.umd.edu sshd-session[2597846]: pam_access(sshd:auth): access denied for user `admin' from `34.62.217.201' Jul 28 01:19:17 cheezit.cs.umd.edu krb5_child[2597849]: Client 'admin@UMD.EDU' not found in Kerberos database Jul 28 01:19:17 cheezit.cs.umd.edu sshd-session[2597840]: error: PAM: System error for admin from 34.62.217.201 Jul 28 01:37:20 cheezit.cs.umd.edu setroubleshoot[2603433]: failed to retrieve rpm info for path '/var/log/falconctl.log': Jul 28 01:37:21 cheezit.cs.umd.edu setroubleshoot[2603433]: 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 Jul 28 01:37:23 cheezit.cs.umd.edu setroubleshoot[2603433]: 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 Jul 28 01:37:35 cheezit.cs.umd.edu setroubleshoot[2603802]: failed to retrieve rpm info for path '/var/lib/sss/pipes/nss': [x2] Jul 28 01:37:36 cheezit.cs.umd.edu setroubleshoot[2603802]: 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] Jul 28 01:37:36 cheezit.cs.umd.edu setroubleshoot[2603802]: 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 Jul 28 01:38:15 cheezit.cs.umd.edu setroubleshoot[2604251]: 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 Jul 28 01:38:15 cheezit.cs.umd.edu setroubleshoot[2604251]: 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 Jul 28 01:38:15 cheezit.cs.umd.edu setroubleshoot[2604251]: 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 Jul 28 01:38:15 cheezit.cs.umd.edu setroubleshoot[2604251]: 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 Jul 28 01:38:15 cheezit.cs.umd.edu setroubleshoot[2604251]: 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 == contest (9 distinct, 41 total) == Jul 28 01:06:29 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] Jul 28 01:48:13 contest setroubleshoot[204380]: SELinux is preventing /usr/libexec/platform-python3.6 from create access on the directory libdnf.u0fE5w. For complete SELinux messages run: sealert -l cb6b25c6-4765-4cf2-88a0-9b3b508e94e9 Jul 28 01:48:13 contest setroubleshoot[204380]: 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 Jul 28 01:48:14 contest setroubleshoot[204380]: 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 Jul 28 01:48:14 contest setroubleshoot[204380]: 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 Jul 28 01:48:14 contest setroubleshoot[204380]: SELinux is preventing /usr/libexec/platform-python3.6 from read access on the directory libdnf.u0fE5w. For complete SELinux messages run: sealert -l 45d103b6-0810-4890-a705-990118577ce8 Jul 28 01:48:18 contest setroubleshoot[204380]: 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 Jul 28 01:48:21 contest setroubleshoot[204380]: SELinux is preventing rhsmcertd-worke from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 22835727-7fef-4cfb-b3b5-881f66888317 Jul 28 01:48:34 contest setroubleshoot[204432]: 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 (1 distinct, 242 total) == Jul 28 01:04:59 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x242] == hackerman (1 distinct, 1 total) == Jul 28 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.YKV0S3”: Permission denied == hazfs.cs.umd.edu (11 distinct, 66 total) == Jul 28 01:56:00 hazfs.cs.umd.edu snmpd[1431]: send response: Failure in sendto [x6] Jul 28 01:56:00 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userweb" [x6] Jul 28 01:56:00 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."zfslist" [x6] Jul 28 01:56:00 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userhome" [x6] Jul 28 01:56:00 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userweb" [x6] Jul 28 01:56:00 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."zfslist" [x6] Jul 28 01:56:00 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userhome" [x6] Jul 28 01:56:00 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userweb" [x6] Jul 28 01:56:00 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."zfslist" [x6] Jul 28 01:56:00 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userhome" [x6] Jul 28 01:56:00 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutNumLines."userweb" [x6] == idm00 (1 distinct, 1 total) == Jul 28 01:51:09 idm00 named[1455]: client @0x7f3315b04908 10.73.240.42#50896: update '73.10.in-addr.arpa/IN' denied == idmp0 (2 distinct, 2 total) == Jul 28 01:24:00 idmp0 named[5198]: client @0x7f992002e6d8 10.73.245.12#54705: update '73.10.in-addr.arpa/IN' denied Jul 28 01:34:53 idmp0 named[5198]: client @0x7f9910005288 10.73.240.43#58305: update '73.10.in-addr.arpa/IN' denied == inbound01.cs.umd.edu (1 distinct, 1 total) == Jul 28 01:43:30 inbound01.cs.umd.edu krb5_child[2547416]: Client 'admin@UMD.EDU' not found in Kerberos database == itmon02 (1 distinct, 43 total) == Jul 28 01:07:52 itmon02 sshd[1834]: error: beginning MaxStartups throttling [x43] == mcstic (3 distinct, 6 total) == Jul 28 01:48:11 mcstic krb5_child[1754298]: Client 'admin@UMD.EDU' not found in Kerberos database [x4] Jul 28 01:48:17 mcstic sshd[1754293]: error: PAM: Authentication failure for admin from 34.156.183.109 Jul 28 01:48:43 mcstic sshd[1754321]: error: Protocol major versions differ: 2 vs. 1 == newhonors2 (1 distinct, 24 total) == Jul 28 01:13:03 newhonors2 dhcpcd[381640]: dhcpcd is not running [x24] == outbound00.cs.umd.edu (1 distinct, 6 total) == Jul 28 01:09:09 outbound00.cs.umd.edu python3[302450]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Jul 28 01:13:06 outbound01.cs.umd.edu python3[2526333]: ldapdb [x6] == sentry-docker00.cs.umd.edu (34 distinct, 34 total) == Jul 28 01:16:59 sentry-docker00.cs.umd.edu systemd-udevd[851341]: link_config: could not get ethtool features for vethfbe64da Jul 28 01:16:59 sentry-docker00.cs.umd.edu systemd-udevd[851341]: Could not set offload features of vethfbe64da: No such device Jul 28 01:16:59 sentry-docker00.cs.umd.edu systemd-udevd[851362]: Could not generate persistent MAC address for veth9a475c7: No such file or directory Jul 28 01:16:59 sentry-docker00.cs.umd.edu systemd-udevd[851363]: Could not generate persistent MAC address for vethb59f708: No such file or directory Jul 28 01:16:59 sentry-docker00.cs.umd.edu systemd-udevd[851388]: Could not generate persistent MAC address for vethb09f80c: No such file or directory Jul 28 01:16:59 sentry-docker00.cs.umd.edu systemd-udevd[851389]: Could not generate persistent MAC address for vethf097e89: No such file or directory Jul 28 01:16:59 sentry-docker00.cs.umd.edu systemd-udevd[851392]: Could not generate persistent MAC address for veth96e9b95: No such file or directory Jul 28 01:16:59 sentry-docker00.cs.umd.edu systemd-udevd[851405]: Could not generate persistent MAC address for veth287b2f4: No such file or directory Jul 28 01:16:59 sentry-docker00.cs.umd.edu systemd-udevd[851440]: Could not generate persistent MAC address for vethb4ed3dc: No such file or directory Jul 28 01:16:59 sentry-docker00.cs.umd.edu systemd-udevd[851441]: Could not generate persistent MAC address for veth793aea1: No such file or directory Jul 28 01:25:02 sentry-docker00.cs.umd.edu systemd-udevd[855593]: Could not generate persistent MAC address for veth0046f2f: No such file or directory Jul 28 01:25:02 sentry-docker00.cs.umd.edu systemd-udevd[855594]: Could not generate persistent MAC address for veth6af7c89: No such file or directory Jul 28 01:37:07 sentry-docker00.cs.umd.edu systemd-udevd[861001]: link_config: could not get ethtool features for vethb4ed3dc Jul 28 01:37:07 sentry-docker00.cs.umd.edu systemd-udevd[861001]: Could not set offload features of vethb4ed3dc: No such device Jul 28 01:37:07 sentry-docker00.cs.umd.edu systemd-udevd[861028]: Could not generate persistent MAC address for veth34d592c: No such file or directory Jul 28 01:37:07 sentry-docker00.cs.umd.edu systemd-udevd[861027]: Could not generate persistent MAC address for veth73dad00: No such file or directory Jul 28 01:37:07 sentry-docker00.cs.umd.edu systemd-udevd[861031]: Could not generate persistent MAC address for veth7508e61: No such file or directory Jul 28 01:37:07 sentry-docker00.cs.umd.edu systemd-udevd[861032]: Could not generate persistent MAC address for vetha871a2d: No such file or directory Jul 28 01:37:07 sentry-docker00.cs.umd.edu systemd-udevd[861052]: Could not generate persistent MAC address for vethe217517: No such file or directory Jul 28 01:37:07 sentry-docker00.cs.umd.edu systemd-udevd[861049]: Could not generate persistent MAC address for vethe52deec: No such file or directory Jul 28 01:37:07 sentry-docker00.cs.umd.edu systemd-udevd[861052]: Could not generate persistent MAC address for veth85facf3: No such file or directory Jul 28 01:37:07 sentry-docker00.cs.umd.edu systemd-udevd[861049]: Could not generate persistent MAC address for veth75ca637: No such file or directory Jul 28 01:45:10 sentry-docker00.cs.umd.edu systemd-udevd[865025]: Could not generate persistent MAC address for veth38376e6: No such file or directory Jul 28 01:45:10 sentry-docker00.cs.umd.edu systemd-udevd[865026]: Could not generate persistent MAC address for vethfee618c: No such file or directory Jul 28 01:57:15 sentry-docker00.cs.umd.edu systemd-udevd[870448]: link_config: could not get ethtool features for veth7508e61 Jul 28 01:57:15 sentry-docker00.cs.umd.edu systemd-udevd[870448]: Could not set offload features of veth7508e61: No such device Jul 28 01:57:15 sentry-docker00.cs.umd.edu systemd-udevd[870468]: Could not generate persistent MAC address for vethf0b2a1b: No such file or directory Jul 28 01:57:15 sentry-docker00.cs.umd.edu systemd-udevd[870469]: Could not generate persistent MAC address for veth000d2b5: No such file or directory Jul 28 01:57:15 sentry-docker00.cs.umd.edu systemd-udevd[870472]: Could not generate persistent MAC address for veth71cd1b1: No such file or directory Jul 28 01:57:15 sentry-docker00.cs.umd.edu systemd-udevd[870488]: Could not generate persistent MAC address for veth094937d: No such file or directory ... 4 more distinct messages not shown == strawberry (2 distinct, 8 total) == Jul 28 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] Jul 28 01:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-2 (9 distinct, 12 total) == Jul 28 01:12:49 submit26-b9-2 setroubleshoot[328754]: 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 Jul 28 01:12:49 submit26-b9-2 setroubleshoot[328754]: 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 Jul 28 01:12:49 submit26-b9-2 setroubleshoot[328754]: 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 [x2] Jul 28 01:12:49 submit26-b9-2 setroubleshoot[328754]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.xr4aes/repodata/repomd.xml. For complete SELinux messages run: sealert -l 1b38f2ec-01ce-4343-8059-ba7494ecc5c4 [x2] Jul 28 01:12:50 submit26-b9-2 setroubleshoot[328754]: 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 [x2] Jul 28 01:12:50 submit26-b9-2 setroubleshoot[328754]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.xr4aes. For complete SELinux messages run: sealert -l 5c54db87-54a3-4a7c-97b4-b5c48d6c3543 Jul 28 01:12:50 submit26-b9-2 setroubleshoot[328754]: 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 Jul 28 01:12:50 submit26-b9-2 setroubleshoot[328754]: 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 Jul 28 01:12:50 submit26-b9-2 setroubleshoot[328754]: 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 == submit26-b9-3 (10 distinct, 13 total) == Jul 28 01:20:35 submit26-b9-3 setroubleshoot[645968]: 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 Jul 28 01:20:36 submit26-b9-3 setroubleshoot[645968]: 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 Jul 28 01:20:36 submit26-b9-3 setroubleshoot[645968]: 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 [x2] Jul 28 01:20:36 submit26-b9-3 setroubleshoot[645968]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.JPaasS/repodata/repomd.xml. For complete SELinux messages run: sealert -l 45a8019e-f6b5-4baa-92c1-862594b40d46 Jul 28 01:20:36 submit26-b9-3 setroubleshoot[645968]: 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 [x2] Jul 28 01:20:36 submit26-b9-3 setroubleshoot[645968]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.JPaasS. For complete SELinux messages run: sealert -l 0b17cc3d-cdc6-4fe2-a11f-3892e7c41dc7 Jul 28 01:20:36 submit26-b9-3 setroubleshoot[645968]: 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 Jul 28 01:20:36 submit26-b9-3 setroubleshoot[645968]: 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 [x2] Jul 28 01:20:36 submit26-b9-3 setroubleshoot[645968]: 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 Jul 28 01:20:36 submit26-b9-3 setroubleshoot[645968]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.QydAFP/repodata/repomd.xml. For complete SELinux messages run: sealert -l 45a8019e-f6b5-4baa-92c1-862594b40d46 == submit26-b9-4 (1 distinct, 3 total) == Jul 28 01:54:53 submit26-b9-4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x3] == submit26-clnb9 (9 distinct, 9 total) == Jul 28 01:31:53 submit26-clnb9 setroubleshoot[1418595]: 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 Jul 28 01:31:53 submit26-clnb9 setroubleshoot[1418595]: 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 Jul 28 01:31:53 submit26-clnb9 setroubleshoot[1418595]: 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 Jul 28 01:31:53 submit26-clnb9 setroubleshoot[1418595]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.ZJ4z4V/repodata/repomd.xml. For complete SELinux messages run: sealert -l 001acdb5-31ef-4e52-b10b-90f467a89ddc Jul 28 01:31:53 submit26-clnb9 setroubleshoot[1418595]: 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 Jul 28 01:31:53 submit26-clnb9 setroubleshoot[1418595]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.ZJ4z4V. For complete SELinux messages run: sealert -l 62b3782e-4730-4488-8178-94dafe9b552c Jul 28 01:31:53 submit26-clnb9 setroubleshoot[1418595]: 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 Jul 28 01:31:53 submit26-clnb9 setroubleshoot[1418595]: 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 Jul 28 01:31:53 submit26-clnb9 setroubleshoot[1418595]: 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