Command: /usr/local/sbin/syslog-digest.py Time : 17.3407s Status : exited 0 Output : Syslog digest — 2026-06-25 23:05 EDT Processed 170,736 lines, filtered 106,054 (62%). 64,682 unknown (321 distinct) from 36 host(s). WARNING: run capped at 50 MB — some lines in this window were skipped. == b0b02.cs.umd.edu (1 distinct, 1 total) == Jun 25 21:50:10 b0b02.cs.umd.edu rustdesk[873134]: cannot open display: == bachata (9 distinct, 9 total) == Jun 25 22:12:17 bachata setroubleshoot[241584]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l d079b109-ad6d-4bc0-9ef3-e254bad3fa2e Jun 25 22:12:17 bachata setroubleshoot[241584]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 0578ceb3-0a08-460b-86b4-e6371f1d0e19 Jun 25 22:12:17 bachata setroubleshoot[241584]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 80784a28-528c-435d-b86d-8a8dafb9e226 Jun 25 22:12:17 bachata setroubleshoot[241584]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.nIwHvM/repodata/repomd.xml. For complete SELinux messages run: sealert -l 47fcf631-39c6-4c67-82f2-586459476365 Jun 25 22:12:17 bachata setroubleshoot[241584]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 3e71ccc6-74b4-4f3e-8e58-e1d0f45ef516 Jun 25 22:12:17 bachata setroubleshoot[241584]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.nIwHvM. For complete SELinux messages run: sealert -l f3ed82cd-1a14-4997-bf18-62da3edb7d18 Jun 25 22:12:17 bachata setroubleshoot[241584]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 22c2000f-ab17-4de7-bac2-285039cea9ce Jun 25 22:12:17 bachata setroubleshoot[241584]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 1afc6d0d-8d51-475c-8e25-d5e2d8815f3e Jun 25 22:12:17 bachata setroubleshoot[241584]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 660eadaf-a616-461c-9100-4aa42cdb3735 == cheezit.cs.umd.edu (1 distinct, 1 total) == Jun 25 21:48:55 cheezit.cs.umd.edu kernel: NFS: v4 server hazfs.cs.umd.edu does not accept raw uid/gids. Reenabling the idmapper. == cskayako (14 distinct, 44 total) == Jun 25 22:00:11 cskayako setroubleshoot[334009]: failed to retrieve rpm info for path '/var/www/html/__swift/cache': [x4] Jun 25 22:00:12 cskayako setroubleshoot[334009]: SELinux is preventing /usr/bin/php from write access on the directory /var/www/html/__swift/cache. For complete SELinux messages run: sealert -l c86f7264-b760-445b-9ee5-18a3f3d4882b [x4] Jun 25 22:00:12 cskayako setroubleshoot[334009]: failed to retrieve rpm info for path '/var/www/html/__swift/cache/210291fbe375f76ca5c7fee95a7e8571.php': [x4] Jun 25 22:00:12 cskayako setroubleshoot[334009]: SELinux is preventing /usr/bin/php from search access on the directory /var/www/html/__swift/cache/210291fbe375f76ca5c7fee95a7e8571.php. For complete SELinux messages run: sealert -l 5dabe20c-ddd2-4750-99c1-798ea2d8fc0d [x4] Jun 25 22:00:12 cskayako setroubleshoot[334009]: SELinux is preventing /usr/bin/php from getattr access on the directory /var/www/html/__swift/cache. For complete SELinux messages run: sealert -l 65d86f86-9ca2-4691-b08a-411b03476876 [x4] Jun 25 22:00:13 cskayako setroubleshoot[334009]: failed to retrieve rpm info for path '/var/www/html/__swift/logs/log.cache_25_Jun_2026_f21a503fe8.txt': [x4] Jun 25 22:00:13 cskayako setroubleshoot[334009]: SELinux is preventing /usr/bin/php from getattr access on the file /var/www/html/__swift/logs/log.cache_25_Jun_2026_f21a503fe8.txt. For complete SELinux messages run: sealert -l c25d7dd2-7c01-4f29-9f11-9f0afc57acba [x4] Jun 25 22:00:13 cskayako setroubleshoot[334009]: SELinux is preventing /usr/bin/php from 'read, append' accesses on the file log.cache_25_Jun_2026_f21a503fe8.txt. For complete SELinux messages run: sealert -l 660f430a-d8bd-4a10-a19c-6d9417c48d45 [x4] Jun 25 22:00:13 cskayako setroubleshoot[334009]: SELinux is preventing /usr/bin/php from open access on the file /var/www/html/__swift/logs/log.cache_25_Jun_2026_f21a503fe8.txt. For complete SELinux messages run: sealert -l 524f0284-4bc7-4f64-827d-7230e6c9b83c [x4] Jun 25 22:00:13 cskayako setroubleshoot[334009]: SELinux is preventing /usr/bin/php from setattr access on the file log.cache_25_Jun_2026_f21a503fe8.txt. For complete SELinux messages run: sealert -l c40264dc-bb4c-4d5d-b489-f91c1cc9c849 [x4] Jun 25 22:04:10 cskayako setroubleshoot[334379]: failed to retrieve rpm info for path '/var/www/html/__swift/cache/SWIFT_Loader.cache': Jun 25 22:04:10 cskayako setroubleshoot[334379]: SELinux is preventing /usr/bin/php from search access on the directory /var/www/html/__swift/cache/SWIFT_Loader.cache. For complete SELinux messages run: sealert -l 5dabe20c-ddd2-4750-99c1-798ea2d8fc0d Jun 25 22:04:10 cskayako setroubleshoot[334379]: failed to retrieve rpm info for path '/var/www/html/__swift/logs': Jun 25 22:04:10 cskayako setroubleshoot[334379]: SELinux is preventing /usr/bin/php from getattr access on the directory /var/www/html/__swift/logs. For complete SELinux messages run: sealert -l 65d86f86-9ca2-4691-b08a-411b03476876 == gle-dind00.cs.umd.edu (1 distinct, 14 total) == Jun 25 21:45:08 gle-dind00.cs.umd.edu setroubleshoot[1076687]: SELinux is preventing /usr/bin/df from getattr access on the file /run/docker/netns/default. For complete SELinux messages run: sealert -l dc8f8a6f-9eca-47fe-9948-17771b58ba35 [x14] == gle-dind01.cs.umd.edu (9 distinct, 63945 total) == Jun 25 21:41:50 gle-dind01.cs.umd.edu kernel: XFS (dm-0): corrupt dinode 51189059, (btree extents). [x7105] Jun 25 21:41:50 gle-dind01.cs.umd.edu kernel: XFS (dm-0): Metadata corruption detected at xfs_iread_bmbt_block+0x25c/0x2d0 [xfs], inode 0x30d1543 xfs_iread_bmbt_block [x7105] Jun 25 21:41:50 gle-dind01.cs.umd.edu kernel: XFS (dm-0): Unmount and run xfs_repair [x7105] Jun 25 21:41:50 gle-dind01.cs.umd.edu kernel: XFS (dm-0): First 72 bytes of corrupted metadata buffer: [x7105] Jun 25 21:41:50 gle-dind01.cs.umd.edu kernel: 00000000: 42 4d 41 33 00 00 00 18 ff ff ff ff ff ff ff ff BMA3............ [x7105] Jun 25 21:41:50 gle-dind01.cs.umd.edu kernel: 00000010: ff ff ff ff ff ff ff ff 00 00 00 00 02 a8 20 68 .............. h [x7105] Jun 25 21:41:50 gle-dind01.cs.umd.edu kernel: 00000020: 00 00 19 ab 00 00 47 3b 72 68 dd 50 2c f2 44 72 ......G;rh.P,.Dr [x7105] Jun 25 21:41:50 gle-dind01.cs.umd.edu kernel: 00000030: 9a 7f 47 d3 05 89 59 79 00 00 00 00 03 0d 15 43 ..G...Yy.......C [x7105] Jun 25 21:41:50 gle-dind01.cs.umd.edu kernel: 00000040: 61 29 5e 6d 00 00 00 00 a)^m.... [x7105] == gle-dind02.cs.umd.edu (1 distinct, 11 total) == Jun 25 21:45:18 gle-dind02.cs.umd.edu setroubleshoot[827870]: SELinux is preventing /usr/bin/df from getattr access on the file /run/docker/netns/default. For complete SELinux messages run: sealert -l 3cdb217f-957d-4c0a-877c-424ff82cda9a [x11] == hazfs.cs.umd.edu (4 distinct, 9 total) == Jun 25 21:45:01 hazfs.cs.umd.edu rpc.mountd[1370]: refused mount request from 10.73.246.82 for /raid/userdata/seriv/junkfood (/): not exported [x3] Jun 25 21:45:34 hazfs.cs.umd.edu zrepl[14922]: [hourlies_push][pruning][UxAN$wVVj$wVVj.Z+Ez.3+mh.7Dsg]: target could not destroy snapshots prune_side="receiver" err="destroys failed @zrepl_20260626_014312_000: dataset is busy" [x4] Jun 25 21:45:34 hazfs.cs.umd.edu zrepl[14922]: [hourlies_push][pruning][UxAN$wVVj$wVVj.Z+Ez.3+mh.7Dsg]: target could not destroy snapshots err="destroys failed @zrepl_20260626_014311_000: dataset is busy" prune_side="receiver" Jun 25 21:48:55 hazfs.cs.umd.edu rpc.idmapd[87070]: nss_getpwnam: name '12595' does not map into domain 'cs.umd.edu' == inbound01.cs.umd.edu (10 distinct, 15 total) == Jun 25 21:45:07 inbound01.cs.umd.edu setroubleshoot[1185818]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 69953503-173e-4381-b44c-b13656f19601 [x2] Jun 25 21:45:07 inbound01.cs.umd.edu setroubleshoot[1185818]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l c7c95fc7-f458-4590-aa1b-4ec05567c9dd [x2] Jun 25 21:45:07 inbound01.cs.umd.edu setroubleshoot[1185818]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l d4eaedd6-b047-4d44-8793-009a90aa0fa2 [x2] Jun 25 21:45:07 inbound01.cs.umd.edu setroubleshoot[1185818]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.tqU6az/repodata/repomd.xml. For complete SELinux messages run: sealert -l a5ec7358-3a5f-4698-873d-2c854ca73ebc Jun 25 21:45:07 inbound01.cs.umd.edu setroubleshoot[1185818]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 2c1e4eab-254c-4ec5-a19e-5c81a7b22e31 [x2] Jun 25 21:45:07 inbound01.cs.umd.edu setroubleshoot[1185818]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.tqU6az. For complete SELinux messages run: sealert -l 92cfec9d-23c6-4451-bd93-7be2a6008dba Jun 25 21:45:07 inbound01.cs.umd.edu setroubleshoot[1185818]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l e971f65e-6e77-4c12-938e-cbc7668df4b5 Jun 25 21:45:07 inbound01.cs.umd.edu setroubleshoot[1185818]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l f606a6fa-059f-44d8-a564-1e05d98cfbee [x2] Jun 25 21:45:07 inbound01.cs.umd.edu setroubleshoot[1185818]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l b49f0053-bf53-4389-a4b7-675396dbfc29 Jun 25 21:45:07 inbound01.cs.umd.edu setroubleshoot[1185818]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.7m6m4m/repodata/repomd.xml. For complete SELinux messages run: sealert -l a5ec7358-3a5f-4698-873d-2c854ca73ebc == irb2156 (1 distinct, 1 total) == Jun 25 21:46:38 irb2156 systemd-resolved[3421]: Using degraded feature set TCP instead of UDP for DNS server 128.8.76.3. == itmon02 (1 distinct, 35 total) == Jun 25 21:42:56 itmon02 sshd[1904]: error: beginning MaxStartups throttling [x35] == jubjub.cs.umd.edu (2 distinct, 4 total) == Jun 25 22:03:55 jubjub.cs.umd.edu sshd[779137]: error: key_cert_check_authority: invalid certificate [x3] Jun 25 22:04:02 jubjub.cs.umd.edu sshd[779137]: error: PAM: Authentication failure for root from emaar.csdips.umd.edu == kc00 (9 distinct, 9 total) == Jun 25 21:56:23 kc00 setroubleshoot[286776]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 36c862ad-6081-4762-8809-5ac61330fbc6 Jun 25 21:56:23 kc00 setroubleshoot[286776]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 44128af8-b56a-4c9e-8f40-38ef639630b0 Jun 25 21:56:23 kc00 setroubleshoot[286776]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 8c2042a5-ce0d-43a6-8b63-f36786c06236 Jun 25 21:56:23 kc00 setroubleshoot[286776]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.5p5AE9/repodata/repomd.xml. For complete SELinux messages run: sealert -l 8419c7b6-0439-4a71-878d-32a56dc5b9e7 Jun 25 21:56:23 kc00 setroubleshoot[286776]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 5a325090-f2a0-4b8b-8fae-77999fc89258 Jun 25 21:56:23 kc00 setroubleshoot[286776]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.5p5AE9. For complete SELinux messages run: sealert -l 87658479-793c-46ab-a94d-aaaedbb4dcb8 Jun 25 21:56:23 kc00 setroubleshoot[286776]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 60848455-c063-4978-b04f-56a44daea874 Jun 25 21:56:23 kc00 setroubleshoot[286776]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 8433f20d-3c3e-4547-9742-7bb65b119f4e Jun 25 21:56:23 kc00 setroubleshoot[286776]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 14bab0dd-e650-47c7-bc61-be9aea963802 == munin (17 distinct, 126 total) == Jun 25 21:42:57 munin setroubleshoot[32636]: SELinux is preventing /usr/bin/ssh from search access on the directory /var/lib/munin/.ssh. For complete SELinux messages run: sealert -l 429b6096-1b97-4570-bade-2ee408de9b6b [x6] Jun 25 21:42:57 munin setroubleshoot[32636]: SELinux is preventing /usr/bin/ssh from name_connect access on the tcp_socket port 22. For complete SELinux messages run: sealert -l 97161da0-8882-45b7-af13-79db981dd216 [x9] Jun 25 21:42:57 munin setroubleshoot[32636]: SELinux is preventing /usr/bin/ssh from read access on the file known_hosts. For complete SELinux messages run: sealert -l 14e7b2d1-684c-4e87-8530-df2a0a906887 [x10] Jun 25 21:42:57 munin setroubleshoot[32636]: SELinux is preventing /usr/bin/ssh from open access on the file /var/lib/munin/.ssh/known_hosts. For complete SELinux messages run: sealert -l f24181fb-56fa-4961-949e-973d756f6c39 [x10] Jun 25 21:42:57 munin setroubleshoot[32636]: SELinux is preventing /usr/bin/ssh from getattr access on the file /var/lib/munin/.ssh/known_hosts. For complete SELinux messages run: sealert -l 488aaccb-5f0d-41ce-8987-00135e366f48 [x10] Jun 25 21:42:57 munin setroubleshoot[32636]: SELinux is preventing /usr/bin/bash from execute access on the file /lib64/ld-linux-x86-64.so.2. For complete SELinux messages run: sealert -l 078fba18-3f42-4117-aa79-41400c3715d2 [x9] Jun 25 21:42:57 munin setroubleshoot[32636]: failed to retrieve rpm info for path '/etc/munin/send-naemon-passive.sh': [x7] Jun 25 21:42:57 munin setroubleshoot[32636]: SELinux is preventing /usr/bin/bash from execute_no_trans access on the file /etc/munin/send-naemon-passive.sh. For complete SELinux messages run: sealert -l 90b4bb38-71c7-48cf-8a26-e8781cde0139 [x9] Jun 25 21:42:57 munin setroubleshoot[32636]: SELinux is preventing /usr/bin/ssh from search access on the directory /var/kerberos/krb5. For complete SELinux messages run: sealert -l 91742286-87f9-4b43-ad1d-a489083f3769 [x6] Jun 25 21:47:49 munin setroubleshoot[34541]: SELinux is preventing /usr/bin/bash from getattr access on the file /usr/bin/ssh. For complete SELinux messages run: sealert -l 572fce0a-8662-4dac-874c-ddd5e14630fe [x8] Jun 25 21:47:50 munin setroubleshoot[34541]: SELinux is preventing /usr/bin/bash from execute access on the file /usr/bin/ssh. For complete SELinux messages run: sealert -l ce4316f8-d2b3-4657-b559-81130a8943c8 [x8] Jun 25 21:47:50 munin setroubleshoot[34541]: SELinux is preventing /usr/bin/bash from read access on the file /usr/bin/ssh. For complete SELinux messages run: sealert -l 58b4099a-64b7-4eef-9bd4-36755bfc6180 [x8] Jun 25 21:47:50 munin setroubleshoot[34541]: SELinux is preventing /usr/bin/ssh from open access on the file /usr/bin/ssh. For complete SELinux messages run: sealert -l 7b330585-8691-4841-bd0c-ebf4a03e6def [x8] Jun 25 21:47:50 munin setroubleshoot[34541]: SELinux is preventing /usr/bin/ssh from execute_no_trans access on the file /usr/bin/ssh. For complete SELinux messages run: sealert -l b5da5a22-e969-41c9-a178-9c2950a30245 [x8] Jun 25 21:47:50 munin setroubleshoot[34541]: SELinux is preventing /usr/bin/ssh from map access on the file /usr/bin/ssh. For complete SELinux messages run: sealert -l 80abb7ca-c5ee-4583-8c8c-7ced0a77cf41 [x8] Jun 25 21:52:50 munin setroubleshoot[36256]: SELinux is preventing /usr/bin/ssh from search access on the directory /var/lib/munin/.ssh/known_hosts. For complete SELinux messages run: sealert -l 429b6096-1b97-4570-bade-2ee408de9b6b Jun 25 22:02:49 munin setroubleshoot[39834]: SELinux is preventing /usr/bin/ssh from search access on the directory /var/kerberos/krb5/user. For complete SELinux messages run: sealert -l 91742286-87f9-4b43-ad1d-a489083f3769 == nagios-worker-avw01.cs.umd.edu (7 distinct, 8 total) == Jun 25 21:59:58 nagios-worker-avw01.cs.umd.edu setroubleshoot[880630]: SELinux is preventing /usr/libexec/platform-python3.6 from create access on the directory labeled user_tmp_t. For complete SELinux messages run: sealert -l 1a3d6f9c-0ec2-4ce1-86c5-aa9c29845121 Jun 25 21:59:59 nagios-worker-avw01.cs.umd.edu setroubleshoot[880630]: SELinux is preventing /usr/libexec/platform-python3.6 from add_name access on the directory labeled user_tmp_t. For complete SELinux messages run: sealert -l 46c1ad6c-8c33-4c74-8c62-0b70add4f192 Jun 25 21:59:59 nagios-worker-avw01.cs.umd.edu setroubleshoot[880630]: SELinux is preventing /usr/libexec/platform-python3.6 from create access on the file labeled user_tmp_t. For complete SELinux messages run: sealert -l 9ffd031c-2d52-4c78-872d-876f7b3c6635 Jun 25 21:59:59 nagios-worker-avw01.cs.umd.edu setroubleshoot[880630]: SELinux is preventing /usr/libexec/platform-python3.6 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l b6831d08-8430-4760-a652-fcac88001b1c Jun 25 21:59:59 nagios-worker-avw01.cs.umd.edu setroubleshoot[880630]: SELinux is preventing /usr/libexec/platform-python3.6 from read access on the directory libdnf.j0VrYH. For complete SELinux messages run: sealert -l 24e165eb-da21-47be-8bd3-16fb4520096e Jun 25 22:00:00 nagios-worker-avw01.cs.umd.edu setroubleshoot[880630]: SELinux is preventing /usr/libexec/platform-python3.6 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l a75bb2fa-7adf-479a-904e-e066b129f5a4 [x2] Jun 25 22:00:12 nagios-worker-avw01.cs.umd.edu setroubleshoot[880630]: SELinux is preventing rhsmcertd-worke from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l d75714ec-6101-41a6-89fa-eb093ed07caa == nagios-worker-v6-avw00.cs.umd.edu (7 distinct, 8 total) == Jun 25 21:53:15 nagios-worker-v6-avw00.cs.umd.edu setroubleshoot[877287]: SELinux is preventing /usr/libexec/platform-python3.6 from create access on the directory labeled user_tmp_t. For complete SELinux messages run: sealert -l d5acc4c4-9ae5-4f5b-b15b-7f19c2c8230c Jun 25 21:53:15 nagios-worker-v6-avw00.cs.umd.edu setroubleshoot[877287]: SELinux is preventing /usr/libexec/platform-python3.6 from add_name access on the directory labeled user_tmp_t. For complete SELinux messages run: sealert -l 964fadad-e886-49e3-ad42-eff36104e907 Jun 25 21:53:15 nagios-worker-v6-avw00.cs.umd.edu setroubleshoot[877287]: SELinux is preventing /usr/libexec/platform-python3.6 from create access on the file labeled user_tmp_t. For complete SELinux messages run: sealert -l 332cd28a-7a11-478a-8b9d-e765b2fdd548 Jun 25 21:53:15 nagios-worker-v6-avw00.cs.umd.edu setroubleshoot[877287]: SELinux is preventing /usr/libexec/platform-python3.6 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l c381dd8d-1c10-4fb8-8938-1d1534e63fb7 Jun 25 21:53:15 nagios-worker-v6-avw00.cs.umd.edu setroubleshoot[877287]: SELinux is preventing /usr/libexec/platform-python3.6 from read access on the directory libdnf.BkEPya. For complete SELinux messages run: sealert -l 22ead808-f263-49e2-913a-5af05bfdb86a Jun 25 21:53:15 nagios-worker-v6-avw00.cs.umd.edu setroubleshoot[877287]: SELinux is preventing /usr/libexec/platform-python3.6 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 34126da5-837a-4fca-97df-5de41d406db5 [x2] Jun 25 21:53:17 nagios-worker-v6-avw00.cs.umd.edu setroubleshoot[877287]: SELinux is preventing rhsmcertd-worke from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l e86c2057-bf49-4291-b44f-c6638881aa07 == open (1 distinct, 1 total) == fileaXJMCQ): failed to open stream: "DrupalTemporaryStreamWrapper::stream_open" call failed in file_unmanaged_save_data() (line 2024 of /var/www/sites/www.cs.umd.edu/cms/includes/file.inc). == outbound00.cs.umd.edu (2 distinct, 8 total) == Jun 25 21:42:33 outbound00.cs.umd.edu setroubleshoot[1193333]: failed to retrieve rpm info for path '/etc/puppetlabs/puppet/ssl/certs/ca.pem': [x5] Jun 25 21:49:09 outbound00.cs.umd.edu python3[1194535]: ldapdb [x3] == outbound01.cs.umd.edu (2 distinct, 9 total) == Jun 25 21:42:33 outbound01.cs.umd.edu setroubleshoot[1180037]: failed to retrieve rpm info for path '/etc/puppetlabs/puppet/ssl/certs/ca.pem': [x5] Jun 25 21:43:08 outbound01.cs.umd.edu python3[1180319]: ldapdb [x4] == quiss (44 distinct, 147 total) == Jun 25 21:46:03 quiss kernel: ata1.00: exception Emask 0x0 SAct 0x800000 SErr 0x0 action 0x0 Jun 25 21:46:03 quiss kernel: ata1.00: irq_stat 0x40000008 [x15] Jun 25 21:46:03 quiss kernel: ata1.00: failed command: READ FPDMA QUEUED [x15] Jun 25 21:46:03 quiss kernel: ata1.00: cmd 60/08:b8:bf:00:00/00:00:00:00:00/40 tag 23 ncq dma 4096 in#012 res 41/40:00:bf:00:00/00:00:00:00:00/00 Emask 0x409 (media error) <F> Jun 25 21:46:03 quiss kernel: ata1.00: status: { DRDY ERR } [x15] Jun 25 21:46:03 quiss kernel: ata1.00: error: { UNC } [x15] Jun 25 21:46:03 quiss kernel: ata1.00: NCQ Send/Recv Log not supported [x30] Jun 25 21:46:03 quiss kernel: I/O error, dev sdb, sector 191 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 [x3] Jun 25 21:46:03 quiss kernel: ata1.00: exception Emask 0x0 SAct 0x80000007 SErr 0x0 action 0x0 Jun 25 21:46:03 quiss kernel: ata1.00: cmd 60/02:f8:bf:00:00/00:00:00:00:00/40 tag 31 ncq dma 1024 in#012 res 41/40:00:bf:00:00/00:00:00:00:00/00 Emask 0x409 (media error) <F> Jun 25 21:46:03 quiss kernel: I/O error, dev sdb, sector 191 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [x3] Jun 25 21:46:03 quiss kernel: Buffer I/O error on dev sdb1, logical block 64, async page read [x3] Jun 25 21:46:03 quiss kernel: ata1.00: exception Emask 0x0 SAct 0x1c0 SErr 0x0 action 0x0 Jun 25 21:46:03 quiss kernel: ata1.00: cmd 60/02:30:c1:00:00/00:00:00:00:00/40 tag 6 ncq dma 1024 in#012 res 41/40:00:c1:00:00/00:00:00:00:00/00 Emask 0x409 (media error) <F> Jun 25 21:46:03 quiss kernel: I/O error, dev sdb, sector 193 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [x3] Jun 25 21:46:03 quiss kernel: Buffer I/O error on dev sdb1, logical block 65, async page read [x3] Jun 25 21:46:03 quiss kernel: ata1.00: exception Emask 0x0 SAct 0x600 SErr 0x0 action 0x0 Jun 25 21:46:03 quiss kernel: ata1.00: cmd 60/02:48:c3:00:00/00:00:00:00:00/40 tag 9 ncq dma 1024 in#012 res 41/40:00:c3:00:00/00:00:00:00:00/00 Emask 0x409 (media error) <F> Jun 25 21:46:03 quiss kernel: I/O error, dev sdb, sector 195 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [x3] Jun 25 21:46:03 quiss kernel: Buffer I/O error on dev sdb1, logical block 66, async page read [x3] Jun 25 21:46:03 quiss kernel: ata1.00: exception Emask 0x0 SAct 0x800 SErr 0x0 action 0x0 Jun 25 21:46:03 quiss kernel: ata1.00: cmd 60/02:58:c5:00:00/00:00:00:00:00/40 tag 11 ncq dma 1024 in#012 res 41/40:00:c5:00:00/00:00:00:00:00/00 Emask 0x409 (media error) <F> Jun 25 21:46:03 quiss kernel: I/O error, dev sdb, sector 197 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [x3] Jun 25 21:46:03 quiss kernel: Buffer I/O error on dev sdb1, logical block 67, async page read [x3] Jun 25 21:56:03 quiss kernel: ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 Jun 25 21:56:03 quiss kernel: ata1.00: cmd 60/08:00:bf:00:00/00:00:00:00:00/40 tag 0 ncq dma 4096 in#012 res 41/40:00:bf:00:00/00:00:00:00:00/00 Emask 0x409 (media error) <F> Jun 25 21:56:03 quiss kernel: ata1.00: exception Emask 0x0 SAct 0x1e SErr 0x0 action 0x0 Jun 25 21:56:03 quiss kernel: ata1.00: cmd 60/02:08:bf:00:00/00:00:00:00:00/40 tag 1 ncq dma 1024 in#012 res 41/40:00:bf:00:00/00:00:00:00:00/00 Emask 0x409 (media error) <F> Jun 25 21:56:03 quiss kernel: ata1.00: exception Emask 0x0 SAct 0x1c00000 SErr 0x0 action 0x0 Jun 25 21:56:03 quiss kernel: ata1.00: cmd 60/02:b0:c1:00:00/00:00:00:00:00/40 tag 22 ncq dma 1024 in#012 res 41/40:00:c1:00:00/00:00:00:00:00/00 Emask 0x409 (media error) <F> ... 14 more distinct messages not shown == redis00.cs.umd.edu (10 distinct, 14 total) == Jun 25 22:11:07 redis00.cs.umd.edu setroubleshoot[474389]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 1ca26373-9285-476f-a676-2cf90fcaf7a9 [x2] Jun 25 22:11:07 redis00.cs.umd.edu setroubleshoot[474389]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 42af489c-d221-44c4-b098-c0dfd3cbf3a7 [x2] Jun 25 22:11:07 redis00.cs.umd.edu setroubleshoot[474389]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l a4e28def-c57d-440a-af51-472bc863689a Jun 25 22:11:07 redis00.cs.umd.edu setroubleshoot[474389]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.sJOX9y/repodata/repomd.xml. For complete SELinux messages run: sealert -l 4de6af61-f9e7-412a-8878-8e9488da5f9c Jun 25 22:11:07 redis00.cs.umd.edu setroubleshoot[474389]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 3b01b3c0-69d1-4f55-9a60-48c6421908e4 Jun 25 22:11:07 redis00.cs.umd.edu setroubleshoot[474389]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.sJOX9y. For complete SELinux messages run: sealert -l 52747315-5cb8-421c-aa12-df09425663fc Jun 25 22:11:07 redis00.cs.umd.edu setroubleshoot[474389]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 0d99d74d-9a79-41b6-9de8-56e8ecedb08b [x2] Jun 25 22:11:07 redis00.cs.umd.edu setroubleshoot[474389]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 2f224458-3646-4c8d-ba1d-337fc79e2955 Jun 25 22:11:07 redis00.cs.umd.edu setroubleshoot[474389]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 83357abf-a2ea-445f-9204-2ccc712802cf [x2] Jun 25 22:11:07 redis00.cs.umd.edu setroubleshoot[474389]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.XVAp6g. For complete SELinux messages run: sealert -l 52747315-5cb8-421c-aa12-df09425663fc == sebatinsky.cs.umd.edu (11 distinct, 11 total) == Jun 25 21:43:16 sebatinsky.cs.umd.edu setroubleshoot[1054044]: SELinux is preventing pdns/comm-main from name_bind access on the udp_socket port 18672. For complete SELinux messages run: sealert -l 0f0383ef-2d2e-42c8-969b-2334867648e0 Jun 25 21:46:16 sebatinsky.cs.umd.edu setroubleshoot[1055054]: SELinux is preventing pdns/comm-main from name_bind access on the udp_socket port 14160. For complete SELinux messages run: sealert -l 0f0383ef-2d2e-42c8-969b-2334867648e0 Jun 25 21:49:19 sebatinsky.cs.umd.edu setroubleshoot[1055515]: SELinux is preventing pdns/comm-main from name_bind access on the udp_socket port 17020. For complete SELinux messages run: sealert -l 0f0383ef-2d2e-42c8-969b-2334867648e0 Jun 25 21:52:21 sebatinsky.cs.umd.edu setroubleshoot[1055783]: SELinux is preventing pdns/comm-main from name_bind access on the udp_socket port 13949. For complete SELinux messages run: sealert -l 0f0383ef-2d2e-42c8-969b-2334867648e0 Jun 25 21:55:21 sebatinsky.cs.umd.edu setroubleshoot[1056495]: SELinux is preventing pdns/comm-main from name_bind access on the udp_socket port 10894. For complete SELinux messages run: sealert -l 0f0383ef-2d2e-42c8-969b-2334867648e0 Jun 25 21:58:21 sebatinsky.cs.umd.edu setroubleshoot[1056899]: SELinux is preventing pdns/comm-main from name_bind access on the udp_socket port 15016. For complete SELinux messages run: sealert -l 0f0383ef-2d2e-42c8-969b-2334867648e0 Jun 25 22:01:22 sebatinsky.cs.umd.edu setroubleshoot[1057368]: SELinux is preventing pdns/comm-main from name_bind access on the udp_socket port 16500. For complete SELinux messages run: sealert -l 0f0383ef-2d2e-42c8-969b-2334867648e0 Jun 25 22:04:23 sebatinsky.cs.umd.edu setroubleshoot[1058051]: SELinux is preventing pdns/comm-main from name_bind access on the udp_socket port 19568. For complete SELinux messages run: sealert -l 0f0383ef-2d2e-42c8-969b-2334867648e0 Jun 25 22:07:21 sebatinsky.cs.umd.edu setroubleshoot[1058435]: SELinux is preventing pdns/comm-main from name_bind access on the udp_socket port 16505. For complete SELinux messages run: sealert -l 0f0383ef-2d2e-42c8-969b-2334867648e0 Jun 25 22:10:21 sebatinsky.cs.umd.edu setroubleshoot[1058903]: SELinux is preventing pdns/comm-main from name_bind access on the udp_socket port 14645. For complete SELinux messages run: sealert -l 0f0383ef-2d2e-42c8-969b-2334867648e0 Jun 25 22:13:22 sebatinsky.cs.umd.edu setroubleshoot[1058994]: SELinux is preventing pdns/comm-main from name_bind access on the udp_socket port 15899. For complete SELinux messages run: sealert -l 0f0383ef-2d2e-42c8-969b-2334867648e0 == sign-irb0101b (9 distinct, 9 total) == Jun 25 22:05:35 sign-irb0101b setroubleshoot[414239]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l e735b8ae-6fd6-4f46-971e-9d9d1fce5a5e Jun 25 22:05:35 sign-irb0101b setroubleshoot[414239]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 1b5d495b-4db4-4e9a-890d-73d981eaa3ea Jun 25 22:05:35 sign-irb0101b setroubleshoot[414239]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 51ebc2b0-96e8-4a98-9712-1d8ed7ecc83f Jun 25 22:05:35 sign-irb0101b setroubleshoot[414239]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.7xDozD/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27c1df81-d4ce-451f-b77e-d2b323f34971 Jun 25 22:05:35 sign-irb0101b setroubleshoot[414239]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 0d082c0b-5747-4f27-8c29-3b26dbaa841f Jun 25 22:05:35 sign-irb0101b setroubleshoot[414239]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.7xDozD. For complete SELinux messages run: sealert -l 1cd9bb63-ea96-435a-a583-029be5b09458 Jun 25 22:05:35 sign-irb0101b setroubleshoot[414239]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 1b3fcf59-e2ae-4b36-850f-754a27baf510 Jun 25 22:05:35 sign-irb0101b setroubleshoot[414239]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 352c534e-cc3a-404b-95bf-237e6c206a4c Jun 25 22:05:35 sign-irb0101b setroubleshoot[414239]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 013ff33b-bca7-4780-8a58-00363f669f12 == sign-irb1104 (10 distinct, 14 total) == Jun 25 22:07:43 sign-irb1104 setroubleshoot[413203]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 1d36dbf0-50cf-47b5-b093-4651c0351b39 [x2] Jun 25 22:07:43 sign-irb1104 setroubleshoot[413203]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l cef6bf6b-6d1c-42f9-bf91-cf51e45f654b [x2] Jun 25 22:07:43 sign-irb1104 setroubleshoot[413203]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l e352b985-78e4-4d2f-9472-5a8cf0991a6f Jun 25 22:07:43 sign-irb1104 setroubleshoot[413203]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.zOFPa1/repodata/repomd.xml. For complete SELinux messages run: sealert -l f315d337-6c32-40de-a00b-70397a64ad97 Jun 25 22:07:43 sign-irb1104 setroubleshoot[413203]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 0aa671aa-565a-415a-b124-1bf483d86e0c Jun 25 22:07:43 sign-irb1104 setroubleshoot[413203]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.zOFPa1. For complete SELinux messages run: sealert -l e5a53aed-1638-4ec1-83db-83ecc01d734c Jun 25 22:07:43 sign-irb1104 setroubleshoot[413203]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l f2d4cf11-d943-4907-a635-31e3d74e3be1 [x2] Jun 25 22:07:43 sign-irb1104 setroubleshoot[413203]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 293e8ac5-73e4-4de7-a102-6816b86e8217 Jun 25 22:07:43 sign-irb1104 setroubleshoot[413203]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 804a16a7-eda8-4534-bbe4-ba934ab98472 [x2] Jun 25 22:07:43 sign-irb1104 setroubleshoot[413203]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.ea7U49. For complete SELinux messages run: sealert -l e5a53aed-1638-4ec1-83db-83ecc01d734c == sign-irb1254 (9 distinct, 9 total) == Jun 25 22:05:22 sign-irb1254 setroubleshoot[413197]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 0c5e0115-75b9-46a1-b6da-29d3fa710680 Jun 25 22:05:22 sign-irb1254 setroubleshoot[413197]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l d02acd7b-51af-4c1f-997e-8a8095179245 Jun 25 22:05:22 sign-irb1254 setroubleshoot[413197]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 3f686ba3-1a90-4b18-891f-c0d559401506 Jun 25 22:05:22 sign-irb1254 setroubleshoot[413197]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.kh3HZk/repodata/repomd.xml. For complete SELinux messages run: sealert -l e4524d69-e865-4594-ada5-17f296dabf18 Jun 25 22:05:22 sign-irb1254 setroubleshoot[413197]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 627a6371-392d-4193-8f71-30a9e1b1dd9b Jun 25 22:05:22 sign-irb1254 setroubleshoot[413197]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.kh3HZk. For complete SELinux messages run: sealert -l c7bf172a-edbf-4095-a64e-34b56d775842 Jun 25 22:05:22 sign-irb1254 setroubleshoot[413197]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 4433549d-a885-4f08-8fe2-f7e3250a1b37 Jun 25 22:05:22 sign-irb1254 setroubleshoot[413197]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l d84c0dba-7036-4daa-8c80-e55cb0bf50e9 Jun 25 22:05:22 sign-irb1254 setroubleshoot[413197]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 522da75d-94f4-425a-a19c-af92d6c45ecb == sign-irb2194 (9 distinct, 9 total) == Jun 25 22:08:07 sign-irb2194 setroubleshoot[411562]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l abe86350-5bf8-4012-b162-3f660a805b28 Jun 25 22:08:07 sign-irb2194 setroubleshoot[411562]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l a61a8cbd-a34c-427f-9922-d0d218435f55 Jun 25 22:08:07 sign-irb2194 setroubleshoot[411562]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 3fcac52e-064a-436e-84c7-007886b65520 Jun 25 22:08:07 sign-irb2194 setroubleshoot[411562]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.QIuuhv/repodata/repomd.xml. For complete SELinux messages run: sealert -l 2decc44c-d7f2-45e7-b281-61b433360932 Jun 25 22:08:07 sign-irb2194 setroubleshoot[411562]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 3a392922-6539-4a75-a719-44ed24109320 Jun 25 22:08:07 sign-irb2194 setroubleshoot[411562]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.QIuuhv. For complete SELinux messages run: sealert -l 8e0c4d1c-5040-4424-9bc0-3a59ebe4a66d Jun 25 22:08:07 sign-irb2194 setroubleshoot[411562]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 1709499a-0ab9-480f-836a-3e82c7265e3e Jun 25 22:08:07 sign-irb2194 setroubleshoot[411562]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l d97997f1-03f5-492f-b04d-03c3223d38df Jun 25 22:08:07 sign-irb2194 setroubleshoot[411562]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 926a83b1-988c-4a1b-88e1-b3e1ea230f69 == sign-irb2254 (9 distinct, 9 total) == Jun 25 21:54:18 sign-irb2254 setroubleshoot[371529]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 8b99af19-9144-4116-bcbb-16baa33f479f Jun 25 21:54:18 sign-irb2254 setroubleshoot[371529]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 1ad62e7a-46b2-486d-9185-de0c94566833 Jun 25 21:54:18 sign-irb2254 setroubleshoot[371529]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l b58a13ac-5fc0-418a-a4d8-c6b774acbc56 Jun 25 21:54:18 sign-irb2254 setroubleshoot[371529]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.hhz0JI/repodata/repomd.xml. For complete SELinux messages run: sealert -l 74342933-6b92-4775-8b4f-50ce4922a165 Jun 25 21:54:18 sign-irb2254 setroubleshoot[371529]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 9d6b4639-6c73-4e77-ab73-2d5e23379034 Jun 25 21:54:18 sign-irb2254 setroubleshoot[371529]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.hhz0JI. For complete SELinux messages run: sealert -l 9d82f4d1-ed07-41e4-a834-e43dc840676d Jun 25 21:54:18 sign-irb2254 setroubleshoot[371529]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 6ae0abbc-71b3-4dda-b26f-a6c6ab3e1749 Jun 25 21:54:18 sign-irb2254 setroubleshoot[371529]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l fc3ad8e0-5ba1-4e81-8371-cba209600021 Jun 25 21:54:18 sign-irb2254 setroubleshoot[371529]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l afc426de-a9c5-44d3-8205-45aa769457f2 == submit26-b9-2 (18 distinct, 23 total) == Jun 25 21:42:38 submit26-b9-2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x6] Jun 25 21:45:16 submit26-b9-2 systemd-coredump[160400]: Process 160395 (public01) of user 1001 dumped core.#012#012Stack trace of thread 160395:#012#0 0x00000000004013dd center (public01 + 0x13dd)#012#1 0x00000000004011f5 main (public01 + 0x11f5)#012#2 0x00007ff91e02a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007ff91e02a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x0000000000401095 _start (public01 + 0x1095)#012ELF object binary architecture: AMD x86-64 Jun 25 21:45:16 submit26-b9-2 systemd-coredump[160413]: Process 160410 (public04) of user 1001 dumped core.#012#012Stack trace of thread 160410:#012#0 0x0000000000401419 center (public04 + 0x1419)#012#1 0x00000000004011f5 main (public04 + 0x11f5)#012#2 0x00007fdd9122a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007fdd9122a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x0000000000401095 _start (public04 + 0x1095)#012ELF object binary architecture: AMD x86-64 Jun 25 21:45:16 submit26-b9-2 systemd-coredump[160421]: Process 160418 (public05) of user 1001 dumped core.#012#012Stack trace of thread 160418:#012#0 0x00000000004013dd center (public05 + 0x13dd)#012#1 0x00000000004011f5 main (public05 + 0x11f5)#012#2 0x00007f144962a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007f144962a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x0000000000401095 _start (public05 + 0x1095)#012ELF object binary architecture: AMD x86-64 Jun 25 21:45:16 submit26-b9-2 systemd-coredump[160431]: Process 160428 (release01) of user 1001 dumped core.#012#012Stack trace of thread 160428:#012#0 0x00000000004013dd center (release01 + 0x13dd)#012#1 0x00000000004011f5 main (release01 + 0x11f5)#012#2 0x00007fab2a42a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007fab2a42a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x0000000000401095 _start (release01 + 0x1095)#012ELF object binary architecture: AMD x86-64 Jun 25 21:45:17 submit26-b9-2 systemd-coredump[160439]: Process 160436 (release02) of user 1001 dumped core.#012#012Stack trace of thread 160436:#012#0 0x00000000004013dd center (release02 + 0x13dd)#012#1 0x00000000004011f5 main (release02 + 0x11f5)#012#2 0x00007f18a962a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007f18a962a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x0000000000401095 _start (release02 + 0x1095)#012ELF object binary architecture: AMD x86-64 Jun 25 21:45:17 submit26-b9-2 systemd-coredump[160448]: Process 160444 (release03) of user 1001 dumped core.#012#012Stack trace of thread 160444:#012#0 0x0000000000401419 center (release03 + 0x1419)#012#1 0x00000000004011f5 main (release03 + 0x11f5)#012#2 0x00007f388782a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007f388782a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x0000000000401095 _start (release03 + 0x1095)#012ELF object binary architecture: AMD x86-64 Jun 25 21:45:17 submit26-b9-2 systemd-coredump[160456]: Process 160453 (release04) of user 1001 dumped core.#012#012Stack trace of thread 160453:#012#0 0x00000000004013dd center (release04 + 0x13dd)#012#1 0x00000000004011f5 main (release04 + 0x11f5)#012#2 0x00007f0fe402a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007f0fe402a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x0000000000401095 _start (release04 + 0x1095)#012ELF object binary architecture: AMD x86-64 Jun 25 21:45:17 submit26-b9-2 systemd-coredump[160464]: Process 160461 (release05) of user 1001 dumped core.#012#012Stack trace of thread 160461:#012#0 0x00000000004013f4 center (release05 + 0x13f4)#012#1 0x00000000004011f5 main (release05 + 0x11f5)#012#2 0x00007fef4e42a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007fef4e42a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x0000000000401095 _start (release05 + 0x1095)#012ELF object binary architecture: AMD x86-64 Jun 25 21:46:11 submit26-b9-2 systemd-coredump[160680]: Process 160677 (release15) of user 1001 dumped core.#012#012Stack trace of thread 160677:#012#0 0x000000000040136b remove_spaces (release15 + 0x136b)#012#1 0x00000000004011f5 main (release15 + 0x11f5)#012#2 0x00007f246182a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007f246182a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x0000000000401095 _start (release15 + 0x1095)#012ELF object binary architecture: AMD x86-64 Jun 25 21:46:13 submit26-b9-2 systemd-coredump[160824]: Process 160819 (public01) of user 1001 dumped core.#012#012Stack trace of thread 160819:#012#0 0x00000000004013dd center (public01 + 0x13dd)#012#1 0x00000000004011f5 main (public01 + 0x11f5)#012#2 0x00007f38e5a2a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007f38e5a2a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x0000000000401095 _start (public01 + 0x1095)#012ELF object binary architecture: AMD x86-64 Jun 25 21:46:13 submit26-b9-2 systemd-coredump[160837]: Process 160834 (public04) of user 1001 dumped core.#012#012Stack trace of thread 160834:#012#0 0x0000000000401419 center (public04 + 0x1419)#012#1 0x00000000004011f5 main (public04 + 0x11f5)#012#2 0x00007f5e2322a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007f5e2322a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x0000000000401095 _start (public04 + 0x1095)#012ELF object binary architecture: AMD x86-64 Jun 25 21:46:14 submit26-b9-2 systemd-coredump[160845]: Process 160842 (public05) of user 1001 dumped core.#012#012Stack trace of thread 160842:#012#0 0x00000000004013dd center (public05 + 0x13dd)#012#1 0x00000000004011f5 main (public05 + 0x11f5)#012#2 0x00007fd90462a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007fd90462a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x0000000000401095 _start (public05 + 0x1095)#012ELF object binary architecture: AMD x86-64 Jun 25 21:46:14 submit26-b9-2 systemd-coredump[160855]: Process 160852 (release01) of user 1001 dumped core.#012#012Stack trace of thread 160852:#012#0 0x00000000004013dd center (release01 + 0x13dd)#012#1 0x00000000004011f5 main (release01 + 0x11f5)#012#2 0x00007fdc32e2a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007fdc32e2a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x0000000000401095 _start (release01 + 0x1095)#012ELF object binary architecture: AMD x86-64 Jun 25 21:46:14 submit26-b9-2 systemd-coredump[160863]: Process 160860 (release02) of user 1001 dumped core.#012#012Stack trace of thread 160860:#012#0 0x00000000004013dd center (release02 + 0x13dd)#012#1 0x00000000004011f5 main (release02 + 0x11f5)#012#2 0x00007fd4ee02a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007fd4ee02a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x0000000000401095 _start (release02 + 0x1095)#012ELF object binary architecture: AMD x86-64 Jun 25 21:46:14 submit26-b9-2 systemd-coredump[160871]: Process 160868 (release03) of user 1001 dumped core.#012#012Stack trace of thread 160868:#012#0 0x0000000000401419 center (release03 + 0x1419)#012#1 0x00000000004011f5 main (release03 + 0x11f5)#012#2 0x00007ff87702a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007ff87702a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x0000000000401095 _start (release03 + 0x1095)#012ELF object binary architecture: AMD x86-64 Jun 25 21:46:14 submit26-b9-2 systemd-coredump[160879]: Process 160876 (release04) of user 1001 dumped core.#012#012Stack trace of thread 160876:#012#0 0x00000000004013dd center (release04 + 0x13dd)#012#1 0x00000000004011f5 main (release04 + 0x11f5)#012#2 0x00007f4b42e2a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007f4b42e2a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x0000000000401095 _start (release04 + 0x1095)#012ELF object binary architecture: AMD x86-64 Jun 25 21:46:14 submit26-b9-2 systemd-coredump[160887]: Process 160884 (release05) of user 1001 dumped core.#012#012Stack trace of thread 160884:#012#0 0x00000000004013f4 center (release05 + 0x13f4)#012#1 0x00000000004011f5 main (release05 + 0x11f5)#012#2 0x00007f6c2c42a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007f6c2c42a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x0000000000401095 _start (release05 + 0x1095)#012ELF object binary architecture: AMD x86-64 == submit26-clnb9 (20 distinct, 20 total) == Jun 25 21:42:45 submit26-clnb9 systemd-coredump[53938]: Process 53935 (release15) of user 1001 dumped core.#012#012Stack trace of thread 53935:#012#0 0x00000000004013b0 remove_spaces (release15 + 0x13b0)#012#1 0x0000000000401205 main (release15 + 0x1205)#012#2 0x00007ff50c82a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007ff50c82a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x00000000004010a5 _start (release15 + 0x10a5)#012ELF object binary architecture: AMD x86-64 Jun 25 21:56:42 submit26-clnb9 systemd-coredump[55469]: Process 55466 (release15) of user 1001 dumped core.#012#012Stack trace of thread 55466:#012#0 0x000000000040136b remove_spaces (release15 + 0x136b)#012#1 0x00000000004011f5 main (release15 + 0x11f5)#012#2 0x00007fc3cbe2a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007fc3cbe2a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x0000000000401095 _start (release15 + 0x1095)#012ELF object binary architecture: AMD x86-64 Jun 25 22:03:09 submit26-clnb9 systemd-coredump[56448]: Process 56445 (release15) of user 1001 dumped core.#012#012Stack trace of thread 56445:#012#0 0x00000000004013b0 remove_spaces (release15 + 0x13b0)#012#1 0x0000000000401205 main (release15 + 0x1205)#012#2 0x00007f672f42a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007f672f42a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x00000000004010a5 _start (release15 + 0x10a5)#012ELF object binary architecture: AMD x86-64 Jun 25 22:06:13 submit26-clnb9 systemd-coredump[56860]: Process 56855 (public01) of user 1001 dumped core.#012#012Stack trace of thread 56855:#012#0 0x00000000004013dd center (public01 + 0x13dd)#012#1 0x00000000004011f5 main (public01 + 0x11f5)#012#2 0x00007f999ec2a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007f999ec2a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x0000000000401095 _start (public01 + 0x1095)#012ELF object binary architecture: AMD x86-64 Jun 25 22:06:13 submit26-clnb9 systemd-coredump[56873]: Process 56870 (public04) of user 1001 dumped core.#012#012Stack trace of thread 56870:#012#0 0x0000000000401419 center (public04 + 0x1419)#012#1 0x00000000004011f5 main (public04 + 0x11f5)#012#2 0x00007f628322a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007f628322a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x0000000000401095 _start (public04 + 0x1095)#012ELF object binary architecture: AMD x86-64 Jun 25 22:06:14 submit26-clnb9 systemd-coredump[56880]: Process 56878 (public05) of user 1001 dumped core.#012#012Stack trace of thread 56878:#012#0 0x00000000004013dd center (public05 + 0x13dd)#012#1 0x00000000004011f5 main (public05 + 0x11f5)#012#2 0x00007fb5e522a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007fb5e522a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x0000000000401095 _start (public05 + 0x1095)#012ELF object binary architecture: AMD x86-64 Jun 25 22:06:14 submit26-clnb9 systemd-coredump[56891]: Process 56888 (release01) of user 1001 dumped core.#012#012Stack trace of thread 56888:#012#0 0x00000000004013dd center (release01 + 0x13dd)#012#1 0x00000000004011f5 main (release01 + 0x11f5)#012#2 0x00007f594422a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007f594422a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x0000000000401095 _start (release01 + 0x1095)#012ELF object binary architecture: AMD x86-64 Jun 25 22:06:14 submit26-clnb9 systemd-coredump[56898]: Process 56896 (release02) of user 1001 dumped core.#012#012Stack trace of thread 56896:#012#0 0x00000000004013dd center (release02 + 0x13dd)#012#1 0x00000000004011f5 main (release02 + 0x11f5)#012#2 0x00007fe54bc2a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007fe54bc2a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x0000000000401095 _start (release02 + 0x1095)#012ELF object binary architecture: AMD x86-64 Jun 25 22:06:15 submit26-clnb9 systemd-coredump[56907]: Process 56904 (release03) of user 1001 dumped core.#012#012Stack trace of thread 56904:#012#0 0x0000000000401419 center (release03 + 0x1419)#012#1 0x00000000004011f5 main (release03 + 0x11f5)#012#2 0x00007f56d3e2a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007f56d3e2a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x0000000000401095 _start (release03 + 0x1095)#012ELF object binary architecture: AMD x86-64 Jun 25 22:06:15 submit26-clnb9 systemd-coredump[56915]: Process 56912 (release04) of user 1001 dumped core.#012#012Stack trace of thread 56912:#012#0 0x00000000004013dd center (release04 + 0x13dd)#012#1 0x00000000004011f5 main (release04 + 0x11f5)#012#2 0x00007efc56a2a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007efc56a2a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x0000000000401095 _start (release04 + 0x1095)#012ELF object binary architecture: AMD x86-64 Jun 25 22:06:16 submit26-clnb9 systemd-coredump[56923]: Process 56920 (release05) of user 1001 dumped core.#012#012Stack trace of thread 56920:#012#0 0x00000000004013f4 center (release05 + 0x13f4)#012#1 0x00000000004011f5 main (release05 + 0x11f5)#012#2 0x00007f003ee2a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007f003ee2a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x0000000000401095 _start (release05 + 0x1095)#012ELF object binary architecture: AMD x86-64 Jun 25 22:06:26 submit26-clnb9 systemd-coredump[57308]: Process 57306 (release15) of user 1001 dumped core.#012#012Stack trace of thread 57306:#012#0 0x000000000040136b remove_spaces (release15 + 0x136b)#012#1 0x00000000004011f5 main (release15 + 0x11f5)#012#2 0x00007f385dc2a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007f385dc2a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x0000000000401095 _start (release15 + 0x1095)#012ELF object binary architecture: AMD x86-64 Jun 25 22:06:29 submit26-clnb9 systemd-coredump[57452]: Process 57448 (public01) of user 1001 dumped core.#012#012Stack trace of thread 57448:#012#0 0x00000000004013dd center (public01 + 0x13dd)#012#1 0x00000000004011f5 main (public01 + 0x11f5)#012#2 0x00007f8937c2a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007f8937c2a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x0000000000401095 _start (public01 + 0x1095)#012ELF object binary architecture: AMD x86-64 Jun 25 22:06:30 submit26-clnb9 systemd-coredump[57466]: Process 57463 (public04) of user 1001 dumped core.#012#012Stack trace of thread 57463:#012#0 0x0000000000401419 center (public04 + 0x1419)#012#1 0x00000000004011f5 main (public04 + 0x11f5)#012#2 0x00007fad7362a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007fad7362a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x0000000000401095 _start (public04 + 0x1095)#012ELF object binary architecture: AMD x86-64 Jun 25 22:06:30 submit26-clnb9 systemd-coredump[57473]: Process 57471 (public05) of user 1001 dumped core.#012#012Stack trace of thread 57471:#012#0 0x00000000004013dd center (public05 + 0x13dd)#012#1 0x00000000004011f5 main (public05 + 0x11f5)#012#2 0x00007fa94262a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007fa94262a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x0000000000401095 _start (public05 + 0x1095)#012ELF object binary architecture: AMD x86-64 Jun 25 22:06:30 submit26-clnb9 systemd-coredump[57484]: Process 57481 (release01) of user 1001 dumped core.#012#012Stack trace of thread 57481:#012#0 0x00000000004013dd center (release01 + 0x13dd)#012#1 0x00000000004011f5 main (release01 + 0x11f5)#012#2 0x00007f71d5c2a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007f71d5c2a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x0000000000401095 _start (release01 + 0x1095)#012ELF object binary architecture: AMD x86-64 Jun 25 22:06:31 submit26-clnb9 systemd-coredump[57492]: Process 57490 (release02) of user 1001 dumped core.#012#012Stack trace of thread 57490:#012#0 0x00000000004013dd center (release02 + 0x13dd)#012#1 0x00000000004011f5 main (release02 + 0x11f5)#012#2 0x00007f563122a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007f563122a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x0000000000401095 _start (release02 + 0x1095)#012ELF object binary architecture: AMD x86-64 Jun 25 22:06:31 submit26-clnb9 systemd-coredump[57500]: Process 57498 (release03) of user 1001 dumped core.#012#012Stack trace of thread 57498:#012#0 0x0000000000401419 center (release03 + 0x1419)#012#1 0x00000000004011f5 main (release03 + 0x11f5)#012#2 0x00007f9f7a62a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007f9f7a62a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x0000000000401095 _start (release03 + 0x1095)#012ELF object binary architecture: AMD x86-64 Jun 25 22:06:31 submit26-clnb9 systemd-coredump[57508]: Process 57506 (release04) of user 1001 dumped core.#012#012Stack trace of thread 57506:#012#0 0x00000000004013dd center (release04 + 0x13dd)#012#1 0x00000000004011f5 main (release04 + 0x11f5)#012#2 0x00007fe03f62a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007fe03f62a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x0000000000401095 _start (release04 + 0x1095)#012ELF object binary architecture: AMD x86-64 Jun 25 22:06:32 submit26-clnb9 systemd-coredump[57517]: Process 57514 (release05) of user 1001 dumped core.#012#012Stack trace of thread 57514:#012#0 0x00000000004013f4 center (release05 + 0x13f4)#012#1 0x00000000004011f5 main (release05 + 0x11f5)#012#2 0x00007f63a162a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007f63a162a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x0000000000401095 _start (release05 + 0x1095)#012ELF object binary architecture: AMD x86-64 == submit9 (4 distinct, 24 total) == Jun 25 21:45:24 submit9 setroubleshoot[583850]: SELinux is preventing /usr/bin/who from read access on the directory userdb. For complete SELinux messages run: sealert -l 1f0cc971-1ec4-4de6-a524-b76fdd7c302d [x6] Jun 25 21:45:24 submit9 setroubleshoot[583850]: SELinux is preventing /usr/bin/who from write access on the sock_file io.systemd.DynamicUser. For complete SELinux messages run: sealert -l e1c69061-f008-4cd8-bfa9-7e51dc1a26dd [x6] Jun 25 21:45:24 submit9 setroubleshoot[583850]: failed to retrieve rpm info for path '/run/systemd/userdb/io.systemd.DynamicUser': [x6] Jun 25 21:45:24 submit9 setroubleshoot[583850]: SELinux is preventing /usr/bin/who from connectto access on the unix_stream_socket /run/systemd/userdb/io.systemd.DynamicUser. For complete SELinux messages run: sealert -l de091f41-e6f5-4682-beb5-b77b06eac892 [x6] == test-ipv6 (20 distinct, 42 total) == Jun 25 21:44:16 test-ipv6 setroubleshoot[559879]: failed to retrieve rpm info for path '/srv/falling-sky/content/images/.htaccess': [x2] Jun 25 21:44:18 test-ipv6 setroubleshoot[559879]: SELinux is preventing /usr/sbin/httpd from read access on the file /srv/falling-sky/content/images/.htaccess. For complete SELinux messages run: sealert -l 1eadb8d1-d675-49ba-aa3c-c5f6840220ac [x2] Jun 25 21:44:20 test-ipv6 setroubleshoot[559879]: SELinux is preventing /usr/sbin/httpd from open access on the file /srv/falling-sky/content/images/.htaccess. For complete SELinux messages run: sealert -l 02666298-fd6b-40d2-9b99-5ce0e76f618f [x2] Jun 25 21:44:21 test-ipv6 setroubleshoot[559879]: SELinux is preventing /usr/sbin/httpd from getattr access on the file /srv/falling-sky/content/images/.htaccess. For complete SELinux messages run: sealert -l 2f8e87e8-46b8-43c6-af58-546a054437ba Jun 25 21:46:02 test-ipv6 setroubleshoot[560215]: failed to retrieve rpm info for path '/srv/falling-sky/content/site/config.js': [x5] Jun 25 21:46:04 test-ipv6 setroubleshoot[560215]: SELinux is preventing /usr/sbin/httpd from getattr access on the file /srv/falling-sky/content/site/config.js. For complete SELinux messages run: sealert -l 2f8e87e8-46b8-43c6-af58-546a054437ba [x5] Jun 25 21:46:06 test-ipv6 setroubleshoot[560215]: SELinux is preventing /usr/sbin/httpd from read access on the file /srv/falling-sky/content/site/config.js. For complete SELinux messages run: sealert -l 1eadb8d1-d675-49ba-aa3c-c5f6840220ac [x5] Jun 25 21:46:07 test-ipv6 setroubleshoot[560215]: SELinux is preventing /usr/sbin/httpd from open access on the file /srv/falling-sky/content/site/config.js. For complete SELinux messages run: sealert -l 02666298-fd6b-40d2-9b99-5ce0e76f618f [x5] Jun 25 21:46:09 test-ipv6 setroubleshoot[560215]: SELinux is preventing /usr/sbin/httpd from map access on the file /srv/falling-sky/content/site/config.js. For complete SELinux messages run: sealert -l 4950ddcc-c9fc-46d0-9516-46d03a249533 [x4] Jun 25 21:46:25 test-ipv6 setroubleshoot[560246]: failed to retrieve rpm info for path '/srv/falling-sky/content/site/dept_logo.png': Jun 25 21:46:27 test-ipv6 setroubleshoot[560246]: SELinux is preventing /usr/sbin/httpd from getattr access on the file /srv/falling-sky/content/site/dept_logo.png. For complete SELinux messages run: sealert -l 2f8e87e8-46b8-43c6-af58-546a054437ba Jun 25 21:46:27 test-ipv6 setroubleshoot[560246]: failed to retrieve rpm info for path '/srv/falling-sky/content/images/hires_ok.png': Jun 25 21:46:28 test-ipv6 setroubleshoot[560246]: SELinux is preventing /usr/sbin/httpd from getattr access on the file /srv/falling-sky/content/images/hires_ok.png. For complete SELinux messages run: sealert -l 2f8e87e8-46b8-43c6-af58-546a054437ba Jun 25 21:46:33 test-ipv6 setroubleshoot[560246]: SELinux is preventing /usr/sbin/httpd from map access on the file /srv/falling-sky/content/images/hires_ok.png. For complete SELinux messages run: sealert -l 4950ddcc-c9fc-46d0-9516-46d03a249533 Jun 25 21:59:02 test-ipv6 setroubleshoot[562529]: failed to retrieve rpm info for path '/srv/falling-sky/content/images-nc/knob_green.png': Jun 25 21:59:04 test-ipv6 setroubleshoot[562529]: SELinux is preventing /usr/sbin/httpd from getattr access on the file /srv/falling-sky/content/images-nc/knob_green.png. For complete SELinux messages run: sealert -l 2f8e87e8-46b8-43c6-af58-546a054437ba Jun 25 21:59:04 test-ipv6 setroubleshoot[562529]: failed to retrieve rpm info for path '/srv/falling-sky/content/images-nc/.htaccess': Jun 25 21:59:05 test-ipv6 setroubleshoot[562529]: SELinux is preventing /usr/sbin/httpd from read access on the file /srv/falling-sky/content/images-nc/.htaccess. For complete SELinux messages run: sealert -l 1eadb8d1-d675-49ba-aa3c-c5f6840220ac Jun 25 21:59:07 test-ipv6 setroubleshoot[562529]: SELinux is preventing /usr/sbin/httpd from open access on the file /srv/falling-sky/content/images-nc/.htaccess. For complete SELinux messages run: sealert -l 02666298-fd6b-40d2-9b99-5ce0e76f618f Jun 25 21:59:08 test-ipv6 setroubleshoot[562529]: SELinux is preventing /usr/sbin/httpd from map access on the file /srv/falling-sky/content/images-nc/knob_green.png. For complete SELinux messages run: sealert -l 4950ddcc-c9fc-46d0-9516-46d03a249533 == tma-0 (1 distinct, 2 total) == Jun 25 21:47:53 tma-0 sshd[31687]: error: PAM: Authentication failure for root from 46.249.98.62 [x2] == tulgey.cs.umd.edu (21 distinct, 42 total) == Jun 25 21:49:54 tulgey.cs.umd.edu setroubleshoot[809542]: SELinux is preventing /usr/sbin/httpd from read access on the lnk_file current. For complete SELinux messages run: sealert -l 203ed425-651d-4233-a284-dd82547d2f8b Jun 25 21:49:54 tulgey.cs.umd.edu setroubleshoot[809542]: failed to retrieve rpm info for path '/var/www/deployment/helpdesk.cs.umd.edu/current': [x3] Jun 25 21:49:54 tulgey.cs.umd.edu setroubleshoot[809542]: SELinux is preventing /usr/sbin/httpd from getattr access on the lnk_file /var/www/deployment/helpdesk.cs.umd.edu/current. For complete SELinux messages run: sealert -l eada131d-2e74-4c13-b242-d8a5551a9c46 [x3] Jun 25 21:49:54 tulgey.cs.umd.edu setroubleshoot[809542]: SELinux is preventing /usr/sbin/httpd from read access on the file .htaccess. For complete SELinux messages run: sealert -l 6a9f0792-77d0-4f0d-a39f-59230488130d [x5] Jun 25 21:49:54 tulgey.cs.umd.edu setroubleshoot[809542]: failed to retrieve rpm info for path '/var/www/deployment/helpdesk.cs.umd.edu/releases/20260625231602-9/public/.htaccess': [x5] Jun 25 21:49:54 tulgey.cs.umd.edu setroubleshoot[809542]: SELinux is preventing /usr/sbin/httpd from open access on the file /var/www/deployment/helpdesk.cs.umd.edu/releases/20260625231602-9/public/.htaccess. For complete SELinux messages run: sealert -l 6ad20759-c8e7-4159-a03e-51fb006cd2ee [x6] Jun 25 21:50:38 tulgey.cs.umd.edu setroubleshoot[810273]: failed to retrieve rpm info for path '/var/www/deployment/helpdesk.cs.umd.edu/current/public/assets/vendor/css/bootstrap.min.css': [x2] Jun 25 21:50:39 tulgey.cs.umd.edu setroubleshoot[810273]: SELinux is preventing /usr/sbin/httpd from read access on the lnk_file /var/www/deployment/helpdesk.cs.umd.edu/current/public/assets/vendor/css/bootstrap.min.css. For complete SELinux messages run: sealert -l 203ed425-651d-4233-a284-dd82547d2f8b [x2] Jun 25 21:50:39 tulgey.cs.umd.edu setroubleshoot[810273]: failed to retrieve rpm info for path '/var/www/deployment/helpdesk.cs.umd.edu/releases/20260625231602-9/public/assets/vendor/css/bootstrap.min.css': Jun 25 21:50:39 tulgey.cs.umd.edu setroubleshoot[810273]: SELinux is preventing /usr/sbin/httpd from map access on the file /var/www/deployment/helpdesk.cs.umd.edu/releases/20260625231602-9/public/assets/vendor/css/bootstrap.min.css. For complete SELinux messages run: sealert -l 640d002a-4bf8-42eb-9f2a-1997b2808a36 Jun 25 21:54:08 tulgey.cs.umd.edu setroubleshoot[810564]: failed to retrieve rpm info for path '/var/www/deployment/helpdesk.cs.umd.edu/current/public': [x2] Jun 25 21:54:09 tulgey.cs.umd.edu setroubleshoot[810564]: SELinux is preventing /usr/sbin/httpd from read access on the lnk_file /var/www/deployment/helpdesk.cs.umd.edu/current/public/. For complete SELinux messages run: sealert -l 203ed425-651d-4233-a284-dd82547d2f8b [x2] Jun 25 21:54:58 tulgey.cs.umd.edu setroubleshoot[810638]: failed to retrieve rpm info for path '/var/www/deployment/helpdesk.cs.umd.edu/current/public/assets/vendor/css/ie10-viewport-bug-workaround.css': Jun 25 21:54:59 tulgey.cs.umd.edu setroubleshoot[810638]: SELinux is preventing /usr/sbin/httpd from read access on the lnk_file /var/www/deployment/helpdesk.cs.umd.edu/current/public/assets/vendor/css/ie10-viewport-bug-workaround.css. For complete SELinux messages run: sealert -l 203ed425-651d-4233-a284-dd82547d2f8b Jun 25 21:54:59 tulgey.cs.umd.edu setroubleshoot[810638]: failed to retrieve rpm info for path '/var/www/deployment/helpdesk.cs.umd.edu/current/public/assets/vendor/js/ie10-viewport-bug-workaround.js': Jun 25 21:54:59 tulgey.cs.umd.edu setroubleshoot[810638]: SELinux is preventing /usr/sbin/httpd from read access on the lnk_file /var/www/deployment/helpdesk.cs.umd.edu/current/public/assets/vendor/js/ie10-viewport-bug-workaround.js. For complete SELinux messages run: sealert -l 203ed425-651d-4233-a284-dd82547d2f8b Jun 25 21:54:59 tulgey.cs.umd.edu setroubleshoot[810638]: failed to retrieve rpm info for path '/var/www/deployment/helpdesk.cs.umd.edu/releases/20260625231602-9/public/assets/vendor/css/ie10-viewport-bug-workaround.css': Jun 25 21:54:59 tulgey.cs.umd.edu setroubleshoot[810638]: SELinux is preventing /usr/sbin/httpd from map access on the file /var/www/deployment/helpdesk.cs.umd.edu/releases/20260625231602-9/public/assets/vendor/css/ie10-viewport-bug-workaround.css. For complete SELinux messages run: sealert -l 640d002a-4bf8-42eb-9f2a-1997b2808a36 Jun 25 22:04:23 tulgey.cs.umd.edu setroubleshoot[813159]: failed to retrieve rpm info for path '/var/www/deployment/helpdesk.cs.umd.edu/current/public/faq/connecting/dns.html': Jun 25 22:12:47 tulgey.cs.umd.edu setroubleshoot[815497]: failed to retrieve rpm info for path '/var/www/deployment/helpdesk.cs.umd.edu/releases/20260625231602-9/public/faq/index.html': Jun 25 22:12:47 tulgey.cs.umd.edu setroubleshoot[815497]: SELinux is preventing /usr/sbin/httpd from map access on the file /var/www/deployment/helpdesk.cs.umd.edu/releases/20260625231602-9/public/faq/index.html. For complete SELinux messages run: sealert -l 640d002a-4bf8-42eb-9f2a-1997b2808a36 == vault (4 distinct, 23 total) == Jun 25 21:45:27 vault setroubleshoot[266555]: SELinux is preventing /usr/bin/who from read access on the directory userdb. For complete SELinux messages run: sealert -l 35083630-532f-451c-8d1d-4b4b4517edf9 [x6] Jun 25 21:45:28 vault setroubleshoot[266555]: SELinux is preventing /usr/bin/who from write access on the sock_file io.systemd.DynamicUser. For complete SELinux messages run: sealert -l 993bde54-5fcf-4b78-96b9-22c6e5b5a743 [x5] Jun 25 21:45:28 vault setroubleshoot[266555]: failed to retrieve rpm info for path '/run/systemd/userdb/io.systemd.DynamicUser': [x6] Jun 25 21:45:28 vault setroubleshoot[266555]: SELinux is preventing /usr/bin/who from connectto access on the unix_stream_socket /run/systemd/userdb/io.systemd.DynamicUser. For complete SELinux messages run: sealert -l f18d5bb6-bbab-4d53-8e51-c8bef4b25931 [x6] == vpn00a.cs.umd.edu (12 distinct, 15 total) == Jun 25 21:44:28 vpn00a.cs.umd.edu setroubleshoot[511648]: failed to retrieve rpm info for path '/etc/puppetlabs/puppet/ssl/crl.pem': [x2] Jun 25 21:44:29 vpn00a.cs.umd.edu setroubleshoot[511648]: SELinux is preventing /usr/sbin/openvpn from search access on the directory /etc/puppetlabs/puppet/ssl/crl.pem. For complete SELinux messages run: sealert -l dbbce48f-aa29-4cd6-baf6-36495c5a3386 [x2] Jun 25 21:44:29 vpn00a.cs.umd.edu setroubleshoot[511648]: SELinux is preventing /usr/sbin/openvpn from getattr access on the file /etc/puppetlabs/puppet/ssl/crl.pem. For complete SELinux messages run: sealert -l 367ce461-e52e-4bb9-a719-8ebadba7de54 [x2] Jun 25 21:52:31 vpn00a.cs.umd.edu setroubleshoot[513100]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l b1083975-941f-4494-8ebc-028802b1174a Jun 25 21:52:31 vpn00a.cs.umd.edu setroubleshoot[513100]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 145c2d89-d3db-41a4-a3c1-e7e25adf8f52 Jun 25 21:52:31 vpn00a.cs.umd.edu setroubleshoot[513100]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l cb280e11-f1fe-43c5-a59f-757ad9e3adfb Jun 25 21:52:31 vpn00a.cs.umd.edu setroubleshoot[513100]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.ZQk9NO/repodata/repomd.xml. For complete SELinux messages run: sealert -l fa850be6-dce5-4665-bec3-6e431ce41ea0 Jun 25 21:52:31 vpn00a.cs.umd.edu setroubleshoot[513100]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l c672987b-a115-4ab8-9aed-8153861e1af5 Jun 25 21:52:31 vpn00a.cs.umd.edu setroubleshoot[513100]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.ZQk9NO. For complete SELinux messages run: sealert -l 5297e3bb-6e58-4a07-8a24-6e57932e5af0 Jun 25 21:52:31 vpn00a.cs.umd.edu setroubleshoot[513100]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 8da41a29-3f8f-447b-aced-b193c910386b Jun 25 21:52:31 vpn00a.cs.umd.edu setroubleshoot[513100]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 78e48822-2556-4079-975f-19fbf6c59d0a Jun 25 21:52:31 vpn00a.cs.umd.edu setroubleshoot[513100]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 61b6b4f6-7493-42c3-900c-fbf2aeef7221 == zebatinsky.cs.umd.edu (11 distinct, 11 total) == Jun 25 21:41:38 zebatinsky.cs.umd.edu setroubleshoot[854283]: SELinux is preventing pdns/comm-main from name_bind access on the udp_socket port 13452. For complete SELinux messages run: sealert -l 7f48f302-3d49-4c48-bb8a-14e306e0c380 Jun 25 21:44:38 zebatinsky.cs.umd.edu setroubleshoot[854592]: SELinux is preventing pdns/comm-main from name_bind access on the udp_socket port 12732. For complete SELinux messages run: sealert -l 7f48f302-3d49-4c48-bb8a-14e306e0c380 Jun 25 21:46:38 zebatinsky.cs.umd.edu setroubleshoot[855341]: SELinux is preventing pdns/comm-main from name_bind access on the udp_socket port 12424. For complete SELinux messages run: sealert -l 7f48f302-3d49-4c48-bb8a-14e306e0c380 Jun 25 21:47:38 zebatinsky.cs.umd.edu setroubleshoot[855381]: SELinux is preventing pdns/comm-main from name_bind access on the udp_socket port 10350. For complete SELinux messages run: sealert -l 7f48f302-3d49-4c48-bb8a-14e306e0c380 Jun 25 21:50:38 zebatinsky.cs.umd.edu setroubleshoot[855832]: SELinux is preventing pdns/comm-main from name_bind access on the udp_socket port 13977. For complete SELinux messages run: sealert -l 7f48f302-3d49-4c48-bb8a-14e306e0c380 Jun 25 21:53:38 zebatinsky.cs.umd.edu setroubleshoot[855892]: SELinux is preventing pdns/comm-main from name_bind access on the udp_socket port 15276. For complete SELinux messages run: sealert -l 7f48f302-3d49-4c48-bb8a-14e306e0c380 Jun 25 21:56:37 zebatinsky.cs.umd.edu setroubleshoot[856901]: SELinux is preventing pdns/comm-main from name_bind access on the udp_socket port 11499. For complete SELinux messages run: sealert -l 7f48f302-3d49-4c48-bb8a-14e306e0c380 Jun 25 22:05:37 zebatinsky.cs.umd.edu setroubleshoot[858441]: SELinux is preventing pdns/comm-main from name_bind access on the udp_socket port 17436. For complete SELinux messages run: sealert -l 7f48f302-3d49-4c48-bb8a-14e306e0c380 Jun 25 22:08:40 zebatinsky.cs.umd.edu setroubleshoot[858502]: SELinux is preventing pdns/comm-main from name_bind access on the udp_socket port 15629. For complete SELinux messages run: sealert -l 7f48f302-3d49-4c48-bb8a-14e306e0c380 Jun 25 22:11:40 zebatinsky.cs.umd.edu setroubleshoot[858955]: SELinux is preventing pdns/comm-main from name_bind access on the udp_socket port 17273. For complete SELinux messages run: sealert -l 7f48f302-3d49-4c48-bb8a-14e306e0c380 Jun 25 22:14:41 zebatinsky.cs.umd.edu setroubleshoot[859295]: SELinux is preventing pdns/comm-main from name_bind access on the udp_socket port 14916. For complete SELinux messages run: sealert -l 7f48f302-3d49-4c48-bb8a-14e306e0c380