Moving this discussion from StackOverflow. Here's my original question: I'm using mod_wsgi-express to serve a simple Flask app on a CentOS 6 server. The app is currently used pretty infrequently.
I'm having an issue where every few days, the app will crash, either serving up 500 errors or not responding at all. This doesn't seem related to load or use. Looking through the error log, I'm seeing occasional "*[notice] caught SIGTERM, shutting down*" messages, after which it appears mod_wsgi-express restarts. I don't know why this is happening. I'm also getting this message: [error] (2)No such file or directory: mod_wsgi (pid=24550, process='localhost:8080', application=''): Call to fopen() failed ff or '/tmp/mod_wsgi-localhost:8080:14699/handler.wsgi'. I've tried running mod_wsgi-express with both gdb and pdb debuggers enabled and haven't seen any bugs related to the actual execution of the Python script. I also got a [info] [client 137.78.237.31] (104)Connection reset by peer: core_output_filter: writing data to the network which kicked off hundreds of [notice] child pid 15952 exit signal Segmentation fault (11) over the course of a couple days. These messages all seem to happen randomly and independent of each other. *The only consistent thing is the SIGTERM signal happening every so often.* I'm confused as to what's going on. The implementation seems pretty simple - it's a simple tool that validates metadata in an uploaded file. ---- NOTE: I have moved the server root to a non-temp directory. I'll see if that helps anything. I also was not running gbd in debug mode. -- 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.
