On 09/30/2013 01:45 PM, Patrick
Hemmer wrote:
I'm running corosync 2.3.2 on ubuntu precise. I'm playing with a
3 node cluster, and whenever I try to start corosync on one of
the nodes, it fails to start properly.
I just do a simple start with `corosync -f`, and whenever I try
to use any of the tools, they error:
# corosync-cmapctl
Failed to initialize the cmap API. Error
CS_ERR_TRY_AGAIN
# corosync-quorumtool
Cannot initialize CMAP service
If I wait long enough (about 9 minutes or 530 seconds), it does
end up starting, and the tools work, but corosync-quorumtool
shows the only member is itself.
However if I start corosync with `strace -f corosync -f` the
tools work fine immediately upon start (though it still doesn't
show the other nodes). Smells like race condition, but dunno
where to begin.
My guess is something is wrong with your network relating to
multicast. Try using udpu mode - it is very stable now and
removes multicast from the list of things that can go wrong.
I am using udpu, see the config
:-)
Regards
-steve
This is the output from `corosync -f` (this node is
10.20.0.212):
notice [TOTEM ] Initializing transport (UDP/IP Unicast).
notice [TOTEM ] Initializing transmit/receive security
(NSS) crypto: none hash: none
notice [TOTEM ] The network interface [10.20.0.212] is
now up.
notice [TOTEM ] adding new UDPU member {10.20.0.127}
notice [TOTEM ] adding new UDPU member {10.20.0.212}
notice [TOTEM ] adding new UDPU member {10.20.2.124}
notice [TOTEM ] A new membership (10.20.0.212:1122820)
was formed. Members joined: 2
notice [TOTEM ] A new membership (10.20.0.127:1122824)
was formed. Members joined: 1 3
### here is where it pauses for almost 9 minutes ###
error [TOTEM ] FAILED TO RECEIVE
notice [TOTEM ] A new membership (10.20.0.212:1122876)
was formed. Members left: 1 3
notice [TOTEM ] A new membership (10.20.0.212:1122936)
was formed. Members
notice [TOTEM ] A new membership (10.20.0.212:1123008)
was formed. Members
notice [TOTEM ] A new membership (10.20.0.212:1123064)
was formed. Members
notice [TOTEM ] A new membership (10.20.0.212:1123124)
was formed. Members
notice [TOTEM ] A new membership (10.20.0.212:1123180)
was formed. Members
notice [TOTEM ] A new membership (10.20.0.212:1123248)
was formed. Members
notice [TOTEM ] A new membership (10.20.0.127:1123256)
was formed. Members joined: 1 3
This is the config (created by `pcs` utility), it's exactly the
same on all 3 nodes, and the other 2 nodes work fine:
----
totem {
version: 2
secauth: off
cluster_name: hapi-server
transport: udpu
}
nodelist {
node {
ring0_addr: i-74eb9c2f
nodeid: 1
}
node {
ring0_addr: i-a3bf0df9
nodeid: 2
}
node {
ring0_addr: i-ebcfcbb0
nodeid: 3
}
}
quorum {
provider: corosync_votequorum
}
logging {
to_syslog: yes
}
----
-Patrick
_______________________________________________
discuss mailing list
discuss@xxxxxxxxxxxx
http://lists.corosync.org/mailman/listinfo/discuss
|
_______________________________________________
discuss mailing list
discuss@xxxxxxxxxxxx
http://lists.corosync.org/mailman/listinfo/discuss
