Hello all,
Is there a way to specify in /etc/sysconfig/pacemaker (or some other place) a
separate logging location for pacemaker_remote? By default, it appears that
nodes running pacemaker_remote get logged to the location set in the
PCMK_logfile variable, which is /var/log/pacemaker/pacemaker
again,
Mike
From: Users on behalf of Ken Gaillot
Sent: Monday, March 18, 2019 11:56:47 AM
To: Cluster Labs - All topics related to open-source clustering welcomed
Subject: Re: [ClusterLabs] logging for pacemaker_remote?
On Mon, 2019-03-18 at 17:57 +, Gilbert
Hello all,
We are running Pacemaker 1.1.21-4 and are trying to figure out how we can do
the equivalent of “systemctl reload pacemaker_remote”. Does anyone know what
signal needs to get sent to the pacemaker_remoted service to reload its config?
Sending a SIGHUP appears to kill the process.
Tha
ce might be marked
as failed, but the cluster should be able to reconnect and reprobe the
state of all resources without fencing.
On Tue, 2020-06-09 at 03:28 +, Gilbert, Mike wrote:
> Hello all,
>
> We are running Pacemaker 1.1.21-4 and are trying to
