Hi,
we are using unicast ("knet")
Greetings
Michael
Sitz der Gesellschaft / Corporate Headquarters: Deutsche Lufthansa
Aktiengesellschaft, Koeln, Registereintragung / Registration: Amtsgericht Koeln
HR B 2168
Vorsitzender des Aufsichtsrats / Chairman of the Supervisory Board: Dr.
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
It will be hard to guess if you are using sctp or udp/udpu.
If possible share the corosync.conf (you can remove sensitive data, but
make it meaningful).
Are you using a firewall ? If yes check :
1. Node firewall is not blocking the communication on the specific interfaces
2. Verify
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
Are you using multicast ?
Best Regards,
Strahil Nikolov
На 9 юни 2020 г. 10:28:25 GMT+03:00, "ROHWEDER-NEUBECK, MICHAEL (EXTERN)"
написа:
>Hello,
>We have massive problems with the redundant ring operation of our
>Corosync / pacemaker 3 Node NFS clusters.
>
>Most of the nodes either have an
Hello,
We have massive problems with the redundant ring operation of our Corosync /
pacemaker 3 Node NFS clusters.
Most of the nodes either have an entire ring offline or only 1 node in a ring.
Example: (Node1 Ring0 333 Ring1 n33 | Node2 Ring0 033 Ring1 3n3 | Node3 Ring0
333 Ring 1 33n)
On Wed, 2020-06-03 at 12:33 +0100, lejeczek wrote:
> hi guys
>
> I wonder about an idea of 'ethmonitor' watching a net iface
> which is of USB type. Such an iface which would physically
> roam between nodes.
> Would 'ethmonitor' work in such a case?
> I've tried and the resource actually got
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
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.
