Project

General

Profile

Actions
Copy link

Bug #3603

closed

The files written by syslog in /var/log/rudder/reports/*.log and slapd in /var/log/rudder/ldap/slapd.log are still empty after a logrotate

Added by Nicolas PERRON over 11 years ago. Updated over 9 years ago.

Status:
Released
Priority:
1 (highest)
Assignee:
Jonathan CLARKE
Category:
Techniques
Target version:
2.4.8
Pull Request:
https://github.com/Normation/rudder-t...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

It seems that a bug occurs about logrotate on the syslog files /var/log/rudder/reports/*.log.
After a logrotate, these files are stil empty, until a restart of rsyslog.

It seems to happend on SLES and Debian.

Related issues 4 (0 open — 4 closed)

Related to Rudder - Bug #3868: The files written by java in /var/log/rudder/core/*.log are still empty after a logrotateRejected2013-08-22Actions
Related to Rudder - Architecture #3873: Change the source of the logrotate file of rudder-agent on RHEL/CentOSRejected2013-08-26Actions
Related to Rudder - Bug #4012: The system Techniques use the wrong logrotate configuration on RHELReleasedJonathan CLARKE2013-10-07Actions
Has duplicate Rudder - Bug #3566: Log permissionsRejectedNicolas PERRON2013-05-01Actions
Actions
Copy link
 #1

Updated by Dennis Cabooter over 11 years ago

This also occurs on Ubuntu. Even a restart of rsyslog does not help.

# ls -al /var/log/rudder/reports/ | grep -v \.gz$
total 13988
drwxr-xr-x 2 root   root    4096 May 24 06:25 .
drwxr-xr-x 8 root   root    4096 Apr 25 10:34 ..
-rw-r----- 1 root   adm        0 May 24 06:25 all.log
-rw-r----- 1 root   adm        0 Apr 18 06:25 extLinuxReport.log
-rw-r----- 1 root   adm        0 Apr 18 06:25 linuxlog.log
-rw-r----- 1 syslog adm        0 Apr 16 17:03 winlog.log
Actions
Copy link
 #2

Updated by Nicolas PERRON over 11 years ago

  • Status changed from New to In progress
  • Assignee set to Nicolas PERRON
  • Priority changed from N/A to 1 (highest)
  • Target version set to 2.4.8

I understand the problem: this is caused by a logrotate which does not reload syslog.

Actions
Copy link
 #3

Updated by Nicolas PERRON over 11 years ago

  • Subject changed from The files written by syslog in /var/log/rudder/reports/*.log are still empty after a logrotate to The files written by syslog in /var/log/rudder/reports/*.log and /var/log/rudder/ldap/slapd.log are still empty after a logrotate

The same problem occurs with slapd and java...

For java I will open a new ticket

Actions
Copy link
 #4

Updated by Nicolas PERRON over 11 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Nicolas PERRON to Matthieu CERDA
  • % Done changed from 0 to 100
  • Pull Request set to https://github.com/Normation/rudder-techniques/pull/175

Pull Request URL added: https://github.com/Normation/rudder-techniques/pull/175

Matthieu, could you review it please ?

Actions
Copy link
 #5

Updated by Nicolas PERRON over 11 years ago

  • Subject changed from The files written by syslog in /var/log/rudder/reports/*.log and /var/log/rudder/ldap/slapd.log are still empty after a logrotate to The files written by syslog in /var/log/rudder/reports/*.log and slapd in /var/log/rudder/ldap/slapd.log are still empty after a logrotate

Nicolas PERRON wrote:

The same problem occurs with slapd and java...

For java I will open a new ticket

The problem with Java is into #3868

Actions
Copy link
 #6

Updated by Jonathan CLARKE about 11 years ago

  • Status changed from Pending technical review to Discussion
  • Assignee changed from Matthieu CERDA to Nicolas PERRON

Nico, comments added in the PR, please address.

Actions
Copy link
 #7

Updated by Nicolas PERRON about 11 years ago

  • Status changed from Discussion to Pending technical review
  • Assignee changed from Nicolas PERRON to Jonathan CLARKE

I've added another logrotate file which is specific to RHEL/CentOS. This will need an adaptation into the packaging. I've opened an issue for that: #3873

Jonathan CLARKE wrote:

Nico, comments added in the PR, please address.

Done. Could you review it again please ?

Actions
Copy link
 #8

Updated by Nicolas PERRON about 11 years ago

Hmm.... the commit does not appear. This is because the modification was into the repository rudder-techniques even if it concerns the system.

Actions
Copy link
 #9

Updated by Nicolas PERRON about 11 years ago

  • Project changed from 34 to 24
  • Status changed from Pending technical review to Pending release
Actions
Copy link
 #10

Updated by Nicolas PERRON about 11 years ago

The commit that fixed this issue is: commit:7c99643900c55dc5e2592b15e23933d2894cdcf5

Actions
Copy link
 #11

Updated by Jonathan CLARKE about 11 years ago

Nicolas PERRON wrote:

The commit that fixed this issue is: commit:7c99643900c55dc5e2592b15e23933d2894cdcf5

Nicolas, please link that commit to this ticket.

Actions
Copy link
 #12

Updated by Nicolas PERRON about 11 years ago

Jonathan CLARKE wrote:

Nicolas PERRON wrote:

The commit that fixed this issue is: commit:7c99643900c55dc5e2592b15e23933d2894cdcf5

Nicolas, please link that commit to this ticket.

Done

Actions
Copy link
 #13

Updated by Nicolas PERRON about 11 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.4.8, which was released today.
Check out:

Actions
Copy link
 #14

Updated by Benoît PECCATTE over 9 years ago

  • Project changed from 24 to Rudder
  • Category set to Techniques
Actions
Copy link

Also available in: Atom PDF