G J Piper
Regular Pleskian
After upgrading to Obsidian today, I have an issue appearing in the logs over and over:
I followed the procedure to generate a local policy module in SELinux for this as it instructs, but it doesn't seem to stop the log entries. Tried restarting the server afterward -- no difference. I have SELinux runniong in "premissive" mode for now just so no unexpected trouble comes along due to these.
I don't seem to have any other symptoms I can see, but the log entries by the hundreds are annoying.
Any ideas?
Code:
Oct 22 13:17:38 pcs-plesk-centos7-web-vm setroubleshoot: SELinux is preventing sh from execute access on the file ldconfig. For complete SELinux messages run: sealert -l 61e5cd70-f069-439d-9e7d-ea412d1db487
Oct 22 13:17:38 pcs-plesk-centos7-web-vm python: SELinux is preventing sh from execute access on the file ldconfig.#012#012***** Plugin catchall (100. confidence) suggests **************************#012#012If you believe that sh should be allowed execute access on the ldconfig file by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'sh' --raw | audit2allow -M my-sh#012# semodule -i my-sh.pp#012
I followed the procedure to generate a local policy module in SELinux for this as it instructs, but it doesn't seem to stop the log entries. Tried restarting the server afterward -- no difference. I have SELinux runniong in "premissive" mode for now just so no unexpected trouble comes along due to these.
I don't seem to have any other symptoms I can see, but the log entries by the hundreds are annoying.
Any ideas?