DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22484>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22484 semaphore problem takes httpd down ------- Additional Comments From [EMAIL PROTECTED] 2003-08-22 17:29 ------- Hi Jeff, Ok, I have to admit we have those: [Sat Aug 16 16:08:16 2003] [notice] Apache/2.0.47 configured -- resuming normal operations [Sat Aug 16 16:38:09 2003] [emerg] (28)No space left on device: couldn't grab the accept mutex [Sat Aug 16 16:38:09 2003] [alert] Child 16480 returned a Fatal error... Apache is exiting! [Sat Aug 16 16:38:10 2003] [emerg] (36)Identifier removed: couldn't grab the accept mutex [...] Unfortunately a colleague deleted the client' logs of that day so... :( Then hp: from what I see in their relasenotes they fixed a bug related to semaphores/modssl/dbm in 2.0.43 so it seems that is s/th different. Besides I take it for granted that they'll report problems once they find/fix them. At this time, I'm a bit clueless because I see no way how we could track this down. Can you give me a hint where I can read about what could cause a child to produce an "Fatal error"? (I googled but didn't find s/th hot). I'm willing to investigate, but I can't trace 170 vhosts one after the other - many of them using PHP. Thanks, vt --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
