According to its d/changelog this is fixed in the Debian revision 2.0.1-3:
* [3c7b0b4] Ship /var/log/pacemaker, the new default directory of the detail
logs.
Without this directory the default configuration emits errors and the
detail log is simply not written.
The /var/log/pacemaker.log* detail log files from Pacemaker 1 are not
moved automatically on upgrade, but this new /var/log/pacemaker
directory and its contents are removed when purging pacemaker-common.
The owner and mode of the log directory is set to let clients like
crm_resource --force-start running as any user in the haclient group
write their messages into the detail log. The logrotate config relies
on these settings as well.
Hi Dimitri,
According to its d/changelog this is fixed in the Debian revision 2.0.1-3:
* [3c7b0b4] Ship /var/log/pacemaker, the new default directory of the detail pacemaker. log* detail log files from Pacemaker 1 are not
logs.
Without this directory the default configuration emits errors and the
detail log is simply not written.
The /var/log/
moved automatically on upgrade, but this new /var/log/pacemaker
directory and its contents are removed when purging pacemaker-common.
The owner and mode of the log directory is set to let clients like
crm_resource --force-start running as any user in the haclient group
write their messages into the detail log. The logrotate config relies
on these settings as well.