log4perl-devel — Ongoing log4perl development

Re: [log4perl-devel] package 'Log::Dispatch::Email::MailSender' notregistered for warnings

[Mike S. <m...@pe...>]

On Tue, 24 Nov 2009, Linke Markus (KSTB 11) wrote:

> Strange enough I now have the same problem again on our production
> server. I have just checked the modules and they are the same as on
> the dev box where upgrading Log::Dispatch had solved the issue before.

As I might have mentioned before, Log::Dispatch is a separate module
maintained by a different crew.

But since you said the upgrade fixed your development box, I suspect
that the upgrade on the production box didn't go over well and maybe
you're still pulling the old version? Try

     $ /usr/local/bin/perl -d -e 1
     DB<1> use Log::Dispatch
     DB<2> print $Log::Dispatch::VERSION

and check the version number printed.

-- Mike

Mike Schilli
m...@pe...

>
> Any ideas?
>
> Thanks,
> Markus
>
>
> -----Original Message-----
> From: Linke Markus (KSTB 11)
> Sent: Freitag, 10. Juli 2009 07:56
> To: Mike Schilli
> Cc: log...@li...
> Subject: Re: [log4perl-devel] package 'Log::Dispatch::Email::MailSender'
> notregistered for warnings
>
> Problem solved; thanks a lot!
>
> -----Original Message-----
> From: Mike Schilli [mailto:m...@pe...]
> Sent: Mittwoch, 8. Juli 2009 18:53
> To: Linke Markus (KSTB 11)
> Cc: Mike Schilli; log...@li...
> Subject: RE: [log4perl-devel] package 'Log::Dispatch::Email::MailSender'
> not registered for warnings
>
> On Wed, 8 Jul 2009, Linke Markus (KSTB 11) wrote:
>
>> I only have 2.21, you think that might be the reason?
>
> Possibly. I'm not affiliated with Log::Dispatch, but its 2.22 change log
> has the line
>
> "- Fixed a misuse of warnings::enabled(). Reported by Darian Patrick. RT
> #39784."
>
> which indicates a fix in this area. Give it a try!
>
> -- Mike
>
> Mike Schilli
> m...@pe...
>
> ------------------------------------------------------------------------
> ------
> Enter the BlackBerry Developer Challenge
> This is your chance to win up to $100,000 in prizes! For a limited time,
>
> vendors submitting new applications to BlackBerry App World(TM) will
> have
> the opportunity to enter the BlackBerry Developer Challenge. See full
> prize
> details at: http://p.sf.net/sfu/Challenge
> _______________________________________________
> log4perl-devel mailing list
> log...@li...
> https://lists.sourceforge.net/lists/listinfo/log4perl-devel
>

Re: [log4perl-devel] package 'Log::Dispatch::Email::MailSender' notregistered for warnings

[Linke M. (K. 11) <mar...@cr...>]

Hi,

Strange enough I now have the same problem again on our production
server. I have just checked the modules and they are the same as on the
dev box where upgrading Log::Dispatch had solved the issue before. 

Any ideas?

Thanks,
Markus


-----Original Message-----
From: Linke Markus (KSTB 11) 
Sent: Freitag, 10. Juli 2009 07:56
To: Mike Schilli
Cc: log...@li...
Subject: Re: [log4perl-devel] package 'Log::Dispatch::Email::MailSender'
notregistered for warnings

Problem solved; thanks a lot! 

-----Original Message-----
From: Mike Schilli [mailto:m...@pe...] 
Sent: Mittwoch, 8. Juli 2009 18:53
To: Linke Markus (KSTB 11)
Cc: Mike Schilli; log...@li...
Subject: RE: [log4perl-devel] package 'Log::Dispatch::Email::MailSender'
not registered for warnings

On Wed, 8 Jul 2009, Linke Markus (KSTB 11) wrote:

> I only have 2.21, you think that might be the reason?

Possibly. I'm not affiliated with Log::Dispatch, but its 2.22 change log
has the line

"- Fixed a misuse of warnings::enabled(). Reported by Darian Patrick. RT
#39784."

which indicates a fix in this area. Give it a try!

-- Mike

Mike Schilli
m...@pe...

------------------------------------------------------------------------
------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time,

vendors submitting new applications to BlackBerry App World(TM) will
have
the opportunity to enter the BlackBerry Developer Challenge. See full
prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
log4perl-devel mailing list
log...@li...
https://lists.sourceforge.net/lists/listinfo/log4perl-devel

[log4perl-devel] Log4perl 1.26 released

[Mike S. <m...@pe...>]

Hi Log4perl enthusiasts,

Log4perl 1.26 has just been released on github:

     http://github.com/mschilli/log4perl/tarball/rel_126

