On 12/03/2019 11:28 AM, Genes Lists via arch-general wrote:
On 12/3/19 5:36 AM, Andy Pieters wrote:
I have experienced this last year and when I recompiled both apache and wsgi with debugging symbols to find out what's what, it suddenly worked again and has since!
That sounds like use of variable before set - as debugging initializes variables to 0 (in C, C++ ... ).
Could be buggy code.
Nope, now wsgi... Funny thing is for 10 years I though all updates I have never had any problems with httpd. The whatever changed in the 11/23 updates it was segfaulting/coredumping repeatedly. I thought the follow-up updates solved it, but then found both servers websites down again. Restarting httpd brings the server back up, but it was shocking to look at the logs and see on one server: -rw-r--r-- 1 root root 71509927 Dec 2 19:22 error_log -rw-r--r-- 1 root root 24306916 Dec 1 00:00 error_log.1 -rw-r--r-- 1 root root 625 Nov 24 00:00 error_log.2 -rw-r--r-- 1 root root 1742 Nov 21 13:19 error_log.3 -rw-r--r-- 1 root root 504 Nov 10 00:00 error_log.4 and then on the other: -rw-r--r-- 1 root root 73141520 Dec 2 19:15 error_log -rw-r--r-- 1 root root 25049886 Dec 1 00:00 error_log.1 -rw-r--r-- 1 root root 1137 Nov 24 00:00 error_log.2 -rw-r--r-- 1 root root 1752 Nov 17 00:01 error_log.3 -rw-r--r-- 1 root root 504 Nov 10 00:00 error_log.4 Yikes! -- David C. Rankin, J.D.,P.E.