Hi Christian, the nodes are only configured in the ha.cf file. Be sure to have the /etc/hosts file configured correctly and I don't see any broadcast interface in your ha.cf ? Maybe that's why it can't find the other node. Have a look at the sample configuration (usually found in: /usr/share/doc/packages/heartbeat/ha.cf)
Looks something like this (you can decide to use unicast, broadcast, multicast or serial for connection between the nodes): # What UDP port to use for bcast/ucast communication? # #udpport 694 # # Baud rate for serial ports... # #baud 19200 # # serial serialportname ... #serial /dev/ttyS0 # Linux #serial /dev/cuaa0 # FreeBSD #serial /dev/cuad0 # FreeBSD 6.x #serial /dev/cua/a # Solaris # # # What interfaces to broadcast heartbeats over? # bcast eth1 # Linux #bcast eth1 eth2 # Linux #bcast le0 # Solaris #bcast le1 le2 # Solaris # # Set up a multicast heartbeat medium # mcast [dev] [mcast group] [port] [ttl] [loop] # # [dev] device to send/rcv heartbeats on # [mcast group] multicast group to join (class D multicast address # 224.0.0.0 - 239.255.255.255) # [port] udp port to sendto/rcvfrom (set this value to the # same value as "udpport" above) # [ttl] the ttl value for outbound heartbeats. this effects # how far the multicast packet will propagate. (0-255) # Must be greater than zero. # [loop] toggles loopback for outbound multicast heartbeats. # if enabled, an outbound packet will be looped back and # received by the interface it was sent on. (0 or 1) # Set this value to zero. # # #mcast eth0 225.0.0.1 694 1 0 # # Set up a unicast / udp heartbeat medium # ucast [dev] [peer-ip-addr] # # [dev] device to send/rcv heartbeats on # [peer-ip-addr] IP address of peer to send packets to # #ucast eth0 192.168.1.2 Regards, Tobi On Sat, 2009-01-31 at 16:14 +0100, Christian Schoepplein wrote: > Hi, > > I try to build a 2 node cluster with heartbeat 2.1.4-4 on Debian. No > ressources and constrains configured yet. > > --- /etc/ha.d/authkeys --- > auth 1 > 1 md5 Hello! > ------------- > > -- /etc/ha.d/ha.cf > logfacility local7 > logfile /var/log/ha-log > debugfile /var/log/ha-debug > #use_logd on > udpport 694 > keepalive 1 # 1 second > deadtime 10 > initdead 80 > bcast eth0 > node amd64 > node cs > ping 192.168.1.100 > crm yes > auto_failback yes > autojoin any > ----------- > > The files above reside on both nodes amd64 and cs. > > But on every node only the local machine shows up as node in the > cluster, they can't find each other. From the logs on amd64: > > crmd[11414]: 2009/01/31_15:58:37 WARN: get_uuid: Could not calculate > UUID for cs > crmd[11414]: 2009/01/31_15:58:37 WARN: populate_cib_nodes: Node cs: no > uuid found > crmd[11414]: 2009/01/31_15:58:38 notice: populate_cib_nodes: Node: amd64 > (uuid: ee86bba2-24b3-4b21-9cbd-1a0a6c75bdaa) > crmd[11414]: 2009/01/31_15:58:38 info: do_ha_control: Connected to > Heartbeatcrmd[11414]: 2009/01/31_15:58:38 info: do_ccm_control: CCM > connection establishe > d... waiting for first callback > crmd[11414]: 2009/01/31_15:58:38 info: do_started: Delaying start, CCM > (00000000 > 00100000) not connected > crmd[11414]: 2009/01/31_15:58:38 info: crmd_init: Starting crmd's > mainloop > crmd[11414]: 2009/01/31_15:58:38 notice: crmd_client_status_callback: > Status update: Client amd64/crmd now has status [online] > > The cib.xml file looks as follows, realy only one node appears :(: > > <cib generated="true" admin_epoch="0" epoch="9" num_updates="2" > have_quorum="true" ignore_dtd="false" num_peers="1" > cib_feature_revision="2.0" > crm_feature_set="2.0" cib-last-written="Sat Jan 31 16:00:00 2009" > ccm_transition="1" dc_uuid="ee86bba2-24b3-4b21-9cbd-1a0a6c75bdaa"> > <configuration> > <crm_config> > <cluster_property_set id="cib-bootstrap-options"> > <attributes> > <nvpair id="cib-bootstrap-options-dc-version" > name="dc-version" value="2.1.4-node: > aa909246edb386137b986c5773344b98c6969999"/> > </attributes> > </cluster_property_set> > </crm_config> > <nodes> > <node id="ee86bba2-24b3-4b21-9cbd-1a0a6c75bdaa" uname="amd64" > type="normal"/> > </nodes> > <resources/> > <constraints/> > </configuration> > </cib> > > The file has been autogenerated during the startup of heartbeat. > > I tryed to add the second node with the following command: > > amd64:~# /usr/lib/heartbeat/hb_addnode cs > > The following shows up in the log: > > heartbeat[11396]: 2009/01/31_16:07:41 info: hb_add_one_node: Adding new > node[cs] to configuration. > heartbeat[11396]: 2009/01/31_16:07:41 ERROR: hb_add_one_node: node(cs) > already exists > heartbeat[11396]: 2009/01/31_16:07:41 ERROR: Add node cs failed > > Whats going wrong there? Why is'nt the node found during startup or how > can I add the node permanently to the cib.xml file? I can't use the GUI > unfortunatly so any other textbased solution would be great! > > > Cheers and sorry for the beinner questions, > > Christian > > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
