/ Zope / Apsis / Pound Mailing List / Archive / 2007 / 2007-01 / Pound 2.2.3 - LogLevel ignored?

[ << ] [ >> ]

[ IP logging on BackEnd servers; / Adam Lis ... ] [ IE Download Problems / Roland Küstermann ... ]

Pound 2.2.3 - LogLevel ignored?
Jens Schleusener <Jens.Schleusener(at)t-systems-sfr.com>		 2007-01-20 22:02:55 [ SNIP ] 
Hi,

I just upgraded from Pound 2.2 to 2.2.3 and have the impression that now 
always "LogLevel 1" is in use and other values of the LogLevel 
configuration variable are ignored (even 0 - no logging).

The relevant portion of my configuration seems to be:

 LogFacility local5
 LogLevel 3

Also removing "LogFacility local5" that I "misused" to log via syslogd in 
/var/log/pound.log didn't change the behaviour.

Pound 2.2 logs with "LogLevel 3" as desired in "Apache combined log 
format".

Greetings 

Jens

-- 
Dr. Jens Schleusener            T-Systems Solutions for Research GmbH
Tel: +49 551 709-2493           Bunsenstr.10
Fax: +49 551 709-2169           D-37073 Goettingen
Jens.Schleusener(at)t-systems.com  http://www.t-systems.com/
Re: [Pound Mailing List] Pound 2.2.3 - LogLevel ignored?
"Simon Matter" <simon.matter(at)invoca.ch>		 2007-01-21 13:22:22 [ SNIP ] 
> Hi,
>
> I just upgraded from Pound 2.2 to 2.2.3 and have the impression that now
> always "LogLevel 1" is in use and other values of the LogLevel
> configuration variable are ignored (even 0 - no logging).
>
> The relevant portion of my configuration seems to be:
>
>  LogFacility local5
>  LogLevel 3
>
> Also removing "LogFacility local5" that I "misused" to log via syslogd in
> /var/log/pound.log didn't change the behaviour.
>
> Pound 2.2 logs with "LogLevel 3" as desired in "Apache combined log
> format".

Hi Jens,

Do you mind trying the patch I suggested yesterday? Maybe it also fixes
the problem you see:
http://www.apsis.ch/pound/pound_list/archive/2007/2007-01/1167845504000/index_html#1169302740000

Regards,
Simon
Re: [Pound Mailing List] Pound 2.2.3 - LogLevel ignored?
Jens Schleusener <Jens.Schleusener(at)t-systems-sfr.com>		 2007-01-22 09:35:32 [ SNIP ] 
Hi Simon,

> > I just upgraded from Pound 2.2 to 2.2.3 and have the impression that now
> > always "LogLevel 1" is in use and other values of the LogLevel
> > configuration variable are ignored (even 0 - no logging).
> >
> > The relevant portion of my configuration seems to be:
> >
> >  LogFacility local5
> >  LogLevel 3
> >
> > Also removing "LogFacility local5" that I "misused" to log via syslogd in
> > /var/log/pound.log didn't change the behaviour.
> >
> > Pound 2.2 logs with "LogLevel 3" as desired in "Apache combined log
> > format".
> 
> Hi Jens,
> 
> Do you mind trying the patch I suggested yesterday? Maybe it also fixes
> the problem you see:
>
http://www.apsis.ch/pound/pound_list/archive/2007/2007-01/1167845504000/index_html#1169302740000

Unfortunately it doesn't fix my problem.

Thanks

Jens 

-- 
Dr. Jens Schleusener            T-Systems Solutions for Research GmbH
Tel: +49 551 709-2493           Bunsenstr.10
Fax: +49 551 709-2169           D-37073 Goettingen
Jens.Schleusener(at)t-systems.com  http://www.t-systems.com/
Re: [Pound Mailing List] Pound 2.2.3 - LogLevel ignored?
Robert Segall <roseg(at)apsis.ch>		 2007-01-22 18:20:17 [ SNIP ] 
On Sat, 2007-01-20 at 22:02 +0100, Jens Schleusener wrote:
> Hi,
> 
> I just upgraded from Pound 2.2 to 2.2.3 and have the impression that now 
> always "LogLevel 1" is in use and other values of the LogLevel 
> configuration variable are ignored (even 0 - no logging).
> 
> The relevant portion of my configuration seems to be:
> 
>  LogFacility local5
>  LogLevel 3
> 
> Also removing "LogFacility local5" that I "misused" to log via syslogd in 
> /var/log/pound.log didn't change the behaviour.
> 
> Pound 2.2 logs with "LogLevel 3" as desired in "Apache combined log 
> format".
> 
> Greetings 
> 
> Jens

We don't see this problem here. Could anybody confirm it?
-- 
Robert Segall
Apsis GmbH
Postfach, Uetikon am See, CH-8707
Tel: +41-44-920 4904
Re: [Pound Mailing List] Pound 2.2.3 - LogLevel ignored?
Jens Schleusener <Jens.Schleusener(at)t-systems-sfr.com>		 2007-01-22 22:49:47 [ SNIP ] 
On Mon, 22 Jan 2007, Robert Segall wrote:

> On Sat, 2007-01-20 at 22:02 +0100, Jens Schleusener wrote:
> > Hi,
> > 
> > I just upgraded from Pound 2.2 to 2.2.3 and have the impression that now 
> > always "LogLevel 1" is in use and other values of the LogLevel 
> > configuration variable are ignored (even 0 - no logging).
> > 
> > The relevant portion of my configuration seems to be:
> > 
> >  LogFacility local5
> >  LogLevel 3
> > 
> > Also removing "LogFacility local5" that I "misused" to log via syslogd in 
> > /var/log/pound.log didn't change the behaviour.
> > 
> > Pound 2.2 logs with "LogLevel 3" as desired in "Apache combined log 
> > format".
> > 
> > Greetings 
> > 
> > Jens
> 
> We don't see this problem here. Could anybody confirm it?

