Command: /usr/local/sbin/syslog-digest.py Time : 0.2205s Status : exited 0 Output : Syslog digest — 2026-09-17 11:05 EDT Processed 8,317 lines, filtered 2,426 (29%). 5,891 unknown (177 distinct) from 22 host(s). == amoeba (9 distinct, 5477 total) == Sep 17 10:37:48 amoeba upowerd[1032]: treating change event as add on /sys/devices/pci0000:00/0000:00:14.0/usb1/1-10 Sep 17 10:37:48 amoeba upowerd[1032]: treating change event as add on /sys/devices/pci0000:00/0000:00:14.0/usb2/2-5 Sep 17 10:38:07 amoeba goa-identity-se[1458288]: GoaKerberosIdentityManager: Using polling for change notification for credential cache type 'KCM' Sep 17 10:38:07 amoeba vmware-user.desktop[1458450]: vmware-user: could not open /proc/fs/vmblock/dev Sep 17 10:38:08 amoeba gsd-usb-protect[1458437]: Failed to fetch USBGuard parameters: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable Sep 17 10:38:08 amoeba gnome-software[1458418]: Only 0 apps for recent list, hiding [x3] Sep 17 10:38:09 amoeba gsd-color[1458373]: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/xrandr_Dell_Inc__DELL_U2718Q_4K8X78B30VWL_gdm_42 Sep 17 10:38:28 amoeba packagekitd[1458354]: Failed to get cache filename for openvox-agent Sep 17 10:39:44 amoeba packagekitd[1458354]: failed to parse public key for /etc/pki/rpm-gpg/RPM-GPG-KEY-PQC-redhat-release [x5467] == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 17 10:47:51 b0b02.cs.umd.edu rustdesk[2125688]: cannot open display: == borealis (2 distinct, 2 total) == Sep 17 10:35:15 borealis tracker-miner-f[548638]: g_hash_table_contains: assertion 'hash_table != NULL' failed Sep 17 10:35:15 borealis tracker-extract[560634]: tracker_module_manager_load_modules: assertion 'initialized == TRUE' failed == cheezit.cs.umd.edu (1 distinct, 1 total) == Sep 17 11:04:17 cheezit.cs.umd.edu sshd-session[196164]: pam_access(sshd:auth): access denied for user `lin' from `74.96.151.253' == csfw00a (1 distinct, 138 total) == Sep 17 10:03:55 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x138] == grosh (1 distinct, 1 total) == Sep 17 11:00:05 grosh (da-udp.*)[2736309]: amanda-udp-restart.service: Failed at step EXEC spawning /usr/bin/systemctl restart amanda-udp.*: No such file or directory == idm00 (1 distinct, 1 total) == Sep 17 10:53:57 idm00 named[4166701]: client @0x7f11a42a41d8 10.73.240.42#55739: update '73.10.in-addr.arpa/IN' denied == idmp0 (2 distinct, 3 total) == Sep 17 10:37:57 idmp0 named[1598691]: client @0x7f2d3400d5c8 10.73.240.43#56097: update '73.10.in-addr.arpa/IN' denied Sep 17 10:40:10 idmp0 named[1598691]: client @0x7f2d4803e0e8 10.73.245.14#58463: update '73.10.in-addr.arpa/IN' denied [x2] == irb2156 (1 distinct, 1 total) == Sep 17 11:00:31 irb2156 (da-udp.*)[248502]: amanda-udp-restart.service: Failed at step EXEC spawning /usr/bin/systemctl restart amanda-udp.*: No such file or directory == itmon02 (1 distinct, 2 total) == Sep 17 10:19:00 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x2] == krispykreme.cs.umd.edu (1 distinct, 3 total) == Sep 17 10:34:17 krispykreme.cs.umd.edu sshd-session[3260252]: error: PAM: Authentication failure for dgottesm from 10.174.97.86 [x3] == munin (2 distinct, 4 total) == Sep 17 10:38:26 munin sudo[3377864]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x2] Sep 17 10:38:26 munin sudo[3377864]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x2] == neodontcare.cs.umd.edu (21 distinct, 21 total) == Sep 17 10:14:04 neodontcare.cs.umd.edu sshd-session[3520873]: error: maximum authentication attempts exceeded for root from 10.227.96.11 port 45528 ssh2 [preauth] Sep 17 10:19:40 neodontcare.cs.umd.edu DISCLAIMER[3536663]: Some Dell systems that use some models of Intel CPUs are susceptible to hangs Sep 17 10:19:40 neodontcare.cs.umd.edu DISCLAIMER[3536663]: and system instability during or after microcode update to newer revisions. Sep 17 10:19:40 neodontcare.cs.umd.edu DISCLAIMER[3536663]: In order to address this, microcode update to these newer revision Sep 17 10:19:40 neodontcare.cs.umd.edu DISCLAIMER[3536663]: has been disabled by default on these systems, and the previously published Sep 17 10:19:40 neodontcare.cs.umd.edu DISCLAIMER[3536663]: microcode revisions are used by default for the OS-driven microcode update. Sep 17 10:19:40 neodontcare.cs.umd.edu DISCLAIMER[3536663]: Please refer to /usr/share/doc/microcode_ctl/caveats/06-8e-9e-0x-dell_readme Sep 17 10:19:40 neodontcare.cs.umd.edu DISCLAIMER[3536663]: and /usr/share/doc/microcode_ctl/README.caveats for details. Sep 17 10:19:40 neodontcare.cs.umd.edu journal: Some Dell systems that use some models of Intel CPUs are susceptible to hangs#012and system instability during or after microcode update to newer revisions.#012In order to address this, microcode update to these newer revision#012has been disabled by default on these systems, and the previously published#012microcode revisions are used by default for the OS-driven microcode update.#012Please refer to /usr/share/doc/microcode_ctl/caveats/06-8e-9e-0x-dell_readme#012and /usr/share/doc/microcode_ctl/README.caveats for details. Sep 17 10:22:26 neodontcare.cs.umd.edu microcode_ctl[3604536]: <4>After installation of a new version of microcode_ctl package, Sep 17 10:22:26 neodontcare.cs.umd.edu journal: After installation of a new version of microcode_ctl package, Sep 17 10:22:26 neodontcare.cs.umd.edu journal: initramfs hasn't been re-generated for all the installed kernel packages. Sep 17 10:22:26 neodontcare.cs.umd.edu journal: The following kernel packages have been skipped: kernel-core-5.14.0-611.47.1.el9_7.x86_64. Sep 17 10:22:26 neodontcare.cs.umd.edu journal: Please re-generate initramfs manually for these kernel packages with the Sep 17 10:22:26 neodontcare.cs.umd.edu journal: "dracut -f --kver KERNEL_VERSION" command in order to get the latest Sep 17 10:22:26 neodontcare.cs.umd.edu journal: Intel CPU microcode included into early initramfs image for it, if needed. Sep 17 10:22:26 neodontcare.cs.umd.edu microcode_ctl[3604536]: initramfs hasn't been re-generated for all the installed kernel packages. Sep 17 10:22:26 neodontcare.cs.umd.edu microcode_ctl[3604536]: The following kernel packages have been skipped: kernel-core-5.14.0-611.47.1.el9_7.x86_64. Sep 17 10:22:26 neodontcare.cs.umd.edu microcode_ctl[3604536]: Please re-generate initramfs manually for these kernel packages with the Sep 17 10:22:26 neodontcare.cs.umd.edu microcode_ctl[3604536]: "dracut -f --kver KERNEL_VERSION" command in order to get the latest Sep 17 10:22:26 neodontcare.cs.umd.edu microcode_ctl[3604536]: Intel CPU microcode included into early initramfs image for it, if needed. == newhonors2 (1 distinct, 24 total) == Sep 17 10:13:02 newhonors2 dhcpcd[2764657]: dhcpcd is not running [x24] == ntop00 (67 distinct, 103 total) == Sep 17 10:05:01 ntop00 sfacctd[48024]: INFO ( default_print/print ): *** Purging cache - START (PID: 234) *** Sep 17 10:05:01 ntop00 sfacctd[48024]: INFO ( default_print/print ): *** Purging cache - END (PID: 234, QN: 1813/1813, ET: 0) *** Sep 17 10:07:01 ntop00 nfacctd[9667]: INFO ( default_print/print ): *** Purging cache - START (PID: 259) *** Sep 17 10:07:01 ntop00 nfacctd[9667]: INFO ( default_print/print ): *** Purging cache - END (PID: 259, QN: 0/0, ET: X) *** Sep 17 10:10:01 ntop00 sfacctd[48024]: INFO ( default_print/print ): *** Purging cache - START (PID: 235) *** Sep 17 10:10:01 ntop00 sfacctd[48024]: INFO ( default_print/print ): *** Purging cache - END (PID: 235, QN: 2507/2507, ET: 0) *** Sep 17 10:11:54 ntop00 sfacctd[48024]: INFO ( default_print/print ): *** Purging cache - START (PID: 2) *** Sep 17 10:11:54 ntop00 sfacctd[48024]: INFO ( default_print/print ): *** Purging cache - END (PID: 2, QN: 1060/1060, ET: 0) *** Sep 17 10:11:54 ntop00 sfacctd[48024]: INFO ( default/core ): OK, Exiting ... Sep 17 10:11:54 ntop00 sfacctd[199410]: INFO ( default/core ): sFlow Accounting Daemon, sfacctd 1.7.9-git (20240801-0 (32fd57eb)) Sep 17 10:11:54 ntop00 sfacctd[199410]: INFO ( default/core ): '--enable-mysql' '--enable-pgsql' '--enable-sqlite3' '--enable-kafka' '--enable-geoipv2' '--enable-jansson' '--enable-rabbitmq' '--enable-nflog' '--enable-ndpi' '--enable-zmq' '--enable-avro' '--enable-serdes' '--enable-redis' '--enable-gnutls' 'AVRO_CFLAGS=-I/usr/local/avro/include' 'AVRO_LIBS=-L/usr/local/avro/lib -lavro' '--enable-l2' '--enable-traffic-bins' '--enable-bgp-bins' '--enable-bmp-bins' '--enable-st-bins' Sep 17 10:11:54 ntop00 sfacctd[199410]: INFO ( default/core ): Reading configuration from cmdline. Sep 17 10:11:54 ntop00 sfacctd[199410]: INFO ( default/core ): waiting for sFlow data on interface=all ip=:: port=6343/udp Sep 17 10:11:54 ntop00 sfacctd[199410]: INFO ( default_print/print ): cache entries=16411 base cache memory=72208400 bytes Sep 17 10:11:54 ntop00 sfacctd[199410]: INFO ( default_print/print ): JSON: setting object handlers. Sep 17 10:12:01 ntop00 nfacctd[9667]: INFO ( default_print/print ): *** Purging cache - START (PID: 260) *** Sep 17 10:12:01 ntop00 nfacctd[9667]: INFO ( default_print/print ): *** Purging cache - END (PID: 260, QN: 0/0, ET: X) *** Sep 17 10:12:05 ntop00 nfacctd[199535]: INFO ( default/core ): NetFlow Accounting Daemon, nfacctd 1.7.9-git (20240801-0 (32fd57eb)) Sep 17 10:12:05 ntop00 nfacctd[199535]: INFO ( default/core ): '--enable-mysql' '--enable-pgsql' '--enable-sqlite3' '--enable-kafka' '--enable-geoipv2' '--enable-jansson' '--enable-rabbitmq' '--enable-nflog' '--enable-ndpi' '--enable-zmq' '--enable-avro' '--enable-serdes' '--enable-redis' '--enable-gnutls' 'AVRO_CFLAGS=-I/usr/local/avro/include' 'AVRO_LIBS=-L/usr/local/avro/lib -lavro' '--enable-l2' '--enable-traffic-bins' '--enable-bgp-bins' '--enable-bmp-bins' '--enable-st-bins' Sep 17 10:12:05 ntop00 nfacctd[199535]: INFO ( default/core ): Reading configuration from cmdline. Sep 17 10:12:05 ntop00 nfacctd[199535]: INFO ( default/core ): waiting for NetFlow/IPFIX data on interface=all ip=:: port=2055/udp Sep 17 10:12:05 ntop00 nfacctd[199535]: INFO ( default_print/print ): cache entries=16411 base cache memory=72208400 bytes Sep 17 10:12:05 ntop00 nfacctd[199535]: INFO ( default_print/print ): JSON: setting object handlers. Sep 17 10:16:01 ntop00 sfacctd[199410]: INFO ( default_print/print ): *** Purging cache - START (PID: 3) *** Sep 17 10:16:01 ntop00 sfacctd[199410]: INFO ( default_print/print ): *** Purging cache - END (PID: 3, QN: 2728/2728, ET: 0) *** Sep 17 10:16:03 ntop00 setroubleshoot[200691]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l 539d53cf-5c9e-4ce3-8be1-3107489dd267 [x10] Sep 17 10:16:03 ntop00 setroubleshoot[200691]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 4a31fdf6-45fc-4da3-a3a4-03f8ff60af3d [x10] Sep 17 10:16:03 ntop00 setroubleshoot[200691]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x10] Sep 17 10:16:03 ntop00 setroubleshoot[200691]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l a19c0db5-f585-4fb9-a34e-811b7321a145 [x10] Sep 17 10:17:01 ntop00 nfacctd[199535]: INFO ( default_print/print ): *** Purging cache - START (PID: 3) *** ... 37 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 17 10:09:09 outbound00.cs.umd.edu python3[984704]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 17 10:13:06 outbound01.cs.umd.edu python3[3244605]: ldapdb [x6] == quiss (2 distinct, 2 total) == Sep 17 10:19:59 quiss nautilus[1581193]: GtkText - did not receive a focus-out event.#012If you handle this event, you must return#012GDK_EVENT_PROPAGATE so the default handler#012gets the event as well Sep 17 11:00:05 quiss (da-udp.*)[741704]: amanda-udp-restart.service: Failed at step EXEC spawning /usr/bin/systemctl restart amanda-udp.*: No such file or directory == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Sep 17 10:06:39 sentry-docker00.cs.umd.edu systemd-udevd[2210044]: link_config: could not set ethtool features for veth4ca5cd1 Sep 17 10:06:39 sentry-docker00.cs.umd.edu systemd-udevd[2210044]: Could not set offload features of veth4ca5cd1: Operation not permitted Sep 17 10:06:39 sentry-docker00.cs.umd.edu systemd-udevd[2210065]: Could not generate persistent MAC address for vethbf9afb3: No such file or directory Sep 17 10:06:39 sentry-docker00.cs.umd.edu systemd-udevd[2210063]: Could not generate persistent MAC address for veth8a7c8d9: No such file or directory Sep 17 10:06:39 sentry-docker00.cs.umd.edu systemd-udevd[2210090]: Could not generate persistent MAC address for veth0178f73: No such file or directory Sep 17 10:06:39 sentry-docker00.cs.umd.edu systemd-udevd[2210092]: Could not generate persistent MAC address for vethe2ccd3a: No such file or directory Sep 17 10:06:39 sentry-docker00.cs.umd.edu systemd-udevd[2210105]: Could not generate persistent MAC address for veth48658c5: No such file or directory Sep 17 10:06:39 sentry-docker00.cs.umd.edu systemd-udevd[2210095]: Could not generate persistent MAC address for veth49bfd21: No such file or directory Sep 17 10:06:39 sentry-docker00.cs.umd.edu systemd-udevd[2210101]: Could not generate persistent MAC address for veth4955315: No such file or directory Sep 17 10:06:39 sentry-docker00.cs.umd.edu systemd-udevd[2210112]: Could not generate persistent MAC address for vethecebdb2: No such file or directory Sep 17 10:06:39 sentry-docker00.cs.umd.edu systemd-udevd[2210137]: Could not generate persistent MAC address for veth789f91e: No such file or directory Sep 17 10:06:39 sentry-docker00.cs.umd.edu systemd-udevd[2210138]: Could not generate persistent MAC address for veth74ed960: No such file or directory Sep 17 10:26:47 sentry-docker00.cs.umd.edu systemd-udevd[2219452]: link_config: could not get ethtool features for veth4955315 Sep 17 10:26:47 sentry-docker00.cs.umd.edu systemd-udevd[2219452]: Could not set offload features of veth4955315: No such device Sep 17 10:26:47 sentry-docker00.cs.umd.edu systemd-udevd[2219489]: Could not generate persistent MAC address for veth083b342: No such file or directory Sep 17 10:26:47 sentry-docker00.cs.umd.edu systemd-udevd[2219490]: Could not generate persistent MAC address for veth0fe97ac: No such file or directory Sep 17 10:26:47 sentry-docker00.cs.umd.edu systemd-udevd[2219493]: Could not generate persistent MAC address for veth81566df: No such file or directory Sep 17 10:26:47 sentry-docker00.cs.umd.edu systemd-udevd[2219494]: Could not generate persistent MAC address for vethcea0fa9: No such file or directory Sep 17 10:26:47 sentry-docker00.cs.umd.edu systemd-udevd[2219499]: Could not generate persistent MAC address for veth1e8a1cf: No such file or directory Sep 17 10:26:47 sentry-docker00.cs.umd.edu systemd-udevd[2219509]: Could not generate persistent MAC address for veth9e7fed1: No such file or directory Sep 17 10:26:47 sentry-docker00.cs.umd.edu systemd-udevd[2219519]: Could not generate persistent MAC address for veth608434f: No such file or directory Sep 17 10:26:47 sentry-docker00.cs.umd.edu systemd-udevd[2219520]: Could not generate persistent MAC address for veth8cb9dff: No such file or directory Sep 17 10:26:47 sentry-docker00.cs.umd.edu systemd-udevd[2219529]: Could not generate persistent MAC address for veth4223f03: No such file or directory Sep 17 10:26:47 sentry-docker00.cs.umd.edu systemd-udevd[2219534]: Could not generate persistent MAC address for veth5f6bbcd: No such file or directory Sep 17 10:46:55 sentry-docker00.cs.umd.edu systemd-udevd[2228874]: link_config: could not get ethtool features for veth81566df Sep 17 10:46:55 sentry-docker00.cs.umd.edu systemd-udevd[2228874]: Could not set offload features of veth81566df: No such device Sep 17 10:46:55 sentry-docker00.cs.umd.edu systemd-udevd[2228906]: Could not generate persistent MAC address for veth9de8c82: No such file or directory Sep 17 10:46:55 sentry-docker00.cs.umd.edu systemd-udevd[2228907]: Could not generate persistent MAC address for vethb7026ec: No such file or directory Sep 17 10:46:55 sentry-docker00.cs.umd.edu systemd-udevd[2228910]: Could not generate persistent MAC address for veth0532cc5: No such file or directory Sep 17 10:46:55 sentry-docker00.cs.umd.edu systemd-udevd[2228911]: Could not generate persistent MAC address for veth43f369b: No such file or directory ... 6 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 17 10:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 17 10:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 17 10:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 17 10:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 17 10:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 17 10:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 17 10:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (9 distinct, 9 total) == Sep 17 10:25:52 submit26-b9-f1 setroubleshoot[2136289]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 3ef7d677-731f-46bf-9c34-c2c55fea665c Sep 17 10:25:52 submit26-b9-f1 setroubleshoot[2136289]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l aa60e26f-72e1-45f1-bc12-aa8b3b669e36 Sep 17 10:25:52 submit26-b9-f1 setroubleshoot[2136289]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l d088fb43-23ee-4ae8-ae6a-5d1c041ee2d6 Sep 17 10:25:52 submit26-b9-f1 setroubleshoot[2136289]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.NBOh5G/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d Sep 17 10:25:52 submit26-b9-f1 setroubleshoot[2136289]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 0fd3339f-3ef2-45f3-9e58-65a58b42f3ee Sep 17 10:25:52 submit26-b9-f1 setroubleshoot[2136289]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.NBOh5G. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 Sep 17 10:25:52 submit26-b9-f1 setroubleshoot[2136289]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 405a8556-cf9f-4ef4-8525-0dca18d4259d Sep 17 10:25:53 submit26-b9-f1 setroubleshoot[2136289]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 3c38e23e-3631-4cb5-81c7-992675c836d9 Sep 17 10:25:53 submit26-b9-f1 setroubleshoot[2136289]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l a070e9b5-2867-47d6-b2e3-3b7d99725848 == submit26-b9-f2 (9 distinct, 12 total) == Sep 17 10:06:48 submit26-b9-f2 setroubleshoot[1272714]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 0659d546-3107-4f75-b00f-008c85f41dc6 Sep 17 10:06:48 submit26-b9-f2 setroubleshoot[1272714]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 156d9270-3466-4356-b86f-1a128825961a Sep 17 10:06:48 submit26-b9-f2 setroubleshoot[1272714]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l c8a40bf5-2fc4-46b3-b813-8592b3523339 [x2] Sep 17 10:06:48 submit26-b9-f2 setroubleshoot[1272714]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.OHIW0J/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 [x2] Sep 17 10:06:48 submit26-b9-f2 setroubleshoot[1272714]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 988123da-b724-4e6a-900c-33a2723fdaf1 [x2] Sep 17 10:06:48 submit26-b9-f2 setroubleshoot[1272714]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.OHIW0J. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8 Sep 17 10:06:48 submit26-b9-f2 setroubleshoot[1272714]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 3a749560-1cec-40ca-a4dc-596841be3885 Sep 17 10:06:48 submit26-b9-f2 setroubleshoot[1272714]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 0aa52f08-94f8-474e-96d8-e818846941af Sep 17 10:06:48 submit26-b9-f2 setroubleshoot[1272714]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l de019dc4-408f-439c-902a-676d18dfe8e7
participants (1)
-
cron/syslog01.cs.umd.edu