Received: (qmail 9992 invoked by uid 2012); 6 Nov 1997 14:13:40 -0000 Message-Id: <19971106141340.9991.qmail@hyperreal.org> Date: 6 Nov 1997 14:13:40 -0000 From: Christ Leijtens Reply-To: leijtens@mediaport.org To: apbugs@hyperreal.org Subject: Apache 1.2.x and 1.3b2 report error message to client when run from xinetd X-Send-Pr-Version: 3.2 >Number: 1371 >Category: os-osf >Synopsis: Apache 1.2.x and 1.3b2 report error message to client when run from xinetd >Confidential: no >Severity: critical >Priority: medium >Responsible: apache >State: closed >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Thu Nov 6 06:20:00 PST 1997 >Last-Modified: Fri Feb 27 02:07:44 PST 1998 >Originator: leijtens@mediaport.org >Organization: >Release: 1.3b2 >Environment: OSF1 weena.spirit.nl V4.0 464 alpha DEC C V5.2-030 on Digital UNIX V4.0 (Rev. 464) Server version Apache/1.3b2. xinetd-2.2.1 >Description: Running Apache releases 1.2.x and 1.3b2 on a DEC Alpha running OSF1 results in error messages directly passed to the client (Netscape): longjmp or siglongjmp function used outside of saved context at moments this problems occurs continuously at other times I have hard time reproducing the error message. It also seems only to occur in "inetd"-mode and not when running as server-type "standalone". Although I am not sure about this. One other person "jorias@massive.de" reported exactly this same problem in news group "comp.infosystems.servers.unix" some month ago. I have contacted him two times. The first time he said the solution was downloading the most recent release. For us this was beta release 1.3b2 as we were already running production release 1.2.4. This was without success. My second question to Alexander Jorrias was to ask him which release and in which mode he had the Apache-daemon running. I did not get a response yet. >How-To-Repeat: Sometimes the problems shows up very regular. A sample web site is: http://mv1.spirit.nl/ >Fix: I have consulted manual pages for longjmp() and consorts where there is a description of undefined behavior of siglongjmp() under two circumstances. This is the documentation on the DEC UNIX/OSF1 man pages. It looks like the exact message received in Netscape is from longjmperror(). As I cannot look at the sources of this function and the man page for longjmperror(3) is missing in my installation >Audit-Trail: State-Changed-From-To: open-feedback State-Changed-By: coar State-Changed-When: Thu Dec 18 08:21:04 PST 1997 State-Changed-Why: Some work was done for inetd mode in 1.3b3; can you please upgrade to that version and see if the problem still exists? Release-Changed-From-To: 1.3b2, 1.2.x-1.3b2 Release-Changed-By: coar Release-Changed-When: Thu Dec 18 08:21:04 PST 1997 State-Changed-From-To: feedback-closed State-Changed-By: dgaudet State-Changed-When: Fri Feb 27 02:07:43 PST 1998 State-Changed-Why: [This is a standard response.] No response from submitter, assuming issue has been resolved. >Unformatted: