www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marc Slemko <ma...@znep.com>
Subject Re: mod_log-any/1396: Logging to a pipe causes server to stop serving documents (fwd)
Date Thu, 20 Nov 1997 04:20:00 GMT
The following reply was made to PR mod_log-any/1396; it has been noted by GNATS.

From: Marc Slemko <marcs@znep.com>
To: Apache bugs database <apbugs@apache.org>
Cc:  Subject: Re: mod_log-any/1396: Logging to a pipe causes server to stop  serving documents
(fwd)
Date: Wed, 19 Nov 1997 21:10:38 -0700 (MST)

 ---------- Forwarded message ----------
 Date: Wed, 19 Nov 1997 10:12:00 -0800
 From: Steve Resnick <steve@ducksfeet.com>
 To: Marc Slemko <marcs@znep.com>
 Subject: Re: mod_log-any/1396: Logging to a pipe causes server to stop  serving documents
 
 At 11:32 PM 11/15/97 -0700, you wrote:
 >Does this problem always happen right away after starting the 
 >server?
 >
 
 The problems start happening within a minute or so from starting the
 server. The problems affect some virtual hosts in an unpredictable
 fashion.  I.e., I cannot predict which server will show problems and 
 cannot reliably get the same results with the same virtual host, although
 it will show up with other virtual hosts. 
 
 
 >How many copies of your process does ps show running?
 >
 
 ps shows one copy of my process. 
 
 >If you try the simplest possible setup (eg. a perl script that
 >does something like:
 >
 >	#!/usr/local/bin/perl
 >	open (FILE, ">>/tmp/log.out") || die "blarg";
 >	while (<>) {
 >		print FILE;
 >	}
 >
 >) does it still have problems?  We need to eliminate your code as 
 >being the problem.
 >
 >If the above is still a problem, how about when you don't have any
 >virtual hosts?
 
 The above produces the same problems. Additionally the perl script above 
 does not actually write anything to /tmp/log.out -- The file is created,
 it is not written to. 
 
 
 
 >
 >What state does ps show your logging process to be in at that time?
 >If you compile it with debugging and try running gdb on it after
 >it starts having problems, does it show it blocking on anything?
 >
 
 ps shows the process as sleeping (state=S). GDB will not run as it does not
 like some of Sun's shared libraries. 
 
 
 
 >You may want to try 1.3b3 when it comes out, because it has better piped
 >logging support.  I suspect, however, that there is something else
 >going on here.
 >
 >Do you have any other logfiles for each vhost?  Grab lsof from somewhere
 >and see how many file descriptors each httpd process has open.
 >
 
 Each vhost in the problematic configuration has an error log and a referer
 log. 
 
 I can send you my httpd.conf if needed. This is confidential, however, as
 it, in effect, contains a list of our customers. 
 
 Thanks 
 
 Steve
 
 >
 

Mime
View raw message