Changes in this release:

1.26 (2009/11/22)
     *   (ms) [RT 50495] Perl code in the config file is now evaluated/
         compiled after the configuration parser has done its work,
         opening up Perl subroutines to all configuration parsers, not
         just PropertyConfigurator. Configuration subs for cspecs,
         filter, warp_message and appender triggers are sheltered. The
         previous, flawed implementation surfaced while using a
         'trigger' category, reported by Olivier Bilodeau.
     *   (ms) [RT 50090] Added non-portable linebreaks to PatternLayout
         (requested by Zdeněk Juran).
     *   (ms) [RT 50094] Docfix for PatternLayout in main manpage
         (spotted by Peter Rabbitson).
     *   (ms) [RT 28679] Added exists() to "Threshold" keyword
         uppercase check.
     *   (ms) Took out Class::Prototyped testcase after it got all
         weird and introduced backward-incompatible changes.

If all goes well, it'll hit CPAN in a couple of days.

-- Mike

Mike Schilli
m...@pe...

Re: [log4perl-devel] simple example doesn't work as expected

[Mike S. <m...@pe...>]

On Sun, 25 Oct 2009, Ali M. wrote:

> this simple example from the mastering perl book doesn't work as expected
> both messages from ERROR and DEBUG prints to the error_log file what
> am i missing ??

Apparently, the book author didn't test the code he was writing down ;).

Here's how to do what you want:

     http://www.mail-archive.com/log...@li.../msg00205.html

-- Mike

Mike Schilli
m...@pe...

[log4perl-devel] simple example doesn't work as expected

[Ali M. <tcl...@gm...>]

this simple example from the mastering perl book doesn't work as expected
both messages from ERROR and DEBUG prints to the error_log file

what am i missing ??


use strict;
use warnings;

use Log::Log4perl qw(:easy);

Log::Log4perl->easy_init(
    {
    file  => ">> error_log",
    level => $ERROR,
    },

    {
    file  => "STDERR",
    level => $DEBUG,
    }
    );

ERROR( "I've got something to say!" );

DEBUG( "Hey! What's going on in there?" );

Re: [log4perl-devel] Log4perl 1.25: Win XP + ActivePerl 5.10: Error running 'nmake test'

[Mike S. <m...@pe...>]

On Mon, 12 Oct 2009, Rindfrey, Klaus (EXT) wrote:

> we use Log4perl 1.21 (with Win XP, Active perl 5.10), which works
> fine.  Now i tried 1.25: The test "059Prototyped" causes an error
> (unfortunately, the contents of the error box I appended is in
> german).

That's no problem at all, I'm originally from Germany :).

The error indicates that the operating system pulled the rug from under
perl, because it thought that it read from an invalid location.

That's very interesting, because there's nothing in the test script that
is supposed to cause such a severe error. What's more, here's a test
report for Log4perl 1.25 on Windows XP, which ran successfully:

     http://www.nntp.perl.org/group/perl.cpan.testers/2009/10/msg5482885.html

One thing I need you to confirm: Does the box you were running the test
on have Class::Prototype installed? It's a rarely used module, so
chances are that it's not installed, in which case the test script
should just report this fact and terminate (as shown in the error report
linked to above).

-- Mike

Mike Schilli
m...@pe...

> Test output:
>
> ###############################################################################
>
> t/052Utf8............ok
> t/053Resurrect.......ok
> t/054Subclass........ok
> t/055AppDestroy......ok
> t/056SyncApp2........skipped
>        all skipped: - only with L4P_ALL_TESTS
> t/057MsgChomp........ok
> t/058Warnings........ok
> t/059Prototyped......dubious
>        Test returned status 5 (wstat 1280, 0x500)
>        after all the subtests completed successfully
> Failed Test       Stat Wstat Total Fail  List of Failed
> -------------------------------------------------------------------------------
> t/059Prototyped.t    5  1280     1    0  ??
> 5 tests and 12 subtests skipped.
> Failed 1/62 test scripts. 0/652 subtests failed.
> Files=62, Tests=652, 40 wallclock secs ( 0.00 cusr +  0.00 csys =  0.00 CPU)
> Failed 1/62 test programs. 0/652 subtests failed.
> NMAKE : fatal error U1077: 'C:\WINNT\system32\cmd.exe' : return code '0x5'
> Stop.
>
> ###############################################################################
>
> Our sytem: Windows XP Professional, Version 2002, Service Pack 3
>
> Our perl:
>
>  This is perl, v5.10.0 built for MSWin32-x86-multi-thread
>  (with 5 registered patches, see perl -V for more detail)
>
>  Copyright 1987-2007, Larry Wall
>
>  Binary build 1004 [287188] provided by ActiveState http://www.ActiveState.com
>  Built Sep  3 2008 13:16:37
>
>
>
>
> Mit freundlichem Gruß / Best regards
>
> Klaus Rindfrey
>
> Siemens AG
> Industry Sector, I IA AS R&D DH A 2
> Tel.    : +49 (9621) 80-5813
> mailto:kla...@si... <mailto:kla...@si...>
> <http://www.siemens.com/automation> http://www.siemens.com/automation <http://www.siemens.com/automation>
>
>
>
> HOTLINE: Configuration Management S7PLUS Amberg
>
> mailto:CMA...@si... <mailto:CMA...@si...>
>
>
>
> Siemens Aktiengesellschaft: Chairman of the Supervisory Board: Gerhard Cromme
> Managing Board: Peter Loescher, Chairman, President and Chief Executive Officer;
> Wolfgang Dehen, Heinrich Hiesinger, Joe Kaeser, Barbara Kux, Hermann Requardt,
> Siegfried Russwurm, Peter Y. Solmssen
> Registered offices: Berlin and Munich;
> Commercial registries: Berlin Charlottenburg, HRB 12300, Munich, HRB 6684
> WEEE-Reg.-No. DE 23691322
>
>

