On Saturday, September 10, 2016 at 5:24:33 PM UTC-6, Graham Dumpleton wrote: > > > On 11 Sep 2016, at 10:50 AM, Joshua Harwood <[email protected] > <javascript:>> wrote: > > > This error generally relates to broken mod_rewrite rules and nothing to do >> with mod_wsgi. >> >> How are mod_rewrite rules, or other Apache directives for redirection >> being used elsewhere in the Apache configuration? >> >> Also, are extended multi language error pages enabled in Apache? There >> are the ErrorDocument directives. >> >> Graham >> >> > Mod_rewrite is being used by cpanel for leech protection and > webmail/cpanel/whm redirects. > > Looking through the httpd.conf it looks as if ErrorDocument directives are > enabled. > > My issue wasn't the message in the virtual host logs but the lack of > things being sent to the virtual host log. > > >> This is better written as: >> >> WSGIDaemonProcess fina.dev.harwoodspike.com user=devharwoodspike >> group=devharwoodspike processes=3 threads=3 >> python-path=/home/devharwoodspike/python-apps/fina/ >> python-home=/home/devharwoodspike/python-apps/virtpython >> display-name=FINA-DEV >> >> The python-home option is what you should use to refer to a Python >> virtual environment. >> >> You should also have: >> >> WSGIApplicationGroup %{GLOBAL} >> >> when delegating only the one application to the daemon process group to >> avoid issues with some third party Python extension modules that aren’t >> implemented correctly so as to work in Python sub interpreters. >> >> Graham >> >> > Thanks for the tip I have updated my configurations with your suggestions. > > Also since I recompiled with r->server = wsgi_server; I have not been able > to re-produce the issue. I even tried re-downloading and recompiling > without any changes and it is still working. > > > Can you clarify the outcome here? > > Are you saying that with the latest mod_wsgi 4.5.6 that it is working as > you expect now without needing to patch the mod_wsgi code? > > My reason for not pursuing the logging issue initially was because I did > want to verify whether it did occur with the very latest as I knew the > logging code had been changed. > > Thanks. > > Graham >
I am not sure I can really clarify as the outcome is rather confusing. When I original compiled 4.5.6, it was still not outputting some of the trackback and debug statements to the virtual host logs. When I recompiled with the modifications I mention above it worked but whenever I recompiled after the modifications (even when I did a fresh download) it continued to work. Either some library updated or I did something that I don't remember doing, or the server knew it was my birthday and was giving me a gift. I have been trying to figure out what changed but I am still at a lose about how this issue resolved itself. If I figure anything out then I will let you know, sorry if this was a waste of time. -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/modwsgi. For more options, visit https://groups.google.com/d/optout.
