On Fri, Apr 22, 2022 at 12:05 PM Tomas Jelinek <tojel...@redhat.com> wrote: > > As discussed in other branches of this thread, you need to figure out > why pacemaker is not starting. Even if one node is not running, corosync > and pacemaker are expected to be able to start on the other node.
Well, when trying to reproduce this behavior I configured SBD with a non-existent device and enabled it. If enabled, pacemaker.service Requires sbd.service. sbd.service failed to start and so pacemaker.service was not started either. Just one example. But as long as the only information we have is "nothing suspicious in logs", we can guess until the doomsday. Output of "journalctl -b" immediately after boot would give at least some starting points. _______________________________________________ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/