NOTE: All string keys MUST be prefixed with the agent name! ie: 'scan_cluster_log_0001'.
-->
<words>
<metaversion="3.0.0"languages="en_CA,jp"/>
<!-- Canadian English -->
<languagename="en_CA"long_name="Canadian English"description="ScanCore scan agent that monitors hardware, like RAM modules, CSS LED status, CPU information, etc.">
In Corosync Process Group: [#!variable!crmd_member!#]
Joined Domain: ........... [#!variable!cluster_member!#]
In Maintenance Mode: ..... [#!variable!maintenance_mode!#]
</key>
<keyname="scan_cluster_alert_0004">The node: [#!variable!node_name!#] pacemaker ID: [#!variable!old_pacemaker_id!#] has changed to: [#!variable!new_pacemaker_id!#]</key>
<keyname="scan_cluster_alert_0005">The node: [#!variable!node_name!#] corosync cluster membership status has changed from: [#!variable!old_in_ccm!#] has changed to: [#!variable!new_in_ccm!#]</key>
<keyname="scan_cluster_alert_0006">The node: [#!variable!node_name!#] corosync process group status changed from: [#!variable!old_crmd_member!#] has changed to: [#!variable!new_crmd_member!#]</key>
<keyname="scan_cluster_alert_0007">The node: [#!variable!node_name!#] cluster domain membership status changed from: [#!variable!old_cluster_member!#] has changed to: [#!variable!new_cluster_member!#]</key>
<keyname="scan_cluster_alert_0008">The node: [#!variable!node_name!#] maintenance mode status has changed from: [#!variable!old_maintenance_mode!#] has changed to: [#!variable!new_maintenance_mode!#]</key>
<keyname="scan_cluster_alert_0009">The node: [#!variable!old_node_name!#] has been renamed to: [#!variable!new_node_name!#]</key>
<keyname="scan_cluster_alert_0010">The node: [#!variable!host_name!#] is no longer in the cluster.</key>
<keyname="scan_cluster_alert_0011">The node: [#!variable!host_name!#] is returning back into the cluster.</key>
<keyname="scan_cluster_alert_0013">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.</key>
<keyname="scan_cluster_alert_0014">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.</key>
<keyname="scan_cluster_alert_0015">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.</key>
<keyname="scan_cluster_alert_0016">The node name: [#!variable!node_name!#] failed to translate to a host UUID. Does the node name match the host name?</key>
<keyname="scan_cluster_log_0003">[ Warning ] - The server: [#!variable!server!#] is in a FAILED state! Checking to see if it's safe to attempt recovery.</key>
<keyname="scan_cluster_log_0004">Searching node: [#!variable!node_name!# (#!variable!host_uuid!#] which is in ready state: [#!variable!node_ready!#].</key>
<keyname="scan_cluster_log_0005">Searching for the server on the local system.</key>
<keyname="scan_cluster_log_0006">Searching for the server on the peer using IP: [#!variable!target_ip!#].</key>
<keyname="scan_cluster_log_0007">The server is running locally and we're a full cluster member. Will attempt recover.</key>
<keyname="scan_cluster_log_0008">Both nodes are up and the server wasn't found anywhere. Attempting recovery.</key>
<keyname="scan_cluster_log_0009">The server was found to be running, but not here (or this node is not fully in the cluster). NOT attempting recovery yet.</key>