Actually, I have already done this in part before.

Can you set:

    LogLevel debug

for the server.

And also add:

    WSGIVerboseLogging On

Look for messages of form:

        if (daemon->group->server) {
            if (wsgi_server_config->verbose_debugging) {
                ap_log_error(APLOG_MARK, APLOG_DEBUG, 0, wsgi_server,
                             "mod_wsgi (pid=%d): Process '%s' logging to "
                             "'%s'.", getpid(), daemon->group->name,
                             daemon->group->server->server_hostname);
            }

            wsgi_server = daemon->group->server;
        }
        else {
            if (wsgi_server_config->verbose_debugging) {
                ap_log_error(APLOG_MARK, APLOG_DEBUG, 0, wsgi_server,
                             "mod_wsgi (pid=%d): Process '%s' forced to log "
                             "to '%s'.", getpid(), daemon->group->name,
                             wsgi_server->server_hostname);
            }
        }

and explain to me what global ServerName is, then what VirtualHost have, and 
what ServerName in those and which has the WSGI application in it.

I may have to add more debug, but that for a start will help me start to 
understand.

Graham

> On 29 Jun 2018, at 12:15 pm, Graham Dumpleton <[email protected]> 
> wrote:
> 
> Only thing I can think to do at this point it create a branch of mod_wsgi and 
> give you access to a version which adds lots of debug output into code 
> starting around:
> 
> https://github.com/GrahamDumpleton/mod_wsgi/blob/develop/src/server/mod_wsgi.c#L10276
>  
> <https://github.com/GrahamDumpleton/mod_wsgi/blob/develop/src/server/mod_wsgi.c#L10276>
> 
> This is where some of the decisions about where logging should go is made. If 
> can see what it finds when doing that, it may help to understand what is 
> going on.
> 
> Graham
> 
>> On 28 Jun 2018, at 2:36 pm, Graham Dumpleton <[email protected] 
>> <mailto:[email protected]>> wrote:
>> 
>> Haven't had a chance to look at it again yet, but am wondering whether it is 
>> the '<VirtualHost *>' in particular.
>> 
>> If you comment out just that VirtualHost, what happens?
>> 
>> It is not normal that you wouldn't have a port number. So if you only have 
>> '<VirtualHost *:80>' entries will be surprised if see an issue.
>> 
>> Are you still using an IP in other VirtualHost's though?
>> 
>>> On 28 Jun 2018, at 2:33 pm, 'Joshua Harwood' via modwsgi 
>>> <[email protected] <mailto:[email protected]>> wrote:
>>> 
>>> I setup an Ubuntu box on AWS to test if other OSes have the same issue and 
>>> I was able to duplicate the issue using the default Ubuntu apache2 package 
>>> and compiled fresh install of python 3.6 / mod_wsgi 4.6.4.
>>> I can share the login key if you want to check it out personally.
>>> 
>>> -- 
>>> 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] 
>>> <mailto:[email protected]>.
>>> To post to this group, send email to [email protected] 
>>> <mailto:[email protected]>.
>>> Visit this group at https://groups.google.com/group/modwsgi 
>>> <https://groups.google.com/group/modwsgi>.
>>> For more options, visit https://groups.google.com/d/optout 
>>> <https://groups.google.com/d/optout>.
>> 
> 

-- 
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.

Reply via email to