Question

Apache Server not starting centos 7

[centos@ip-172-31-19-60 ~]$ sudo systemctl status httpd.service -l ● httpd.service - The Apache HTTP Server Loaded: loaded (/usr/lib/systemd/system/httpd.service; disabled; vendor preset: disabled) Active: failed (Result: exit-code) since Mon 2020-04-13 06:51:48 UTC; 21min ago Docs: man:httpd(8) man:apachectl(8) Process: 1355 ExecStop=/bin/kill -WINCH ${MAINPID} (code=exited, status=1/FAILURE) Process: 1354 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=exited, status=1/FAILUR E) Main PID: 1354 (code=exited, status=1/FAILURE)

Apr 13 06:51:48 ip-172-31-19-60.us-east-2.compute.internal httpd[1354]: (13)Permission denied : AH00072: make_sock: could not bind to address 0.0.0.0:10 Apr 13 06:51:48 ip-172-31-19-60.us-east-2.compute.internal httpd[1354]: no listening sockets available, shutting down Apr 13 06:51:48 ip-172-31-19-60.us-east-2.compute.internal httpd[1354]: AH00015: Unable to op en logs Apr 13 06:51:48 ip-172-31-19-60.us-east-2.compute.internal systemd[1]: httpd.service: main pr ocess exited, code=exited, status=1/FAILURE Apr 13 06:51:48 ip-172-31-19-60.us-east-2.compute.internal kill[1355]: kill: cannot find proc ess “” Apr 13 06:51:48 ip-172-31-19-60.us-east-2.compute.internal systemd[1]: httpd.service: control process exited, code=exited status=1 Apr 13 06:51:48 ip-172-31-19-60.us-east-2.compute.internal systemd[1]: Failed to start The Ap ache HTTP Server. Apr 13 06:51:48 ip-172-31-19-60.us-east-2.compute.internal systemd[1]: Unit httpd.service ent ered failed state. Apr 13 06:51:48 ip-172-31-19-60.us-east-2.compute.internal systemd[1]: httpd.service failed. Apr 13 06:59:34 ip-172-31-19-60.us-east-2.compute.internal systemd[1]: Unit httpd.service can not be reloaded because it is inactive.


Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

Hi @prathiabhishek,

Looking at the provided logs, I can see a couple of issues. Firstly, Apache is trying to start and listen on port 10. Have you changed the default configuration about port 80 to port 10? If you have, make sure the port is not used by another service. If you intend to use port 10, then execute the following command

netstat -tulpne | grep 10

See if anything is listening on it.

Another issue might be the lack of space/inodes on your Droplet.

You can check it by executing the following commands

df -h
df -i

If you have any of the partitions full, please make sure to free some space.

Lastly, when you try to restart apache and it fails, please do check

journalctl -xe

It should provide you with the full error behind the failing.

Regards, KDSys