Apache keeps needing to be restarted
I recently run easyapache and updated from apache 2.2 to apache 2.4 and from php 5.3 to php 5.4 and since doing so I now have to restart http at least once a day, sometimes twice a day.
What would cause this? and how would I rectify?
Any help will be gratefully received.
-
and since doing so I now have to restart http at least once a day, sometimes twice a day.
For what reason exactly? You don't mention that.0 -
I have no idea what causes this, I just noticed one of the sites was offline, then when I checked the other sites they were all offline as well, I rebooted http and all were online again, the sites go offline upto a couple of times a day, but only since updating apache and php. 0 -
Have you checked your error logs for clues? 0 -
I have but I'm still learning centos and I couldn't see anything that stuck out and was wondering if it could be a configuration issue maybe? 0 -
I recently run easyapache and updated from apache 2.2 to apache 2.4 and from php 5.3 to php 5.4 and since doing so I now have to restart http at least once a day, sometimes twice a day. What would cause this? and how would I rectify? Any help will be gratefully received.
We operate a WordPress site and it used to get 500 Read Timeout Errors. It took some time to investigate but we found out Apache had crashed while the older sockets were still open so we had to kill off all the old processes then restart Apache clean. So far, no more 500 Read Timeout Errors and the WordPress site is loading properly.0 -
I have but I'm still learning centos and I couldn't see anything that stuck out and was wondering if it could be a configuration issue maybe?
Hello, What entries do you notice in /usr/local/apache/logs/error_log when Apache is not responding? Thank you.0 -
Hi Michael, It's just happened again and I see in the logs these two entries [Wed Jun 17 16:00:02.037586 2015] [mpm_prefork:notice] [pid 27086] AH00173: SIGHUP received. Attempting to restart AH00112: Warning: DocumentRoot [Wed Jun 17 16:00:03.009821 2015] [core:notice] [pid 27086] AH00060: seg fault or similar nasty error detected in the parent process
Could these be the cause?0 -
Upgraded the server and it seems ok now :) 0 -
I am happy to see the issue is now resolved. To clarify, what exactly was upgraded (E.g. CPU, Memory)? Thank you. 0 -
Hi Michael, I had two colo servers, and only one is now being used, so I asked the host to swap the HDD's over from the 8GB dual core with the ones in the 32GB dual quad core server. I'm now looking to have the server optimised.. Regards Pete 0 -
I had two colo servers, and only one is now being used, so I asked the host to swap the HDD's over from the 8GB dual core with the ones in the 32GB dual quad core server. I'm now looking to have the server optimised..
Thank you for the update. Note you may find our "Workarounds and Optimization" forum helpful. Thank you.0
Please sign in to leave a comment.
Comments
11 comments