We are happy to announce that Vesta is back under active development as of 25 February 2024. We are working on v1 candidate and expect to engage more with the community over the coming months. We are committed to open source, and we encourage contributors to help us build the future of Vesta.
Error: httpd restart failed
-
- Posts: 2
- Joined: Mon Mar 05, 2018 12:15 pm
- Os: CentOS 6x
- Web: apache + nginx
Error: httpd restart failed
I tried to resolve this as best I could by google search. I paid for support on vestacp.com website but no one has contacted me yet. I am really in hot water right now. I need a kind person to help me.
For the last 2 days the httpd does not want to restart. For a while nginx also did not want to restart but I got it fix.
In Vestacp I get this message when I click httpd to restart: Error: httpd restart failed.
In the Terminal after typing this command "service httpd restart" I get this message:
Job for httpd.service failed because the control process exited with error code. See "systemctl status httpd.service" and "journalctl -xe" for details.
systemctl status httpd.service
● httpd.service - The Apache HTTP Server
Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Mon 2018-03-05 07:36:33 EST; 2min 46s ago
Process: 7234 ExecStop=/bin/kill -WINCH ${MAINPID} (code=exited, status=1/FAILURE)
Process: 7232 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE)
Main PID: 7232 (code=exited, status=1/FAILURE)
Mar 05 07:36:32 vps105566.vps.ovh.ca systemd[1]: Starting The Apache HTTP Server...
Mar 05 07:36:33 vps105566.vps.ovh.ca httpd[7232]: AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using myserverdomain.com. Set the 'ServerName' directive globally to suppress this message
Mar 05 07:36:33 vps105566.vps.ovh.ca httpd[7232]: no listening sockets available, shutting down
Mar 05 07:36:33 vps105566.vps.ovh.ca httpd[7232]: AH00015: Unable to open logs
Mar 05 07:36:33 vps105566.vps.ovh.ca systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE
Mar 05 07:36:33 vps105566.vps.ovh.ca kill[7234]: kill: cannot find process ""
Mar 05 07:36:33 vps105566.vps.ovh.ca systemd[1]: httpd.service: control process exited, code=exited status=1
Mar 05 07:36:33 vps105566.vps.ovh.ca systemd[1]: Failed to start The Apache HTTP Server.
Mar 05 07:36:33 vps105566.vps.ovh.ca systemd[1]: Unit httpd.service entered failed state.
Mar 05 07:36:33 vps105566.vps.ovh.ca systemd[1]: httpd.service failed.
----------------------------
The no listening sockets available, shutting down
httpd port 8080 and 8443 are not used by any other services.
It could be the AH00015: Unable to open logs.
For the last 2 days the httpd does not want to restart. For a while nginx also did not want to restart but I got it fix.
In Vestacp I get this message when I click httpd to restart: Error: httpd restart failed.
In the Terminal after typing this command "service httpd restart" I get this message:
Job for httpd.service failed because the control process exited with error code. See "systemctl status httpd.service" and "journalctl -xe" for details.
systemctl status httpd.service
● httpd.service - The Apache HTTP Server
Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Mon 2018-03-05 07:36:33 EST; 2min 46s ago
Process: 7234 ExecStop=/bin/kill -WINCH ${MAINPID} (code=exited, status=1/FAILURE)
Process: 7232 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE)
Main PID: 7232 (code=exited, status=1/FAILURE)
Mar 05 07:36:32 vps105566.vps.ovh.ca systemd[1]: Starting The Apache HTTP Server...
Mar 05 07:36:33 vps105566.vps.ovh.ca httpd[7232]: AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using myserverdomain.com. Set the 'ServerName' directive globally to suppress this message
Mar 05 07:36:33 vps105566.vps.ovh.ca httpd[7232]: no listening sockets available, shutting down
Mar 05 07:36:33 vps105566.vps.ovh.ca httpd[7232]: AH00015: Unable to open logs
Mar 05 07:36:33 vps105566.vps.ovh.ca systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE
Mar 05 07:36:33 vps105566.vps.ovh.ca kill[7234]: kill: cannot find process ""
Mar 05 07:36:33 vps105566.vps.ovh.ca systemd[1]: httpd.service: control process exited, code=exited status=1
Mar 05 07:36:33 vps105566.vps.ovh.ca systemd[1]: Failed to start The Apache HTTP Server.
Mar 05 07:36:33 vps105566.vps.ovh.ca systemd[1]: Unit httpd.service entered failed state.
Mar 05 07:36:33 vps105566.vps.ovh.ca systemd[1]: httpd.service failed.
----------------------------
The no listening sockets available, shutting down
httpd port 8080 and 8443 are not used by any other services.
It could be the AH00015: Unable to open logs.
Re: Error: httpd restart failed
yes
AH00015: Unable to open logs
usually has to do with your server having run out of diskspace. Removing a few backups from VestaCP backend usually does the trick.
AH00015: Unable to open logs
usually has to do with your server having run out of diskspace. Removing a few backups from VestaCP backend usually does the trick.