#
# AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
"POT-Creation-Date: 2018-05-14 18:03-0500\n"
"PO-Revision-Date: 2018-05-14 18:03-0500\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
"Content-Type: application/x-publican; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
#, no-c-format
msgid "Start and Verify Cluster"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Start the Cluster"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Now that corosync is configured, it is time to start the cluster. The command below will start corosync and pacemaker on both nodes in the cluster. If you are issuing the start command from a different node than the one you ran the <literal>pcs cluster auth</literal> command on earlier, you must authenticate on the current node you are logged into before you will be allowed to start the cluster."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs cluster start --all\n"
"pcmk-1: Starting Cluster...\n"
"pcmk-2: Starting Cluster..."
msgstr ""
#. Tag: para
#, no-c-format
msgid "An alternative to using the <literal>pcs cluster start --all</literal> command is to issue either of the below command sequences on each node in the cluster separately:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# pcs cluster start\n"
"Starting Cluster..."
msgstr ""
#. Tag: para
#, no-c-format
msgid "or"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# systemctl start corosync.service\n"
"# systemctl start pacemaker.service"
msgstr ""
#. Tag: para
#, no-c-format
msgid "In this example, we are not enabling the corosync and pacemaker services to start at boot. If a cluster node fails or is rebooted, you will need to run <literal>pcs cluster start <replaceable>nodename</replaceable></literal> (or <literal>--all</literal>) to start the cluster on it. While you could enable the services to start at boot, requiring a manual start of cluster services gives you the opportunity to do a post-mortem investigation of a node failure before returning it to the cluster."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Verify Corosync Installation"
msgstr ""
#. Tag: para
#, no-c-format
msgid "First, use <literal>corosync-cfgtool</literal> to check whether cluster communication is happy:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# corosync-cfgtool -s\n"
"Printing ring status.\n"
"Local node ID 1\n"
"RING ID 0\n"
" id = 192.168.122.101\n"
" status = ring 0 active with no faults"
msgstr ""
#. Tag: para
#, no-c-format
msgid "We can see here that everything appears normal with our fixed IP address (not a 127.0.0.x loopback address) listed as the <emphasis role=\"strong\">id</emphasis>, and <emphasis role=\"strong\">no faults</emphasis> for the status."
msgstr ""
#. Tag: para
#, no-c-format
msgid "If you see something different, you might want to start by checking the node’s network, firewall and selinux configurations."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Next, check the membership and quorum APIs:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# corosync-cmapctl | grep members\n"
"runtime.totem.pg.mrp.srp.members.1.config_version (u64) = 0\n"
"runtime.totem.pg.mrp.srp.members.1.ip (str) = r(0) ip(192.168.122.101)\n"
"runtime.totem.pg.mrp.srp.members.1.join_count (u32) = 1\n"
"runtime.totem.pg.mrp.srp.members.1.status (str) = joined\n"
"runtime.totem.pg.mrp.srp.members.2.config_version (u64) = 0\n"
"runtime.totem.pg.mrp.srp.members.2.ip (str) = r(0) ip(192.168.122.102)\n"
"runtime.totem.pg.mrp.srp.members.2.join_count (u32) = 2\n"
"runtime.totem.pg.mrp.srp.members.2.status (str) = joined\n"
"\n"
"[root@pcmk-1 ~]# pcs status corosync\n"
"Membership information\n"
" --------------------------\n"
" Nodeid Votes Name\n"
" 1 1 pcmk-1 (local)\n"
" 2 1 pcmk-2"
msgstr ""
#. Tag: para
#, no-c-format
msgid "You should see both nodes have joined the cluster."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Verify Pacemaker Installation"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Now that we have confirmed that Corosync is functional, we can check the rest of the stack. Pacemaker has already been started, so verify the necessary processes are running:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# ps axf\n"
" PID TTY STAT TIME COMMAND\n"
" 2 ? S 0:00 [kthreadd]\n"
"...lots of processes...\n"
" 1362 ? Ssl 0:35 corosync\n"
" 1379 ? Ss 0:00 /usr/sbin/pacemakerd -f\n"
" 1380 ? Ss 0:00 \\_ /usr/libexec/pacemaker/pacemaker-based\n"
" 1381 ? Ss 0:00 \\_ /usr/libexec/pacemaker/pacemaker-fenced\n"
" 1382 ? Ss 0:00 \\_ /usr/libexec/pacemaker/pacemaker-execd\n"
" 1383 ? Ss 0:00 \\_ /usr/libexec/pacemaker/pacemaker-attrd\n"
" 1384 ? Ss 0:00 \\_ /usr/libexec/pacemaker/pacemaker-schedulerd\n"
" 1385 ? Ss 0:00 \\_ /usr/libexec/pacemaker/pacemaker-controld"
msgstr ""
#. Tag: para
#, no-c-format
msgid "If that looks OK, check the <literal>pcs status</literal> output:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs status\n"
"Cluster name: mycluster\n"
"WARNING: no stonith devices and stonith-enabled is not false\n"
"Stack: corosync\n"
"Current DC: pcmk-2 (version 1.1.16-12.el7_4.5-94ff4df) - partition with quorum\n"
"Last updated: Fri Jan 12 16:15:29 2018\n"
"Last change: Fri Jan 12 15:49:47 2018\n"
"\n"
"2 nodes configured\n"
"0 resources configured\n"
"\n"
"Online: [ pcmk-1 pcmk-2 ]\n"
"\n"
"No active resources\n"
"\n"
"Daemon Status:\n"
" corosync: active/disabled\n"
" pacemaker: active/disabled\n"
" pcsd: active/enabled"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Finally, ensure there are no startup errors (aside from messages relating to not having STONITH configured, which are OK at this point):"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# journalctl | grep -i error"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Other operating systems may report startup errors in other locations, for example <literal>/var/log/messages</literal>."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Repeat these checks on the other node. The results should be the same."
msgstr ""