[log4perl-devel] Log4perl 1.25: Win XP + ActivePerl 5.10: Error running 'nmake test'

[Rindfrey, K. (EXT) <kla...@si...>]

Hi,

we use Log4perl 1.21 (with Win XP, Active perl 5.10), which works fine.
Now i tried 1.25: The test "059Prototyped" causes an error (unfortunately, the contents of the error box I appended is in german).

Test output:

###############################################################################
 
t/052Utf8............ok
t/053Resurrect.......ok
t/054Subclass........ok
t/055AppDestroy......ok
t/056SyncApp2........skipped
        all skipped: - only with L4P_ALL_TESTS
t/057MsgChomp........ok
t/058Warnings........ok
t/059Prototyped......dubious
        Test returned status 5 (wstat 1280, 0x500)
        after all the subtests completed successfully
Failed Test       Stat Wstat Total Fail  List of Failed
-------------------------------------------------------------------------------
t/059Prototyped.t    5  1280     1    0  ??
5 tests and 12 subtests skipped.
Failed 1/62 test scripts. 0/652 subtests failed.
Files=62, Tests=652, 40 wallclock secs ( 0.00 cusr +  0.00 csys =  0.00 CPU)
Failed 1/62 test programs. 0/652 subtests failed.
NMAKE : fatal error U1077: 'C:\WINNT\system32\cmd.exe' : return code '0x5'
Stop.

###############################################################################

Our sytem: Windows XP Professional, Version 2002, Service Pack 3

Our perl:

  This is perl, v5.10.0 built for MSWin32-x86-multi-thread
  (with 5 registered patches, see perl -V for more detail)

  Copyright 1987-2007, Larry Wall

  Binary build 1004 [287188] provided by ActiveState http://www.ActiveState.com
  Built Sep  3 2008 13:16:37

 
 

Mit freundlichem Gruß / Best regards

Klaus Rindfrey

Siemens AG
Industry Sector, I IA AS R&D DH A 2
Tel.    : +49 (9621) 80-5813
mailto:kla...@si... <mailto:kla...@si...> 
<http://www.siemens.com/automation> http://www.siemens.com/automation <http://www.siemens.com/automation> 

 

HOTLINE: Configuration Management S7PLUS Amberg 

mailto:CMA...@si... <mailto:CMA...@si...> 

 

Siemens Aktiengesellschaft: Chairman of the Supervisory Board: Gerhard Cromme
Managing Board: Peter Loescher, Chairman, President and Chief Executive Officer; 
Wolfgang Dehen, Heinrich Hiesinger, Joe Kaeser, Barbara Kux, Hermann Requardt,
Siegfried Russwurm, Peter Y. Solmssen
Registered offices: Berlin and Munich; 
Commercial registries: Berlin Charlottenburg, HRB 12300, Munich, HRB 6684
WEEE-Reg.-No. DE 23691322

Re: [log4perl-devel] Appender::File : File handle gets undef

[Mike S. <m...@pe...>]

On Mon, 5 Oct 2009, Ronald Fischer wrote:

> The "file switching" is done using the following code:
>
> Log::Log4perl->appender_by_name($requestlogger_appender_name)-
> >file_switch($relpathname);

You might be running out of file handles due to a bug fixed in release
1.25. Please make sure you run the latest Log4perl from CPAN.

-- Mike

Mike Schilli
m...@pe...

