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 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Version|2.2.3 |2.2.4 ------- Additional Comments From [EMAIL PROTECTED] 2007-01-28 13:11 ------- Version 2.2.4 is now available; it was added after the 2.2.4 release. I am seeing this problem on Windows Server 2003. My server has two pipes: one for access and one for error log. The syntax is as follows: ErrorLog "| d:/httpd-2.2.4-ssl/bin/rotatelogs.exe d:/servername/logs/error-%Y-%m-%d.log 300 -420" LogLevel warn CustomLog "| d:/httpd-2.2.4/bin/rotatelogs.exe d:/servername/logs/access-%Y-%m-%d.log 300 -420" common I can start the ApacheLounge distro from command line and it generates two empty cmd.exe windows, a total of four shells with rotatelogs.exe (two under the parent, two under the child) visible in Process Explorer, as well as two zombies. Trying to start the service (installed with d:\httpd-2.2.4-ssl\bin\httpd -d d:/servername -n Apache224 -k install) gives me an error dialog that tells me to look in the Event Log, which has three entries: One about the Win32DisableAcceptEx directive (not relevant to this issue) One that says The Apache service named reported the following error: >>> (22)Invalid argument: Couldn't start the ErrorLog process One that says The Apache service named reported the following error: >>> Unable to open logs . This gives me TWO zombies. Then I turned off the ErrorLog pipe, and used instead a normal file path with LogLevel debug. The server starts and serves pages. I initially saw two cmd.exe + rotatelogs.exe hang off the parent and child respectively. These eventually went away, and I now have two zombies (haven't reconciled their PIDs). The Error log contains no red flags. The access-2007-01-28.log is created, but contains nothing but a large number of lines reading: piped log program ' d:/httpd-2.2.4/bin/rotatelogs.exe d:/servername/logs/access-%Y-%m-%d.log 300 -420' failed unexpectedly Interestingly, my test box behaves very similarly with 2.2.3, which I have been running in Production with rotatelogs. I have to go in and manually reap the dead rotatelogs.exe processes from time to time, but at least it works. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
