log4perl - log4j for Perl

On Fri, 27 Jan 2006, Ford, Andy wrote:

> > This looks similar to something that got fixed in Log::Log4perl 1.0.
> > Are you using the latest from CPAN? Also, make sure it's not picking
> > up an old version from somewhere else, i.e.
> >
> >     perl -MLog::Log4perl -le 'print $Log::Log4perl::VERSION'
> >
> > should print 1.02.
> >
>
> It's log4perl 1.02.

Looks like Carp isn't working correctly on this platform. What does

    perl -MCarp -le 'print $Carp::VERSION'

print?

> Just started using log4perl about two days ago and I'm having a blast,

Great to hear :).

> #!/usr/bin/perl
> use warnings;
> use strict;
> use Log::Log4perl qw(get_logger :levels);
> my $logger = get_logger("URLbot");
> $logger->level($DEBUG);
> my $stdout_appender =  Log::Log4perl::Appender->new(
>                          "Log::Log4perl::Appender::Screen",
>                          name      => "screenlog",
>                          stderr    => 0);
> $logger->add_appender($stdout_appender);
> $logger->fatal("Just checking to see if you're awake");
>
> produces the following output with my HP-UX/Perl 5.6.1 system:
>
> Odd number of elements in hash assignment at /opt/perl5//lib/site_perl/5.6.1/Log/Log4perl/Appender/Screen.pm line 27.
> Use of uninitialized value in print at /opt/perl5//lib/site_perl/5.6.1/Log/Log4perl/Appender/Screen.pm line 32.

Sorry to say, this works for me without a hitch on both perl56 and perl58
and Log4perl 1.02 on Linux and FreeBSD.

-- Mike

Mike Schilli
m@...

> -----Original Message-----
> From: Mike Schilli [mailto:m@...]
> Sent: Sunday, January 29, 2006 2:10 AM
> > >
> > >     perl -MLog::Log4perl -le 'print $Log::Log4perl::VERSION'
> > >
> > > should print 1.02.
> > >
> >
> > It's log4perl 1.02.
>=20
> Looks like Carp isn't working correctly on this platform. What does
>=20
>     perl -MCarp -le 'print $Carp::VERSION'
>=20
> print?

Prints nothing, just a newline. Is that bad in perl 5.6.1?

perl -e 'use Carp' is fine, but no version.

Let me see here...Looked in the Carp.pm file and there's no $VERSION in it.

What else can I try to test my Carp?

Andy Ford
A.G. Edwards & Sons Technology Group, Inc.
Enterprise Event Management
314-955-6647
andyford@...



---------------------------------------------------------------------------=
----------
A.G. Edwards & Sons' outgoing and incoming e-mails are electronically
archived and subject to review and/or disclosure to someone other=20
than the recipient.

---------------------------------------------------------------------------=
----------

On Mon, 30 Jan 2006, Ford, Andy wrote:

> Prints nothing, just a newline. Is that bad in perl 5.6.1?
> perl -e 'use Carp' is fine, but no version.

Interesting, I've just reproduced the behaviour on an old perl-5.6.1
installation, featuring a non-versioned Carp. When I replaced the old
Carp.pm by

    http://search.cpan.org/src/NWCLARK/perl-5.8.7/lib/Carp.pm

the tests succeeded.

-- Mike

Mike Schilli
m@...

On Mon, 30 Jan 2006, Mike Schilli wrote:

> When I replaced the old Carp.pm by
>     http://search.cpan.org/src/NWCLARK/perl-5.8.7/lib/Carp.pm
> the tests succeeded.

Also, I've put some logic in place that lets Log4perl's test suite
pass (with skip warnings) if it detects a buggy Carp.pm in the
upcoming Log::Log4perl 1.03 release.

-- Mike

Mike Schilli
m@...

On Fri, 27 Jan 2006, Ford, Andy wrote:

> Posted this in the CPAN bug tracking system, then I discovered this
> list. oOps.

Actually, either way of reporting bugs is fine.

> Subject:      test failures: t/020Easy.t, t/024WarnDieCarp.t, & t/051Extra.t
>
> This is perl, v5.6.1 built for PA-RISC2.0
> HP-UX hqmnntu1 B.11.00 A 9000/800 891950666
>
> t/020Easy............ok 1/20
>
> # Failed test in t/020Easy.t at line 197.
> t/020Easy............NOK 20# '2006/01/24 09:37:13
> LOGCARP at t/020Easy.t line 196
> # LOGCARP at t/020Easy.t line 196
> # at t/020Easy.t line 193
> # '
> # doesn't match '(?-xism:LOGCARP.*020Easy.t line 193)'
> # Looks like you failed 1 test of 20.
> t/020Easy............dubious

This looks similar to something that got fixed in Log::Log4perl 1.0.
Are you using the latest from CPAN? Also, make sure it's not picking
up an old version from somewhere else, i.e.

    perl -MLog::Log4perl -le 'print $Log::Log4perl::VERSION'

should print 1.02.

-- Mike

Mike Schilli
m@...

On Wed, 18 Jan 2006, Jeff Macdonald wrote:

> I'd like to do this (shortend line):
> layout.ConversionPattern = %d{yyyy-MM-dd\tHH:mm:ss}\t%m%n
> but I get this:
>
> ERROR: trying to set layout for mail-parser to 'ARRAY(0x98770ec)' failed at
> /home/jeff/projects/mail-parser-6/test-6/cpan-lib/Log/Log4perl/Config.pm
> line 464.
>
> I want to embed tabs in the log format. How can I do that? I've also tried
> \\t.