> We recently found that once in a while (every couple of hours),
> File.pm crashes on a write operation.  By inserting a suitable check,
> we found that the file handle happens to be undef in
> File::Appender::log().
>
> The logger in question is a bit unusual in that it undergoes frequent
> file switches - frequent means that
> on times there might be even serveral  file switches per second.
>
> The appender is defined by passing a reference to a string to
> Log::Log4perl::init(), like this:
>
> init(\ qq(
> ...
>      log4perl.appender.Reqlog=Log::Log4perl::Appender::File
>      log4perl.appender.Reqlog.name=$requestlogger_appender_name
>      log4perl.appender.Reqlog.filename=$initial_reqlog
>      log4perl.appender.Reqlog.mode=append
>      log4perl.appender.Reqlog.layout=Log::Log4perl::Layout::PatternLayout
>      log4perl.appender.Reqlog.layout.ConversionPattern=%.5p
>      %d{HH:mm:ss} %M(%L) %m%n
> ...
> ));
>
> The variables interpolated into this string are defined as follows:
>
> use File::Spec::Functions qw(devnull);
> my $initial_reqlog=devnull; # NUL on Windows
> my $requestlogger_appender_name='ReqlogApp';
>
...
>
> During the lifetime of the program (which runs uninterrupted for days,
> sometimes a few weeks), maybe
> 30-100 files per day are created that way, but the number of file
> switches is considerably higher,
> because sometimes only one or two lines (or even none!) are logged into
> one log file, then a switch to
> another logfile occurs, then a switch back to the first one, etc.  I
> mention this, because it might be
> possible that our problems are related to the file switch pattern.
>
> At the moment we have no idea why the file handle suddenly would be
> undef, and we try to research
> further. At the moment, it would already help if someone could point out
> whether
>
> - the problem of "disappearing file handle" has already bee seen before,
> or
> - have a better guess what could be the cause of our problem (maybe
> Windows gets upset
> due to so many "opening and closing of files"?)
>
> Ronald
>
>
>
>
> --
> Ronald Fischer <ro...@em...>
> +  If a packet hits a pocket on a socket on a port,
> +  and the bus is interrupted and the interrupt's not caught,
> +  then the socket packet pocket has an error to report.
> +             (cited after Peter van der Linden)
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9&#45;12, 2009. Register now&#33;
> http://p.sf.net/sfu/devconf
> _______________________________________________
> log4perl-devel mailing list
> log...@li...
> https://lists.sourceforge.net/lists/listinfo/log4perl-devel
>

Re: [log4perl-devel] Redirecting Screen appender does not work

[Mike S. <m...@pe...>]

On Mon, 5 Oct 2009, Ronald Fischer wrote:

> I have defined a screen appender like this:
>      log4perl.appender.Screen=Log::Log4perl::Appender::Screen
>      log4perl.appender.Screen.layout=Log::Log4perl::Layout::PatternLayout
>      log4perl.appender.Screen.layout.ConversionPattern=%.1p %d{HH:mm}
>      %M{2}(%L) %m%n
> But when I run my program with redirection, say
>   myprog.pl .... >screen.log
> the logging output still is displayed on the console, and screen.log
> ends up with length zero.

By default, the screen appender writes to STDERR, which your redirection
doesn't capture. To have it to write to STDOUT instead, use

     log4perl.appender.Screen.stderr = 0

in your configuration file.

-- Mike

Mike Schilli
m...@pe...

[log4perl-devel] Appender::File : File handle gets undef

[Ronald F. <yn...@mm...>]

We recently found that once in a while (every couple of hours), File.pm
crashes on a write operation. 
By inserting a suitable check, we found that the file handle happens to
be undef in File::Appender::log().

The logger in question is a bit unusual in that it undergoes frequent
file switches - frequent means that 
on times there might be even serveral  file switches per second.

The appender is defined by passing a reference to a string to
Log::Log4perl::init(), like this:

init(\ qq(
...
      log4perl.appender.Reqlog=Log::Log4perl::Appender::File
      log4perl.appender.Reqlog.name=$requestlogger_appender_name
      log4perl.appender.Reqlog.filename=$initial_reqlog
      log4perl.appender.Reqlog.mode=append
      log4perl.appender.Reqlog.layout=Log::Log4perl::Layout::PatternLayout
      log4perl.appender.Reqlog.layout.ConversionPattern=%.5p
      %d{HH:mm:ss} %M(%L) %m%n
...
));

The variables interpolated into this string are defined as follows:

use File::Spec::Functions qw(devnull);
my $initial_reqlog=devnull; # NUL on Windows
my $requestlogger_appender_name='ReqlogApp';

The "file switching" is done using the following code:

Log::Log4perl->appender_by_name($requestlogger_appender_name)->file_switch($relpathname);

