Apache server not running but server status is reporting it as up

glucz

Member
Jul 7, 2005
14
0
151
This may be a bug report, but I have not found a better place to post.

In my system logs I have:

Oct 15 23:09:59 ns9 systemd: httpd.service stop-sigterm timed out. Killing.
Oct 15 23:09:59 ns9 systemd: Unit httpd.service entered failed state.
Oct 15 23:09:59 ns9 systemd: httpd.service failed.

Apache had been dead for an hour when I noticed. I checked the emails and saw no recovery attempt from the server. I logged into the panel and WHM service status showed apache as UP.

also chkservd.log said:
httpd [Service check failed to complete

I then restarted /scripts/restartsrv chkservd
... no change. The system still showed apache as up.

I restarted apache manually and it restarted without problems.

chkservd.log now say:
httpd [[check command:N/A][socket connect:+]]...

Here is the apache error log that also shows that no restart attempt was made:
[Thu Oct 15 23:04:51.487367 2020] [core:warn] [pid 15546:tid 47988325827648] AH00045: child process 19816 still did not exit, sending a SIGTERM
[Thu Oct 15 23:04:51.579013 2020] [core:warn] [pid 15546:tid 47988325827648] AH00045: child process 10532 still did not exit, sending a SIGTERM
[Thu Oct 15 23:04:53.580223 2020] [core:warn] [pid 15546:tid 47988325827648] AH00045: child process 19816 still did not exit, sending a SIGTERM
[Thu Oct 15 23:04:53.580272 2020] [core:warn] [pid 15546:tid 47988325827648] AH00045: child process 10532 still did not exit, sending a SIGTERM
[Thu Oct 15 23:04:55.582118 2020] [core:warn] [pid 15546:tid 47988325827648] AH00045: child process 10532 still did not exit, sending a SIGTERM
[Thu Oct 15 23:04:57.584292 2020] [core:error] [pid 15546:tid 47988325827648] AH00046: child process 10532 still did not exit, sending a SIGKILL
[Thu Oct 15 23:04:58.584894 2020] [mpm_worker:notice] [pid 15546:tid 47988325827648] AH00295: caught SIGTERM, shutting down

[ N 2020-10-15 23:04:58.6438 10624/T7 age/Cor/CoreMain.cpp:641 ]: Signal received. Gracefully shutting down... (send signal 2 more time(s) to force shutdown)
[ N 2020-10-15 23:04:58.6465 10624/T1 age/Cor/CoreMain.cpp:1216 ]: Received command to shutdown gracefully. Waiting until all clients have disconnected...
[ N 2020-10-15 23:04:58.6575 10624/Tz Ser/Server.h:902 ]: [ServerThr.15] Freed 0 spare client objects
[ N 2020-10-15 23:04:58.6634 10624/Tz Ser/Server.h:558 ]: [ServerThr.15] Shutdown finished
.....
[ N 2020-10-15 23:04:58.9408 10624/T1 age/Cor/CoreMain.cpp:1295 ]: Passenger core shutdown finished
[Fri Oct 16 00:10:47.102297 2020] [hostinglimits:notice] [pid 19763:tid 47330798380096] mod_hostinglimits: use Min UID 1000
[Fri Oct 16 00:10:47.102719 2020] [hostinglimits:notice] [pid 19763:tid 47330798380096] mod_hostinglimits: version 1.0-37. LVE mechanism enabled

The last 2 lines are the manual restart.

I suspect that this may be a bug and I decided to post this as service monitoring and recovery is quite important.


Thanks
 
Last edited:

cPanelLauren

Technical Support Community Manager
Staff member
Nov 14, 2017
13,237
1,232
313
Houston
I agree that service monitoring is indeed very important. I think this warrants further investigation.
Can you please open a ticket using the link in my signature? Once open please reply with the Ticket ID here so that we can update this thread with the resolution once the ticket is resolved.


Thanks!