On Tue, 7 Sep 2004, Russ Garrett wrote:
I can watch them for hours in the apache mod_status view, and they'll show the same last request. They won't respond to a kill -15, I have to kill -9 them. Strace reports they're doing absolutely nothing.
Could you use 'gcore' to drop a core from one of these spinning processes and get a backtrace, or simply attach gdb to one of them and see if you can get a backtrace. Chances are it's off in the middle of nowhere, but by poking around a bit and looking at 'ap_request' and walking through 'ap_request->headers_in' you should be able to get an idea of the exact request that caused it to go nuts.
Yeah, I was going to after I sent my last e-mail, but one only just popped up again. Turns out that it's waiting on a mutex inside glibc, which kind of indicates to me that it's a library bug (we're running v2.2.5, which is obviously not the newest version, since it's Debian stable)...
Again, zend_variables.c line 44 makes an appearance, so it looks like it's only happenning when it tries to free up a define()d constant. I'll backtrace some more processes when they die and see if they die in the same place (on the same constant?). Trying to request the script again manually unsurprisingly comes to nothing.
Anyhow, the whole backtrace is here, I'd be interested to see what you think:
http://static.last.fm/phpbug/bt.txt
Russ
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
