These forums are locked and archived, but all topics have been migrated to the new forum. You can search for this topic on the new forum: Search for Cannot Start Apache on the new forum.
I have this VPS that has been running all this while without a problem. Suddenly, httpd stops. And now when I try to start it, it simply fails.
# service httpd start Starting httpd: [FAILED]
That's all I get.
I look inside '/etc/httpd/logs/error_log' and this is all there is
... [Wed Dec 17 14:37:35 2014] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
Where can I get more information about what may be the problem?
Hi,
What operating system are you using? Did you recently install any custom software? Are you subscribed to any non-standard repositories?
Best Regards,
Peter Knowles
TPN Solutions
Email: pknowles@tpnsolutions.com
Phone: 604-782-9342
Skype: tpnsupport
Website: http://www.tpnsolutions.com
Best Regards,
Peter Knowles | TPN Solutions
Email: pknowles@tpnsolutions.com | Skype: tpnassist
CentOS 6 32bit
No, no custom software installed recently.
Only other repository I have added is EPEL.
As far as I remember, nothing on this VPS was changed in the last 24 hours. Suddenly I got an email from a remote Webmin's Server Status module that this server's web site was "down."
I logged in via SSH. Found a httpd process using 100% of the CPU. I reboot, and when the server comes online, httpd will not start.
Since this is a VPS, can the host server be a cause?
Are you using SSL or have a SSL Apache module enabled?
Yes, I am using SSL and the module is enabled.
Hi,
What type of VPS are you using, OpenVZ, KVM/Xen-based, or other?
Best Regards,
Peter Knowles
TPN Solutions
Email: pknowles@tpnsolutions.com
Phone: 604-782-9342
Skype: tpnsupport
Website: http://www.tpnsolutions.com
Best Regards,
Peter Knowles | TPN Solutions
Email: pknowles@tpnsolutions.com | Skype: tpnassist
Type of VPS: KVM.
Did you by chance recently install an SSL certificate?
If so, take a peek at the Apache error logs contained within the domain where SSL was installed... those are located in $HOME/logs/error_log.
-Eric
Thank you, Eric, that was exactly it!
I am so embarrassed to admit that I had set up a new certificate and completely forgot about it less than 24 hours later.