Self-confirming ;-)

Originally the problem appeared on a SUSE 9.x system but I had reproduced 
"my" problem also on the newest openSUSE 10.2. On both systems runs 
"syslog-ng" (version 1.6.5 respectively 1.6.11).

I installed also Pound 2.2.1 and found the same problem so my problem
occurs between 2.2 and 2.2.1.

I simply do a "./configure --with-ssl" respectively "./configure 
--with-ssl --with-owner=wwwrun", a "make" and thereafter (as "root") a 
"make install".

Here my simple full test-configuration file (in principle):

 ListenHTTPS
   Address 1.2.3.4
   Port    443
   Cert    "/path/to/pound.pem"
   Client 40

   Service
     BackEnd
       Address 192.168.0.10
       Port    80
     End
   End
 End

 LogFacility local5
 LogLevel 3

Ok, if nobody but me has the problem I have probably a stupid bug
in my pound/syslog-ng configuration.

Greetings

Jens

-- 
Dr. Jens Schleusener            T-Systems Solutions for Research GmbH
Tel: +49 551 709-2493           Bunsenstr.10
Fax: +49 551 709-2169           D-37073 Goettingen
Jens.Schleusener(at)t-systems.com  http://www.t-systems.com/
Re: [Pound Mailing List] Pound 2.2.3 - LogLevel ignored?
Robert Segall <roseg(at)apsis.ch>		 2007-01-23 15:42:59 [ SNIP ] 
On Mon, 2007-01-22 at 22:49 +0100, Jens Schleusener wrote:
> Self-confirming ;-)
> 
> Originally the problem appeared on a SUSE 9.x system but I had reproduced 
> "my" problem also on the newest openSUSE 10.2. On both systems runs 
> "syslog-ng" (version 1.6.5 respectively 1.6.11).
> 
> I installed also Pound 2.2.1 and found the same problem so my problem
> occurs between 2.2 and 2.2.1.
> 
> I simply do a "./configure --with-ssl" respectively "./configure 
> --with-ssl --with-owner=wwwrun", a "make" and thereafter (as "root") a 
> "make install".
> 
> Here my simple full test-configuration file (in principle):
> 
>  ListenHTTPS
>    Address 1.2.3.4
>    Port    443
>    Cert    "/path/to/pound.pem"
>    Client 40
> 
>    Service
>      BackEnd
>        Address 192.168.0.10
>        Port    80
>      End
>    End
>  End
> 
>  LogFacility local5
>  LogLevel 3
> 
> Ok, if nobody but me has the problem I have probably a stupid bug
> in my pound/syslog-ng configuration.

Whatever you have done with syslog it can't affect the log string
format. However, there is another problem - just try this for your
config file:

LogFacility local5
LogLevel 3

ListenHTTPS
Address 1.2.3.4
   Port    443
   Cert    "/path/to/pound.pem"
   Client 40

   Service
     BackEnd
       Address 192.168.0.10
       Port    80
     End
   End
End

Let me know if it helps.
-- 
Robert Segall
Apsis GmbH
Postfach, Uetikon am See, CH-8707
Tel: +41-44-920 4904
Re: [Pound Mailing List] Pound 2.2.3 - LogLevel ignored?
Jens Schleusener <Jens.Schleusener(at)t-systems-sfr.com>		 2007-01-23 16:40:17 [ SNIP ] 
Hi Robert,

> On Mon, 2007-01-22 at 22:49 +0100, Jens Schleusener wrote:
> > Self-confirming ;-)
> > 
> > Originally the problem appeared on a SUSE 9.x system but I had reproduced 
> > "my" problem also on the newest openSUSE 10.2. On both systems runs 
> > "syslog-ng" (version 1.6.5 respectively 1.6.11).
> > 
> > I installed also Pound 2.2.1 and found the same problem so my problem
> > occurs between 2.2 and 2.2.1.
> > 
> > I simply do a "./configure --with-ssl" respectively "./configure 
> > --with-ssl --with-owner=wwwrun", a "make" and thereafter (as "root") a 
> > "make install".
> > 
> > Here my simple full test-configuration file (in principle):
> > 
> >  ListenHTTPS
> >    Address 1.2.3.4
> >    Port    443
> >    Cert    "/path/to/pound.pem"
> >    Client 40
> > 
> >    Service
> >      BackEnd
> >        Address 192.168.0.10
> >        Port    80
> >      End
> >    End
> >  End
> > 
> >  LogFacility local5
> >  LogLevel 3
> > 
> > Ok, if nobody but me has the problem I have probably a stupid bug
> > in my pound/syslog-ng configuration.
> 
> Whatever you have done with syslog it can't affect the log string
> format. However, there is another problem - just try this for your
> config file:
> 
> LogFacility local5
> LogLevel 3
> 
> ListenHTTPS
> Address 1.2.3.4
>    Port    443
>    Cert    "/path/to/pound.pem"
>    Client 40
> 
>    Service
>      BackEnd
>        Address 192.168.0.10
>        Port    80
>      End
>    End
> End
> 
> Let me know if it helps.

Great, that helps!

Thanks

Jens

-- 
Dr. Jens Schleusener            T-Systems Solutions for Research GmbH
Tel: +49 551 709-2493           Bunsenstr.10
Fax: +49 551 709-2169           D-37073 Goettingen
Jens.Schleusener(at)t-systems.com  http://www.t-systems.com/
MailBoxer