There is an actual example of what you see in the logs further down in that 
post.

[Mon Feb 05 21:11:52.378725 2018] [wsgi:info] [pid 31535:tid 140409583761152] 
mod_wsgi (pid=31535): Exiting process 'blah'.
[Mon Feb 05 21:11:52.404508 2018] [wsgi:info] [pid 31550:tid 140409652811520] 
mod_wsgi (pid=31550): Daemon process request time limit exceeded, stopping 
process 'blah'.
[Mon Feb 05 21:11:52.404559 2018] [wsgi:info] [pid 31550:tid 140409849104256] 
mod_wsgi (pid=31550): Shutdown requested 'blah'.
[Mon Feb 05 21:11:52.404619 2018] [wsgi:info] [pid 31550:tid 140409849104256] 
mod_wsgi (pid=31550): Dumping stack trace for active Python threads.
[Mon Feb 05 21:11:52.404624 2018] [wsgi:info] [pid 31550:tid 140409849104256] 
mod_wsgi (pid=31550): Thread 140409636026112 executing file 
"/usr/lib/python3.5/socket.py", line 677, in create_connection
[Mon Feb 05 21:11:52.404628 2018] [wsgi:info] [pid 31550:tid 140409849104256] 
mod_wsgi (pid=31550): called from file "/usr/lib/python3.5/smtplib.py", line 
300, in _get_socket,
[Mon Feb 05 21:11:52.404631 2018] [wsgi:info] [pid 31550:tid 140409849104256] 
mod_wsgi (pid=31550): called from file "/usr/lib/python3.5/smtplib.py", line 
308, in connect,
[Mon Feb 05 21:11:52.404633 2018] [wsgi:info] [pid 31550:tid 140409849104256] 
mod_wsgi (pid=31550): called from file "/usr/lib/python3.5/smtplib.py", line 
226, in __init__,
[Mon Feb 05 21:11:52.404636 2018] [wsgi:info] [pid 31550:tid 140409849104256] 
mod_wsgi (pid=31550): called from file 
"/var/www/.virtualenvs/www-elNfpBxP/lib/python3.5/site-packages/django/core/mail/backends/smtp.py",
 line 42, in open,
....

As to docs changes, have created:

    https://github.com/GrahamDumpleton/mod_wsgi/issues/261 
<https://github.com/GrahamDumpleton/mod_wsgi/issues/261>
    https://github.com/GrahamDumpleton/mod_wsgi/issues/262 
<https://github.com/GrahamDumpleton/mod_wsgi/issues/262>

Graham

> On 7 Feb 2018, at 2:49 pm, Jesus Cea <j...@jcea.es> wrote:
> 
> On 07/02/18 04:01, Graham Dumpleton wrote:
>> BTW, you can see example of stack trace generated when request-timeout
>> occurs in recent mailing list discussion at:
>> 
>>     https://groups.google.com/d/msg/modwsgi/_i6MGs6fh6w/nH3x7_nuAwAJ
> 
> Humm. If you are refering to this comment of you:
> 
> """
> You started using request-timeout, good. When using that option you get
> the track trace automatically when process shutdown due to it.
> """
> 
> "request-timeout" generating tracebacks is not documented anywhere in
> <https://modwsgi.readthedocs.io/en/develop/configuration-directives/WSGIDaemonProcess.html>.
> 
> It should be documented too that the traceback is dumped at loglevel "info".
> 
> A random thought about this is that the general advice in the
> documentation about "LogLevel info" should be replaced by "LogLevel
> wsgi:info". This way it could be left in production, as I just did :).
> The other approach is very verbose for the entire Apache server and modules.
> 
> -- 
> Jesús Cea Avión                         _/_/      _/_/_/        _/_/_/
> j...@jcea.es - http://www.jcea.es/     _/_/    _/_/  _/_/    _/_/  _/_/
> Twitter: @jcea                        _/_/    _/_/          _/_/_/_/_/
> jabber / xmpp:j...@jabber.org  _/_/  _/_/    _/_/          _/_/  _/_/
> "Things are not so easy"      _/_/  _/_/    _/_/  _/_/    _/_/  _/_/
> "My name is Dump, Core Dump"   _/_/_/        _/_/_/      _/_/  _/_/
> "El amor es poner tu felicidad en la felicidad de otro" - Leibniz
> 
> -- 
> 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 modwsgi+unsubscr...@googlegroups.com.
> To post to this group, send email to modwsgi@googlegroups.com.
> Visit this group at https://groups.google.com/group/modwsgi.
> For more options, visit 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 modwsgi+unsubscr...@googlegroups.com.
To post to this group, send email to modwsgi@googlegroups.com.
Visit this group at https://groups.google.com/group/modwsgi.
For more options, visit https://groups.google.com/d/optout.

Reply via email to