Hi, I'm trying to troubleshoot a poorly performing django site. This started acting up when I upgraded on Fedora to python 3.10.
I've seen this post: https://groups.google.com/g/modwsgi/c/_i6MGs6fh6w?pli=1 and ttps://modwsgi.readthedocs.io/en/develop/user-guides/debugging-techniques.html#tracking-request-and-response But I'm not sure how to debug with the wsgi middleware for error logging. I've inspected the error_log, at /var/log/httpd, and see the problem reported there, but not sure where to try to fix it. I did try increasing KeepAliveTimeout in my httpd.conf but the problem in general is very weird...it'll work fine for a few clicks and then hang up again with a timeout. Restarting apache fixes it momentarily and then it's buggered again. Doesn't seem to be port conflicts since nip.io returns various ports, and nip.io is working fine when applied to my other sites on the same server. And other sites on the same server not using modwsgi work fine too. Any ideas or comments of where to look next would be appreciated. error_log [Thu Mar 10 13:32:13.737319 2022] [wsgi:error] [pid 1239:tid 1393] (70007)The timeout specified has expired: [client xxx.xxx.xxx.xxx:51768] mod_wsgi (pid=1239): Failed to proxy response from daemon. [Thu Mar 10 13:34:08.063648 2022] [wsgi:error] [pid 3409:tid 3439] [client xxx.xxx.xxx.xxx:51770] Timeout when reading response headers from daemon process 'myarchive': /var/www/html/myarchive/myarchive/wsgi.py, referer: http://myarchive.xxx.xxx.xxx.xxx.nip.io/ephemera/ Thank you, Bob -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/modwsgi/CALWZDaN8o4L8YMNz-PvUOwNTM8FQNQCg63p84LacHjmtHB%3D5cA%40mail.gmail.com.
