Bug#493573: Backtrace on 'hung' apache2 (while trying to stop service)

2008-08-18 Thread Stefan Fritsch
On Monday 18 August 2008, Chris Horn wrote: Chris Horn wrote: I'm not really a programmer (so this may be obvious from the backtrace), but disabling the PHP5 module completely solves the problem. Sorry for so much traffic, but I bring good news. I just upgraded all of my MySQL packages

Bug#493573: Backtrace on 'hung' apache2 (while trying to stop service)

2008-08-17 Thread Stefan Fritsch
On Saturday 16 August 2008, you wrote: Stefan Fritsch wrote: On Friday 15 August 2008, Chris Horn wrote: To re-create normal situation: 1. /etc/init.d/apache2 start 2. /etc/init.d/apache2 stop 3. apache2 is now hung Does this happen for you always or only sometimes? Does it only

Bug#493573: Backtrace on 'hung' apache2 (while trying to stop service)

2008-08-17 Thread Chris Horn
I'm not really a programmer (so this may be obvious from the backtrace), but disabling the PHP5 module completely solves the problem. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#493573: Backtrace on 'hung' apache2 (while trying to stop service)

2008-08-17 Thread Chris Horn
Chris Horn wrote: I'm not really a programmer (so this may be obvious from the backtrace), but disabling the PHP5 module completely solves the problem. Sorry for so much traffic, but I bring good news. I just upgraded all of my MySQL packages to 'testing' and now everything appears to work.

Bug#493573: Backtrace on 'hung' apache2 (while trying to stop service)

2008-08-16 Thread Stefan Fritsch
Hi, does anybody have an idea what is going wrong here or how to debug this? On Friday 15 August 2008, Chris Horn wrote: (gdb) bt full #0 0xb7e630ee in __lll_lock_wait_private () from /lib/libpthread.so.0 No symbol table info available. #1 0xb7e606e1 in _L_lock_23 () from

Bug#493573: Backtrace on 'hung' apache2 (while trying to stop service)

2008-08-16 Thread Stefan Fritsch
On Friday 15 August 2008, Chris Horn wrote: To re-create normal situation: 1. /etc/init.d/apache2 start 2. /etc/init.d/apache2 stop 3. apache2 is now hung Does this happen for you always or only sometimes? Does it only happen after apache processed some requests? I cannot reproduce it.

Bug#493573: Backtrace on 'hung' apache2 (while trying to stop service)

2008-08-16 Thread Chris Horn
Stefan Fritsch wrote: On Friday 15 August 2008, Chris Horn wrote: To re-create normal situation: 1. /etc/init.d/apache2 start 2. /etc/init.d/apache2 stop 3. apache2 is now hung Does this happen for you always or only sometimes? Does it only happen after apache processed some requests? I

Bug#493573: Backtrace on 'hung' apache2 (while trying to stop service)

2008-08-14 Thread Chris Horn
Package: apache2.2-common Version: 2.2.9-6 Followup-For: Bug #493573 Stopping apache2 via /etc/init.d/apache2 stop does not work. All of the worker threads are stopped, but the main '/usr/sbin/apache2 -k start' process (the one in the PID file) lingers on. After the 60 second timeout the PID