HI all,
sry for double posting.
In have a strange problem with apache2 : Each sunday morning between 5
a.m. and 7 a.m. some apache's in different vservers shutdown and do not
come back.
I'm running debian etch on the vservers and debian sid on the hosts. The
silliest thing is that each Sunday these were different vservers. I only
get the following message in apache's error log:
[Sun Mar 18 06:26:43 2007] [warn] child process 30762 still did not
exit, sending a SIGTERM
[Sun Mar 18 06:26:43 2007] [warn] child process 30763 still did not
exit, sending a SIGTERM
[Sun Mar 18 06:26:43 2007] [warn] child process 30764 still did not
exit, sending a SIGTERM
[Sun Mar 18 06:26:43 2007] [warn] child process 30765 still did not
exit, sending a SIGTERM
[Sun Mar 18 06:26:43 2007] [warn] child process 30767 still did not
exit, sending a SIGTERM
[Sun Mar 18 06:26:43 2007] [warn] child process 367 still did not exit,
sending a SIGTERM
[Sun Mar 18 06:26:43 2007] [warn] child process 21930 still did not
exit, sending a SIGTERM
[Sun Mar 18 06:26:45 2007] [warn] child process 30762 still did not
exit, sending a SIGTERM
[Sun Mar 18 06:26:45 2007] [warn] child process 30763 still did not
exit, sending a SIGTERM
[Sun Mar 18 06:26:45 2007] [warn] child process 30764 still did not
exit, sending a SIGTERM
[Sun Mar 18 06:26:45 2007] [warn] child process 30765 still did not
exit, sending a SIGTERM
[Sun Mar 18 06:26:45 2007] [warn] child process 30767 still did not
exit, sending a SIGTERM
[Sun Mar 18 06:26:45 2007] [warn] child process 367 still did not exit,
sending a SIGTERM
[Sun Mar 18 06:26:45 2007] [warn] child process 21930 still did not
exit, sending a SIGTERM
[Sun Mar 18 06:26:47 2007] [notice] caught SIGTERM, shutting down
Limit's weren't hit.
I would be thankful for each hint.
Best regards
Oliver
_______________________________________________
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver
Received on Sun Mar 18 12:17:02 2007