During the lifetime of the program (which runs uninterrupted for days,
sometimes a few weeks), maybe 
30-100 files per day are created that way, but the number of file
switches is considerably higher,
because sometimes only one or two lines (or even none!) are logged into
one log file, then a switch to 
another logfile occurs, then a switch back to the first one, etc.  I
mention this, because it might be 
possible that our problems are related to the file switch pattern. 

At the moment we have no idea why the file handle suddenly would be
undef, and we try to research
further. At the moment, it would already help if someone could point out
whether

- the problem of "disappearing file handle" has already bee seen before,
or
- have a better guess what could be the cause of our problem (maybe
Windows gets upset
due to so many "opening and closing of files"?)

Ronald




-- 
Ronald Fischer <ro...@em...>
+  If a packet hits a pocket on a socket on a port, 
+  and the bus is interrupted and the interrupt's not caught,
+  then the socket packet pocket has an error to report.
+		(cited after Peter van der Linden)

[log4perl-devel] Redirecting Screen appender does not work

[Ronald F. <yn...@mm...>]

According to the docs:

  "Log::Log4perl::Appender::Screen - Log to STDOUT/STDERR"

I have defined a screen appender like this:

      log4perl.appender.Screen=Log::Log4perl::Appender::Screen
      log4perl.appender.Screen.layout=Log::Log4perl::Layout::PatternLayout
      log4perl.appender.Screen.layout.ConversionPattern=%.1p %d{HH:mm}
      %M{2}(%L) %m%n

But when I run my program with redirection, say

   myprog.pl .... >screen.log

the logging output still is displayed on the console, and screen.log
ends up with length zero.

This is on Windows 2000 using ActiveState Perl.

Ronald

-- 
Ronald Fischer <ro...@em...>
+  If a packet hits a pocket on a socket on a port, 
+  and the bus is interrupted and the interrupt's not caught,
+  then the socket packet pocket has an error to report.
+		(cited after Peter van der Linden)

[log4perl-devel] Log4perl 1.25 released

[Mike S. <m...@pe...>]

Hi Log4perl enthusiasts,

release 1.25 just went out to log4perl.com, here's the changes:

1.25 (2009/09/27)
     *   (ms) Appender::File is now closing (or sysclosing) the file
              on file_close() instead of just undef'ing the handle.
     *   (ms) Added l4p-tmpl helper script to help whipping up a new
              log4perl configuration file.
     *   (ms) Fixed uninitialized warning on XML configuration files,
              reported by jbkilian on the sourceforge mailing list.
     *   (ms) Applied patch [RT 43426] by AFF <af...@cp...> to have
              appender_thresholds_adjust return number of appenders changed.
     *   (ms) [RT 34400] New :nostrict target which allows redefining a
              category within a Log4perl configuration file without error
              or even a warning.
     *   (ms) [RT 34401] Applied patch by Jae Gangemi, who fixed
              code references in @INC on Win32 systems.
     *   (ms) [RT 32259] Patternlayout now supports %R, which returns the
              number of milliseconds elapsed from last logging event to
              the current logging event (thanks to Emmanuel Rodriguez for
              the patch).
     *   (ms) [RT 30899] Color configuration and attribute support
              added to ScreenColoredLevels appender by Jason Kohles.
     *   (ms) [RT 28987] If UNIVERSAL is available, appender existence is
              now verified by checking can() on the appender's new()
              method (applied modified patch by Gabriel Berriz).

If all goes well, it'll hit CPAN in a couple of days.

Enjoy!

-- Mike

Mike Schilli
m...@pe...

Re: [log4perl-devel] log4perl License?

[Mike S. <m...@pe...>]

On Fri, 11 Sep 2009, Terry Kummell wrote:

> Do we need to license log4perl in order to use it in our product?

Hi Terry,

Log4perl is provided under the same license as perl itself:

     http://dev.perl.org/licenses/

Hope that helps!

-- Mike

Mike Schilli
m...@pe...

[log4perl-devel] log4perl License?

[Terry K. <TKu...@al...>]

Do we need to license log4perl in order to use it in our product?

 

Regards,

Terry

 

--------------------------

Terry Kummell

Aldon Computer Group

6001 Shellmound St.  Suite 600

Emeryville, CA 94608

(510) 285-8527

 

Re: [log4perl-devel] Limiting file size in log4perl

[Mike S. <m...@pe...>]

On Wed, 26 Aug 2009, Ronald Fischer wrote:

> Thanks a lot! The perldoc says that FileRotate "provides a simple
> object for logging to files under the Log::Dispatch::* system", so I'm
> surprised that it will also work with Log::Log4perl, but I'll give it
> a try.

Yep, Log4perl fully supports the Log::Dispatch appenders:

     http://search.cpan.org/dist/Log-Log4perl/lib/Log/Log4perl.pm#Additional_Appenders_via_Log::Dispatch

