pacemaker v2 appears to be missing log directory

[Dimitri John Ledkov]

# journalctl -u pacemaker | grep 'logging to'
May 08 12:30:49 nice-mako pacemakerd[325]: error: Directory '/var/log/pacemaker' does not exist: logging to '/var/log/pacemaker/pacemaker.log' is disabled
May 08 12:30:49 nice-mako pacemaker-fenced[329]: error: Directory '/var/log/pacemaker' does not exist: logging to '/var/log/pacemaker/pacemaker.log' is disabled
May 08 12:30:49 nice-mako pacemaker-based[328]: error: Directory '/var/log/pacemaker' does not exist: logging to '/var/log/pacemaker/pacemaker.log' is disabled
May 08 12:30:49 nice-mako pacemaker-schedulerd[332]: error: Directory '/var/log/pacemaker' does not exist: logging to '/var/log/pacemaker/pacemaker.log' is disabled
May 08 12:30:49 nice-mako pacemaker-attrd[331]: error: Directory '/var/log/pacemaker' does not exist: logging to '/var/log/pacemaker/pacemaker.log' is disabled
May 08 12:30:49 nice-mako pacemaker-execd[330]: error: Directory '/var/log/pacemaker' does not exist: logging to '/var/log/pacemaker/pacemaker.log' is disabled
May 08 12:30:49 nice-mako pacemaker-controld[333]: error: Directory '/var/log/pacemaker' does not exist: logging to '/var/log/pacemaker/pacemaker.log' is disabled

I guess pacemaker v2 should either be configured to log to journal by default, or that directory needs to be created? or configuration changed to log to /var/log/pacemaker.log?

[Paride Legovini (paride)]

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
    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.

[Rafael David Tinoco (rafaeldtinoco)]

As Paride mentioned, this is already fixed in Eoan and Focal and was an issue for Disco.

[Rafael David Tinoco (rafaeldtinoco)]

Thank you for taking the time to report this bug. In an effort to keep an
up-to-date and valid list of bugs to work on, I have reviewed this report
to verify it still requires effort and occurs on an Ubuntu release in
standard support, and it does not.

It is unfortunate that we were unable to resolve this defect, however
there appears to be no further action possible at this time. I am
therefore moving the bug to 'Incomplete'. If you disagree or have
new information, we would be grateful if you could please add a comment
stating why and then change the status of the bug to 'New'.