Uploaded image for project: 'logback'
  1. logback
  2. LOGBACK-1217

SizeAndTimeBasedRollingPolicy not deleting files with 4 digit "%i"

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Duplicate
    • Affects Version/s: 1.1.3, 1.1.7
    • Fix Version/s: None
    • Component/s: logback-core
    • Environment:

      RHEL 6.4, JDK 1.8

      Description

      We are using SizeAndTimeBasedRollingPolicy/SizeAndTimeBasedFNATP in our product (logback 1.1.3). Please refer to the attached appender description. Here is the fileNameAppender :

      <fileNamePattern>${MY_LOGS}/myabc-%d{yyyy-MM-dd}.%i.gz</fileNamePattern>

      The log files generated have the following names : myabc-2016-11-21.0.gz, myabc-2016-11-21.1.gz, myabc-2016-11-21.2.gz etc.

      The problem is if a log file has extension (%i) more than 3 digits, it is not being deleted after 30 days (maxHistory). For example, myabc-2016-11-21.0.gz gets deleted after 30 days, but myabc-2016-11-21.1000.gz is NOT getting deleted.

      Is it a bug in logback? Is there any other appender/configuration which I need to add to the logback configuration file to make sure files with more than 3 digit extension also gets deleted?

      I have upgraded from 1.1.3 to 1.1.7. But that didn't help.

      [I posted this to user mailing list, but didn't get any reply. Because of this, issue large amount log files are not getting cleaned up at our customer's production causing disk scaling issue. Considering the urgency, I am posting it as a bug.]

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                ceki Ceki Gülcü
                Reporter:
                arnabbiswas1 Arnab Biswas
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: