Hi,
I installed Apache 2.4.3 with vhosts and in the httpd.conf, for each
vhost, I have the usual CustomLog and Errorlog directive:
CustomLog "/httpd/domainname/logs/access_log" combined
Errorlog "/httpd/domainname/logs/error_log"
The CustomLog results go to the folder indicated as usual (i
> Problem is that I want the error logging to go the local folder of each
> vhost (which is what is happening on my other servers with previous versions
> of Apache).
Are you running in perl as CGI, and did you change from mod_cgi to
mod_cgid when you moved to 2.4?
---
On Tue, Mar 19, 2013 at 08:29:56PM -0400, Pierre Forget wrote:
> If I make a voluntary error in my Perl script, I get in the
> /httpd/domainname/logs/error_log:
>
> [Tue Mar 19 20:19:25.500222 2013] [cgid:error] [pid 17263:tid
> 2921331520] [client 24.122.245.237:56995] End of script output
> befo
At 20:29 2013-03-19, you wrote:
Hi,
I installed Apache 2.4.3 with vhosts and in the httpd.conf, for
each vhost, I have the usual CustomLog and Errorlog directive:
CustomLog "/httpd/domainname/logs/access_log" combined
Errorlog "/httpd/domainname/logs/error_log"
The CustomLog results go to
Hi,
In response to Pete Houston.
Yes, I seem to use event. because httpd -l gives me:
Compiled in modules:
core.c
mod_so.c
http_core.c
event.c
And certainly mod_cgid because it is in the lines of httpd.conf and active.
Can we go around the side effects of the logs, and get the logs to
On Wed, Mar 20, 2013 at 4:42 PM, Pierre Forget
wrote:
> Hi,
>
> In response to Pete Houston.
>
> Yes, I seem to use event. because httpd -l gives me:
>
> Compiled in modules:
> core.c
> mod_so.c
> http_core.c
> event.c
>
> And certainly mod_cgid because it is in the lines of httpd.conf and
Hi,
Thank you very much, I finally got back my logs at the right place
recompiling with:
--with-mpm=prefork --enable-cgi
I find it odd that the newer version cannot get the logs at the
right place. If you have many vhost, it must be a nightmare to have
all the logs in the same file.
Unle