If there's an equivalent in Log4perl (like for a file appender), using
the native appenders is recommended because they provide additional
functionality.

-- Mike

Mike Schilli
m...@pe...

Re: [log4perl-devel] Limiting file size in log4perl

[Ronald F. <yn...@mm...>]

On Tue, 25 Aug 2009 09:39 -0700, "Mike Schilli" <m...@pe...>
wrote:
> > Is there an easy way to limit the size of a log file? I'm not looking
> > for a rollover solution, but for one, where a new file is created if
> > the old one exceeds a certain size.
> 
> That's pretty much the case with Log::Dispatch::FileRotate, a given file
> size, and a max value of 1. 

Thanks a lot! The perldoc says that FileRotate "provides a simple object 
for logging to files under the Log::Dispatch::* system", so I'm
surprised
that it will also work with Log::Log4perl, but I'll give it a try.

Ronald
-- 
Ronald Fischer <ro...@em...>
+  If a packet hits a pocket on a socket on a port, 
+  and the bus is interrupted and the interrupt's not caught,
+  then the socket packet pocket has an error to report.
+		(cited after Peter van der Linden)

Re: [log4perl-devel] Limiting file size in log4perl

[Mike S. <m...@pe...>]

On Mon, 24 Aug 2009, Ronald Fischer wrote:

> Is there an easy way to limit the size of a log file? I'm not looking
> for a rollover solution, but for one, where a new file is created if
> the old one exceeds a certain size.

That's pretty much the case with Log::Dispatch::FileRotate, a given file
size, and a max value of 1. If somefile.log grows larger than 'size'
bytes, it'll move it over to somefile.log.1 and moves it over to
somefile.log. Alternatively, you can use an external rotator with
similar settings.

If you don't want to roll over, but truncate the logfile in this case
(although this seems weird, as you might end up with an almost-empty
logfile at times), you need to write your own appender as outlined in

     http://search.cpan.org/dist/Log-Log4perl/lib/Log/Log4perl/FAQ.pm#How_can_I_write_my_own_appender?

> My idea is to intercept each call to Log4perl, test the size of the
> log file, and switch to a new log file if the old one got too big.

That's exactly what Log::Dispatch::FileRotate does if you call it with
a max value of 1.

-- Mike

Mike Schilli
m...@pe...

[log4perl-devel] Limiting file size in log4perl

[Ronald F. <yn...@mm...>]

Is there an easy way to limit the size of a log file? I'm not looking 
for a rollover solution, but for one, where a new file is created if
the old one exceeds a certain size.

My idea is to intercept each call to Log4perl, test the size of the
log file, and switch to a new log file if the old one got too big. 
But maybe there is something built into Log4perl already, which
works in that way? I checked the perldoc's and didn't find anything
suitable though...

Ronald
-- 
Ronald Fischer <ro...@em...>
+  If a packet hits a pocket on a socket on a port, 
+  and the bus is interrupted and the interrupt's not caught,
+  then the socket packet pocket has an error to report.
+		(cited after Peter van der Linden)

Re: [log4perl-devel] package 'Log::Dispatch::Email::MailSender' not registered for warnings

[Linke M. (K. 11) <mar...@cr...>]

Problem solved; thanks a lot! 

-----Original Message-----
From: Mike Schilli [mailto:m...@pe...] 
Sent: Mittwoch, 8. Juli 2009 18:53
To: Linke Markus (KSTB 11)
Cc: Mike Schilli; log...@li...
Subject: RE: [log4perl-devel] package 'Log::Dispatch::Email::MailSender'
not registered for warnings

On Wed, 8 Jul 2009, Linke Markus (KSTB 11) wrote:

> I only have 2.21, you think that might be the reason?

Possibly. I'm not affiliated with Log::Dispatch, but its 2.22 change log
has the line

"- Fixed a misuse of warnings::enabled(). Reported by Darian Patrick. RT
#39784."

which indicates a fix in this area. Give it a try!

-- Mike

Mike Schilli
m...@pe...

[log4perl-devel] Log::Log4perl 1.24 released

[Mike S. <m...@pe...>]

Log::Log4perl 1.24 has just been released to CPAN.

It contains the following changes:

1.24 (2009/07/08)
     *   (ms) Fixed bug with Log::Log4perl::Util::tmpfile_name which
 	     surfaced on VMS, reported by Ben Humphreys.
     *   (ms) Fixed system-wide threshold to no longer lower appender
 	     thresholds. Bug reported by Jean-Denis Muys.
     *   (ms) Added benchmark to determine impact of eval-free handlers
     *   (ms) Merged with eval_free branch. Now there are no more
 	     eval("") statements left in the code, making it much easier
              to debug. Performance on init() is about the same,
              performance on init_and_watch() (noops and logged
              statements alike) is 25% slower but still in the range
              of 400,000/sec on my 1.80Ghz CPU.

