[Vserver] Apache Problem at Sunday morning
[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 ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] Apache Problem at Sunday morning
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
Re: [Vserver] Apache Problem at Sunday morning
On Sunday 18 March 2007 08:43, Cryptronic wrote: the first thing i would look at is what cron jobs are running in guests and also host on sunday mornings? it sounds like a cron.weekly script may be raising havoc? 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 -- Chuck ...and the hordes of M$*ft users descended upon me in their anger, and asked 'Why do you not get the viruses or the BlueScreensOfDeath or insecure system troubles and slowness or pay through the nose for an OS as *we* do?!!', and I answered...'I use Linux'. The Book of John, chapter 1, page 1, and end of book ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] Apache Problem at Sunday morning
On Sun, Mar 18, 2007 at 12:43:40PM +, Cryptronic wrote: 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. [Sun Mar 18 06:26:43 2007] [warn] child process 30762 still did not exit, sending a SIGTERM I have the same on multiple Debian Sarge machines, running apache1.3 and apache2.0, not running any vserver patches. I'd say vserver unrelated. I bet each sunday morning between 5 and 7 your logrotation kicks in, and apache doesn't reload cleanly -- Debian unsolved bug for years; quickfix is a killall -9 apache2 then apache2ctl start in the logrotation script. A bug was filed on apache on the BTS (not by me) but I can't find it back. Tom ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] Apache Problem at Sunday morning
Hi all, thanks you two, I think this is a very possible thing ;) I patched all the logrotate files. Thanks for the hints. best regards Oliver Tom Laermans schrieb: On Sun, Mar 18, 2007 at 12:43:40PM +, Cryptronic wrote: 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. [Sun Mar 18 06:26:43 2007] [warn] child process 30762 still did not exit, sending a SIGTERM I have the same on multiple Debian Sarge machines, running apache1.3 and apache2.0, not running any vserver patches. I'd say vserver unrelated. I bet each sunday morning between 5 and 7 your logrotation kicks in, and apache doesn't reload cleanly -- Debian unsolved bug for years; quickfix is a killall -9 apache2 then apache2ctl start in the logrotation script. A bug was filed on apache on the BTS (not by me) but I can't find it back. Tom ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
