Richard Burton richard-at-atomwide.com |log4perl_sourceforge| wrote:
> Hi all
>
> I am trying to capture unhandled exceptions that are sent to STDERR,
> e.g. for example the following could would give such an error
[snip]
>
> I can catch this using stealth as loggers outlined in
>
> http://searc
Mike Schilli m-at-perlmeister.com |log4perl_sourceforge| wrote:
> On Tue, 24 Feb 2009, Robert Jacobson wrote:
>
>> Those are mostly the expected values from the Layout I specified
>> (time, log level, script name, hostname, PID, ?, message).
>
> That's peculiar .
Robert Jacobson wrote:
> If I add equivalent code to my existing conditional for the definition
> of errorappender, i.e.:
>
> if ($self->{errorappender}) {
> # Pass back the appender to be synchronized as a dependency
> # to the configuration file parse
error messages to this appender. errorappender must be
defined in the Log4perl configuration, or DBI_Buffer will fail to init.
=item flushsignal
Normally, DBI_Buffer will only write messages to the database upon
receiving a log() request. However, if the database goes down, and
messages are buffe
Ah, apparently I *had* left some appenders using DBI_Buffer (DBI
appender subclass) in my config. I retested a bunch of things today
and I could not reproduce the error unless I had my DBI_Buffer appender
in the config.
Further investigation showed that the mysql server was reaching its
maximum
Mike Schilli m-at-perlmeister.com |log4perl_sourceforge| wrote:
> On Fri, 20 Feb 2009, Robert Jacobson wrote:
>>> I wonder what kind of config change would cause
>>> this. Are you removing an appender by any chance?
>>
>> Nope, usually I'm only changing the lo
Mike Schilli m-at-perlmeister.com |log4perl_sourceforge| wrote:
> Hmm, that's peculiar. I wonder what kind of config change would cause
> this. Are you removing an appender by any chance?
Nope, usually I'm only changing the log level.
But I can reproduce the error without changing anything in the
I have been using Log4perl for quite some time in a large project of mine.
There are about 20 perl programs, all of which should always be running. I'm
using init_and_watch to allow users to update the configuration file; i.e:
# Init Log4perl
Log::Log4perl->init_and_watch("../ANSlog.
