Lejeczek,
Thanks for raising this. We'll improve the error message to make it
clear that the cluster needs to be stopped in order to proceed.
Tomas
Dne 24. 07. 23 v 14:22 Michal Pospíšil (he / him) napsal(a):
Hello all,
One more useful link that I forgot to include in my original reply -
Hello all,
One more useful link that I forgot to include in my original reply - list
of corosync options and when it is possible to update them:
https://github.com/corosync/corosync/wiki/Config-file-values
Cheers,
Michal
On Mon, 24 Jul 2023 at 13:04, Michal Pospíšil (he / him) <
Hi lejeczek,
Unfortunately, that command shouldn't work in this situation. The problem
is that the cluster (corosync) is running. From the man page:
update [auto_tie_breaker=[0|1]] [last_man_standing=[0|1]]
[last_man_standing_window=[]] [wait_for_all=[0|1]]
Add, remove or change
Hi guys.
That below should work, right?
-> $ pcs quorum update last_man_standing=1 --skip-offline
Checking corosync is not running on nodes...
Warning: Unable to connect to dzien (Failed to connect to
dzien port 2224: No route to host)
Warning: dzien: Unable to check if corosync is not
