Shawn this is really weird -- we run log4j in lots of installations and
have never seen an issue like this.
I wonder if you might be running some other log rotation software (like
logrotate) that is somehow getting in the way or conflicting?
-Mike
On 11/01/2014 01:45 PM, Shawn Heisey wrote:
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;
Queries happen at a fairly constant low level and updates happen once a
minute, so I know for sure that there is activity during the missing
blocks of time. I need to investigate a problem that occurred during
the time that is not logged, which means I have nothing to investigate.
This is the log4j configuration that I'm using:
http://apaste.info/9vC
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
Is this a bug, or have I done something wrong in my config? Should I be
putting this on the log4j mailing list instead of here? My best guess
about how this is happening is that an entire logfile is getting deleted
during rotation.
Thanks,
Shawn
