• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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