2009/11/27 atomekk <[email protected]>:
>> So, believe you are just seeing the normal Apache server child
>> processes, which as I saw can come and go and change in number anyway.
>>
>> Graham
>
> As i'm running wsgi daemon under specified user 'cms' and i got two
> instances of it so i guess top -u cms shows correct processes:
>
> top -u cms
> 11195 cms       19   0  104m  13m 3904 S  0.0  0.4   0:00.00 httpd
> 12777 cms       19   0  124m  37m  12m S  0.0  1.0   0:01.33 httpd
>
> and
>
> ps auxwww | grep wsgi
> cms      11195  0.0  0.3 106560 14272 ?        Sl   10:05   0:00
> (wsgi:tpnssl)
> cms      12777  1.9  0.9 127232 38656 ?        Sl   10:18   0:01
> (wsgi:gleaxssl)

Which shows you have another daemon process group called 'gleaxssl'.

So, one process per daemon process group.

> top and ps auxwww shows the same PID numbers. Maybe i'm understand it
> wrong :/.

No you aren't confused, top doesn't show the overridden names. The
htop on some systems may, but top doesn't. And BSD derived system (or
'ps' program to be correct), which show the overridden name.

They are the same processes.

> Anyway after today error in Apache logs i mentioned in first post,
> website was down till i restarted apache again.

If a daemon process dies, then one will automatically be restarted in its place.

> Maybe i should remove that inactivity-timeout directive ?

The inactivity timeout doesn't make the process go away, it just means
that it will shutdown and restart. It is purely to throw stuff out of
memory and reduce process back to starting memory size. Actual
application wouldn't be reloaded until next request for that
application.

What you should do is ensure that in Apache configuration you have:

  LogLevel info

rather than default of:

  LogLevel warn

This will cause mod_wsgi to output lot of logging about daemon
processes and when they are started, stopped, restarted and
unexpectedly exited.

You should be able to get a better idea of what is going on from that.

Details of setting LogLevel can be found in:

  http://code.google.com/p/modwsgi/wiki/DebuggingTechniques

Graham

--

You received this message because you are subscribed to the Google Groups 
"modwsgi" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/modwsgi?hl=en.


Reply via email to