logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shawn Heisey <apa...@elyograg.org>
Subject RollingFileAppender appears to be losing log entries
Date Sun, 02 Nov 2014 17:13:39 GMT
I asked this question on the solr-user mailing list first, but got no response.  It's a major
party weekend, so I'm not really surprised, and I think this is probably a problem with log4j,
not Solr.

There appear to be large blocks of time missing in my solr logfiles created with slf4j->log4j
and rotated using the log4j config:

End of solr.log.1: INFO  - 2014-10-31 12:52:25.073;
Start of solr.log: INFO  - 2014-11-01 02:27:27.404;

End of solr.log.2: INFO  - 2014-10-29 06:30:32.661;
Start of solr.log.1: INFO  - 2014-10-30 07:01:34.241;

There is about 2.5 hours missing for the first pair, and over 24 hours missing for the second.
 I have not checked all the logfiles to see if they are missing time.

Queries happen at a fairly constant low level at almost all hours, and updates happen once
a minute, so I know for sure that there is activity during the missing blocks of time.  I
had a weird problem during the time that is missing, so I have no way to determine what happened.

This is the log4j configuration that I'm using:


These are the logging jars that I have in jetty's lib/ext:

-rw-r--r-- 1 ncindex ncindex  16515 Apr 11  2014 jcl-over-slf4j-1.7.6.jar
-rw-r--r-- 1 ncindex ncindex   4959 Apr 11  2014 jul-to-slf4j-1.7.6.jar
-rw-r--r-- 1 ncindex ncindex 489883 Apr 11  2014 log4j-1.2.17.jar
-rw-r--r-- 1 ncindex ncindex  28688 Apr 11  2014 slf4j-api-1.7.6.jar
-rw-r--r-- 1 ncindex ncindex   8869 Apr 11  2014 slf4j-log4j12-1.7.6.jar

I did find this blog post describing a similar problem with a different Appender:


I'm not running on Windows, I'm on CentOS 6.  Linux normally does not have problems with renaming
files even when they are open, and I am not running anything else on the system that could
open logfiles with an exclusive lock.

My logfiles where I redirect stdout and stderr from Jetty don't show anything related, and
I don't see anything like the error mentioned on that blog post in any of the surviving logfiles
from log4j.

Is this a bug, or have I done something wrong in my config?  My best guess about how this
is happening is that an entire logfile is getting deleted during rotation.  Is there anything
I can do to shed some light on what's happening, at least to pinpoint which software package
is behaving badly?


To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org

View raw message