Topic: 2.2.4 ErrorLog Piping Broken?

[VoodooMill]

Hi all,

First time here, glad to find this community.

Has anyone experienced issues with piping ErrorLog in 2.2.4?

I've compiled version 2.2.4 with mod_ssl and mod_deflate. Compilation went fine, but when I attempt to start the Apache service it won't start.

Windows App log shows:
The Apache service named reported the following error:
>>> (22)Invalid argument: Couldn't start ErrorLog process .

It is accompanied by another entry:
The Apache service named reported the following error:
>>> Unable to open logs .

I've run the syntax check on my config and it comes back OK. ErrorLog works fine when logging directly to a file, but not piping. CustomLog pipes just fine.

The error comes up when piping through rotatelogs or cronolog.

I am using the same configuration files of our current production 2.2.3 server (everything hums along quite happily ).

Thanks much!

=START EDIT
I also forgot to mention that when I started Apache in console everything seemed to work with the configuration I want. Only problem is I don't want to run in console.
=STOP EDIT

[tonyg]

check this out.. the problem is in the log.c changes I hope they fix quickly, it is unusable right now.
http://issues.apache.org/bugzilla/show_bug.cgi?id=16393

[tonyg]

sorry, wrong link ....here is the right one


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

[VoodooMill]

Thanks for replying tonyg and for the link. I won't be upgrading without log piping working.