Details
-
Bug
-
Resolution: Fixed
-
Major
-
1.1.7
-
None
Description
I am using version 1.1.7 with configuration like this:
<appender name="DAILY" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>${LOG_FILE_PATH}/${LOG_FILE_NAME}</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>${LOG_FILE_PATH}/history/${LOG_FILE_NAME}.%d{${LOG_ROLLER_PATTERN}}.gz</fileNamePattern> <maxHistory>10</maxHistory> </rollingPolicy> <encoder> <charset>UTF-8</charset> <pattern>%d{yyyy-MM-dd HH:mm:ss.SSS}%-5level [%thread] [us.%X{user}.%X{method}] %logger{36} :%line - %msg%n</pattern> </encoder> </appender>
I get a lot of tmp files, also one of the dates did not roll, I'm guessing because of this. Here is the history folder (which is missing core.log.2016-11-15.gz):
rw-rr- 1 was2 was2 614 Nov 9 00:00 core.log.2016-11-08.gz
rw-rr- 1 was2 was2 496642 Nov 10 00:00 core.log.2016-11-09.gz
rw-rr- 1 was2 was2 610396 Nov 11 00:00 core.log.2016-11-10.gz
rw-rr- 1 was2 was2 545713 Nov 12 00:00 core.log.2016-11-11.gz
rw-rr- 1 was2 was2 619 Nov 13 00:00 core.log.2016-11-12.gz
rw-rr- 1 was2 was2 1945 Nov 14 00:00 core.log.2016-11-13.gz
rw-rr- 1 was2 was2 253380 Nov 15 00:00 core.log.2016-11-14.gz
rw-rr- 1 was2 was2 125 Nov 17 00:00 core.log.2016-11-16.gz
And here is the main folder full of .tmp files, which also contains one log from Nov 15-th im guessing this did not roll:
rw-rr- 1 was2 was2 1843 Nov 17 03:35 core.log
rw-rr- 1 was2 was2 10694966 Nov 7 16:34 core.log1251035985773639.tmp
rw-rr- 1 was2 was2 4558149 Nov 8 16:34 core.log1251037974705639.tmp
rw-rr- 1 was2 was2 9143206 Nov 9 12:06 core.log1337493058412639.tmp
rw-rr- 1 was2 was2 1310469 Nov 10 09:14 core.log1423836762896639.tmp
rw-rr- 1 was2 was2 223 Nov 10 00:00 core.log1423864481062639.tmp
rw-rr- 1 was2 was2 2065 Nov 10 03:35 core.log1423907071247639.tmp
rw-rr- 1 was2 was2 59466 Nov 11 08:36 core.log1510234689348639.tmp
rw-rr- 1 was2 was2 223 Nov 11 00:00 core.log1510236118472639.tmp
rw-rr- 1 was2 was2 223 Nov 11 00:00 core.log1510241853601639.tmp
rw-rr- 1 was2 was2 1857 Nov 11 03:35 core.log1510243065701639.tmp
rw-rr- 1 was2 was2 1857 Nov 11 03:35 core.log1510312478035639.tmp
rw-rr- 1 was2 was2 13060757 Nov 15 16:16 core.log1855834771052639.tmp
rw-rr- 1 was2 was2 10990200 Nov 16 14:51 core.log2028636767874639.tmp
rw-rr- 1 was2 was2 224575 Nov 17 09:31 core.log2028637267722639.tmp
rw-rr- 1 was2 was2 110 Nov 17 00:00 core.log2028637697572639.tmp
rw-rr- 1 was2 was2 12414327 Oct 28 17:54 core.log297050049899639.tmp
rw-rr- 1 was2 was2 2065 Oct 29 03:35 core.log383464039845639.tmp
rw-rr- 1 was2 was2 2288 Oct 30 23:00 core.log469878051788639.tmp
rw-rr- 1 was2 was2 959128 Oct 31 23:01 core.log572782684433639.tmp
rw-rr- 1 was2 was2 2065 Nov 1 23:01 core.log659187192708639.tmp
rw-rr- 1 was2 was2 4583881 Nov 2 11:48 core.log745587413713639.tmp
rw-rr- 1 was2 was2 3264836 Nov 3 10:44 core.log819037667277639.tmp
rw-rr- 1 was2 was2 646577 Nov 4 11:13 core.log905438294240639.tmp
This is out test server. Our production is even worse. There is hourly rolling.
Attachments
Issue Links
- relates to (in)
-
LOGBACK-1064 wrong log filename
- Open
-
LOGBACK-173 Log Rotation/Gzip process leaving .tmp files behind
- Resolved