[ClusterLabs] Coming in Pacemaker 2.0.0: /var/log/pacemaker/pacemaker.log

Ken Gaillot kgaillot at redhat.com
Wed Jan 10 17:34:13 EST 2018


Starting with Pacemaker 2.0.0, the Pacemaker detail log will be kept by
default in /var/log/pacemaker/pacemaker.log (rather than
/var/log/pacemaker.log). This will keep /var/log cleaner.

Pacemaker will still prefer any log file specified in corosync.conf.

The initial proposal, after discussion at last year's summit, was to
use /var/log/cluster/pacemaker.log instead. That turned out to be slightly problematic: it broke some regression tests in a way that wasn't easily fixable, and more significantly, it raises the question of what package should own /var/log/cluster (which different distributions might want to answer differently).

So instead, the default log locations can be overridden when building
pacemaker. The ./configure script now has these two options:

--with-logdir
Where to keep pacemaker.log (default /var/log/pacemaker)

--with-bundledir
Where to keep bundle logs (default /var/log/pacemaker/bundles, which
hasn't changed)

Thus, if a packager wants to preserve the 1.1 locations, they can use:

./configure --with-logdir=/var/log

And if a packager wants to use /var/log/cluster as originally planned,
they can use:

./configure --with-logdir=/var/log/cluster --with-
bundledir=/var/log/cluster/bundles

and ensure that pacemaker depends on whatever package owns
/var/log/cluster.
-- 
Ken Gaillot <kgaillot at redhat.com>




More information about the Users mailing list