Command: /usr/local/sbin/syslog-digest.py Time : 0.7504s Status : exited 0 Output : Syslog digest — 2026-07-27 18:05 EDT Processed 5,475 lines, filtered 4,007 (73%). 1,468 unknown (677 distinct) from 28 host(s). == abuse (1 distinct, 346 total) == Jul 27 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, 58 total) == Jul 27 17:05:05 alec.cs.umd.edu setroubleshoot[3717250]: failed to retrieve rpm info for path '/run/netns/netns-9dfd0347-71eb-5698-085c-c769043aa5c3': [x12] Jul 27 17:05:06 alec.cs.umd.edu sedispatch[1526]: AVC Message regarding setroubleshoot, ignoring message [x24] Jul 27 17:05:06 alec.cs.umd.edu setroubleshoot[3717250]: 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 [x22] == ar102 (364 distinct, 364 total) == Jul 21 14:08:37 ar102 cosmic-session[67961]: [2026-07-21T18:08:37Z 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:08:40 ar102 cosmic-session[67961]: [2026-07-21T18:08:40Z 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:08:43 ar102 cosmic-session[67961]: [2026-07-21T18:08:43Z 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:08:46 ar102 cosmic-session[67961]: [2026-07-21T18:08:46Z 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:08:49 ar102 cosmic-session[67961]: [2026-07-21T18:08:49Z 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:08:52 ar102 cosmic-session[67961]: [2026-07-21T18:08:52Z 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:08:55 ar102 cosmic-session[67961]: [2026-07-21T18:08:55Z 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:08:58 ar102 cosmic-session[67961]: [2026-07-21T18:08:58Z 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:09:01 ar102 cosmic-session[67961]: [2026-07-21T18:09:01Z 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:09:04 ar102 cosmic-session[67961]: [2026-07-21T18:09:04Z 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:09:07 ar102 cosmic-session[67961]: [2026-07-21T18:09:07Z 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:09:10 ar102 cosmic-session[67961]: [2026-07-21T18:09:10Z 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:09:13 ar102 cosmic-session[67961]: [2026-07-21T18:09:13Z 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:09:16 ar102 cosmic-session[67961]: [2026-07-21T18:09:16Z 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:09:19 ar102 cosmic-session[67961]: [2026-07-21T18:09:19Z 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:09:22 ar102 cosmic-session[67961]: [2026-07-21T18:09:22Z 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:09:25 ar102 cosmic-session[67961]: [2026-07-21T18:09:25Z 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:09:28 ar102 cosmic-session[67961]: [2026-07-21T18:09:28Z 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:09:31 ar102 cosmic-session[67961]: [2026-07-21T18:09:31Z 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:09:34 ar102 cosmic-session[67961]: [2026-07-21T18:09:34Z 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:09:37 ar102 cosmic-session[67961]: [2026-07-21T18:09:37Z 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:09:40 ar102 cosmic-session[67961]: [2026-07-21T18:09:40Z 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:09:43 ar102 cosmic-session[67961]: [2026-07-21T18:09:43Z 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:09:46 ar102 cosmic-session[67961]: [2026-07-21T18:09:46Z 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:09:49 ar102 cosmic-session[67961]: [2026-07-21T18:09:49Z 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:09:52 ar102 cosmic-session[67961]: [2026-07-21T18:09:52Z 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:09:55 ar102 cosmic-session[67961]: [2026-07-21T18:09:55Z 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:09:58 ar102 cosmic-session[67961]: [2026-07-21T18:09:58Z 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:10:01 ar102 cosmic-session[67961]: [2026-07-21T18:10:01Z 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:10:04 ar102 cosmic-session[67961]: [2026-07-21T18:10:04Z ERROR cosmic_osd::components::audio] failed to connect to cosmic-settings's varlink service: Io(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) ... 334 more distinct messages not shown == b0b02.cs.umd.edu (77 distinct, 94 total) == Jul 27 17:05:30 b0b02.cs.umd.edu setroubleshoot[1279088]: failed to retrieve rpm info for path '/run/systemd/userdb/io.systemd.Machine': [x7] Jul 27 17:05:31 b0b02.cs.umd.edu setroubleshoot[1279088]: SELinux is preventing /usr/bin/who from connectto access on the unix_stream_socket /run/systemd/userdb/io.systemd.Machine. For complete SELinux messages run: sealert -l a5294584-718f-4459-b7fe-b94996c1833e [x8] Jul 27 17:12:07 b0b02.cs.umd.edu DISCLAIMER[1348648]: Microcode update for Intel Broadwell-EP/EX (BDX-ML B/M/R0; family 6, model 79, Jul 27 17:12:07 b0b02.cs.umd.edu DISCLAIMER[1348648]: stepping 1; CPUID 0x406f1) CPUs is disabled as it may cause system instability. Jul 27 17:12:07 b0b02.cs.umd.edu DISCLAIMER[1348648]: Please refer to /usr/share/doc/microcode_ctl/caveats/06-4f-01_readme Jul 27 17:12:07 b0b02.cs.umd.edu DISCLAIMER[1348648]: and /usr/share/doc/microcode_ctl/README.caveats for details. Jul 27 17:12:07 b0b02.cs.umd.edu journal: Microcode update for Intel Broadwell-EP/EX (BDX-ML B/M/R0; family 6, model 79,#012stepping 1; CPUID 0x406f1) CPUs is disabled as it may cause system instability.#012Please refer to /usr/share/doc/microcode_ctl/caveats/06-4f-01_readme#012and /usr/share/doc/microcode_ctl/README.caveats for details. Jul 27 17:12:19 b0b02.cs.umd.edu setroubleshoot[1354816]: SELinux is preventing /usr/sbin/usermod from getattr access on the file /etc/authselect/nsswitch.conf. For complete SELinux messages run: sealert -l 8858678d-7f98-4fa0-9047-4fa142780399 Jul 27 17:12:22 b0b02.cs.umd.edu setroubleshoot[1354816]: SELinux is preventing /usr/sbin/usermod from read access on the file /etc/authselect/nsswitch.conf. For complete SELinux messages run: sealert -l 4d751405-1a78-415c-a25d-fd2c961fa0e0 Jul 27 17:12:25 b0b02.cs.umd.edu setroubleshoot[1354816]: SELinux is preventing /usr/sbin/usermod from open access on the file /etc/authselect/nsswitch.conf. For complete SELinux messages run: sealert -l cdbbe10b-a12e-4b4b-969c-63aa159afb72 Jul 27 17:14:59 b0b02.cs.umd.edu rsyslogd[1396582]: warning during parsing file /etc/rsyslog.d/50_rsyslog.conf, on or before line 51: backward-compatible insecure default in use: omrelp action uses tls="off" (plain RELP without TLS); see https://docs.rsyslog.com/doc/faq/tls_mode0_disables_tls.html; use global(compatibility.defaults.secure="strict") to enable the secure default [v8.2606.0 try https://www.rsyslog.com/e/2357 ] [x2] Jul 27 17:14:59 b0b02.cs.umd.edu rsyslogd[1396582]: warning during parsing file (null), on or before line 5: backward-compatible insecure default in use: global(abortOnUncleanConfig="off"); use global(compatibility.defaults.secure="strict") to enable the secure default [v8.2606.0 try https://www.rsyslog.com/e/2357 ] [x2] Jul 27 17:29:25 b0b02.cs.umd.edu microcode_ctl[1542901]: <4>After installation of a new version of microcode_ctl package, Jul 27 17:29:25 b0b02.cs.umd.edu microcode_ctl[1542901]: initramfs hasn't been re-generated for all the installed kernel packages. Jul 27 17:29:25 b0b02.cs.umd.edu microcode_ctl[1542901]: The following kernel packages have been skipped: kernel-core-5.14.0-611.49.1.el9_7.x86_64. Jul 27 17:29:25 b0b02.cs.umd.edu microcode_ctl[1542901]: Please re-generate initramfs manually for these kernel packages with the Jul 27 17:29:25 b0b02.cs.umd.edu microcode_ctl[1542901]: "dracut -f --kver KERNEL_VERSION" command in order to get the latest Jul 27 17:29:25 b0b02.cs.umd.edu microcode_ctl[1542901]: Intel CPU microcode included into early initramfs image for it, if needed. Jul 27 17:29:25 b0b02.cs.umd.edu journal: After installation of a new version of microcode_ctl package, Jul 27 17:29:25 b0b02.cs.umd.edu journal: initramfs hasn't been re-generated for all the installed kernel packages. Jul 27 17:29:25 b0b02.cs.umd.edu journal: The following kernel packages have been skipped: kernel-core-5.14.0-611.49.1.el9_7.x86_64. Jul 27 17:29:25 b0b02.cs.umd.edu journal: Please re-generate initramfs manually for these kernel packages with the Jul 27 17:29:25 b0b02.cs.umd.edu journal: "dracut -f --kver KERNEL_VERSION" command in order to get the latest Jul 27 17:29:25 b0b02.cs.umd.edu journal: Intel CPU microcode included into early initramfs image for it, if needed. Jul 27 17:33:22 b0b02.cs.umd.edu gsd-screensaver[5752]: Error releasing name org.freedesktop.ScreenSaver: The connection is closed Jul 27 17:33:22 b0b02.cs.umd.edu kernel: sda1: Can't mount, would change RO state Jul 27 17:33:23 b0b02.cs.umd.edu loginctl[1608929]: Failed to issue method call: Remote peer disconnected Jul 27 17:33:23 b0b02.cs.umd.edu rpc.gssd[1260]: event_dispatch() returned 0! Jul 27 17:33:28 b0b02.cs.umd.edu kernel: watchdog: watchdog0: watchdog did not stop! Jul 27 17:33:45 b0b02.cs.umd.edu kernel: shpchp 0000:05:01.0: pci_hp_register failed with error -16 ... 47 more distinct messages not shown == bachata (10 distinct, 10 total) == Jul 27 17:38:08 bachata smbd[1996004]: [2026/07/27 17:38:08.638670, 0] ../../source3/smbd/smb2_service.c:117(chdir_current_service) Jul 27 17:38:08 bachata smbd[1996004]: chdir_current_service: vfs_ChDir(/fs/junkfood/nelson) failed: Permission denied. Current token: uid=20608, gid=20608, 20 groups: 20608 319050000 25274 319000009 25057 30872 25195 30043 25038 15228 31006 15294 15206 15248 25025 30742 25200 319100011 30871 30736 Jul 27 17:38:08 bachata smbd[1996004]: [2026/07/27 17:38:08.640116, 0] ../../source3/smbd/smbXsrv_tcon.c:914(smbXsrv_tcon_disconnect) Jul 27 17:38:08 bachata smbd[1996004]: smbXsrv_tcon_disconnect: disconnect(0x79181b8c, 'nelson'): chdir_current_service() failed: NT_STATUS_INTERNAL_ERROR Jul 27 17:38:08 bachata smbd[1996004]: [2026/07/27 17:38:08.645156, 0] ../../source3/smbd/smbXsrv_tcon.c:1028(smbXsrv_tcon_disconnect_all) Jul 27 17:38:08 bachata smbd[1996004]: smbXsrv_tcon_disconnect_all: count[3] errors[1] first[NT_STATUS_INTERNAL_ERROR] Jul 27 17:38:08 bachata smbd[1996004]: [2026/07/27 17:38:08.645303, 0] ../../source3/smbd/smbXsrv_session.c:1900(smbXsrv_session_logoff) Jul 27 17:38:08 bachata smbd[1996004]: smbXsrv_session_logoff: smbXsrv_session_logoff(0x4ba5db4e): smb2srv_tcon_disconnect_all() failed: NT_STATUS_INTERNAL_ERROR Jul 27 17:38:08 bachata smbd[1996004]: [2026/07/27 17:38:08.645409, 0] ../../source3/smbd/smbXsrv_session.c:1728(smbXsrv_session_remove_channel_done) Jul 27 17:38:08 bachata smbd[1996004]: smbXsrv_session_remove_channel_done: smbXsrv_session_logoff(1269160782) failed: NT_STATUS_INTERNAL_ERROR == contest (10 distinct, 44 total) == Jul 27 17:06:15 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 27 17:48:13 contest setroubleshoot[185948]: SELinux is preventing /usr/libexec/platform-python3.6 from create access on the directory libdnf.sW9AsK. For complete SELinux messages run: sealert -l cb6b25c6-4765-4cf2-88a0-9b3b508e94e9 Jul 27 17:48:13 contest setroubleshoot[185948]: 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 27 17:48:13 contest setroubleshoot[185948]: 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 27 17:48:14 contest setroubleshoot[185948]: 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] Jul 27 17:48:14 contest setroubleshoot[185948]: SELinux is preventing /usr/libexec/platform-python3.6 from read access on the directory libdnf.sW9AsK. For complete SELinux messages run: sealert -l 45d103b6-0810-4890-a705-990118577ce8 Jul 27 17:48:14 contest setroubleshoot[185948]: 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 27 17:48:14 contest setroubleshoot[185948]: 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 27 17:48:14 contest setroubleshoot[185948]: SELinux is preventing /usr/libexec/platform-python3.6 from create access on the file repomd.xml. For complete SELinux messages run: sealert -l fc20ff92-ea83-4f38-a24b-ddfd737a3141 Jul 27 17:48:22 contest setroubleshoot[185948]: 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 == csfw00a (2 distinct, 254 total) == Jul 27 17:04:32 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x250] Jul 27 17:25:13 csfw00a ospf6d[1477]: [EC 100663307] Could not send entire message [x4] == frozone (1 distinct, 1 total) == Jul 27 17:34:43 frozone systemd-tmpfiles[559030]: Failed to remove "/var/tmp/test.log", ignoring: Operation not permitted == gle-dind02.cs.umd.edu (20 distinct, 20 total) == Jul 27 17:05:53 gle-dind02.cs.umd.edu microcode_ctl[718796]: <4>After installation of a new version of microcode_ctl package, Jul 27 17:05:53 gle-dind02.cs.umd.edu microcode_ctl[718796]: initramfs hasn't been re-generated for all the installed kernel packages. Jul 27 17:05:53 gle-dind02.cs.umd.edu journal: After installation of a new version of microcode_ctl package, Jul 27 17:05:53 gle-dind02.cs.umd.edu journal: initramfs hasn't been re-generated for all the installed kernel packages. Jul 27 17:05:53 gle-dind02.cs.umd.edu journal: The following kernel packages have been skipped: kernel-core-4.18.0-553.89.1.el8_10.x86_64. Jul 27 17:05:53 gle-dind02.cs.umd.edu journal: Please re-generate initramfs manually for these kernel packages with the Jul 27 17:05:53 gle-dind02.cs.umd.edu journal: "dracut -f --kver KERNEL_VERSION" command in order to get the latest Jul 27 17:05:53 gle-dind02.cs.umd.edu journal: Intel CPU microcode included into early initramfs image for it, if needed. Jul 27 17:05:53 gle-dind02.cs.umd.edu microcode_ctl[718796]: The following kernel packages have been skipped: kernel-core-4.18.0-553.89.1.el8_10.x86_64. Jul 27 17:05:53 gle-dind02.cs.umd.edu microcode_ctl[718796]: Please re-generate initramfs manually for these kernel packages with the Jul 27 17:05:53 gle-dind02.cs.umd.edu microcode_ctl[718796]: "dracut -f --kver KERNEL_VERSION" command in order to get the latest Jul 27 17:05:53 gle-dind02.cs.umd.edu microcode_ctl[718796]: Intel CPU microcode included into early initramfs image for it, if needed. Jul 27 17:05:53 gle-dind02.cs.umd.edu systemd[1]: cgroup compatibility translation between legacy and unified hierarchy settings activated. See cgroup-compat debug messages for details. Jul 27 17:07:38 gle-dind02.cs.umd.edu kernel: acpi PNP0A03:00: fail to add MMCONFIG information, can't access extended PCI configuration space under this bridge. Jul 27 17:07:39 gle-dind02.cs.umd.edu kernel: sd 0:0:0:1: Power-on or device reset occurred Jul 27 17:07:43 gle-dind02.cs.umd.edu kernel: printk: systemd: 17 output lines suppressed due to ratelimiting Jul 27 17:07:44 gle-dind02.cs.umd.edu rpc.statd[1019]: Flags: TI-RPC Jul 27 17:07:45 gle-dind02.cs.umd.edu systemd[1]: resmon.service: Supervising process 1090 which is not our child. We'll most likely not notice when it exits. Jul 27 17:07:47 gle-dind02.cs.umd.edu setroubleshoot[1080]: Deleting alert 59e7e42a-b525-4d1f-b015-61d6fa54b08a, it is allowed in current policy Jul 27 17:07:47 gle-dind02.cs.umd.edu setroubleshoot[1080]: Deleting alert 5e9c31e4-56d0-4818-a84f-e897edebb05e, it is allowed in current policy == grosh (1 distinct, 1 total) == Jul 27 17:22:42 grosh kernel: snd_hda_codec_nvhdmi hdaudioC1D0: HDMI: pin NID 0x7 not registered == hackerman (7 distinct, 12 total) == Jul 27 17:19:00 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.XAUBT3”: Permission denied Jul 27 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 27 17:20:13 hackerman gnome-software[2060381]: Only 0 apps for recent list, hiding Jul 27 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.VQRCT3”: Permission denied Jul 27 17:20:29 hackerman packagekitd[1225551]: Failed to get cache filename for libreoffice [x2] Jul 27 17:20:29 hackerman packagekitd[1225551]: Failed to get cache filename for kernel [x2] Jul 27 17:20:39 hackerman packagekitd[1225551]: failed to parse public key for /etc/pki/rpm-gpg/RPM-GPG-KEY-PQC-redhat-release == idm00 (1 distinct, 1 total) == Jul 27 17:51:08 idm00 named[1455]: client @0x7f330c00c5b8 10.73.240.42#63701: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Jul 27 17:34:53 idmp0 named[5198]: client @0x7f991403c8e8 10.73.240.43#64688: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 38 total) == Jul 27 17:07:56 itmon02 sshd[1834]: error: beginning MaxStartups throttling [x38] == itmon03 (32 distinct, 32 total) == Jul 27 17:07:35 itmon03 kernel: shpchp 0000:05:01.0: pci_hp_register failed with error -16 Jul 27 17:07:35 itmon03 kernel: shpchp 0000:05:01.0: Slot initialization failed Jul 27 17:07:35 itmon03 kernel: shpchp 0000:05:02.0: pci_hp_register failed with error -16 Jul 27 17:07:35 itmon03 kernel: shpchp 0000:05:02.0: Slot initialization failed Jul 27 17:07:35 itmon03 kernel: shpchp 0000:05:03.0: pci_hp_register failed with error -16 Jul 27 17:07:35 itmon03 kernel: shpchp 0000:05:03.0: Slot initialization failed Jul 27 17:07:35 itmon03 kernel: shpchp 0000:05:04.0: pci_hp_register failed with error -16 Jul 27 17:07:35 itmon03 kernel: shpchp 0000:05:04.0: Slot initialization failed Jul 27 17:07:35 itmon03 kernel: device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log. Jul 27 17:07:42 itmon03 lvm[692]: PV /dev/vda2 online, VG rhel is complete. Jul 27 17:07:42 itmon03 kernel: snd_hda_intel 0000:00:1b.0: no codecs found! Jul 27 17:07:48 itmon03 systemd[1]: resmon.service: Supervising process 1004 which is not our child. We'll most likely not notice when it exits. Jul 27 17:07:53 itmon03 irqbalance[794]: Cannot change IRQ 35 affinity: Operation not permitted Jul 27 17:07:53 itmon03 irqbalance[794]: IRQ 35 affinity is now unmanaged Jul 27 17:07:53 itmon03 irqbalance[794]: Cannot change IRQ 40 affinity: Operation not permitted Jul 27 17:07:53 itmon03 irqbalance[794]: IRQ 40 affinity is now unmanaged Jul 27 17:07:57 itmon03 setroubleshoot[982]: SELinux is preventing /usr/lib/systemd/systemd from execute access on the file su. For complete SELinux messages run: sealert -l 5457ddcc-62c8-4eb1-bb3f-53e95cd9a06b Jul 27 17:07:59 itmon03 setroubleshoot[982]: SELinux is preventing /usr/bin/su from 'read, open' accesses on the file /usr/bin/su. For complete SELinux messages run: sealert -l 264841b1-6ffc-49c7-b9af-7e7c30dc4d73 Jul 27 17:07:59 itmon03 setroubleshoot[982]: SELinux is preventing /usr/bin/su from execute_no_trans access on the file /usr/bin/su. For complete SELinux messages run: sealert -l 4948d4c1-e105-4887-959c-7d7a1563c690 Jul 27 17:07:59 itmon03 setroubleshoot[982]: SELinux is preventing /usr/bin/su from map access on the file /usr/bin/su. For complete SELinux messages run: sealert -l 326c9d5e-ac97-4c5a-9182-b18d8775ba64 Jul 27 17:07:59 itmon03 setroubleshoot[982]: SELinux is preventing /usr/bin/su from read access on the file /usr/bin/su. For complete SELinux messages run: sealert -l 28f41ab5-9ad2-4ef8-a1a6-98652b406076 Jul 27 17:08:04 itmon03 setroubleshoot[982]: SELinux is preventing /usr/bin/naemon from map access on the file /etc/naemon/naemon.cfg. For complete SELinux messages run: sealert -l 23aafddb-d12f-4b80-8073-64ecf7ad1244 Jul 27 17:08:05 itmon03 setroubleshoot[982]: failed to retrieve rpm info for path '/etc/naemon/conf.d/commands.cfg': Jul 27 17:08:10 itmon03 setroubleshoot[982]: SELinux is preventing /usr/bin/naemon from map access on the file /etc/naemon/conf.d/commands.cfg. For complete SELinux messages run: sealert -l b8fc37d3-29fd-418c-9c44-00a29d756fd2 Jul 27 17:08:10 itmon03 setroubleshoot[982]: SELinux is preventing /usr/bin/naemon from execute_no_trans access on the file /usr/bin/naemon. For complete SELinux messages run: sealert -l c94f1ade-b0f8-4407-a943-96c6fbc2773d Jul 27 17:08:10 itmon03 setroubleshoot[982]: failed to retrieve rpm info for path '/var/lib/naemon/retention.dat': Jul 27 17:08:10 itmon03 setroubleshoot[982]: SELinux is preventing /usr/bin/naemon from map access on the file /var/lib/naemon/retention.dat. For complete SELinux messages run: sealert -l 472ca7f9-367d-471b-8c64-a572e9ef608e Jul 27 17:08:53 itmon03 kernel: block dm-0: the capability attribute has been deprecated. Jul 27 17:09:43 itmon03 irqbalance[794]: Cannot change IRQ 37 affinity: Operation not permitted Jul 27 17:09:43 itmon03 irqbalance[794]: IRQ 37 affinity is now unmanaged ... 2 more distinct messages not shown == memcached00.cs.umd.edu (38 distinct, 40 total) == Jul 27 17:05:11 memcached00.cs.umd.edu microcode_ctl[3719215]: <4>After installation of a new version of microcode_ctl package, Jul 27 17:05:11 memcached00.cs.umd.edu journal: After installation of a new version of microcode_ctl package, Jul 27 17:05:11 memcached00.cs.umd.edu journal: initramfs hasn't been re-generated for all the installed kernel packages. Jul 27 17:05:11 memcached00.cs.umd.edu journal: The following kernel packages have been skipped: kernel-core-5.14.0-570.33.2.el9_6.x86_64. Jul 27 17:05:11 memcached00.cs.umd.edu journal: Please re-generate initramfs manually for these kernel packages with the Jul 27 17:05:11 memcached00.cs.umd.edu journal: "dracut -f --kver KERNEL_VERSION" command in order to get the latest Jul 27 17:05:11 memcached00.cs.umd.edu journal: Intel CPU microcode included into early initramfs image for it, if needed. Jul 27 17:05:11 memcached00.cs.umd.edu microcode_ctl[3719215]: initramfs hasn't been re-generated for all the installed kernel packages. Jul 27 17:05:11 memcached00.cs.umd.edu microcode_ctl[3719215]: The following kernel packages have been skipped: kernel-core-5.14.0-570.33.2.el9_6.x86_64. Jul 27 17:05:11 memcached00.cs.umd.edu microcode_ctl[3719215]: Please re-generate initramfs manually for these kernel packages with the Jul 27 17:05:11 memcached00.cs.umd.edu microcode_ctl[3719215]: "dracut -f --kver KERNEL_VERSION" command in order to get the latest Jul 27 17:05:11 memcached00.cs.umd.edu microcode_ctl[3719215]: Intel CPU microcode included into early initramfs image for it, if needed. Jul 27 17:05:23 memcached00.cs.umd.edu irqbalance[3720379]: Cannot change IRQ 33 affinity: Operation not permitted [x2] Jul 27 17:05:23 memcached00.cs.umd.edu irqbalance[3720379]: IRQ 33 affinity is now unmanaged [x2] Jul 27 17:07:40 memcached00.cs.umd.edu kernel: shpchp 0000:05:01.0: pci_hp_register failed with error -16 Jul 27 17:07:40 memcached00.cs.umd.edu kernel: shpchp 0000:05:01.0: Slot initialization failed Jul 27 17:07:40 memcached00.cs.umd.edu kernel: shpchp 0000:05:02.0: pci_hp_register failed with error -16 Jul 27 17:07:40 memcached00.cs.umd.edu kernel: shpchp 0000:05:02.0: Slot initialization failed Jul 27 17:07:40 memcached00.cs.umd.edu kernel: shpchp 0000:05:03.0: pci_hp_register failed with error -16 Jul 27 17:07:40 memcached00.cs.umd.edu kernel: shpchp 0000:05:03.0: Slot initialization failed Jul 27 17:07:40 memcached00.cs.umd.edu kernel: shpchp 0000:05:04.0: pci_hp_register failed with error -16 Jul 27 17:07:40 memcached00.cs.umd.edu kernel: shpchp 0000:05:04.0: Slot initialization failed Jul 27 17:07:41 memcached00.cs.umd.edu kernel: device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log. Jul 27 17:07:42 memcached00.cs.umd.edu kernel: sd 0:0:0:0: Power-on or device reset occurred Jul 27 17:07:44 memcached00.cs.umd.edu lvm[694]: PV /dev/sda2 online, VG rhel_redis00 is complete. Jul 27 17:07:44 memcached00.cs.umd.edu kernel: snd_hda_intel 0000:00:1b.0: no codecs found! Jul 27 17:07:44 memcached00.cs.umd.edu systemd-udevd[676]: could not read from '/sys/module/isst_if_common/initstate': No such device Jul 27 17:07:52 memcached00.cs.umd.edu kernel: block dm-0: the capability attribute has been deprecated. Jul 27 17:07:53 memcached00.cs.umd.edu setroubleshoot[1600]: SELinux is preventing /usr/bin/redis-server from name_bind access on the tcp_socket port 6380. For complete SELinux messages run: sealert -l 005628ab-03a7-4987-b3ca-496da8baac52 Jul 27 17:07:54 memcached00.cs.umd.edu setroubleshoot[1600]: SELinux is preventing /usr/bin/redis-server from write access on the directory /var/lib/redis/redis-server-prod/(null). For complete SELinux messages run: sealert -l 131d1285-be3a-4bad-91f9-ff8c16e9ab86 ... 8 more distinct messages not shown == nagios-worker-avw01.cs.umd.edu (15 distinct, 15 total) == Jul 27 17:07:27 nagios-worker-avw01.cs.umd.edu kernel: shpchp 0000:05:01.0: pci_hp_register failed with error -16 Jul 27 17:07:27 nagios-worker-avw01.cs.umd.edu kernel: shpchp 0000:05:01.0: Slot initialization failed Jul 27 17:07:27 nagios-worker-avw01.cs.umd.edu kernel: shpchp 0000:05:02.0: pci_hp_register failed with error -16 Jul 27 17:07:27 nagios-worker-avw01.cs.umd.edu kernel: shpchp 0000:05:02.0: Slot initialization failed Jul 27 17:07:27 nagios-worker-avw01.cs.umd.edu kernel: shpchp 0000:05:03.0: pci_hp_register failed with error -16 Jul 27 17:07:27 nagios-worker-avw01.cs.umd.edu kernel: shpchp 0000:05:03.0: Slot initialization failed Jul 27 17:07:27 nagios-worker-avw01.cs.umd.edu kernel: shpchp 0000:05:04.0: pci_hp_register failed with error -16 Jul 27 17:07:27 nagios-worker-avw01.cs.umd.edu kernel: shpchp 0000:05:04.0: Slot initialization failed Jul 27 17:07:28 nagios-worker-avw01.cs.umd.edu kernel: sd 0:0:0:0: Power-on or device reset occurred Jul 27 17:07:30 nagios-worker-avw01.cs.umd.edu kernel: printk: systemd: 15 output lines suppressed due to ratelimiting Jul 27 17:07:30 nagios-worker-avw01.cs.umd.edu kernel: snd_hda_intel 0000:00:1b.0: no codecs found! Jul 27 17:07:31 nagios-worker-avw01.cs.umd.edu avahi-daemon[867]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns! Jul 27 17:07:35 nagios-worker-avw01.cs.umd.edu setroubleshoot[986]: Deleting alert 5691524d-a494-4c69-9c51-f295478001c9, it is allowed in current policy Jul 27 17:07:37 nagios-worker-avw01.cs.umd.edu setroubleshoot[986]: SELinux is preventing /usr/sbin/lldpd from using the setcap access on a process. For complete SELinux messages run: sealert -l b8bb7077-37a4-477b-917b-23e07c16bd1d Jul 27 17:07:37 nagios-worker-avw01.cs.umd.edu setroubleshoot[986]: SELinux is preventing /usr/sbin/lldpcli from using the dac_read_search capability. For complete SELinux messages run: sealert -l 50d45d6b-f1bd-4b76-8f1b-9e1d6c7b1693 == neodontcare.cs.umd.edu (4 distinct, 9 total) == Jul 27 17:07:05 neodontcare.cs.umd.edu tracker-extract[4083120]: tracker_module_manager_load_modules: assertion 'initialized == TRUE' failed [x5] Jul 27 17:07:48 neodontcare.cs.umd.edu tracker-extract[4083219]: Could not get mimetype, Error when getting information for file “/fs/junkfood/gasarch/4913”: No such file or directory Jul 27 17:07:48 neodontcare.cs.umd.edu tracker-extract[4083219]: Task for 'file:///fs/junkfood/gasarch/4913' finished with error: Error when getting information for file “/fs/junkfood/gasarch/4913”: No such file or directory Jul 27 17:25:11 neodontcare.cs.umd.edu tracker-miner-f[2945379]: g_hash_table_contains: assertion 'hash_table != NULL' failed [x2] == newhonors2 (1 distinct, 24 total) == Jul 27 17:13:03 newhonors2 dhcpcd[366709]: dhcpcd is not running [x24] == outbound00.cs.umd.edu (1 distinct, 6 total) == Jul 27 17:09:09 outbound00.cs.umd.edu python3[187223]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Jul 27 17:13:06 outbound01.cs.umd.edu python3[2411142]: ldapdb [x6] == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Jul 27 17:13:39 sentry-docker00.cs.umd.edu systemd-udevd[623733]: link_config: could not get ethtool features for vethdcb5eac Jul 27 17:13:39 sentry-docker00.cs.umd.edu systemd-udevd[623733]: Could not set offload features of vethdcb5eac: No such device Jul 27 17:13:39 sentry-docker00.cs.umd.edu systemd-udevd[623800]: Could not generate persistent MAC address for veth78a1061: No such file or directory Jul 27 17:13:39 sentry-docker00.cs.umd.edu systemd-udevd[623801]: Could not generate persistent MAC address for vethb570df5: No such file or directory Jul 27 17:13:39 sentry-docker00.cs.umd.edu systemd-udevd[623804]: Could not generate persistent MAC address for vethde41228: No such file or directory Jul 27 17:13:39 sentry-docker00.cs.umd.edu systemd-udevd[623805]: Could not generate persistent MAC address for vethd15dd78: No such file or directory Jul 27 17:13:39 sentry-docker00.cs.umd.edu systemd-udevd[623828]: Could not generate persistent MAC address for veth7dca8fa: No such file or directory Jul 27 17:13:39 sentry-docker00.cs.umd.edu systemd-udevd[623829]: Could not generate persistent MAC address for veth9817049: No such file or directory Jul 27 17:13:39 sentry-docker00.cs.umd.edu systemd-udevd[623838]: Could not generate persistent MAC address for veth2155c37: No such file or directory Jul 27 17:13:39 sentry-docker00.cs.umd.edu systemd-udevd[623851]: Could not generate persistent MAC address for vethf9e43d1: No such file or directory Jul 27 17:22:11 sentry-docker00.cs.umd.edu systemd-udevd[628363]: Could not generate persistent MAC address for veth3dd77de: No such file or directory Jul 27 17:22:11 sentry-docker00.cs.umd.edu systemd-udevd[628364]: Could not generate persistent MAC address for vethc0f60d4: No such file or directory Jul 27 17:33:47 sentry-docker00.cs.umd.edu systemd-udevd[633479]: link_config: could not get ethtool features for veth7dca8fa Jul 27 17:33:47 sentry-docker00.cs.umd.edu systemd-udevd[633479]: Could not set offload features of veth7dca8fa: No such device Jul 27 17:33:47 sentry-docker00.cs.umd.edu systemd-udevd[633501]: Could not generate persistent MAC address for vethd0d2a9a: No such file or directory Jul 27 17:33:47 sentry-docker00.cs.umd.edu systemd-udevd[633502]: Could not generate persistent MAC address for veth9cce03a: No such file or directory Jul 27 17:33:47 sentry-docker00.cs.umd.edu systemd-udevd[633527]: Could not generate persistent MAC address for veth403726e: No such file or directory Jul 27 17:33:47 sentry-docker00.cs.umd.edu systemd-udevd[633528]: Could not generate persistent MAC address for veth7d27a35: No such file or directory Jul 27 17:33:47 sentry-docker00.cs.umd.edu systemd-udevd[633531]: Could not generate persistent MAC address for veth25adb3f: No such file or directory Jul 27 17:33:47 sentry-docker00.cs.umd.edu systemd-udevd[633532]: Could not generate persistent MAC address for veth682746a: No such file or directory Jul 27 17:33:47 sentry-docker00.cs.umd.edu systemd-udevd[633579]: Could not generate persistent MAC address for veth7ac596f: No such file or directory Jul 27 17:33:47 sentry-docker00.cs.umd.edu systemd-udevd[633580]: Could not generate persistent MAC address for vethc21ea07: No such file or directory Jul 27 17:42:19 sentry-docker00.cs.umd.edu systemd-udevd[637887]: Could not generate persistent MAC address for vethb79b318: No such file or directory Jul 27 17:42:19 sentry-docker00.cs.umd.edu systemd-udevd[637888]: Could not generate persistent MAC address for veth3fa567d: No such file or directory Jul 27 17:53:55 sentry-docker00.cs.umd.edu systemd-udevd[642920]: link_config: could not get ethtool features for veth7ac596f Jul 27 17:53:55 sentry-docker00.cs.umd.edu systemd-udevd[642920]: Could not set offload features of veth7ac596f: No such device Jul 27 17:53:56 sentry-docker00.cs.umd.edu systemd-udevd[643002]: Could not generate persistent MAC address for vethf71e6d7: No such file or directory Jul 27 17:53:56 sentry-docker00.cs.umd.edu systemd-udevd[643001]: Could not generate persistent MAC address for veth547f1b0: No such file or directory Jul 27 17:53:56 sentry-docker00.cs.umd.edu systemd-udevd[643043]: Could not generate persistent MAC address for veth575ea42: No such file or directory Jul 27 17:53:56 sentry-docker00.cs.umd.edu systemd-udevd[643044]: Could not generate persistent MAC address for veth2fe5f6c: No such file or directory ... 6 more distinct messages not shown == starkweather2.cs.umd.edu (19 distinct, 19 total) == Jul 27 17:07:32 starkweather2.cs.umd.edu kernel: shpchp 0000:05:01.0: pci_hp_register failed with error -16 Jul 27 17:07:32 starkweather2.cs.umd.edu kernel: shpchp 0000:05:01.0: Slot initialization failed Jul 27 17:07:32 starkweather2.cs.umd.edu kernel: shpchp 0000:05:02.0: pci_hp_register failed with error -16 Jul 27 17:07:32 starkweather2.cs.umd.edu kernel: shpchp 0000:05:02.0: Slot initialization failed Jul 27 17:07:32 starkweather2.cs.umd.edu kernel: shpchp 0000:05:03.0: pci_hp_register failed with error -16 Jul 27 17:07:32 starkweather2.cs.umd.edu kernel: shpchp 0000:05:03.0: Slot initialization failed Jul 27 17:07:32 starkweather2.cs.umd.edu kernel: shpchp 0000:05:04.0: pci_hp_register failed with error -16 Jul 27 17:07:32 starkweather2.cs.umd.edu kernel: shpchp 0000:05:04.0: Slot initialization failed Jul 27 17:07:33 starkweather2.cs.umd.edu kernel: sd 0:0:0:1: Power-on or device reset occurred Jul 27 17:07:36 starkweather2.cs.umd.edu kernel: printk: systemd: 15 output lines suppressed due to ratelimiting Jul 27 17:07:36 starkweather2.cs.umd.edu systemd-tmpfiles[737]: [/etc/tmpfiles.d/httpd.conf:1] Unknown group 'apache'. Jul 27 17:07:36 starkweather2.cs.umd.edu systemd-tmpfiles[737]: [/usr/lib/tmpfiles.d/mod_fcgid.conf:1] Unknown group 'apache'. Jul 27 17:07:36 starkweather2.cs.umd.edu systemd-tmpfiles[737]: [/etc/tmpfiles.d/smokeping.conf:1] Unknown group 'apache'. Jul 27 17:07:36 starkweather2.cs.umd.edu kernel: snd_hda_intel 0000:00:1b.0: no codecs found! Jul 27 17:07:37 starkweather2.cs.umd.edu avahi-daemon[841]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns! Jul 27 17:07:38 starkweather2.cs.umd.edu systemd[1]: resmon.service: Supervising process 956 which is not our child. We'll most likely not notice when it exits. Jul 27 17:07:42 starkweather2.cs.umd.edu setroubleshoot[941]: Deleting alert 89143eb3-48b6-4def-a3d9-8a76b964000a, it is allowed in current policy Jul 27 17:07:46 starkweather2.cs.umd.edu setroubleshoot[941]: SELinux is preventing /usr/sbin/lldpd from using the setcap access on a process. For complete SELinux messages run: sealert -l f67b49e4-77ea-4dc1-8e51-d8b7f18589ed Jul 27 17:08:11 starkweather2.cs.umd.edu systemd[1]: smokeping.service: Start request repeated too quickly. == strawberry (2 distinct, 8 total) == Jul 27 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 27 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 27 17:12:49 submit26-b9-2 setroubleshoot[309289]: 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 27 17:12:49 submit26-b9-2 setroubleshoot[309289]: 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 27 17:12:49 submit26-b9-2 setroubleshoot[309289]: 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 27 17:12:49 submit26-b9-2 setroubleshoot[309289]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.BbykhR/repodata/repomd.xml. For complete SELinux messages run: sealert -l 1b38f2ec-01ce-4343-8059-ba7494ecc5c4 Jul 27 17:12:49 submit26-b9-2 setroubleshoot[309289]: 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 27 17:12:49 submit26-b9-2 setroubleshoot[309289]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.BbykhR. For complete SELinux messages run: sealert -l 5c54db87-54a3-4a7c-97b4-b5c48d6c3543 Jul 27 17:12:49 submit26-b9-2 setroubleshoot[309289]: 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 27 17:12:49 submit26-b9-2 setroubleshoot[309289]: 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 27 17:12:49 submit26-b9-2 setroubleshoot[309289]: 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 27 17:20:35 submit26-b9-3 setroubleshoot[637781]: 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 27 17:20:35 submit26-b9-3 setroubleshoot[637781]: 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 27 17:20:35 submit26-b9-3 setroubleshoot[637781]: 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 27 17:20:35 submit26-b9-3 setroubleshoot[637781]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.wNbcGp/repodata/repomd.xml. For complete SELinux messages run: sealert -l 45a8019e-f6b5-4baa-92c1-862594b40d46 Jul 27 17:20:35 submit26-b9-3 setroubleshoot[637781]: 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 27 17:20:35 submit26-b9-3 setroubleshoot[637781]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.wNbcGp. For complete SELinux messages run: sealert -l 0b17cc3d-cdc6-4fe2-a11f-3892e7c41dc7 Jul 27 17:20:35 submit26-b9-3 setroubleshoot[637781]: 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 27 17:20:36 submit26-b9-3 setroubleshoot[637781]: 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 27 17:20:36 submit26-b9-3 setroubleshoot[637781]: 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-clnb9 (9 distinct, 9 total) == Jul 27 17:31:53 submit26-clnb9 setroubleshoot[1402283]: 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 27 17:31:53 submit26-clnb9 setroubleshoot[1402283]: 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 27 17:31:53 submit26-clnb9 setroubleshoot[1402283]: 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 27 17:31:53 submit26-clnb9 setroubleshoot[1402283]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.d35fM2/repodata/repomd.xml. For complete SELinux messages run: sealert -l 001acdb5-31ef-4e52-b10b-90f467a89ddc Jul 27 17:31:53 submit26-clnb9 setroubleshoot[1402283]: 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 27 17:31:53 submit26-clnb9 setroubleshoot[1402283]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.d35fM2. For complete SELinux messages run: sealert -l 62b3782e-4730-4488-8178-94dafe9b552c Jul 27 17:31:53 submit26-clnb9 setroubleshoot[1402283]: 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 27 17:31:53 submit26-clnb9 setroubleshoot[1402283]: 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 27 17:31:53 submit26-clnb9 setroubleshoot[1402283]: 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 == test-ipv6 (2 distinct, 2 total) == Jul 27 17:08:19 test-ipv6 irqbalance[801]: Cannot change IRQ 30 affinity: Operation not permitted Jul 27 17:08:19 test-ipv6 irqbalance[801]: IRQ 30 affinity is now unmanaged