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 11:56 ------- >I read about other HP-UX und Solaris users who appear to face the very same >symptom. HP suppplies a compiled binary so many users will stick with this I >suppose. If there is some fix for this in the HP-supplied binary but not in Apache or APR, we'd love to hear about it :) I hope that isn't the situation. >One of our first thoughts here was that one of the vhosts may generate an error >that causes the parent to shut down but we could not confirm this when >>searching >the logs. And I have to admit we haven't got the time to trace down this any >further right now. In the case that a child returned a fatal error which forced a shutdown, there should be a message in error_log written by the parent by this code: ap_log_error(APLOG_MARK, APLOG_ALERT, 0, ap_server_conf, "Child %" APR_PID_T_FMT " returned a Fatal error..." APR_EOL_STR "Apache is exiting!", pid->pid); In all likelihood the fatal error was simply the first unexpected ENOSPC from attempting to acquire the mutex, then that child returned a fatal error, then the semaphore got cleaned up, then remaining children that hadn't already died due to shutdown started getting EINVAL on their semaphore operations. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