Enjoy!

-- Mike

Mike Schilli
m...@pe...

Re: [log4perl-devel] package 'Log::Dispatch::Email::MailSender' not registered for warnings

[Mike S. <m...@pe...>]

On Wed, 8 Jul 2009, Linke Markus (KSTB 11) wrote:

> I only have 2.21, you think that might be the reason?

Possibly. I'm not affiliated with Log::Dispatch, but its 2.22 change log
has the line

"- Fixed a misuse of warnings::enabled(). Reported by Darian Patrick. RT
#39784."

which indicates a fix in this area. Give it a try!

-- Mike

Mike Schilli
m...@pe...

Re: [log4perl-devel] package 'Log::Dispatch::Email::MailSender' not registered for warnings

[Linke M. (K. 11) <mar...@cr...>]

Hi Mike,

I only have 2.21, you think that might be the reason? 

mxint1@zus45a-5402 mxint1 $ perl -e 'use Log::Log4perl; use
Log::Dispatch 2.22;'
Log::Dispatch version 2.22 required--this is only version 2.21 at -e
line 1.
BEGIN failed--compilation aborted at -e line 1.        

Given the kind of environment it's going to be a lot of pain to get this
updated, so I would only like to do this if it is really required ...

Cheers,
Markus
 

-----Original Message-----
From: Mike Schilli [mailto:m...@pe...] 
Sent: Dienstag, 7. Juli 2009 17:35
To: Linke Markus (KSTB 11)
Cc: log...@li...
Subject: Re: [log4perl-devel] package 'Log::Dispatch::Email::MailSender'
not registered for warnings

On Tue, 7 Jul 2009, Linke Markus (KSTB 11) wrote:

> After successfully running the whole script it throws a warning:
> package 'Log::Dispatch::Email::MailSender' not registered for warnings

> at 
> /app/CMpkg2/perl_588/lib/site_perl/5.8.8/Log/Dispatch/Email/MailSender
> .p m line 58 END failed--call queue aborted.

Which version of Log::Dispatch are you using, the latest from CPAN,
2.22?

-- Mike

Mike Schilli
m...@pe...

Re: [log4perl-devel] package 'Log::Dispatch::Email::MailSender' not registered for warnings

[Mike S. <m...@pe...>]

On Tue, 7 Jul 2009, Linke Markus (KSTB 11) wrote:

> After successfully running the whole script it throws a warning:
> package 'Log::Dispatch::Email::MailSender' not registered for warnings
> at
> /app/CMpkg2/perl_588/lib/site_perl/5.8.8/Log/Dispatch/Email/MailSender.p
> m line 58 END failed--call queue aborted.

Which version of Log::Dispatch are you using, the latest from CPAN,
2.22?

-- Mike

Mike Schilli
m...@pe...

[log4perl-devel] package 'Log::Dispatch::Email::MailSender' not registered for warnings

[Linke M. (K. 11) <mar...@cr...>]

Hi,

I'm using Log4perl for a while but have a problem which I haven't seen
before.

After successfully running the whole script it throws a warning:

2009-07-07 16:50:05 [valuations.pl:main]  INFO> Duplicated valuations
removed.
2009-07-07 16:50:05 [valuations.pl:main]  INFO> Unchanged valuations
removed.
2009-07-07 16:50:05 [valuations.pl:main]  INFO> Report on duplicate
entries in MTM#IMPORT#HELIOS1_DBF completed.
2009-07-07 16:50:05 [valuations.pl:main]  INFO> Duplicated valuations
removed from MTM#IMPORT#HELIOS1_DBF.
2009-07-07 16:50:05 [valuations.pl:main]  INFO>
2009-07-07 16:50:05 [valuations.pl:main]  INFO> Summary of results:
2009-07-07 16:50:05 [valuations.pl:main]  INFO> -------------------
2009-07-07 16:50:05 [valuations.pl:main]  INFO>
2009-07-07 16:50:05 [valuations.pl:main]  INFO> All files (1) with 5
entries uploaded to Mx.3 financial database.
2009-07-07 16:50:05 [valuations.pl:main]  INFO> Murex trade missing for
0 valuations total.
2009-07-07 16:50:05 [valuations.pl:main]  INFO> valuations on dead deals
0 valuations total.
2009-07-07 16:50:05 [valuations.pl:main]  INFO> currency mismatch for
valuation 0 valuations total.
2009-07-07 16:50:05 [valuations.pl:main]  INFO> No valuations provided
4253 valuations total.
2009-07-07 16:50:05 [valuations.pl:main]  INFO> done. Please run import
processing script now.
package 'Log::Dispatch::Email::MailSender' not registered for warnings
at
/app/CMpkg2/perl_588/lib/site_perl/5.8.8/Log/Dispatch/Email/MailSender.p
m line 58
END failed--call queue aborted.                         

