I'v really tried to reduce everything to a minimum to insulate the problem.

So, here's the config file:

ServerRoot "C:\Program Files\Apache
DocumentRoot "htdocs"
Listen 80

LoadModule mime_module ../../modules/mod_mime.so
LoadModule log_config_module ../../modules/mod_log_config.so

# for mod_perl
LoadFile "c:/TempApache/Perl/bin/perl58.dll"
LoadModule perl_module ../../modules/mod_perl.so

SetHandler perl-script
PerlResponseHandler ModPerl::Registry
PerlOptions +ParseHeaders

TransferLog logs/access.log
ErrorLog logs/error.log
TypesConfig conf/mime.types
LogLevel debug

and here's the script (/perl/warning.pl):

warn "Hello You Script\n";
use strict;
print "Content-Type: text/html\n\n";
print "I think I issued a warning";

There's really nothing more.


----- Original Message -----
From: "Malcolm J Harwood"
Cc: "Lionel MARTIN"
Sent: Thursday, May 11, 2006 7:52 AM
Subject: Re: Where do the "warn" message go? (Ap2 & MP2 on Win32)

> On Thursday 11 May 2006 01:40 am, Lionel MARTIN wrote:
>> I tried to put a "LogLevel debug" in my httpd.conf, so that everything
>> gets
>> logged, but this didn't make a difference: my warn messages don't get
>> logged.

>> What else could I try, in order to find out why?

> Are your logs going through syslog, or directly to file? If it's through
> syslog that could be filtering for you.
> Do you have a signal handler for warn installed at all? It's possible
> that's
> eating your warns.
> What modules do you have loaded? (I've seen odd cases with some modules
> causing warns to get eaten).
> Have you tried reducing your script to just the warn statement?
> What happens under ModPerl::PerlRun as opposed to ModPerl::Registry?
> --
> To know and yet think we do not know is the highest attainment.
> Not to know and yet think we do know is a disease.
> - Lao-tzu