Failed to start apache

K

kulbon

Verified User
Joined
Jun 7, 2020
Messages
15
Hi, i have installed CustomBuild GUI plugin and update PHP from 7.2.19 to 7.2.31. After that httpd cant start.

Jun 08 07:53:07 user systemd[1]: Starting The Apache HTTP Server...
Jun 08 07:53:07 user systemd[1]: httpd.service: Main process exited, code=exited, status=1/FAILURE
Jun 08 07:53:07 user kill[9804]: kill: failed to parse argument: '': No such file or directory
Jun 08 07:53:07 user systemd[1]: httpd.service: Control process exited, code=exited status=1
Jun 08 07:53:07 user systemd[1]: Failed to start The Apache HTTP Server.
Jun 08 07:53:07 user systemd[1]: httpd.service: Unit entered failed state.
Jun 08 07:53:07 user systemd[1]: httpd.service: Failed with result 'exit-code'.

Could someone help me?

httpd.service: Main process exited, code=exited, status=1/FAILURE
Jun 08 08:07:08 user kill[3017]: kill: failed to parse argument: '': No such file or directory
Jun 08 08:07:08 user systemd[1]: httpd.service: Control process exited, code=exited status=1
Jun 08 08:07:08 user systemd[1]: Failed to start The Apache HTTP Server.
Jun 08 08:07:08 user systemd[1]: httpd.service: Unit entered failed state.
Jun 08 08:07:08 user systemd[1]: httpd.service: Failed with result 'exit-code'.
Jun 08 08:07:50 user systemd[1]: httpd.service: Failed to set invocation ID on control group /system.slice/httpd.service, ignoring: Operation not permi
Jun 08 08:07:50 user systemd[1]: Starting The Apache HTTP Server...
Jun 08 08:07:50 user systemd[1]: httpd.service: Main process exited, code=exited, status=1/FAILURE
Jun 08 08:07:50 user kill[3044]: kill: failed to parse argument: '': No such file or directory
Jun 08 08:07:50 user systemd[1]: httpd.service: Control process exited, code=exited status=1
Jun 08 08:07:50 user systemd[1]: Failed to start The Apache HTTP Server.
Jun 08 08:07:50 user systemd[1]: httpd.service: Unit entered failed state.
Jun 08 08:07:50 user systemd[1]: httpd.service: Failed with result 'exit-code'.
 
Last edited:
There was also:
Code: 
[Mon Jun 08 08:23:06.858826 2020] [core:emerg] [pid 16621:tid 139660455032960] (28)No space left on device: AH00023: Couldn't create the proxy mutex
[Mon Jun 08 08:23:06.858868 2020] [proxy:crit] [pid 16621:tid 139660455032960] (28)No space left on device: AH02478: failed to create proxy mutex
Code: 
ipcs -s

showed that Semaphores reached limits and

Code: 
for whatever in `ipcs -s | awk '{print $2}'`; do ipcrm -s $whatever; done

cleaned semaphored and apache started successfully
 
kulbon said:
There was also:
Code: 
[Mon Jun 08 08:23:06.858826 2020] [core:emerg] [pid 16621:tid 139660455032960] (28)No space left on device: AH00023: Couldn't create the proxy mutex
[Mon Jun 08 08:23:06.858868 2020] [proxy:crit] [pid 16621:tid 139660455032960] (28)No space left on device: AH02478: failed to create proxy mutex
Code: 
ipcs -s

showed that Semaphores reached limits and

Code: 
for whatever in `ipcs -s | awk '{print $2}'`; do ipcrm -s $whatever; done

cleaned semaphored and apache started successfully
Click to expand...
Take care after sometime those errors returns and apache is down then. ( i had to set the limit higher)
 
I have changed WEB server from apache to nginx_apache in CustomBuild plugin. Next thing i did was Rewrite WEB server configuration files.

All previously configured and working sites now are not working.
I have ERR_CONNECTION_REFUSED.

I changed back to apache but now my sites displays: Apache is functioning normally/

What happened? How to get it back on apache or nginx_apache ?

EDIT I See that httpd is listening on port 8080, but ther is nothing listetning on port 80
 
Last edited:
You must log in or register to reply here.
Back
Top