Ulrich,
Jan Friesse schrieb am 20.10.2020 um 18:05 in Nachricht
<9e9edd13-847c-a81f-9b28-0ecf8f17f...@redhat.com>:
I've forgot to mention one very important change (in text, release notes
at github release is already fixed):
...
- Default token timeout was changed from 1 seconds to 3 seco
Hi,
Have you reloaded corosync configuration after modifying corosync.conf?
I don't see it in your procedure. Modifying the config file has no
effect until you reload it with 'corosync-cfgtool -R'.
It should not be needed to modify CIB and add the new node manually. If
everything is done cor
Hello,
We are trying to upgrade our product from Corosync 2.X to Corosync 3.X. Our
procedure includes upgrade where we stopthe cluster, replace rpms and restart
the cluster. Upgrade works fine, but we also need to implement rollback in case
something goes wrong.
When we rollback and reload old
Thanks for the reply.
I do see backup config command in pcs, but not in crmsh.
What would that be in crmsh? Would something like this work after Corosync
started in the state with all resources inactive? I'll try this:
crm configure save
crm configure load
Thank you!
_Vitaly Zolotusky
> On
Hi guys,
ocassionally stopping a VirtualDomain resource via "crm resource stop" does not
work, and in the end the node is fenced, which is ugly.
I had a look at the RA to see what it does. After trying to stop the domain via
"virsh shutdown ..." in a configurable time it switches to "virsh destr
Have you tried to backup the config via crmsh/pcs and when you downgrade to
restore from it ?
Best Regards,
Strahil Nikolov
В четвъртък, 22 октомври 2020 г., 15:40:43 Гринуич+3, Vitaly Zolotusky
написа:
Hello,
We are trying to upgrade our product from Corosync 2.X to Corosync 3.X. O
22.10.2020 23:29, Lentes, Bernd пишет:
> Hi guys,
>
> ocassionally stopping a VirtualDomain resource via "crm resource stop" does
> not work, and in the end the node is fenced, which is ugly.
> I had a look at the RA to see what it does. After trying to stop the domain
> via "virsh shutdown ..."
>>> "Lentes, Bernd" schrieb am 22.10.2020
um
22:29 in Nachricht
<684655755.160569.1603398597074.javamail.zim...@helmholtz-muenchen.de>:
> Hi guys,
>
> ocassionally stopping a VirtualDomain resource via "crm resource stop" does
> not work, and in the end the node is fenced, which is ugly.
> I had