• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

Apache failing each morning

G

glennj

Guest
My server has started to stop responding to web requests (ie. apache not working) each morning... the time isn't always the same... but I do always have this in the log file each time...

[Thu Aug 03 04:14:17 2006] [warn] child process 3723 still did not exit, sending a SIGTERM
[Thu Aug 03 04:14:17 2006] [warn] child process 3724 still did not exit, sending a SIGTERM
[Thu Aug 03 04:14:17 2006] [warn] child process 3725 still did not exit, sending a SIGTERM
[Thu Aug 03 04:14:17 2006] [warn] child process 3726 still did not exit, sending a SIGTERM
[Thu Aug 03 04:14:17 2006] [warn] child process 3727 still did not exit, sending a SIGTERM
[Thu Aug 03 04:14:17 2006] [warn] child process 3728 still did not exit, sending a SIGTERM
[Thu Aug 03 04:14:17 2006] [warn] child process 3729 still did not exit, sending a SIGTERM
[Thu Aug 03 04:14:17 2006] [warn] child process 2963 still did not exit, sending a SIGTERM
[Thu Aug 03 04:14:17 2006] [warn] child process 8102 still did not exit, sending a SIGTERM
[Thu Aug 03 04:14:17 2006] [warn] child process 8103 still did not exit, sending a SIGTERM
[Thu Aug 03 04:14:17 2006] [warn] child process 8104 still did not exit, sending a SIGTERM
[Thu Aug 03 04:14:17 2006] [warn] child process 8105 still did not exit, sending a SIGTERM
[Thu Aug 03 04:14:17 2006] [warn] child process 8106 still did not exit, sending a SIGTERM
[Thu Aug 03 04:14:17 2006] [warn] child process 8107 still did not exit, sending a SIGTERM
[Thu Aug 03 04:14:17 2006] [warn] child process 8108 still did not exit, sending a SIGTERM
[Thu Aug 03 04:14:17 2006] [warn] child process 8169 still did not exit, sending a SIGTERM
[Thu Aug 03 04:14:17 2006] [warn] child process 8170 still did not exit, sending a SIGTERM
[Thu Aug 03 04:14:17 2006] [warn] child process 13302 still did not exit, sending a SIGTERM
[Thu Aug 03 04:14:17 2006] [warn] child process 13327 still did not exit, sending a SIGTERM
[Thu Aug 03 04:14:17 2006] [warn] child process 13334 still did not exit, sending a SIGTERM

Anyone have any ideas why this is happening? A simple restart on Apache via SSH and all is well again, although the Plesk watchdog doesn't seem to be able to restart it for some reason...

Please help me... I want a good nights sleep! :)
 
glennj,

Let me ask you this, do you have SIM installed on your server? Prior to the SIGTERM entries, did you have a message:

[error] [client 127.0.0.1] File does not exist: /var/www/html/index.html ?

I had a similiar problem. I created the file /var/www/html/index.html. No more problem.

Not sure if this is what is causing your problem or not, but it solved mine.
 
Back
Top