I'm running modwsgi in daemon mode and getting a "Truncated or oversized
response headers received..." error from Apache, which I believe means the
daemon died. This happens when I do an Apache graceful restart and there
is an open HTTP connection being handled by modwsgi at the time of the
restart. The daemon dies almost immediately. If there is no open HTTP
connection, then a graceful restart works fine. An ordinary (non-graceful)
restart also works.
This is a mature modwsgi/Django application that runs just fine in every
other way. I don't think I've ever tried doing a graceful restart before,
so it's entirely possible this behavior has always been there and I just
didn't notice it.
My version of modwsgi is pretty recent I believe. If the issue is with
Apache, I could upgrade to 2.4.x, but it's not obvious that that is
relevant here.
Apache 2.2.17, MPM worker mode
modwsgi 4.4.9
Python 2.7.6
MPM config:
ServerLimit 6
StartServers 2
MaxClients 150
ThreadsPerChild 25
MinSpareThreads 25
MaxSpareThreads 75
modwsgi config:
WSGIDaemonProcess site-1 threads=50 shutdown-timeout=60
WSGIApplicationGroup %{GLOBAL}
WSGIProcessGroup site-1
WSGIPassAuthorization on
--
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 http://groups.google.com/group/modwsgi.
For more options, visit https://groups.google.com/d/optout.
