httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From KASPAR Sandro <>
Subject Re: [users@httpd] cgi script error output logging
Date Thu, 11 May 2017 18:37:06 GMT
Hi Luca,

Yes I checked the error log format. Unfortunately, this only applies to log lines generated
by apache and not to the lines created by cgi scripts. The lines created by a cgi script are
just redirected to the httpd-error.log as they are. For example if you print "test" to stderr
in a cgi script, this gets written just like that to the error log. No vhost information,
no timestamp, no user, just what you printed.

My error log format is:

ErrorLogFormat "%v [%{u}t] [%-m:%l] [pid %P:tid %T] %7F: %E: [client\ %a] %M% ,\ referer\

But as I said, the ErrorLogFormat is not applied to log lines generated by cgi scripts.

The apache version I am using is 2.4.25.


From: Luca Toscano <>
Sent: Thursday, May 11, 2017 2:53:35 PM
Subject: Re: [users@httpd] cgi script error output logging

Hi Sandro,

have you checked ? What is
the current format that you are using? Also, what version of httpd?


2017-05-11 10:07 GMT+02:00 KASPAR Sandro <<>>:

Hi suomi,

Thank you for your answer. Unfortunately I am not using php-fpm but fcgid. As far as I know
there is no such possibility in fcgid.

Any other ideas?


From: fedora <<>>
Sent: Thursday, May 11, 2017 6:54 AM
Subject: Re: [users@httpd] cgi script error output logging

Hi Sandro

are you using php-fpm as a cgi frontend? If yes: the stdout and stderr
are both redirectet to the php-fpm log (/var/log/php-fpm/*) if you have
in /etc/php-fpm/www.conf:

catch_workers_output = yes

I don't think this will solve all your problems, but it is a good
starting point.


On 05/10/2017 03:59 PM, KASPAR Sandro wrote:
> Hi,
> According to this documentation everything
a cgi script sends to stderr is written to the apache  error log file.
> Unfortunately I can not control those scripts running on my server and often garbage
is sent to stderr and then written to my error log. Because there isn't even a timestamp or
any other useful information on those lines, I can't find out, which vhost created  the error.
In addition those log lines often lack a "new line" at the end, and it the next log message
gets appended to the current line instead of being written to a new line. Because of this,
the next line which would have been in the correct format is also lost, because it can't be
parsed automatically anymore.
> Is there any way to change this behaviour? What I would like to achieve is to have the
cgi errors in a seperate logfile or even better change the log format of these lines. For
example prefix the log line with the vhost and a timestamp.
> Because I don't have control over the cgi scripts, I would need to configure this in
apaches main or vhost configuration. Unfortunately I could not find anything about cgi script
output logging in the apache documentation (except that everything sent to  stderr is written
to httpd-error.log) or mailing list archives.
> Any ideas appreciated. Thanks in advance!
> Sandro Kaspar
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:<>
> For additional commands, e-mail:<>

To unsubscribe, e-mail:<>
For additional commands, e-mail:<>

View raw message