httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 41346] - apache 2.2.4 couldn't start rotatelogs.exe
Date Fri, 19 Jan 2007 10:44:12 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=41346>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=41346





------- Additional Comments From trash_bin@nurfuerspam.de  2007-01-19 02:44 -------
(In reply to comment #5)
> I used Process Explorer to check it. And still - no zombies. And I didn't use 
> binaries from the site you mentioned.

I haven't any zombies only after killing the httpd.exe process tree using
Process Explorer. But they will be there if the service or user process is
terminated gracefully.

Indeed both the ASF vs. the apachelounge.com (AL) binary distros deny to run as
service when an 'ErrorLog' directive in the main server goes through a piped
process.

A piped 'ErrorLog' within 'VirtualHost' does not obstruct it from starting, as
well as a piped 'CustomLog' directive within main server. Nevertheless I used to
move that to the same 'VirtualHost':

Listen 127.0.0.1:81
ServerName 127.0.0.1:81
ErrorLog "logs/error.log"
#CustomLog "logs/access.log" common
<VirtualHost 127.0.0.1:81>
  ServerName localhost:81
  ErrorLog "|C:/Apache2/bin/rotatelogs.exe -l \
    C:/Apache2/logs/error.%Y-%m-%d_%H-%M-%S.log 60"
  CustomLog "|C:/Apache2/bin/rotatelogs.exe -l \
    C:/Apache2/logs/access.%Y-%m-%d_%H-%M-%S.log 60" common
</VirtualHost>

The behaviour of the AL distro is slightly different from that of the ASF. AL
produces more zombies at runtime, two of them are already present outside the
httpd.exe process tree immediately after starting. ASF does not reveal them
immediately, but two zombies (instead of four with AL) stay around after
terminating the server.

Occasionally one of the zombies seems not to have any commandline parameter as
shown by Process Explorer. Otherwise all two or four zombies are shown as
'CustomLog' processes, writing to the access.*.log file.

On my experiments I didn't experience any locked files i. e. I could delete the
log files before killing the rotatelogs zombies. Locked files have been reported
an even more serious problem in the past. Probably locking occurs after a
greater number of service start/stops?




-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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


Mime
View raw message