The new cluster: [#!variable!cluster_name!#] has been found. The cluster: [#!variable!old_cluster_name!#] has been renamed to: [#!variable!new_cluster_name!#]. The new node: [#!variable!node_name!#] has been found in the cluster: [#!variable!cluster_name!#]; Host Name/UUID: .......... [#!variable!host_name!#] / [#!variable!host_uuid!#] Pacemaker ID: ............ [#!variable!pacemaker_id!#] Corosync Cluster Member: . [#!variable!in_ccm!#] In Corosync Process Group: [#!variable!crmd_member!#] Joined Domain: ........... [#!variable!cluster_member!#] In Maintenance Mode: ..... [#!variable!maintenance_mode!#] The node: [#!variable!node_name!#] pacemaker ID: [#!variable!old_pacemaker_id!#] has changed to: [#!variable!new_pacemaker_id!#] The node: [#!variable!node_name!#] corosync cluster membership status has changed from: [#!variable!old_in_ccm!#] has changed to: [#!variable!new_in_ccm!#] The node: [#!variable!node_name!#] corosync process group status changed from: [#!variable!old_crmd_member!#] has changed to: [#!variable!new_crmd_member!#] The node: [#!variable!node_name!#] cluster domain membership status changed from: [#!variable!old_cluster_member!#] has changed to: [#!variable!new_cluster_member!#] The node: [#!variable!node_name!#] maintenance mode status has changed from: [#!variable!old_maintenance_mode!#] has changed to: [#!variable!new_maintenance_mode!#] The node: [#!variable!old_node_name!#] has been renamed to: [#!variable!new_node_name!#] The node: [#!variable!host_name!#] is no longer in the cluster. The node: [#!variable!host_name!#] is returning back into the cluster. The Cluster CIB for the cluster: [#!variable!cluster_name!#] has changed. The difference is: ==== #!variable!difference!# ==== The server: [#!variable!server!#] was found to be failed in pacemaker, but it was successfully recovered. This does NOT mean the server rebooted, but it may have. Checking the server is advised. The server: [#!variable!server!#] was found to be failed in pacemaker. The attempt to recover it appears to have failed. The server might well still be running ok, checking the server is advised. The server: [#!variable!server!#] had been found to be failed in pacemaker. It's now recovered. This does NOT mean the server rebooted, but it may have. Checking the server is advised. Starting: [#!variable!program!#]. This host is a: [#!variable!host_type!#], this agent is only useful on nodes. Exiting. [ Warning ] - The server: [#!variable!server!#] is in a FAILED state! Checking to see if it's safe to attempt recovery. Searching node: [#!variable!node_name!# (#!variable!host_uuid!#] which is in ready state: [#!variable!node_ready!#]. Searching for the server on the local system. Searching for the server on the peer using IP: [#!variable!target_ip!#]. The server is running locally and we're a full cluster member. Will attempt recover. Both nodes are up and the server wasn't found anywhere. Attempting recovery. The server was found to be running, but not here (or this node is not fully in the cluster). NOT attempting recovery yet. Attempting recovery now... Checking to see if the server has recovered yet... Found the stale DRBD fenced attribute: [#!variable!attribute!#], removing it. Yes No