Hi Jeff,

I don't get your error message (there's probably something else with
your config file), but "\t" in your conversion pattern will print a
literal "\t". If you want real tabs, you can just type them literally
into the configuration file:

  use Log::Log4perl qw(get_logger);

  my $conf = q(
    log4perl.category.Bar.Twix         = WARN, Screen
    log4perl.appender.Screen          = Log::Log4perl::Appender::Screen
    log4perl.appender.Screen.filename = test.log
    log4perl.appender.Screen.layout   = Log::Log4perl::Layout::PatternLayout
    log4perl.appender.Screen.layout.ConversionPattern = \
       %d{yyyy-MM-dd     HH:mm:ss}       %m%n
  );

  Log::Log4perl::init(\$conf);

  my $logger = get_logger("Bar::Twix");
  $logger->error("Blah");

This will result in

2006-01-18[tab]19:15:09[tab]Blah

-- Mike

Mike Schilli
m@...

yes, it turned out I had other errors too. Thanks for the reply.

On Wed, Jan 18, 2006 at 07:20:03PM -0800, Mike Schilli wrote:
> On Wed, 18 Jan 2006, Jeff Macdonald wrote:
> 
> > I'd like to do this (shortend line):
> > layout.ConversionPattern = %d{yyyy-MM-dd\tHH:mm:ss}\t%m%n
> > but I get this:
> >
> > ERROR: trying to set layout for mail-parser to 'ARRAY(0x98770ec)' failed at
> > /home/jeff/projects/mail-parser-6/test-6/cpan-lib/Log/Log4perl/Config.pm
> > line 464.
> >
> > I want to embed tabs in the log format. How can I do that? I've also tried
> > \\t.
> 
> Hi Jeff,
> 
> I don't get your error message (there's probably something else with
> your config file), but "\t" in your conversion pattern will print a
> literal "\t". If you want real tabs, you can just type them literally
> into the configuration file:
> 
>   use Log::Log4perl qw(get_logger);
> 
>   my $conf = q(
>     log4perl.category.Bar.Twix         = WARN, Screen
>     log4perl.appender.Screen          = Log::Log4perl::Appender::Screen
>     log4perl.appender.Screen.filename = test.log
>     log4perl.appender.Screen.layout   = Log::Log4perl::Layout::PatternLayout
>     log4perl.appender.Screen.layout.ConversionPattern = \
>        %d{yyyy-MM-dd     HH:mm:ss}       %m%n
>   );
> 
>   Log::Log4perl::init(\$conf);
> 
>   my $logger = get_logger("Bar::Twix");
>   $logger->error("Blah");
> 
> This will result in
> 
> 2006-01-18[tab]19:15:09[tab]Blah
> 
> -- Mike
> 
> Mike Schilli
> m@...

-- 
:: Jeff Macdonald | Principal Engineer, Messaging Technologies
:: e-Dialog | jmacdonald@...
:: 131 Hartwell Ave. | Lexington, MA 02421 
:: v: 781-372-1922 | f: 781-863-8118 
:: http://www.e-dialog.com

On Wed, 4 Jan 2006, Anthony Chee wrote:

> Besides INFO, DEBUG, ...... built-in level, can I build custom level OTHER
> for my program?

Sure, check out the "custom log levels" of the main manual page:

    http://log4perl.sourceforge.net/d/Log/Log4perl.html#d21fb

-- Mike

Mike Schilli
m@...

Thanks for help.

It mentioned create_custom_level can be put in configuration file. I would
like to know what's the syntax?

Is it something like

Log4perl.Logger.create_custom_level() = WARN ?

Regards,
Anthony
 

-----Original Message-----
From: Mike Schilli [mailto:m@...] 
Sent: Wednesday, January 04, 2006 12:28 PM
To: Anthony Chee
Cc: log4perl-devel@...
Subject: Re: [log4perl-devel] Custom Level/Priority

On Wed, 4 Jan 2006, Anthony Chee wrote:

> Besides INFO, DEBUG, ...... built-in level, can I build custom level OTHER
> for my program?

Sure, check out the "custom log levels" of the main manual page:

    http://log4perl.sourceforge.net/d/Log/Log4perl.html#d21fb

-- Mike

Mike Schilli
m@...

On Wed, 4 Jan 2006, Anthony Chee wrote:

> It mentioned create_custom_level can be put in configuration file. I would
> like to know what's the syntax?

It says that "These levels can also be *used* in your config file", which means
you define them (in Perl) before you call Log::Log4perl::init(...) in
your code. Levels defined before init() can then used in the config file.

-- Mike

Mike Schilli
m@...

Anthony Chee wrote:

> Hi,
>
> Besides INFO, DEBUG, ...... built-in level, can I build custom level 
> OTHER for my program?
>
> Regards,
>
> Anthony
>

This *isnt* to say youre *wrong*, but Id point you to some guidance in 
the docs.


from perldoc Log::Log4perl, section Log Levels

But nobody does that, really. Neither does anyone need more logging 
levels than these predefined
ones. If you think you do, I would suggest you look into steering your 
logging behaviour via the
category mechanism.

If you need to find out if the currently configured logging level would 
allow a logger’s logging
statement to go through, use the logger’s "is_level()" methods:



'OTHER' seems both reasonable, and a cop-out, both at the same time.

Youve got *the-man* answering questions, I'll wager that if you
speak to your particular circumstance, and why you chose the OTHER way 
(pun intended),
he can respond to the tradeoffs in your case.