[ClusterLabs] Antw: [EXT] Re: Corosync node gets unique Ring ID

[Ulrich Windl]

Hi!

Most stupid question: All your nodes had the same corosync configuration file
when they started?

Ulrich

>>> Igor Tverdovskiy <igor.tverdovskiy.pe at gmail.com> schrieb am 26.01.2021 um
04:01
in Nachricht
<CAARZOogxQ6Hpd960HYoe0mOep7uHG4YnsRpwTaq6LA+ZUurb4g at mail.gmail.com>:
> BTW checked log, corosync reload failed:
> ‑‑ Logs begin at Thu 2021‑01‑14 15:41:10 UTC, end at Tue 2021‑01‑26
> 01:42:48 UTC. ‑‑
> Jan 22 14:33:09 destination‑standby corosync[13180]: Starting Corosync
> Cluster Engine (corosync): [ OK ]
> Jan 22 14:33:09 destination‑standby systemd[1]: Started Corosync Cluster 
> Engine.
> Jan 26 01:41:18 destination‑standby systemd[1]: Reloading Corosync
> Cluster Engine.
> Jan 26 01:42:48 destination‑standby systemd[1]: corosync.service
> reload operation timed out. Stopping.
> Jan 26 01:42:48 destination‑standby systemd[1]: Reload failed for
> Corosync Cluster Engine.
> 
> However the issue started exactly after reload (see in previous email
> corosync.log)
> _______________________________________________
> Manage your subscription:
> https://lists.clusterlabs.org/mailman/listinfo/users 
> 
> ClusterLabs home: https://www.clusterlabs.org/