Command: /usr/local/sbin/syslog-digest.py Time : 0.5489s Status : exited 0 Output : Syslog digest — 2026-07-28 18:05 EDT Processed 4,578 lines, filtered 3,713 (81%). 865 unknown (261 distinct) from 27 host(s). == abuse (1 distinct, 346 total) == Jul 28 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 ] [x346] == alec.cs.umd.edu (3 distinct, 60 total) == Jul 28 17:05:42 alec.cs.umd.edu setroubleshoot[4073357]: failed to retrieve rpm info for path '/run/netns/netns-9dfd0347-71eb-5698-085c-c769043aa5c3': [x12] Jul 28 17:05:43 alec.cs.umd.edu sedispatch[1526]: AVC Message regarding setroubleshoot, ignoring message [x24] Jul 28 17:05:43 alec.cs.umd.edu setroubleshoot[4073357]: 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 (100 distinct, 100 total) == Jul 21 15:29:39 ar102 cosmic-session[67961]: [2026-07-21T19: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" }) Jul 21 15:29:42 ar102 cosmic-session[67961]: [2026-07-21T19:29: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 15:29:45 ar102 cosmic-session[67961]: [2026-07-21T19:29: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 15:29:48 ar102 cosmic-session[67961]: [2026-07-21T19:29: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 15:29:51 ar102 cosmic-session[67961]: [2026-07-21T19:29: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 15:29:54 ar102 cosmic-session[67961]: [2026-07-21T19:29: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 15:29:57 ar102 cosmic-session[67961]: [2026-07-21T19:29: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 15:30:00 ar102 cosmic-session[67961]: [2026-07-21T19:30: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 15:30:03 ar102 cosmic-session[67961]: [2026-07-21T19:30: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 15:30:06 ar102 cosmic-session[67961]: [2026-07-21T19:30: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 15:30:09 ar102 cosmic-session[67961]: [2026-07-21T19:30: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 15:30:12 ar102 cosmic-session[67961]: [2026-07-21T19:30: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 15:30:15 ar102 cosmic-session[67961]: [2026-07-21T19:30: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 15:30:18 ar102 cosmic-session[67961]: [2026-07-21T19:30: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 15:30:21 ar102 cosmic-session[67961]: [2026-07-21T19:30: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 15:30:24 ar102 cosmic-session[67961]: [2026-07-21T19:30: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 15:30:27 ar102 cosmic-session[67961]: [2026-07-21T19:30: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 15:30:30 ar102 cosmic-session[67961]: [2026-07-21T19:30: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 15:30:33 ar102 cosmic-session[67961]: [2026-07-21T19:30: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 15:30:36 ar102 cosmic-session[67961]: [2026-07-21T19:30: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 15:30:39 ar102 cosmic-session[67961]: [2026-07-21T19:30: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 15:30:42 ar102 cosmic-session[67961]: [2026-07-21T19:30: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 15:30:45 ar102 cosmic-session[67961]: [2026-07-21T19:30: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 15:30:48 ar102 cosmic-session[67961]: [2026-07-21T19:30: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 15:30:51 ar102 cosmic-session[67961]: [2026-07-21T19:30: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 15:30:54 ar102 cosmic-session[67961]: [2026-07-21T19:30: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 15:30:57 ar102 cosmic-session[67961]: [2026-07-21T19:30: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 15:31:00 ar102 cosmic-session[67961]: [2026-07-21T19:31: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 15:31:03 ar102 cosmic-session[67961]: [2026-07-21T19:31: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 15:31:06 ar102 cosmic-session[67961]: [2026-07-21T19:31:06Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) ... 70 more distinct messages not shown == b0b02.cs.umd.edu (1 distinct, 1 total) == Jul 28 17:35:18 b0b02.cs.umd.edu rustdesk[375287]: cannot open display: == bachata (4 distinct, 4 total) == Jul 28 17:09:32 bachata kernel: clocksource: timekeeping watchdog on CPU0: Marking clocksource 'tsc' as unstable because the skew is too large: Jul 28 17:09:32 bachata kernel: clocksource: 'kvm-clock' wd_nsec: 495981889 wd_now: b448c087e6e64 wd_last: b448beaee5923 mask: ffffffffffffffff Jul 28 17:09:32 bachata kernel: clocksource: 'tsc' cs_nsec: 498652336 cs_now: 18bb203ae2c144 cs_last: 18bb1ff9a692ec mask: ffffffffffffffff Jul 28 17:09:32 bachata kernel: clocksource: 'kvm-clock' (not 'tsc') is current clocksource. == contest (10 distinct, 44 total) == Jul 28 17:05:10 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] Jul 28 17:48:14 contest setroubleshoot[241245]: SELinux is preventing /usr/libexec/platform-python3.6 from create access on the directory libdnf.Gx3HCd. For complete SELinux messages run: sealert -l cb6b25c6-4765-4cf2-88a0-9b3b508e94e9 Jul 28 17:48:14 contest setroubleshoot[241245]: 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 17:48:14 contest setroubleshoot[241245]: 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 17:48:15 contest setroubleshoot[241245]: 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 17:48:15 contest setroubleshoot[241245]: SELinux is preventing /usr/bin/gpgconf from add_name access on the directory repomd.xml.asc. For complete SELinux messages run: sealert -l 41cf7b1b-0f34-4609-98f2-b66e7825fef7 Jul 28 17:48:15 contest setroubleshoot[241245]: SELinux is preventing /usr/libexec/platform-python3.6 from read access on the directory libdnf.Gx3HCd. For complete SELinux messages run: sealert -l 45d103b6-0810-4890-a705-990118577ce8 Jul 28 17:48:15 contest setroubleshoot[241245]: 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] Jul 28 17:48:15 contest setroubleshoot[241245]: 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 Jul 28 17:48:17 contest setroubleshoot[241245]: SELinux is preventing /usr/libexec/platform-python3.6 from create access on the directory libdnf.fdsglu. For complete SELinux messages run: sealert -l cb6b25c6-4765-4cf2-88a0-9b3b508e94e9 == csfw00a (2 distinct, 26 total) == Jul 28 17:06:04 csfw00a ospf6d[1477]: [EC 100663307] Could not send entire message [x16] Jul 28 17:06:04 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x10] == frozone (1 distinct, 1 total) == Jul 28 17:34:44 frozone systemd-tmpfiles[659449]: Failed to remove "/var/tmp/test.log", ignoring: Operation not permitted == hackerman (7 distinct, 12 total) == Jul 28 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.X9H1S3”: Permission denied Jul 28 17:20:04 hackerman gnome-software[2060381]: can't reliably fixup error code 4 in domain g-io-error-quark: Not a directory [x4] Jul 28 17:20:13 hackerman gnome-software[2060381]: Only 0 apps for recent list, hiding Jul 28 17:20:29 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.19QWS3”: Permission denied Jul 28 17:20:30 hackerman packagekitd[1561905]: Failed to get cache filename for libreoffice [x2] Jul 28 17:20:30 hackerman packagekitd[1561905]: Failed to get cache filename for kernel [x2] Jul 28 17:20:39 hackerman packagekitd[1561905]: failed to parse public key for /etc/pki/rpm-gpg/RPM-GPG-KEY-PQC-redhat-release == idm00 (1 distinct, 1 total) == Jul 28 17:51:08 idm00 named[1455]: client @0x7f330c098ad8 10.73.240.42#49395: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Jul 28 17:36:03 idmp0 named[5198]: client @0x7f98e88e1668 10.73.240.43#62495: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 42 total) == Jul 28 17:08:29 itmon02 sshd[1834]: error: beginning MaxStartups throttling [x42] == mirrors.cs.umd.edu (38 distinct, 38 total) == Jul 28 17:45:49 mirrors.cs.umd.edu kernel: ACPI: RSDP 00000000000f52b0 00014 (v00 BOCHS ) Jul 28 17:45:49 mirrors.cs.umd.edu kernel: ACPI: RSDT 000000007ffe3c0e 00034 (v01 BOCHS BXPC 00000001 BXPC 00000001) Jul 28 17:45:49 mirrors.cs.umd.edu kernel: ACPI: FACP 000000007ffe3a18 00074 (v01 BOCHS BXPC 00000001 BXPC 00000001) Jul 28 17:45:49 mirrors.cs.umd.edu kernel: ACPI: DSDT 000000007ffdf040 049D8 (v01 BOCHS BXPC 00000001 BXPC 00000001) Jul 28 17:45:49 mirrors.cs.umd.edu kernel: ACPI: FACS 000000007ffdf000 00040 Jul 28 17:45:49 mirrors.cs.umd.edu kernel: ACPI: APIC 000000007ffe3a8c 00090 (v03 BOCHS BXPC 00000001 BXPC 00000001) Jul 28 17:45:49 mirrors.cs.umd.edu kernel: ACPI: SSDT 000000007ffe3b1c 000CA (v01 BOCHS VMGENID 00000001 BXPC 00000001) Jul 28 17:45:49 mirrors.cs.umd.edu kernel: ACPI: WAET 000000007ffe3be6 00028 (v01 BOCHS BXPC 00000001 BXPC 00000001) Jul 28 17:45:49 mirrors.cs.umd.edu kernel: Zone ranges: Jul 28 17:45:49 mirrors.cs.umd.edu kernel: DMA [mem 0x00001000-0x00ffffff] Jul 28 17:45:49 mirrors.cs.umd.edu kernel: DMA32 [mem 0x01000000-0xffffffff] Jul 28 17:45:49 mirrors.cs.umd.edu kernel: Normal empty Jul 28 17:45:49 mirrors.cs.umd.edu kernel: Movable zone start for each node Jul 28 17:45:49 mirrors.cs.umd.edu kernel: Early memory node ranges Jul 28 17:45:49 mirrors.cs.umd.edu kernel: node 0: [mem 0x00001000-0x0009efff] Jul 28 17:45:49 mirrors.cs.umd.edu kernel: node 0: [mem 0x00100000-0x7ffd9fff] Jul 28 17:45:49 mirrors.cs.umd.edu kernel: Built 1 zonelists in Node order, mobility grouping on. Total pages: 515939 Jul 28 17:45:49 mirrors.cs.umd.edu kernel: Policy zone: DMA32 Jul 28 17:45:49 mirrors.cs.umd.edu kernel: ACPI: All ACPI Tables successfully acquired Jul 28 17:45:49 mirrors.cs.umd.edu kernel: ACPI: Enabled 3 GPEs in block 00 to 0F Jul 28 17:45:49 mirrors.cs.umd.edu kernel: acpi PNP0A03:00: fail to add MMCONFIG information, can't access extended PCI configuration space under this bridge. Jul 28 17:45:49 mirrors.cs.umd.edu kernel: ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11 Jul 28 17:45:49 mirrors.cs.umd.edu kernel: Dquot-cache hash table entries: 512 (order 0, 4096 bytes) Jul 28 17:45:49 mirrors.cs.umd.edu kernel: ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 10 Jul 28 17:45:49 mirrors.cs.umd.edu kernel: ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 10 Jul 28 17:45:49 mirrors.cs.umd.edu kernel: ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11 Jul 28 17:45:49 mirrors.cs.umd.edu kernel: sd 2:0:0:0: Power-on or device reset occurred Jul 28 17:45:54 mirrors.cs.umd.edu systemd[1]: [/usr/lib/systemd/system/lldpd.service:16] Unknown lvalue 'ProtectKernelTunables' in section 'Service' Jul 28 17:45:54 mirrors.cs.umd.edu systemd[1]: [/usr/lib/systemd/system/lldpd.service:17] Unknown lvalue 'ProtectControlGroups' in section 'Service' Jul 28 17:45:54 mirrors.cs.umd.edu systemd[1]: [/usr/lib/systemd/system/lldpd.service:18] Unknown lvalue 'ProtectKernelModules' in section 'Service' ... 8 more distinct messages not shown == munin (2 distinct, 54 total) == Jul 28 17:47:50 munin sudo[2369275]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x27] Jul 28 17:47:50 munin sudo[2369275]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x27] == netman.cs.umd.edu (1 distinct, 2 total) == Jul 28 17:40:27 netman.cs.umd.edu krb5_child[2189358]: Client 'admin@UMD.EDU' not found in Kerberos database [x2] == newhonors2 (1 distinct, 24 total) == Jul 28 17:13:02 newhonors2 dhcpcd[413962]: dhcpcd is not running [x24] == outbound00.cs.umd.edu (1 distinct, 6 total) == Jul 28 17:09:09 outbound00.cs.umd.edu python3[526101]: ldapdb [x6] == outbound01.cs.umd.edu (3 distinct, 9 total) == Jul 28 17:10:38 outbound01.cs.umd.edu krb5_child[2750009]: Client 'admin@UMD.EDU' not found in Kerberos database [x2] Jul 28 17:13:06 outbound01.cs.umd.edu python3[2750455]: ldapdb [x6] Jul 28 17:28:46 outbound01.cs.umd.edu krb5_child[2754460]: Preauthentication failed == peach.cs.umd.edu (4 distinct, 4 total) == Jul 28 17:40:35 peach.cs.umd.edu kernel: clocksource: timekeeping watchdog on CPU1: Marking clocksource 'tsc' as unstable because the skew is too large: Jul 28 17:40:35 peach.cs.umd.edu kernel: clocksource: 'kvm-clock' wd_nsec: 504024070 wd_now: 89dfd4a63e7c3 wd_last: 89dfd2c591bbd mask: ffffffffffffffff Jul 28 17:40:35 peach.cs.umd.edu kernel: clocksource: 'tsc' cs_nsec: 471341906 cs_now: 12e9cc7aee0ce2 cs_last: 12e9cc3d448346 mask: ffffffffffffffff Jul 28 17:40:35 peach.cs.umd.edu kernel: clocksource: 'kvm-clock' (not 'tsc') is current clocksource. == sentry-docker00.cs.umd.edu (38 distinct, 38 total) == Jul 28 17:10:31 sentry-docker00.cs.umd.edu systemd-udevd[1303478]: link_config: could not get ethtool features for veth89f96e0 Jul 28 17:10:31 sentry-docker00.cs.umd.edu systemd-udevd[1303478]: Could not set offload features of veth89f96e0: No such device Jul 28 17:10:32 sentry-docker00.cs.umd.edu systemd-udevd[1303496]: Could not generate persistent MAC address for veth158d801: No such file or directory Jul 28 17:10:32 sentry-docker00.cs.umd.edu systemd-udevd[1303497]: Could not generate persistent MAC address for vethb60abb5: No such file or directory Jul 28 17:23:38 sentry-docker00.cs.umd.edu systemd-udevd[1309237]: Could not generate persistent MAC address for veth06749cb: No such file or directory Jul 28 17:23:38 sentry-docker00.cs.umd.edu systemd-udevd[1309238]: Could not generate persistent MAC address for veth6e6794f: No such file or directory Jul 28 17:23:38 sentry-docker00.cs.umd.edu systemd-udevd[1309272]: Could not generate persistent MAC address for veth8de1c15: No such file or directory Jul 28 17:23:38 sentry-docker00.cs.umd.edu systemd-udevd[1309244]: Could not generate persistent MAC address for vethf385001: No such file or directory Jul 28 17:23:38 sentry-docker00.cs.umd.edu systemd-udevd[1309290]: Could not generate persistent MAC address for vethb322ca3: No such file or directory Jul 28 17:23:38 sentry-docker00.cs.umd.edu systemd-udevd[1309291]: Could not generate persistent MAC address for vethc21aaa4: No such file or directory Jul 28 17:23:38 sentry-docker00.cs.umd.edu systemd-udevd[1309359]: Could not generate persistent MAC address for veth0461278: No such file or directory Jul 28 17:23:38 sentry-docker00.cs.umd.edu systemd-udevd[1309363]: Could not generate persistent MAC address for vethf73a71d: No such file or directory Jul 28 17:30:36 sentry-docker00.cs.umd.edu systemd-udevd[1313169]: Could not generate persistent MAC address for veth4fe1edf: No such file or directory Jul 28 17:30:36 sentry-docker00.cs.umd.edu systemd-udevd[1313170]: Could not generate persistent MAC address for vethf83781a: No such file or directory Jul 28 17:43:46 sentry-docker00.cs.umd.edu systemd-udevd[1318634]: link_config: could not get ethtool features for veth06749cb Jul 28 17:43:46 sentry-docker00.cs.umd.edu systemd-udevd[1318634]: Could not set offload features of veth06749cb: No such device Jul 28 17:43:47 sentry-docker00.cs.umd.edu systemd-udevd[1318685]: Could not generate persistent MAC address for veth44462da: No such file or directory Jul 28 17:43:47 sentry-docker00.cs.umd.edu systemd-udevd[1318686]: Could not generate persistent MAC address for vethc20412e: No such file or directory Jul 28 17:43:47 sentry-docker00.cs.umd.edu systemd-udevd[1318689]: Could not generate persistent MAC address for veth36935e3: No such file or directory Jul 28 17:43:47 sentry-docker00.cs.umd.edu systemd-udevd[1318690]: Could not generate persistent MAC address for vetha29b043: No such file or directory Jul 28 17:43:47 sentry-docker00.cs.umd.edu systemd-udevd[1318696]: Could not generate persistent MAC address for vethf235691: No such file or directory Jul 28 17:43:47 sentry-docker00.cs.umd.edu systemd-udevd[1318711]: Could not generate persistent MAC address for veth4794607: No such file or directory Jul 28 17:43:47 sentry-docker00.cs.umd.edu systemd-udevd[1318715]: Could not generate persistent MAC address for veth5023780: No such file or directory Jul 28 17:43:47 sentry-docker00.cs.umd.edu systemd-udevd[1318716]: Could not generate persistent MAC address for veth9c89377: No such file or directory Jul 28 17:50:40 sentry-docker00.cs.umd.edu systemd-udevd[1322612]: link_config: could not get ethtool features for veth4fe1edf Jul 28 17:50:40 sentry-docker00.cs.umd.edu systemd-udevd[1322612]: Could not set offload features of veth4fe1edf: No such device Jul 28 17:50:40 sentry-docker00.cs.umd.edu systemd-udevd[1322629]: Could not generate persistent MAC address for vethb104f18: No such file or directory Jul 28 17:50:40 sentry-docker00.cs.umd.edu systemd-udevd[1322630]: Could not generate persistent MAC address for veth8e81542: No such file or directory Jul 28 18:03:55 sentry-docker00.cs.umd.edu systemd-udevd[1328193]: link_config: could not set ethtool features for veth36935e3 Jul 28 18:03:55 sentry-docker00.cs.umd.edu systemd-udevd[1328193]: Could not set offload features of veth36935e3: Operation not permitted ... 8 more distinct messages not shown == smokeping-slave (3 distinct, 3 total) == Jul 28 17:38:39 smokeping-slave systemd-networkd[72]: Failed to increase receive buffer size for general netlink socket, ignoring: Operation not permitted Jul 28 17:38:40 smokeping-slave systemd[1]: resmon.service: Supervising process 193 which is not our child. We'll most likely not notice when it exits. Jul 28 17:38:40 smokeping-slave nologin[282]: Attempted login by UNKNOWN (UID: 65534) on UNKNOWN == strawberry (2 distinct, 8 total) == Jul 28 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] Jul 28 17:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-2 (9 distinct, 9 total) == Jul 28 17:12:50 submit26-b9-2 setroubleshoot[368012]: 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 17:12:50 submit26-b9-2 setroubleshoot[368012]: 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 17:12:50 submit26-b9-2 setroubleshoot[368012]: 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 Jul 28 17:12:50 submit26-b9-2 setroubleshoot[368012]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.QQfysB/repodata/repomd.xml. For complete SELinux messages run: sealert -l 1b38f2ec-01ce-4343-8059-ba7494ecc5c4 Jul 28 17:12:50 submit26-b9-2 setroubleshoot[368012]: 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 Jul 28 17:12:50 submit26-b9-2 setroubleshoot[368012]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.QQfysB. For complete SELinux messages run: sealert -l 5c54db87-54a3-4a7c-97b4-b5c48d6c3543 Jul 28 17:12:50 submit26-b9-2 setroubleshoot[368012]: 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 17:12:50 submit26-b9-2 setroubleshoot[368012]: 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 17:12:50 submit26-b9-2 setroubleshoot[368012]: 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 (9 distinct, 9 total) == Jul 28 17:20:36 submit26-b9-3 setroubleshoot[662392]: 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 17:20:36 submit26-b9-3 setroubleshoot[662392]: 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 17:20:36 submit26-b9-3 setroubleshoot[662392]: 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 Jul 28 17:20:36 submit26-b9-3 setroubleshoot[662392]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.7FkX8v/repodata/repomd.xml. For complete SELinux messages run: sealert -l 45a8019e-f6b5-4baa-92c1-862594b40d46 Jul 28 17:20:36 submit26-b9-3 setroubleshoot[662392]: 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 Jul 28 17:20:36 submit26-b9-3 setroubleshoot[662392]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.7FkX8v. For complete SELinux messages run: sealert -l 0b17cc3d-cdc6-4fe2-a11f-3892e7c41dc7 Jul 28 17:20:36 submit26-b9-3 setroubleshoot[662392]: 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 17:20:36 submit26-b9-3 setroubleshoot[662392]: 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 Jul 28 17:20:36 submit26-b9-3 setroubleshoot[662392]: 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, 1 total) == Jul 28 17:52:00 submit26-b9-4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-clnb9 (9 distinct, 10 total) == Jul 28 17:31:54 submit26-clnb9 setroubleshoot[1451325]: 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] Jul 28 17:31:54 submit26-clnb9 setroubleshoot[1451325]: 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 17:31:54 submit26-clnb9 setroubleshoot[1451325]: 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 17:31:54 submit26-clnb9 setroubleshoot[1451325]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.gWtjIe/repodata/repomd.xml. For complete SELinux messages run: sealert -l 001acdb5-31ef-4e52-b10b-90f467a89ddc Jul 28 17:31:54 submit26-clnb9 setroubleshoot[1451325]: 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 17:31:54 submit26-clnb9 setroubleshoot[1451325]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.gWtjIe. For complete SELinux messages run: sealert -l 62b3782e-4730-4488-8178-94dafe9b552c Jul 28 17:31:54 submit26-clnb9 setroubleshoot[1451325]: 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 17:31:54 submit26-clnb9 setroubleshoot[1451325]: 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 17:31:54 submit26-clnb9 setroubleshoot[1451325]: 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 == vannorden (8 distinct, 12 total) == Jul 28 17:07:00 vannorden systemd[1]: Failed to mount RPC Pipe File System. Jul 28 17:07:00 vannorden systemd[1]: Dependency failed for rpc_pipefs.target. Jul 28 17:07:00 vannorden systemd[1]: Dependency failed for RPC security service for NFS client and server. Jul 28 17:07:00 vannorden auditd[94]: Cannot change priority (Operation not permitted) [x5] Jul 28 17:07:00 vannorden systemd[1]: auditd.service: Start request repeated too quickly. Jul 28 17:07:01 vannorden sm-notify[270]: Unable to open /proc/fs/lockd/nlm_end_grace: Permission denied Jul 28 17:07:15 vannorden systemd[1]: docker-caddy.service: Start request repeated too quickly. Jul 28 17:07:15 vannorden systemd[1]: Dependency failed for Daemon for puppetboard.