Rudder

Good catch, thanks.

Matthieu, could you look for the first version of that bug, and correct it ? Denis analysis seems OK, so it should be a matter of minutes.

I don't see any problem here. slapd runs as root, so it is correct that the file shuold belong to root.

However, slapd rarely writes to it's log file. Maybe this is why you see this?

Could you try resetting the logrotate config to it's initial value, and then after there has been a logroate and you see a 0 byte sized file, run "/etc/init.d/slapd status"? This should output some lines in the file.

If not, I can't reproduce this, it works OK for me (on Debian 6).

I do confirm the issue

On debian, the user running syslog is root

ps  -aux | grep syslog
Warning: bad ps syntax, perhaps a bogus '-'? See http://procps.sf.net/faq.html
root      1795  0.0  0.0   9616   884 pts/1    S+   18:42   0:00 grep syslog
root     25632  0.0  0.2 200596  5004 ?        Sl   Jan23  17:50 /usr/sbin/rsyslogd -c4

while on ubuntu it is not

root@server:/var/log/rudder/reports#  ps  -aux | grep syslog
Warning: bad ps syntax, perhaps a bogus '-'? See http://procps.sf.net/faq.html
syslog   14309  0.0  0.3  55572  4708 ?        Sl   17:36   0:00 rsyslogd -c5
root     14850  0.0  0.0   3912   832 pts/0    S+   17:42   0:00 grep --color=auto syslog

We need a separate logrotate file for ubuntu

PR is there https://github.com/Normation/rudder-techniques/pull/306

Applied in changeset policy-templates:commit:f0b04c1e5d0b5bc2df26d59d1c14576c42dcfc4b.

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

• The release announcement: http://www.rudder-project.org/pipermail/rudder-announce/2014-March/000077.html
• The full ChangeLog: http://www.rudder-project.org/foswiki/bin/view/System/Documentation:ChangeLog26
• Download information: https://www.rudder-project.org/site/get-rudder/downloads/