Bug#398223: Acknowledgement (apache2: [notice] caught SIGTERM, shutting down)

2007-01-14 Thread Ralf Mattes
bOn Sun, 2007-01-14 at 10:44 +0800, Clayton wrote: Hi Ralf, I re-enabled the SSL stuff and sure enough, apache2 died again this morning, this time with your logrotate mods above in place. Fine, However, sorry to say that the logrotate log file that was generated only contains a time

Bug#398223: Acknowledgement (apache2: [notice] caught SIGTERM, shutting down)

2007-01-14 Thread Clayton
On Sun, 14 Jan 2007 14:39:47 +0100 Ralf Mattes [EMAIL PROTECTED] wrote: Gosh, read it. It's all there! Sorry for the noise, but it is not as obvious as you seem to think. Sure, on a good day I should have been able to figure it out myself, but to state something that I think is obvious: very

Bug#398223: Acknowledgement (apache2: [notice] caught SIGTERM, shutting down)

2007-01-13 Thread Clayton
On Sun, 07 Jan 2007 17:11:40 +0100 Ralf Mattes [EMAIL PROTECTED] wrote: Hmm, apache2 invokes logrotate weeky, so maybe there's a bug in the logrotate script. I'd change /etc/logrotate/apache2 to: /var/log/apache2/*.log { weekly missingok rotate 52 compress

Bug#398223: Acknowledgement (apache2: [notice] caught SIGTERM, shutting down)

2007-01-07 Thread Clayton
After enduring seven consecutive Sunday morning Apache2 shutdowns (ie. this is REALLY reproducible on my end) I commented out the following in my one SSL-enabled virtual host: NameVirtualHost *:443 VirtualHost *:443 DocumentRoot /var/www/langex ServerName www.langex.net

Bug#398223: Acknowledgement (apache2: [notice] caught SIGTERM, shutting down)

2007-01-07 Thread Ralf Mattes
On Sun, 2007-01-07 at 23:06 +0800, Clayton wrote: After enduring seven consecutive Sunday morning Apache2 shutdowns (ie. this is REALLY reproducible on my end) I commented out the following in my one SSL-enabled virtual host: NameVirtualHost *:443 VirtualHost *:443 DocumentRoot

Bug#398223: Acknowledgement (apache2: [notice] caught SIGTERM, shutting down)

2006-11-19 Thread Clayton
It just happened again. It seemes to be happening at the same time every day (though not every day) I guess when cron is running something? This time a little more info in the logs, I think (or maybe I just didn't notice last time): [Sun Nov 19 06:29:07 2006] [notice] caught SIGTERM, shutting