On Tuesday, June 16, 2015, Chris Warrick <kwpol...@gmail.com> wrote: > On Tue, Jun 16, 2015 at 8:14 PM, Néstor Boscán <nesto...@gmail.com > <javascript:;>> wrote: > > I tried that but it didn't work. > > > > I had to change /etc/selinux/config and reboot to make it work. It > would be > > nice if the wsgi module generated some log that explains why you get the > > 403. There are several posibilities. > > Well, that’s not wsgi’s fault. There was a “permission denied” error, > that’s everything wsgi ever knew. > As a RHEL sysadmin, you should know that this is most likely caused by > braindead syslinux and to read the audit log. > > PS. please don’t top-post. > > -- > Chris Warrick <https://chriswarrick.com/> > PGP: 5EAAEA16 >
Yes but it could log which os file was it trying to access. Thanks for all the replies. Regards, Nestor
-- https://mail.python.org/mailman/listinfo/python-list
