Apache fails to start after reboot
Ticket #:8684231
This was the first ticket I've ever submitted to cpanel.
My yum update was failing due to an issue with some python packages and mod_ssl was supposedly missing.
So the tech made some changes and yum update did indeed finish without any errors. The next time I logged into WHM, in the top right corner a big yellow button said the "server needs to be rebooted for the new kernel to take effect" (that may not be word for word). So I clicked on the yellow button and confirmed to reboot the server.
I went to sleep to wake up to 80 emails from my server stating httpd is down. I shelled in, it wouldn't restart. I tried restarting apache via WHM, it still wouldn't start. I rebooted the server again, same thing happen via shell and WHM:
[root@ ~]# service httpd stop
Redirecting to /bin/systemctl stop httpd.service
[root@ ~]# service httpd start
Redirecting to /bin/systemctl start httpd.service
Job for httpd.service failed because the control process exited with error code.
See "systemctl status httpd.service" and "journalctl -xe" for details.
[root@ ~]#
[root@xxxxxxx ~]# service httpd status -l Redirecting to /bin/systemctl status -l httpd.service ? httpd.service - Apache web server managed by cPanel EasyApache Loaded: loaded (/etc/systemd/system/httpd.service; enabled; vendor preset: di sabled) Active: failed (Result: exit-code) since Tue 2017-07-04 16:05:30 CDT; 3min 11 s ago Process: 25855 ExecStart=/usr/local/cpanel/scripts/restartsrv_httpd --no-verbo se (code=exited, status=1/FAILURE) Jul 04 16:05:30 xxxxxxx.xxxxxxx-hosting1.com systemd[1]: Starting Apache web se rver managed by cPanel EasyApache... Jul 04 16:05:30 xxxxxxx.xxxxxxx-hosting1.com restartsrv_httpd[25855]: httpd: Sy ntax error on line 235 of /etc/apache2/conf/httpd.conf: Syntax error on line 32 of /etc/apache2/conf.d/modsec2.conf: Syntax error on line 61 of /etc/apache2/con f.d/modsec/modsec2.cpanel.conf: Could not open configuration file /etc/apache2/c onf.d/modsec_vendor_configs/configserver/00_configserver.conf: No such file or d irectory Jul 04 16:05:30 xxxxxxx.xxxxxxx-hosting1.com systemd[1]: httpd.service: control process exited, code=exited status=1 Jul 04 16:05:30 xxxxxxx.xxxxxxx-hosting1.com systemd[1]: Failed to start Apache web server managed by cPanel EasyApache. Jul 04 16:05:30 xxxxxxx.xxxxxxx-hosting1.com systemd[1]: Unit httpd.service ent ered failed state. Jul 04 16:05:30 xxxxxxx.xxxxxxx-hosting1.com systemd[1]: httpd.service failed. [root@xxxxxxx ~]#
The above references /etc/apache2/ ... This path doesn't exist. I replied to the cpanel ticket about 7 hours ago stating my webserver/apache was down and woke up to no response. Now my ticket shows it's 80 something in the queue again? Note, prior to seeing help for the kernel update, the server was fully functional. Can you please expedite this?
[root@xxxxxxx ~]# service httpd status -l Redirecting to /bin/systemctl status -l httpd.service ? httpd.service - Apache web server managed by cPanel EasyApache Loaded: loaded (/etc/systemd/system/httpd.service; enabled; vendor preset: di sabled) Active: failed (Result: exit-code) since Tue 2017-07-04 16:05:30 CDT; 3min 11 s ago Process: 25855 ExecStart=/usr/local/cpanel/scripts/restartsrv_httpd --no-verbo se (code=exited, status=1/FAILURE) Jul 04 16:05:30 xxxxxxx.xxxxxxx-hosting1.com systemd[1]: Starting Apache web se rver managed by cPanel EasyApache... Jul 04 16:05:30 xxxxxxx.xxxxxxx-hosting1.com restartsrv_httpd[25855]: httpd: Sy ntax error on line 235 of /etc/apache2/conf/httpd.conf: Syntax error on line 32 of /etc/apache2/conf.d/modsec2.conf: Syntax error on line 61 of /etc/apache2/con f.d/modsec/modsec2.cpanel.conf: Could not open configuration file /etc/apache2/c onf.d/modsec_vendor_configs/configserver/00_configserver.conf: No such file or d irectory Jul 04 16:05:30 xxxxxxx.xxxxxxx-hosting1.com systemd[1]: httpd.service: control process exited, code=exited status=1 Jul 04 16:05:30 xxxxxxx.xxxxxxx-hosting1.com systemd[1]: Failed to start Apache web server managed by cPanel EasyApache. Jul 04 16:05:30 xxxxxxx.xxxxxxx-hosting1.com systemd[1]: Unit httpd.service ent ered failed state. Jul 04 16:05:30 xxxxxxx.xxxxxxx-hosting1.com systemd[1]: httpd.service failed. [root@xxxxxxx ~]#
The above references /etc/apache2/ ... This path doesn't exist. I replied to the cpanel ticket about 7 hours ago stating my webserver/apache was down and woke up to no response. Now my ticket shows it's 80 something in the queue again? Note, prior to seeing help for the kernel update, the server was fully functional. Can you please expedite this?
-
Hello @Jeffro_Home, I've updated the ticket status to reflect it's urgency. You should receive a response from one of our Technical Analysts shortly. As far as the error message, it looks similar to what was reported on the following post: mod_security completely messed up beyond repair In that case, the temporary workaround was to create the missing file and restart Apache: mkdir /etc/apache2/conf.d/modsec_vendor_configs/configserver touch /etc/apache2/conf.d/modsec_vendor_configs/configserver/00_configserver.conf /scripts/restartsrv_httpd
Thank you.0 -
Thanks. That did seem to get httpd running, but the server is barely responsive. There's almost nothing on this server and it's much slower than my other (nearly identical) server that has many accounts hosted on it. 0 -
Hi, Try performing a stress test on the server to see its responsiveness. This will be helpful for further investigation whether the hardware is okay or not.. 0 -
Thanks. That did seem to get httpd running, but the server is barely responsive. There's almost nothing on this server and it's much slower than my other (nearly identical) server that has many accounts hosted on it.
The following thread is a good place to start if you'd like to troubleshoot CPU/Memory issues on the system: Troubleshooting high server loads on Linux servers Thank you.0
Please sign in to leave a comment.
Comments
4 comments