You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[root@rh72-01 ~]# pcs status
Cluster name: cluster1
WARNING: no stonith devices and stonith-enabled is not false
Last updated: Wed Feb 24 13:48:41 2016 Last change: Wed Feb 24 13:48:35 2016 by hacluster via crmd on rh72-02
Stack: corosync
Current DC: rh72-02 (version 1.1.14-70404b0) - partition with quorum
2 nodes and 0 resources configured
We executed pcs cluster kill command in rh72-02 node.
[root@rh72-02 ~]# pcs cluster kill
After having stopped, corosync and Pacemaker of the rh72-02 node reboot.
Feb 24 13:51:25 rh72-02 systemd: Started Corosync Cluster Engine.
Feb 24 13:51:25 rh72-02 systemd: Started Pacemaker High Availability Cluster Manager.
Feb 24 13:51:25 rh72-02 systemd: Starting Pacemaker High Availability Cluster Manager...
As a result, the rh72-02 node does not stop.
[root@rh72-01 ~]# pcs status
Cluster name: cluster1
WARNING: no stonith devices and stonith-enabled is not false
Last updated: Wed Feb 24 13:53:11 2016 Last change: Wed Feb 24 13:48:35 2016 by hacluster via crmd on rh72-02
Stack: corosync
Current DC: rh72-01 (version 1.1.14-70404b0) - partition with quorum
2 nodes and 0 resources configured
Running pcs cluster kill kills all cluster daemons. However systemd detects pacemaker is not running and starts it again. If you want to stop cluster on a node, run pcs cluster stop on that node.
Hi All,
We installed pcsd0.9.148 on RHEL7.2.
[root@rh72-01 ~]# pcs status
Cluster name: cluster1
WARNING: no stonith devices and stonith-enabled is not false
Last updated: Wed Feb 24 13:48:41 2016 Last change: Wed Feb 24 13:48:35 2016 by hacluster via crmd on rh72-02
Stack: corosync
Current DC: rh72-02 (version 1.1.14-70404b0) - partition with quorum
2 nodes and 0 resources configured
Online: [ rh72-01 rh72-02 ]
Full list of resources:
PCSD Status:
rh72-01: Online
rh72-02: Online
Daemon Status:
corosync: active/disabled
pacemaker: active/disabled
pcsd: active/disabled
We executed pcs cluster kill command in rh72-02 node.
[root@rh72-02 ~]# pcs cluster kill
After having stopped, corosync and Pacemaker of the rh72-02 node reboot.
Feb 24 13:51:25 rh72-02 systemd: Started Corosync Cluster Engine.
Feb 24 13:51:25 rh72-02 systemd: Started Pacemaker High Availability Cluster Manager.
Feb 24 13:51:25 rh72-02 systemd: Starting Pacemaker High Availability Cluster Manager...
As a result, the rh72-02 node does not stop.
[root@rh72-01 ~]# pcs status
Cluster name: cluster1
WARNING: no stonith devices and stonith-enabled is not false
Last updated: Wed Feb 24 13:53:11 2016 Last change: Wed Feb 24 13:48:35 2016 by hacluster via crmd on rh72-02
Stack: corosync
Current DC: rh72-01 (version 1.1.14-70404b0) - partition with quorum
2 nodes and 0 resources configured
Online: [ rh72-01 rh72-02 ]
Full list of resources:
PCSD Status:
rh72-01: Online
rh72-02: Online
Daemon Status:
corosync: active/disabled
pacemaker: active/disabled
pcsd: active/disabled
Is it right movement to reboot after kill command?
Or can you restrain reboot by setting?
Best Regards,
Hideo Yamauchi.
The text was updated successfully, but these errors were encountered: