Jason Tower wrote:
Also, here's another wrinkle in the mix. When we were testing, we
repeatedly crashed Apache in this way (mostly on purpose) and then
were doing a "service httpd restart" (essentially just a kill and
restart). Eventually, Apache couldn't restart itself, complaining of
insufficient space on the device, and referencing semaphores.
Presumably, the box had run out of semaphores because Apache and
PHP's threading had been screwed up in some way. A reboot fixed it.
I don't think that really provides any insight into the situation,
but does anyone know of a way to clear those semaphores?
Aaron S. Joyner
that's a well known redhat/apache issue, i used see it on my rh9
webservers that had extended (100+ day) uptimes. afaik, nothing short
of a reboot will fix it. none of my mandrake boxes seem to be affected
by it though.
jason
That's strange, I have a couple rh9 servers that have 200+ day uptimes
and I've never seen that problem before. Mind if I ask what you were
running on those rh9 boxes, roughly? Mostly PHP stuff I'm going to
hazard a guess?
Aaron S. Joyner
--
TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug
TriLUG Organizational FAQ : http://trilug.org/faq/
TriLUG Member Services FAQ : http://members.trilug.org/services_faq/
TriLUG PGP Keyring : http://trilug.org/~chrish/trilug.asc
