The message 'Truncated or oversized response headers received from daemon process' is going to come up when your mod_wsgi daemon process crashes for some reason.
There are various reasons why a Python web application under mod_wsgi can crash which relate to Python C extensions and so it may not relate at all to mod_wsgi. Can you send me the parts of the Apache configuration where you configure the mod_wsgi daemon process and then delegate the WSGI application to it. That is, WSGIDaemonProcess, WSGIProcessGroup, WSGIApplicationGroup, WSGIScriptAlias directives with parameters to them, and the surrounding Apache configuration providing context for where they are used. In particular I am trying to determine if you are forcing the use of the main Python interpreter context. http://code.google.com/p/modwsgi/wiki/CheckingYourInstallation#Sub_Interpreter_Being_Used The reason for this is that if not using the main Python interpreter context, some C extensions for Python can crash. http://code.google.com/p/modwsgi/wiki/ApplicationIssues#Python_Simplified_GIL_State_API The changed dynamics of how things are managed in the newer version could perhaps result in those issues being triggered. It could still also be a mod_wsgi issue as there were some significant internal changes made. If you can reliably reproduce this, then it would help if you can get a C level stack trace for where the crash is occurring. You can do this by following instructions in: http://code.google.com/p/modwsgi/wiki/DebuggingTechniques#Debugging_Crashes_With_GDB Specifically, attach gdb to one of the daemon processes and then hit it with requests until it crashes. At that point enter into gdb: thread apply all bt and it should give a stack trace for all the threads. Graham On 12/12/2014, at 4:19 PM, [email protected] wrote: > When I upgraded from 4.3.0 to 4.4.0 I've started to get errors “Truncated or > oversized response headers received from daemon process” and seg faults. > > I downgraded and everything went back to working. > > I'm seeing this on a Django app that uses AJAX to send to a custom view in > the admin. I've also seen this with a bot that is claiming to be Google. But > since it is only visiting one of my sites I'm expect it's not from Google. > > I'm using Centos 6.6, python 2.7.8, and Apache 2.4.10. > > Is there a new setting I need to change or is this a bug? I didn't see > anything in the change log that I need to change > > -- > 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. -- 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.
