Hey Jonathon, SELinux is on permissive. Checked that early on. :)
The biggest clue for me seems to be that if we open up the "/>" to Allow by default things work. Otherwise they don't.
Leam
On 10/28/18 9:26 AM, Jonathon Koyle wrote:
It may be getting denied by SELinux, I suspect the label on
Hi everyone,
I'm stumbled upon some strange issues with the apache2. At first some
facts about the environment there the apache2 was running:
* Virtuozzo 7 with a stripped down version of Ubuntu 18.04 as container OS.
* The thread/processes limit is set to 1500 for the container.
* The apache2
I missed a slash in that regular expression (/.*)? rather than (.*)?
On Sun, Oct 28, 2018, 07:26 Jonathon Koyle wrote:
> It may be getting denied by SELinux, I suspect the label on your aliased
> directory die not allow httpd access. You will likely need to look into
> semanage, something like
It may be getting denied by SELinux, I suspect the label on your aliased
directory die not allow httpd access. You will likely need to look into
semanage, something like this may do what you need, but I'm not an expert
at SELinux myself... redhat provides some explanation here:
https://access.redh
