Red Hat Bugzilla – Bug 600479
corosync won't shutdown with firewall enabled
Last modified: 2016-04-26 10:00:07 EDT
+++ This bug was initially created as a clone of Bug #576000 +++
Description of problem:
When setting up and you forget your firewall on (like I did).
totem gets stuck in the gather state:
Mar 23 09:39:16 corosync [TOTEM ] entering GATHER state from 3.
Mar 23 09:39:18 corosync [TOTEM ] The consensus timeout expired.
Our current shutdown relies on the ability to send a token.
It hooks into sched_work() which gets fired on token_send.
In the above state we are not in a state to send a token
so we can't shutdown.
We probably need to check that the totem state is operational
before calling schedwrk_create(), if not call
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.enable firewall (default one)
2.service corosync restart
it will never shutdown
*** This bug has been marked as a duplicate of bug 599327 ***