Job for httpd service failed because the control process exited with error code See systemctl status httpd service and journalctl -xe for details

Question

I have installed a fresh copy of Centos 7  Then I restarted Apache but the Apache failed to start  I have 3 days stucked in this issue  Even the support can not figure out the error     sudo service httpd start      Failed to start apache    Job for httpd service failed because the control process exited with error code  See  systemctl status httpd service  and  journalctl -xe  for details       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 2016-05-09 16 08 02 BST  59s ago       Docs  man httpd 8              man apachectl 8    Main PID  5710  code exited  status 1 FAILURE     May 09 16 08 02 mike079 startdedicated de systemd 1   Starting The Apache HTTP Server     May 09 16 08 02 mike079 startdedicated de httpd 5710    98 Address already in use  AH00072  make sock  could not bind to address 85 25 12 20 80  May 09 16 08 02 startdedicated de httpd 5710   no listening sockets available  shutting down  May 09 16 08 02 startdedicated de httpd 5710   AH00015  Unable to open logs  May 09 16 08 02 startdedicated de systemd 1   httpd service  main process exited  code exited  status 1 FAILURE  May 09 16 08 02 startdedicated de kill 5712   kill  cannot find process     May 09 16 08 02  startdedicated de systemd 1   httpd service  control process exited  code exited status 1  May 09 16 08 02startdedicated de systemd 1   Failed to start The Apache HTTP Server   May 09 16 08 02 startdedicated de systemd 1   Unit httpd service entered failed state   May 09 16 08 02 mike  httpd service failed

User · Answer

lt VirtualHost   80 gt      ServerName www YOURDOMAIN COM     ServerAlias YOURDOMAIN COM     DocumentRoot  var www YOURDOMAIN COM public html     ErrorLog  var www YOURDOMAIN COM error log     CustomLog  var www YOURDOMAIN COM requests log combined      DocumentRoot  var www YOURDOMAIN COM public html      lt Directory   gt          Options FollowSymLinks         AllowOverride None      lt  Directory gt       lt Directory  var www YOURDOMAIN COM public html gt          Options Indexes FollowSymLinks MultiViews         AllowOverride All         Order allow deny         allow from all      lt  Directory gt    lt  VirtualHost gt

User · Answer

on command line type journalctl -xe and the results will be  SELinux is preventing  usr sbin httpd from name bind access on the tcp socket port 83 or 80   This means that the SELinux is running on your machine and you need to disable it  then edit the configuration file by type the following  nano  etc selinux config   Then find the line SELINUX enforce and change to SELINUX disabled  Then type the following and run the command to start httpd  setenforce 0  Lastly start a server  systemctl start httpd

User · Answer

Some other service may be using port 80  try to stop the other services  HTTPD  SSL  NGINX  PHP  with the command sudo systemctl stop  and then use the command sudo systemctl start httpd

User · Answer

In my case I got the error simply because I had changed the Listen 80 to listen 443 in the file   etc httpd conf httpd conf    Since I had installed mod ssl using the yum commands  yum -y install mod ssl     there was a duplicate listen 443 directive in the file ssl conf created during mod ssl installation   You can verify this if you have duplicate listen 80 or 443 by running the below command in linux centos  My linux   grep   443   etc httpd conf d     below is sample output    etc httpd conf d ssl conf Listen 443 https  etc httpd conf d ssl conf  lt VirtualHost  default  443 gt   etc httpd conf d ssl conf  ServerName www example com 443   Simply reverting the listen 443 in httd conf to listen 80 fixed my issue

User · Answer

Allow Apache Through the Firewall  Allow the default HTTP and HTTPS port  ports 80 and 443  through firewalld   sudo firewall-cmd --permanent --add-port 80 tcp sudo firewall-cmd --permanent --add-port 443 tcp   And reload the firewall   sudo firewall-cmd --reload

User · Answer

From your output      no listening sockets available  shutting down   what basically means  that any port in which one apache is going to be listening is already being used by another application   netstat -punta   grep LISTEN  Will give you a list of all the ports being used and the information needed to recognize which process is so you can kill stop or do whatever you want to do with it   After doing a nmap of your ip I can see that   80 tcp    open     http   so I guess you sorted it out

User · Answer

I got the same error because of a simple typo in vhost conf  Remember to make sure you don t have any errors in the config files   apachectl configtest

[apache] Job for httpd.service failed because the control process exited with error code. See "systemctl status httpd.service" and "journalctl -xe" for details

Examples related to apache

Examples related to centos

Examples related to centos7

Examples related to httpd.conf

Examples related to http-status-code-415