Job for HTTPD. The service failed because the control process exited with the error code. See "systemctl status HTTPD. Service" and "journalctl - xe" for details.
/root @ iZ25a4sazz ~ # systemctl status HTTPD. Service
? . The HTTPD. Service - The Apache HTTP Server
The Loaded: the Loaded (/usr/lib/systemd/system/HTTPD. Service; Disabled; Vendor preset: disabled)
Active: failed (Result: exit - code) since Sun 18:12:34 2016-08-07 CST; A line of 26 s
Docs: man: HTTPD (8)
Man: apachectl (8)
Process: 1749 ExecStop=/bin/kill the WINCH ${MAINPID} (code=exited, status=1/FAILURE)
Process: 1748 ExecStart=/usr/sbin/HTTPD $OPTIONS - DFOREGROUND (code=exited, status=0/SUCCESS)
The Main PID: 1748 (code=exited, status=0/SUCCESS)
Aug 07 18:12:34 iZ25a4sazz systemd [1] : Starting The Apache HTTP Server...
Aug 07 18:12:34 iZ25a4sazz HTTPD [1748] : HTTPD (pid 31214) already running
Aug 07 18:12:34 iZ25a4sazz kill [1749] : kill: always find a process ", "
Aug 07 18:12:34 iZ25a4sazz systemd [1] : HTTPD. Service: control the process exited, code=exited the status=1
Aug 07 18:12:34 iZ25a4sazz systemd [1] : Failed to start The Apache HTTP Server.
Aug 07 18:12:34 iZ25a4sazz systemd [1] : Unit HTTPD. Service rose failed state.
Aug 07 18:12:34 iZ25a4sazz systemd [1] : HTTPD. The service failed.
CodePudding user response:
The original poster is changed the configuration by yourself? Generally installed system after HTTPD is can use, is to start?Reinstall the original poster is likely to be his?
Could it be that the ins and outs?
CodePudding user response:
I use yum source is installed to see the state like thatCodePudding user response:
"Journalctl - xe" look at the print information,CodePudding user response:
The building Lord, please solved this problem you encounter the same problemCodePudding user response:
Check the log file contentCodePudding user response:
Ps - ef | grep HTTPD whether existing processes, if any, kill off manually, then in systemctl start HTTPD. Try the serviceCodePudding user response:
Meet the same problem, how to solveCodePudding user response:
Firewall - CMD - add - service=HTTPLooking at,
CodePudding user response:
Kill off the HTTPD process and restartCodePudding user response:
Pkill HTTPDAnd then restart, isn't it directly himself out HTTPD executable files, because is not a service, so service kill not to drop,,,
CodePudding user response:
The same problemHTTPD. Service - The Apache HTTP Server
The Loaded: the Loaded (/usr/lib/systemd/system/HTTPD. Service; Disabled; T: vendor prese disabled)
Active: failed (Result: exit - code) since Sun 20:06:42 2018-09-30 CST; 51 s line 4 min
Docs: man: HTTPD (8)
Man: apachectl (8)
Process: 15049 ExecStop=/bin/kill the WINCH ${MAINPID} (code=exited, status=1/FAI LURE)
Process: 15048 ExecStart=/usr/sbin/HTTPD $OPTIONS - DFOREGROUND (code=exited, s tatus=1/FAILURE)
The Main PID: 15048 (code=exited, status=1/FAILURE)
Sep 30 20:06:42 VM_0_13_centos HTTPD [15048] : AH00558: HTTPD: Could not relia... E
Sep 30 20:06:42 VM_0_13_centos HTTPD [15048] : (98) Address already in use: AH0... 0
Sep 30 20:06:42 VM_0_13_centos HTTPD [15048] : no listening sockets available,... N
Sep 30 20:06:42 VM_0_13_centos HTTPD [15048] : AH00015: Unable to open logs
Sep 30 20:06:42 VM_0_13_centos systemd [1] : HTTPD. Service: the main process exite... E
Sep 30 20:06:42 VM_0_13_centos kill [15049] : kill: always find a process ", "
Sep 30 20:06:42 VM_0_13_centos systemd [1] : HTTPD. Service: control the process ex... 1
Sep 30 20:06:42 VM_0_13_centos systemd [1] : Failed to start The Apache HTTP S...
Sep 30 20:06:42 VM_0_13_centos systemd [1] : Unit HTTPD. Service rose failed...
Sep 30 20:06:42 VM_0_13_centos systemd [1] : HTTPD. The service failed.
Hint: Some lines were ellipsized, use the -l to show in full.
CodePudding user response:
Aug 07 18:12:34 iZ25a4sazz HTTPD [1748] : HTTPD (pid 31214) already runningHere, your HTTPD is already running
CodePudding user response:
The error of the building Lord was written by the configuration file is wrong, have lead to serviceCodePudding user response:
The existence of the corresponding process and view the following port 80 exist to kill, to use systemctl start HTTPD. ServiceCodePudding user response:
I also encountered the same problem, systemctl status HTTPD. Service HTTPD process has been running, and then find the corresponding HTTPD process, found that there are five HTTPD process running, specific what reason is not clear, just like that, I got my server kill off pid corresponding process, restarted the lineCodePudding user response:
Killall HTTPDSystemctl restart HTTPD
So try
CodePudding user response:
I also encountered this problem
Excuse me how should solve