[Pacemaker] why pacemaker stops cman?

[Andrew Beekhof]

When Pacemaker is used with cman, Pacemaker provides the fencing capabilities.
So at the point Pacemaker is stopped, fencing is impossible.
This makes it unsafe for cman (which initiates fencing for its own reasons) to continue running.

Also, CMAN's fenced is not very good at shutting down cleanly.
So we bring down all the services, leave the fencing domain, kill fenced, and then shut down pacemaker and the rest of cman.
This has proven to be the only way to reliably get fenced to stop.


On 12/07/2013, at 10:39 PM, Andrey Groshev <greenx at yandex.ru> wrote:

> # service pacemaker stop
> Waiting for shutdown of managed resources.....             [  OK  ]
> Signaling Pacemaker Cluster Manager to terminate:          [  OK  ]
> Waiting for cluster services to unload:..                  [  OK  ]
> Stopping cluster:
>   Leaving fence domain...                                 [  OK  ]
>   Stopping gfs_controld...                                [  OK  ]
>   Stopping dlm_controld...                                [  OK  ]
>   Stopping fenced...                                      [  OK  ]
>   Stopping cman...                                        [  OK  ]
>   Waiting for corosync to shutdown:                       [  OK  ]
>   Unloading kernel modules...                             [  OK  ]
>   Unmounting configfs...                                  [  OK  ]
> 
> # service cman status
> corosync dead but subsys locked
> 
> 
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> 
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org