>Number: 4865 >Category: general >Synopsis: server hangs after some time of running >Confidential: no >Severity: critical >Priority: medium >Responsible: apache >State: open >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Sun Aug 15 21:20:01 PDT 1999 >Last-Modified: >Originator: [EMAIL PROTECTED] >Organization: apache >Release: 1.3.6 >Environment: HPUX-11, latest patches, HP ANSI C compiler. >Description: All modules (max) are dynamically loadable.
My server would hang (stop responding) after a while. I've noticed that in error_log I get tons of these: [Sun Aug 15 20:34:34 1999] [error] mod_ssl: Child could not open SSLMutex lockfile /local/httpd/logs/ssl_mutex.18669 (System error follows) [Sun Aug 15 20:34:34 1999] [error] System: No such file or directory (errno: 2) [Sun Aug 15 20:34:34 1999] [error] mod_ssl: Child could not open SSLMutex lockfile /local/httpd/logs/ssl_mutex.18669 (System error follows) [Sun Aug 15 20:34:34 1999] [error] System: No such file or directory (errno: 2) [Sun Aug 15 20:34:36 1999] [error] mod_ssl: Child could not open SSLMutex lockfile /local/httpd/logs/ssl_mutex.18669 (System error follows) [Sun Aug 15 20:34:36 1999] [error] System: No such file or directory (errno: 2) >How-To-Repeat: >Fix: I think there should be a code to check for this mutex file existance instead of looping like crazy and killing my system. I'm not sure why this file disappears. I use latest OPen_SSL. >Audit-Trail: >Unformatted: [In order for any reply to be added to the PR database, you need] [to include <[EMAIL PROTECTED]> in the Cc line and make sure the] [subject line starts with the report component and number, with ] [or without any 'Re:' prefixes (such as "general/1098:" or ] ["Re: general/1098:"). If the subject doesn't match this ] [pattern, your message will be misfiled and ignored. The ] ["apbugs" address is not added to the Cc line of messages from ] [the database automatically because of the potential for mail ] [loops. If you do not include this Cc, your reply may be ig- ] [nored unless you are responding to an explicit request from a ] [developer. Reply only with text; DO NOT SEND ATTACHMENTS! ]
