> On 13 Sep 2016, at 3:17 AM, Huw Jones <[email protected]> wrote:
> 
> Hi there,
> 
> I'm trying to figure out where to start figuring out what this issue is. I 
> can see from the error logs the following every ten minutes:
> 
> [Mon Sep 12 18:47:20 2016] [info] mod_wsgi (pid=8415): Process 
> 'localhost:8080' has died, deregister and restart it.
> [Mon Sep 12 18:47:20 2016] [info] mod_wsgi (pid=8415): Process 
> 'localhost:8080' terminated by signal 9
> [Mon Sep 12 18:47:20 2016] [info] mod_wsgi (pid=8415): Process 
> 'localhost:8080' has been deregistered and will no longer be monitored.
> [Mon Sep 12 18:47:20 2016] [info] mod_wsgi (pid=8479): Starting process 
> 'localhost:8080' with uid=48, gid=48 and threads=5.
> [Mon Sep 12 18:47:20 2016] [info] mod_wsgi (pid=8479): Python home 
> /opt/virtualenv/venv.
> [Mon Sep 12 18:47:20 2016] [info] mod_wsgi (pid=8479): Initializing Python.
> [Mon Sep 12 18:47:20 2016] [info] mod_wsgi (pid=8479): Attach interpreter ''.
> [Mon Sep 12 18:47:20 2016] [info] mod_wsgi (pid=8479): Imported 'mod_wsgi'.
> [Mon Sep 12 18:47:20 2016] [info] mod_wsgi (pid=8479, 
> process='localhost:8080', application=''): Loading WSGI script 
> '/tmp/mod_wsgi-localhost:8080:0/handler.wsgi'.
> [Mon Sep 12 18:48:00 2016] [error] 
> /opt/virtualenv/venv/lib/python2.7/site-packages/sqlalchemy/engine/default.py:475:
>  SAWarning: Unicode type received non-unicode bind param value.
> [Mon Sep 12 18:48:00 2016] [error]   processors[key](compiled_params[key])
> [Mon Sep 12 18:57:43 2016] [info] mod_wsgi (pid=8395): Process 
> 'localhost:8080' has died, deregister and restart it.

I need to see a longer section of the logs as not enough there to correlate 
messages based on display pid.

The termination by signal 9 instance implies that something external explicitly 
sent the process that signal as neither Apache nor mod_wsgi will ever generate 
a SIGKILL.

Are you running some external monitoring process on your Linux distro which 
kills processes if they use up more than a certain about of memory?

> I'm running mod_wsgi-express from an init script with the following command:
> 
> source activate;mod_wsgi-express start-server --user apache --group apache 
> --port 8080 --socket-timeout 600 --log-level info --processes 4 
> --log-directory /var/log/app --access-log --startup-log --rotate-logs 
> /opt/sites/app/rest.wsgi > /dev/null 2>&1 & echo $!;deactivate
> 
> Just wondering where I should start to debug this. I'm also wondering whether 
> I need to apply something like the WSGIApplicationGroup to be GLOBAL or 
> something?

When you using mod_wsgi-express is always use the main interpreter context so 
not need to set that. You can see above how application is ‘’. The empty string 
is what you see when using ‘%{GLOBAL}’.

Graham

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