Linux – Can’t restart httpd.service on CentOS 7 (Apache server)

centos7httpdhttpd.conflinux

I used the command "service httpd restart" on my centOS apache server, and the following error occurred:

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

How do I solve this error? I tried reinstalling my httpd using the "yum reinstall httpd" command, but it doesn't work.

Best Answer

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

(empahsis mine)

How do I solve this error?

Read the error message carefully, note that it provides useful information on what to do to gather more information, specifically it mentions 2 commands that you should run
- systemctl status httpd.service
- journalctl -xe
Run the commands mentioned in the helpful error message (the latter will likely be most useful) but look at both.
Carefully read the contents of the information provided by the commands. It will contain information that you can use to solve the problem.

Related Solutions

Php – Apache Failure on Centos 7 not starting

You don't need to modify systemd configurations. This is more likely an Apache config error.

You probably need to load the systemd module for apache. In CentOS 7's default httpd config there is a file 00-systemd.conf which is pulled into the apache config using the module include line that has this information. I bet if you load that, you'll find you problem resolved.

$ cat conf.modules.d/00-systemd.conf
# This file configures systemd module:
LoadModule systemd_module modules/mod_systemd.so

This usually occurs if you are copying over a config from another system that doesn't use systemd or perhaps upgrading from Apache 2.2 to Apache 2.4 where that module include directive isn't in the httpd.conf.

Centos – firewall-cmd on OpenVZ CentOS 7

First of all, check if you have ipv6 access, and if not; alter your etc/firewalld/firewalld.conf to set IPv6_rpfilter = 0 and run systemctl restart firewalld.service

If still nothing, check journalctl -u firewalld for further details.

However it may well be that your host needs to provide the NETFILTER="full" capability to your container config, also they will need to allocate the beancounter numiptent to something around 500 or more.

Doing those configs should allow firewalld to start on a centos7 OpenVZ container and anything else, your logs will provide the answers to.

Cheers

Best Answer

Related Solutions

Php – Apache Failure on Centos 7 not starting

Centos – firewall-cmd on OpenVZ CentOS 7

Related Topic