Received: (qmail 4399 invoked by uid 2012); 18 Dec 1998 15:04:50 -0000 Message-Id: <19981218150450.4398.qmail@hyperreal.org> Date: 18 Dec 1998 15:04:50 -0000 From: Steven Harris Reply-To: steve@playgal.com To: apbugs@hyperreal.org Subject: Logging To A File Freezes Apache X-Send-Pr-Version: 3.2 >Number: 3555 >Category: mod_log-any >Synopsis: Logging To A File Freezes Apache >Confidential: no >Severity: serious >Priority: medium >Responsible: apache >State: feedback >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Fri Dec 18 07:10:01 PST 1998 >Last-Modified: Sat Dec 19 18:10:01 PST 1998 >Originator: steve@playgal.com >Organization: >Release: 1.3.3 >Environment: FreeBSD members.unfaithful.com 2.2.5-RELEASE FreeBSD 2.2.5-RELEASE #0: Wed Oct 7 20:27:40 PDT 1998 root@indigo.playgal.com:/usr/src/sys/compile/OPTWWW i386 >Description: As you all know, it is easy to setup a "CustomLog" to log to an application. Eg. CustomLog "| /usr/bin/myscript.pl" "%h" etc.. Now, all works well if this perl script is okay. However when the application fails, apache tries to restart it. (ie. myscript.pl keeps popping up as a new process all the time). After some time, apache freezes completely and is unusable. The rest of the system remains fine. >How-To-Repeat: Setup a customlog directive to a program (eg. a perl script) which does not work properly and returns error. >Fix: Nope. >Audit-Trail: State-Changed-From-To: open-feedback State-Changed-By: marc State-Changed-When: Fri Dec 18 10:45:56 PST 1998 State-Changed-Why: What do you mean by "does not work properly"? Please give an example logging script that can be used to reproduce this. From: Marc Slemko To: Apache bugs database Cc: Subject: Re: mod_log-any/3555: Logging To A File Freezes Apache (fwd) Date: Sat, 19 Dec 1998 18:01:05 -0800 (PST) ---------- Forwarded message ---------- Date: Sat, 19 Dec 1998 09:23:49 +1000 (EST) From: Steven Harris To: marc@apache.org Cc: apache-bugdb@apache.org Subject: Re: mod_log-any/3555: Logging To A File Freezes Apache Sure, If you have a perl script as such: #!/usr/local/bin/perl # # Do something bad require 'doesnt-exist'; Then reference this perl script in a customlog line: Eg. CustomLog "| /usr/bin/myperl.pl" "%h" Apache normally starts ONE copy of the perl script. However because this perl script bombs out, it keeps trying to restart the perl script (everytime it tries to log a hit as defined in the CustomLog). Eventually we had the maximum number of apache processes running and apache stopped responding to any requests. Steve On 18 Dec 1998 marc@apache.org wrote: > [In order for any reply to be added to the PR database, ] > [you need to include 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! ] > > > Synopsis: Logging To A File Freezes Apache > > State-Changed-From-To: open-feedback > State-Changed-By: marc > State-Changed-When: Fri Dec 18 10:45:56 PST 1998 > State-Changed-Why: > What do you mean by "does not work properly"? Please give > an example logging script that can be used to reproduce this. > > >Unformatted: [In order for any reply to be added to the PR database, ] [you need to include 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! ]