0cd5218f50
Closes-Bug: #1352053 Minor ormatting, capitalization and verb tense corrections Corrections to IP addresses in some examples and replacing "VIP" with "virtual IP" for simplicity. Calling out split-brain possibility in 2-node cluster with required quorum override Amended with feedback from Andreas Jaeger and Christian Berendt on patch set 1 and 2 Change-Id: I1cc532d73483ad82d1ceaec92a8caf11071a7d0e
55 lines
2.3 KiB
XML
55 lines
2.3 KiB
XML
<section xmlns="http://docbook.org/ns/docbook"
|
|
xmlns:xi="http://www.w3.org/2001/XInclude"
|
|
xmlns:xlink="http://www.w3.org/1999/xlink"
|
|
version="5.0"
|
|
xml:id="_starting_corosync">
|
|
|
|
<title>Starting Corosync</title>
|
|
|
|
<para>Corosync is started as a regular system service. Depending on your
|
|
distribution, it may ship with an LSB init script, an
|
|
upstart job, or a systemd unit file. Either way, the service is
|
|
usually named <literal>corosync</literal>:</para>
|
|
<itemizedlist>
|
|
<listitem>
|
|
<para><literal>/etc/init.d/corosync start</literal> (LSB)
|
|
</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para><literal>service corosync start</literal> (LSB, alternate)
|
|
</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para><literal>start corosync</literal> (upstart)
|
|
</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para><literal>systemctl start corosync</literal> (systemd)
|
|
</para>
|
|
</listitem>
|
|
</itemizedlist>
|
|
<para>You can now check the Corosync connectivity with two tools.</para>
|
|
<para>The <literal>corosync-cfgtool</literal> utility, when invoked with the <literal>-s</literal> option,
|
|
gives a summary of the health of the communication rings:</para>
|
|
<screen><prompt>#</prompt> <userinput>corosync-cfgtool -s</userinput>
|
|
<computeroutput>Printing ring status.
|
|
Local node ID 435324542
|
|
RING ID 0
|
|
id = 192.168.42.82
|
|
status = ring 0 active with no faults
|
|
RING ID 1
|
|
id = 10.0.42.100
|
|
status = ring 1 active with no faults</computeroutput></screen>
|
|
<para>The <literal>corosync-objctl</literal> utility can be used to dump the Corosync cluster
|
|
member list:</para>
|
|
<screen><prompt>#</prompt> <userinput>corosync-objctl runtime.totem.pg.mrp.srp.members</userinput>
|
|
<computeroutput>runtime.totem.pg.mrp.srp.435324542.ip=r(0) ip(192.168.42.82) r(1) ip(10.0.42.100)
|
|
runtime.totem.pg.mrp.srp.435324542.join_count=1
|
|
runtime.totem.pg.mrp.srp.435324542.status=joined
|
|
runtime.totem.pg.mrp.srp.983895584.ip=r(0) ip(192.168.42.87) r(1) ip(10.0.42.254)
|
|
runtime.totem.pg.mrp.srp.983895584.join_count=1
|
|
runtime.totem.pg.mrp.srp.983895584.status=joined</computeroutput></screen>
|
|
<para>You should see a <literal>status=joined</literal> entry for each of your constituent
|
|
cluster nodes.</para>
|
|
</section>
|