Fwd: process_status_message: bad node [dbms1] in message

Víctor Romero romero at kde.org
Wed Mar 6 08:23:22 MST 2002




Actually Im setting up a two node high availability cluster with postgresql
+ heartbeat.. with a serial cable... the main problem I get the topic's line
continously and dont know why, Im pretty sure the host names are right and so
on... Looking into the heartbeat code I see the following :

thisnode = lookup_node(from);
if (thisnode == NULL) {
#if defined(MITJA)
                /* If a node isn't in the configfile, add it... */
                ha_log(LOG_WARNING
                ,   "process_status_message: new node [%s] in message"
                ,       from);
                add_node(from, NORMALNODE);
                thisnode = lookup_node(from);
                if (thisnode == NULL) {
                        goto psm_done;
                }
#else
                /* If a node isn't in the configfile - whine */
                ha_log(LOG_ERR
                ,   "process_status_message: bad node [%s] in message"
                ,       from);
                ha_log_message(msg);
                goto psm_done;
#endif
}


	So without the Mitja def it will never work, inst it?

	Actually Im using the debian's woody packaged hearbeat....

	Heres some info :


Linux dbms0 2.4.17 #4 SMP Wed Jan 30 15:53:04 CET 2002 i686 unknown

ii  heartbeat      0.4.9.0l-7     Subsystem for High-Availability Linux

heartbeat: 2002/03/05_16:19:47 info: **************************
heartbeat: 2002/03/05_16:19:47 info: Configuration validated. Starting
heartbeat 0.4.9.0l
heartbeat: 2002/03/05_16:19:47 info: heartbeat: version 0.4.9.0l
heartbeat: 2002/03/05_16:19:47 info: Heartbeat generation: 10
heartbeat: 2002/03/05_16:19:47 notice: Starting serial heartbeat on tty
/dev/ttyS0
heartbeat: 2002/03/05_16:19:47 info: Local status now set to: 'up'
heartbeat: 2002/03/05_16:19:47 info: Heartbeat restart on node dbms0
heartbeat: 2002/03/05_16:19:47 ERROR: process_status_message: bad node
[dbms1] in message
heartbeat: 2002/03/05_16:19:47 info: MSG: Dumping message with 9 fields
heartbeat: 2002/03/05_16:19:47 info: MSG[0]: t=status
heartbeat: 2002/03/05_16:19:47 info: MSG[1]: st=active
heartbeat: 2002/03/05_16:19:47 info: MSG[2]: src=dbms1
heartbeat: 2002/03/05_16:19:47 info: MSG[3]: seq=6b
heartbeat: 2002/03/05_16:19:47 info: MSG[4]: hg=4
heartbeat: 2002/03/05_16:19:47 info: MSG[5]: ts=3c84e1f3
heartbeat: 2002/03/05_16:19:47 info: MSG[6]: ld=0.00 0.00 0.00 1/33 3549
heartbeat: 2002/03/05_16:19:47 info: MSG[7]: ttl=3
heartbeat: 2002/03/05_16:19:47 info: MSG[8]: auth=1 75fcba4d
heartbeat: 2002/03/05_16:19:47 ERROR: process_status_message: bad node
[dbms1] in message


#
#	Tell what machines are in the cluster
#	node	nodename ...	-- must match uname -n
#node	ken3
#node	kathy
#	node    nodename ...    -- must match uname -n
# everything beyond this point is preserved

node dbms0
node dmbs1


#
#       An example where a shared filesystem is to be used.
#       Note that multiple aguments are passed to this script using
#       the delimiter '::' to separate each argument.
#
#node1  10.0.0.170 Filesystem::/dev/sda1::/data1::ext2
#dbms1
#dbms0
# everything beyond this point is preserved

dbms0  servicios
dmbs1  servicios



auth 1
1 crc

-------------------------------------------------------

-------------------------------------------------------



More information about the Linux-HA mailing list