Rudder

This is heavely rooted to http://www.rudder-project.org/redmine/issues/6384. Each time we try to manage logs produced by a Java source with logrotate, it ends badly.

The solution for that one is simple:

- remove configuration for that log in logrotate => #6385
- use http://logback.qos.ch/manual/appenders.html#onRollingPolicies to manage the rotation and compression of the logs (this ticket)

So, today we have the following configuration for /var/log/rudder/compliance/non-compliant-reports.log logrotation:

/var/log/rudder/compliance/non-compliant-reports.log {
        daily
        missingok
        rotate 365
        compress
        notifempty
        create 640 root adm
        delaycompress
}

We can't get exactly the same configuration, because the windows (number of past report) is limited to 20 in logback (it can be change, be require code that we certainly don't want to do for futur-proofing, see: https://github.com/qos-ch/logback/blob/master/logback-core/src/main/java/ch/qos/logback/core/rolling/FixedWindowRollingPolicy.java#L43 ).

So the corresponding logback appender with fixe windows configuration would be:

<appender name="XXXX" class="ch.qos.logback.core.rolling.RollingFileAppender">
    <file>/var/log/rudder/compliance/non-compliant-reports.log</file>
    <append>true</append>

    <rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy">
      <fileNamePattern>non-compliant-reports.%i.gz</fileNamePattern>
      <minIndex>1</minIndex>
      <maxIndex>365</maxIndex>
    </rollingPolicy>

    <triggeringPolicy class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy">
      <maxFileSize>5MB</maxFileSize>
    </triggeringPolicy>

    <encoder>
      <pattern>%-4relative [%thread] %-5level %logger{35} - %msg%n</pattern>
    </encoder>
  </appender>

And based on time:

<appender name="XXXX" class="ch.qos.logback.core.rolling.RollingFileAppender">
    <file>/var/log/rudder/compliance/non-compliant-reports.log</file>
    <append>true</append>

    <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
      <!-- daily rollover -->
      <fileNamePattern>non-compliant-reports.%d{yyyy-MM-dd}.log.gz</fileNamePattern>
      <maxHistory>365</maxHistory>
    </rollingPolicy>

    <encoder>
      <pattern>%-4relative [%thread] %-5level %logger{35} - %msg%n</pattern>
    </encoder>
  </appender>

The chosen solution is to use the default time rolling pattern, so that we are switching from a non working solution to a working one - even if we change the naming scheme.

New pull request: https://github.com/Normation/rudder/pull/837

Applied in changeset rudder|commit:11a7bb1d9b7bf13a55d0e5c3d56ec9c598a630f5.

This bug has been fixed in Rudder 2.10.12, 2.11.9 and 3.0.3 which were released today.

• Announcement 2.10 2.11 3.0
• Changelog 2.10 2.11 3.0
• Download information: https://www.rudder-project.org/site/get-rudder/downloads/