DO NOT REPLY [Bug 20289] New: - Upgraded to 1.3.27 from 1.3.23 and now ErrorLog directives crash httpd

[bu...@apache.org]

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=20289>.
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=20289

Upgraded to 1.3.27 from 1.3.23 and now ErrorLog directives crash httpd

           Summary: Upgraded to 1.3.27 from 1.3.23 and now ErrorLog
                    directives crash httpd
           Product: Apache httpd-1.3
           Version: 1.3.27
          Platform: PC
               URL: http://nextleveldesign.net/esmdocs/apache/
        OS/Version: Linux
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Other
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: emetsger@nextleveldesign.net


Bear with me as I'm short on sleep.

We've been running 1.3.23, and are upgrading to 1.3.27.

1.3.27 refused to start.  strace showed a SIGSEV at the end of the execution. 
No core file.  We have an 'Include' of virtual hosts (20 hosts) at the end of
the main httpd.conf.  I commented the include out and the server started just
fine.  I finally narrowed it down to the "ErrorLog" directive in my included
virtualhost file.  I deleted each reference to an ErrorLog and the server
started just fine.  I verified by visiting each site.

To be sure it wasn't a permissions problem I double checked each file referenced
by the ErrorLog directives.  I performed a 'chmod -R web:web /weblogs' (the base
of my weblogs directory tree).    I'm convinced its not a permissions issue or
ownership issue.

Here is where it gets weird(er).  If I eliminate 19 of the 20 virtualhosts in my
include file (it doesn't matter which ones I keep or throw away) and there is
only one virtualhost in the file, the ErrorLog directive for that single
virtualhost is accepted and the server starts.

Additionaly, when I start the server with SSL enabled, it won't start either
(gratuitous logging takes place on behalf of mod_ssl).

Some details about the install:
DSO install, default modules built from configure.
Added mod_ssl as a shared module
Added php 4.3.1 as a shared module via apxs (PHP sites render just fine).
PHP was compiled with a whole lotta stuff (incl LDAP, IMAP, MySQL, SASL; they
all seem to work fine).
'ldd' finds all shared libraries.

Any ideas?  The URL above has text files with some of the debug output. 
Considering the level of weirdness I woudl think someone would have come across
this before but I didn't find anything in bugzilla.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org