Project

General

Profile

Actions

User story #3195

closed

When upgrading Rudder from 2.4 to 2.5~beta1, the logback.xml files is not updated

Added by Nicolas CHARLES almost 12 years ago. Updated over 9 years ago.

Status:
Released
Priority:
1 (highest)
Assignee:
Matthieu CERDA
Category:
Packaging
Target version:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

On a system that was updated from Rudder 2.4 to 2.5~beta1, the logback.xml were not upgraded
(on orch-1 I have /opt/rudder/etc/logback.xml /opt/rudder/etc/logback.xml.dpkg-old, on orch-3 I have logback.xml and logback.xml.rpmnew )

So all my expected logs are not there

Is it the expected behaviour ?

(the guy who did the upgrade doesn't remember being asked a question)


Related issues 1 (0 open1 closed)

Related to Rudder - User story #2988: Log agent's report about failure in a dedicated logfileReleasedVincent MEMBRÉ2012-12-12Actions
Actions #1

Updated by Nicolas CHARLES almost 12 years ago

The following entries are missing in te upgraded Rudder, hence need a migration script

  <property name="REPORT_DIR" value="/var/log/rudder/compliance" />

  <!--
    A file log appender for exploitation logs about failure reports.
  -->
    <appender name="REPORTLOG" class="ch.qos.logback.core.FileAppender">
    <file>${REPORT_DIR}/non-compliant-reports.log</file>
    <append>true</append>
        <encoder>
      <pattern>%msg%n</pattern>
    </encoder>
  </appender>
   <!-- Here come non compliant reports logger -->

   <logger name="non-compliant-reports" level="info" additivity="false">
     <appender-ref ref="REPORTLOG" />
   <!--  <appender-ref ref="REPORTSYSLOG" /> -->
     <!-- comment the following appender if you don't want to have logs about non compliant reports in both stdout and reportlog -->
     <appender-ref ref="STDOUT" />
   </logger>

Actions #2

Updated by Nicolas CHARLES almost 12 years ago

  • Tracker changed from Question to 6
Actions #3

Updated by Nicolas CHARLES almost 12 years ago

As stated in https://github.com/Normation/rudder-packages/pull/7 , the following path needs to be created

/var/log/rudder/compliance

Actions #4

Updated by Vincent MEMBRÉ almost 12 years ago

Logback will create the directory if the appender is properly set ( so if the upgrade is done, then logback will be able to create the directory).

The only condition for logback is to have the right to create directory in /var/log/rudder

Actions #5

Updated by Vincent MEMBRÉ almost 12 years ago

  • Status changed from New to Pending technical review
Actions #6

Updated by Matthieu CERDA almost 12 years ago

  • Assignee changed from Jonathan CLARKE to Matthieu CERDA
  • % Done changed from 0 to 100

Grabbin' this.

The pull request looks okay, I approve.

Actions #7

Updated by Vincent MEMBRÉ almost 12 years ago

  • Status changed from Pending technical review to Pending release

Applied in changeset commit:31a881b9a5a99920d2784fc986961ee32f0367aa.

Actions #8

Updated by Matthieu CERDA almost 12 years ago

Applied in changeset commit:cf38b2f83f116623491d9527a2598ae4dae02c80.

Actions #9

Updated by Nicolas PERRON almost 12 years ago

  • Project changed from Rudder to 34
  • Category deleted (11)
Actions #10

Updated by François ARMAND over 11 years ago

  • Status changed from Pending release to Released
Actions #11

Updated by Benoît PECCATTE over 9 years ago

  • Project changed from 34 to Rudder
  • Category set to Packaging
Actions #12

Updated by Benoît PECCATTE over 9 years ago

  • Tracker changed from 6 to User story
Actions

Also available in: Atom PDF