Has anybody seen this before?

My config looks like this:

2009-07-07 16:51:07 [valuations.pl:main]  INFO> Program
./scripts/valuations.pl started with timestamp 0707165107.
2009-07-07 16:51:07 [valuations.pl:main] DEBUG> log4perl.logger=DEBUG,
File, Detail, Screen, Mailer, MailerInfo
log4perl.appender.Screen=Log::Log4perl::Appender::ScreenColoredLevels
log4perl.appender.Screen.layout=Log::Log4perl::Layout::PatternLayout
log4perl.appender.Screen.layout.ConversionPattern=%d{yyyy-MM-dd
HH:mm:ss} [%F{1}:%c{1}] %5p> %m%n
log4perl.appender.Screen.min_level=INFO

log4perl.appender.File=Log::Dispatch::File
log4perl.appender.File.filename=xxx
log4perl.appender.File.mode=append
log4perl.appender.File.min_level=info
log4perl.appender.File.TZ=GMT
log4perl.appender.File.DatePattern=yyyy-MM-dd-a
log4perl.appender.File.max=10
log4perl.appender.File.layout=Log::Log4perl::Layout::PatternLayout
log4perl.appender.File.layout.ConversionPattern=%d{yyyy-MM-dd HH:mm:ss}
[%F{1}:%c{1}] %5p> %m%n

log4perl.appender.Detail=Log::Dispatch::File
log4perl.appender.Detail.filename=xxx
log4perl.appender.Detail.mode=append
log4perl.appender.Detail.min_level=debug
log4perl.appender.Detail.TZ=GMT
log4perl.appender.Detail.DatePattern=yyyy-MM-dd-a
log4perl.appender.Detail.max=3
log4perl.appender.Detail.layout=Log::Log4perl::Layout::PatternLayout
log4perl.appender.Detail.layout.ConversionPattern=%d{yyyy-MM-dd
HH:mm:ss} [%F{1}:%c{1}] %5p> %m%n

log4perl.appender.Mailer         = Log::Dispatch::Email::MailSender
log4perl.appender.Mailer.to      = em...@em...
log4perl.appender.Mailer.from    = em...@em...
log4perl.appender.Mailer.smtp    = host
log4perl.appender.Mailer.Server  = host
log4perl.appender.Mailer.buffer  = 0
log4perl.appender.Mailer.subject = subject
log4perl.appender.Mailer.min_level=error
log4perl.appender.Mailer.layout  = Log::Log4perl::Layout::PatternLayout
log4perl.appender.Mailer.layout.ConversionPattern=%d{yyyy-MM-dd
HH:mm:ss} %5p> %m%n

log4perl.appender.MailerInfo         = Log::Dispatch::Email::MailSender
log4perl.appender.MailerInfo.to      = em...@em...
log4perl.appender.MailerInfo.from    = em...@em...
log4perl.appender.MailerInfo.smtp    = host
log4perl.appender.MailerInfo.Server  = host
log4perl.appender.MailerInfo.buffer  = 0
log4perl.appender.MailerInfo.subject = subject
log4perl.appender.MailerInfo.min_level=info
log4perl.appender.MailerInfo.layout  =
Log::Log4perl::Layout::PatternLayout
log4perl.appender.MailerInfo.layout.ConversionPattern=%d{yyyy-MM-dd
HH:mm:ss} %5p> %m%n
2009-07-07 16:51:07 [valuations.pl:main] DEBUG> reading dbsource.mxres
file to get database information    

Obviously if I remove the Log::Dispatch::Email::MailSender I dont get
this error, but also no email notification. I have to use
Email::MailSender, because I need to overwrite the email-sender address.

Thanks,
Markus

Re: [log4perl-devel] Log4perl

[Mike S. <m...@pe...>]

On Mon, 6 Jul 2009, Oladipo, Segun wrote:

> Need to install Log4perl but stuck behind a firewall.  Obtained
> information that it is possible to download the zipped file to a local
> repository and install using ppm.

The PPM is for Activestate Perl only, and it wasn't updated with the
last release by accident. I've just run the script that pushed the
current (1.23) release to
http://log4perl.sourceforge.net/ppm/Log-Log4perl.ppd, please try again!

Regarding your Firewall, if you have http access to the outside world
(as you seem to have if you can download a zipped file) you should as
well be able to use the normal CPAN installer (which can be configured
to use http).

-- Mike

Mike Schilli
m...@pe...