www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Luc De Pourcq <luc.de.pou...@skynet.be>
Subject mod_proxy/3620: Apache exit after an emergency message
Date Mon, 04 Jan 1999 11:40:02 GMT

>Number:         3620
>Category:       mod_proxy
>Synopsis:       Apache exit after an emergency message
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Mon Jan  4 03:50:01 PST 1999
>Last-Modified:
>Originator:     luc.de.pourcq@skynet.be
>Organization:
apache
>Release:        1.3.3
>Environment:
OS/2 Warp Server 4.  
TCP/IP 4.02w
Fixpack 36
Lan server 5.1
For compiler see http://silk.apana.org.au/apache/Configuration.full.txt
(my Apache compiled version come from this site)
>Description:
[Mon Jan  4 11:50:23 1999] [notice] Apache/1.3.3 (OS/2) configured -- resuming normal operations
[Mon Jan  4 11:51:27 1999] [emerg] (9)Bad file number: OS2SEM: Error 105 getting accept lock.
Exiting!
[Mon Jan  4 11:51:27 1999] [emerg] (9)Bad file number: OS2SEM: Error 105 getting accept lock.
Exiting!
[Mon Jan  4 11:51:27 1999] [emerg] (9)Bad file number: OS2SEM: Error 105 getting accept lock.
Exiting!
[Mon Jan  4 11:51:27 1999] [emerg] (9)Bad file number: OS2SEM: Error 105 getting accept lock.
Exiting!
[Mon Jan  4 11:51:27 1999] [emerg] (9)Bad file number: OS2SEM: Error 105 getting accept lock.
Exiting!
[Mon Jan  4 11:51:27 1999] [emerg] (9)Bad file number: OS2SEM: Error 105 getting accept lock.
Exiting!
[Mon Jan  4 11:51:27 1999] [emerg] (9)Bad file number: OS2SEM: Error 105 getting accept lock.
Exiting!
[Mon Jan  4 11:51:27 1999] [emerg] (9)Bad file number: OS2SEM: Error 105 getting accept lock.
Exiting!
[Mon Jan  4 11:51:27 1999] [emerg] (9)Bad file number: OS2SEM: Error 105 getting accept lock.
Exiting!
[Mon Jan  4 11:51:27 1999] [emerg] (9)Bad file number: OS2SEM: Error 105 getting accept lock.
Exiting!
[Mon Jan  4 11:51:27 1999] [emerg] (9)Bad file number: OS2SEM: Error 105 getting accept lock.
Exiting!
[Mon Jan  4 11:51:27 1999] [emerg] (9)Bad file number: OS2SEM: Error 105 getting accept lock.
Exiting!
[Mon Jan  4 11:51:27 1999] [emerg] (9)Bad file number: OS2SEM: Error 105 getting accept lock.
Exiting!
[Mon Jan  4 11:51:27 1999] [emerg] (9)Bad file number: OS2SEM: Error 105 getting accept lock.
Exiting!
[Mon Jan  4 11:51:27 1999] [emerg] (9)Bad file number: OS2SEM: Error 105 getting accept lock.
Exiting!
[Mon Jan  4 11:51:27 1999] [emerg] (9)Bad file number: OS2SEM: Error 105 getting accept lock.
Exiting!
[Mon Jan  4 11:51:28 1999] [emerg] (9)Bad file number: OS2SEM: Error 105 getting accept lock.
Exiting!
[Mon Jan  4 11:51:28 1999] [alert] Child 392 returned a Fatal error... 
Apache is exiting!
[Mon Jan  4 11:51:30 1999] [emerg] (9)Bad file number: OS2SEM: Error 105 getting accept lock.
Exiting!
>How-To-Repeat:

>Fix:
With version 1.3.1 I get not problem.
New version 1.3.2 and 1.3.3 provide this errors.
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <apbugs@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[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!         ]




Mime
View raw message