Ken,
Thank you very much for the response. That method does allow us to reload the
configs, but it's a bit heavy-handed for our use case. All we're wanting to do
is rotate the log files. Is there any other mechanism we could use to achieve
that goal?
Thanks!
Mike
On 6/9/20, 7:10 AM, "Users o
On Tue, 2020-06-09 at 19:38 +, Gilbert, Mike wrote:
> Ken,
>
> Thank you very much for the response. That method does allow us to
> reload the configs, but it's a bit heavy-handed for our use case. All
> we're wanting to do is rotate the log files. Is there any other
> mechanism we could use t
Currently it's not possible. However you should be able to put the
cluster into maintenance mode, restart pacemaker_remote, then take the
cluster out of maintenance mode.
Test it to be sure. I believe the connection resource might be marked
as failed, but the cluster should be able to reconnect an
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
