I was following this tutorial to setup two virtual hosts in Centos 7.

The issue is i am getting the following error while restarting the httpd.

[userme@server ~]$ sudo systemctl restart httpd.service 
[sudo] password for userme: 
Job for httpd.service failed because the control process exited with error code. See "systemctl status httpd.service" and "journalctl -xe" for details.

My configurations are

[userme@server ~]$ cat /etc/hosts   server.workstation.com server   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6

[userme@server ~]$ hostname

[userme@server ~]$ cat /etc/sysconfig/network
# Created by anaconda

[userme@server ~]$ cat /etc/resolv.conf 
# Generated by NetworkManager
search workstation.com
nameserver fe80::1%p3p1

[userme@server ~]$ domainname 

EDIT As per request

[userme@server ~]$ systemctl status httpd -l
● httpd.service - The Apache HTTP Server
   Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Thu 2018-01-18 12:55:25 +04; 57min ago
     Docs: man:httpd(8)
  Process: 1285 ExecStop=/bin/kill -WINCH ${MAINPID} (code=exited, status=1/FAILURE)
  Process: 1283 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE)
 Main PID: 1283 (code=exited, status=1/FAILURE)

Jan 18 12:55:25 server.workstation.com systemd[1]: Starting The Apache HTTP Server...
Jan 18 12:55:25 server.workstation.com httpd[1283]: AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using server.workstation.com. Set the 'ServerName' directive globally to suppress this message
Jan 18 12:55:25 server.workstation.com systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE
Jan 18 12:55:25 server.workstation.com kill[1285]: kill: cannot find process ""
Jan 18 12:55:25 server.workstation.com systemd[1]: httpd.service: control process exited, code=exited status=1
Jan 18 12:55:25 server.workstation.com systemd[1]: Failed to start The Apache HTTP Server.
Jan 18 12:55:25 server.workstation.com systemd[1]: Unit httpd.service entered failed state.
Jan 18 12:55:25 server.workstation.com systemd[1]: httpd.service failed.

[userme@server ~]$ sudo firewall-cmd --list-all
public (active)
  target: default
  icmp-block-inversion: no
  interfaces: p3p1
  services: ssh dhcpv6-client
  masquerade: no
  rich rules:

[userme@server ~]$ apachectl configtest
Syntax OK

What is the issue with my network/hostname settings ? Any help would be appreciated.

  • That's usually just a warning, not a fatal error. So what's the output of systemctl status httpd -l? Jan 18, 2018 at 9:52
  • Note that the domainname utility has little to do with a host's hostname. It gives the YP/NIS domain name, which is something else.
    – Kusalananda
    Jan 18, 2018 at 9:53
  • @UlrichSchwarz Outpu added as per the comment.
    – ran
    Jan 18, 2018 at 9:57
  • @Kusalananda Hmm, i am not using NIS/YP here. So i don't need to worry about the blank domainname output, right ?
    – ran
    Jan 18, 2018 at 10:00
  • @ran Correct. That's normal behaviour if you're not using YP/NIS.
    – Kusalananda
    Jan 18, 2018 at 10:01

2 Answers 2


This looks like an issue with SELINUX that is enable be default on CentOS 7.

Setting SELINUX=permissive and rebooting the server will log the issues to /var/log/audit/audit.log so that set the appropriate SELINUX setting can be set up to allow the SELINUX to protect the server.

In addition setting up firewalld to allow access to ports 80 and 443 to allow external connections is needed:

firewall-cmd --add-service=http
firewall-cmd --add-service=https

linode has a good write up for firewalld but I've not found a good SELINUX resource...


As per your error message: Set the 'ServerName' directive globally to suppress this message

Within the httpd.conf file you should find ServerName, and above it you may find the following note:

ServerName gives the name and port that the server uses to identify itself.
This can often be determined automatically, but we recommend you specify
it explicitly to prevent problems during startup.

If your host doesn't have a registered DNS name, enter its IP address here.

So adding the line:

ServerName server:[PORT]

Should fix your startup issues.

  • Yess, this fixes my failure error (Process: 1734 ExecStop=/bin/kill -WINCH ${MAINPID} (code=exited, status=1/FAILURE))
    – ran
    Jan 18, 2018 at 12:11

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .