From: Tomas Ulin
Date: June 23 2004 10:31am
Subject: Re: DB node hang on start
List-Archive: http://lists.mysql.com/cluster/30
Message-Id: <40D95BED.4050105@mysql.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit


Since there was alo another person on the list with "similar problem" I 
cloned a fresh copy of the mysql-4.1 tree and tested.  I can succesfully 
get the cluster running on a 2-node config (so there is nothing wrong in 
the clone):

A common reason for nodes hanging is if there are several nodes trying 
to connect via same node id. Please verify that you have unique id's

> 2004-06-20 16:49:34 [NDB] INFO     -- Angel pid: 5558 ndb pid: 5560
> 2004-06-20 16:49:34 [NDB] INFO     -- NDB Cluster -- DB node 2                         <---------------------
> 2004-06-20 16:49:34 [NDB] INFO     -- Version 3.5.0 (beta) --
> 2004-06-20 16:49:34 [NDB] INFO     -- Start initiated (version 3.5.0)
> 

on one and on the second

> ............... [NDB] INFO     -- NDB Cluster -- DB node 3                         <-----------------------

Another thing to try is to replace "names" on COMPUTER by ipaddresses, 
this has been know to cause problems in the past.

I followed the following procedure (after build):

#macine mc02
 > make install prefix=/space/tomas/mysql
 > cd mysql-test
 > ndb/ndbcluster --initial --small --discless
-- successfull
-- edit ndbcluster/1.ndb_mgm/config.ini  s/locahost/mc02, change 
COMPUTER 3 to mc03
 > rsync -r /space/tomas/mysql mc03:/space/tomas/.

autotest@mc02:/space/tomas/mysql/mysql-test/ndbcluster/1.ndb_mgm> 
ndb_mgmd -c config.ini -l Ndb.cfg
autotest@mc02> ndbd --connect-string="host=mc02:2200;nodeid=2" -i
autotest@mc03> ndbd --connect-string="host=mc02:2200;nodeid=3" -i

Matteo Brancaleoni wrote:

>Hi
>
>  
>
>>for 2 nodes  on different machines (I'm assuming you have the same config file
>>as you showed before):
>>-- kill all ndb processes
>>-- <vi|emacs> config.ini
>>-- change computer 2 to your other host  (nothing else)
>>-- start ndb_mgmd
>>-- start ndbd -i on "computer 1", Ndb.cfg|NDB_CONNECSTRING should read
>>"host=bestia:2200;nodeid=2"
>>-- ssh to your other machine
>>-- start ndbd -i on "computer 2", Ndb.cfg|NDB_CONNECSTRING should read
>>"host=bestia:2200;nodeid=3", also make sure you have the dir
>>/root/ndb/ndb_data2 on that computer
>>    
>>
>
>Ok, done that (as already done, btw I followed that procedure exactly),
>but ndbd -i on "computer 2" stick@ "-- Start initiated (version 3.5.0)"
>and on the mgm console, with the "all status" command I see :
>
>NDB> all status
>Node 2: Starting (Start phase 2) (Version 3.5.0)
>  
>Node 3: No contact
>  
>NDB>
>
>where Node 3 is the one on the remote machine...
>no change even if waiting more that 10 minutes.
>
>So seems that Node3(computer 2) starts, get it's configuration
>(and tcpdump confirms that) but then doesn't communicate
>with the other node and/or the MGM process.
>
>Matteo.
>
>
>  
>