Synchronized Appender locking up system with semaphores about log4perl HOT 3 OPEN

ok, we found out what's the problem. If any log4perl module outputs something to stderr/stdout and you're using the recipe to catch all output from stderr & stdout and redirect to log4perl you run into a semaphore deadlock as you're entering the 'log' subroutine again in a recursion and it waits indefinitly.

For the moment I have monkey patched the 'log' method of the Appender to run a counter and only lock/umlock the semaphore if counter == 0, also error handling is not done properly here, if the log method dies you're also left with a locked semaphore and system is in deadlock mode.

from log4perl.

Hi,

I had the same issue. The semaphore errors were showing up in the Centos 7 syslogs and my software stopped processing all together. Had to fall back to the following configuration:

log4perl.appender.Logfile = Log::Log4perl::Appender::File
log4perl.appender.Logfile.autoflush = 1
log4perl.appender.Logfile.mode = append
log4perl.appender.Logfile.syswrite = 1

(i.e. not using Log::Log4perl::Appender::Synchronized)

from log4perl.

Thanks for the report. Could one of you please put here a code snippet that demonstrates the problem, or even better put it in a .t for easy adding?

from log4perl.