On 28/09/16 16:30 -0400, Scott Greenlese wrote: > Also, I have tried simulating a failed cluster node (to trigger a > STONITH action) by killing the corosync daemon on one node, but all > that does is respawn the daemon ... causing a temporary / transient > failure condition, and no fence takes place. Is there a way to > kill corosync in such a way that it stays down? Is there a best > practice for STONITH testing?
This makes me seriously wonder what could cause this involuntary daemon-scoped high availability... Are you sure you are using upstream provided initscript/unit file? (Just hope there's no fence_corosync_restart.) -- Jan (Poki)
pgpbBS3jdAmnn.pgp
Description: PGP signature
_______________________________________________ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org