Hello Geert,
I did that when I changed the first data node to Linux also. The only change
I made in the config.ini was in the dataDir path of each data node. I
changed these paths from a windows path c:\mysql\data_ars to /mysq/data_ars.
This error did not occur for the first data node when I restarted the
management node with the new path for the 1st data node in the config.ini. I
had done an --initial then also. I noticed it writes logs to the
/mysql/data_ars directory in both Linux nodes. So I guess it has read the
config.ini file correctly.
Best Regards,
Subodh
-----Original Message-----
From: Geert.Vanderkelen@stripped [mailto:Geert.Vanderkelen@stripped]
Sent: Wednesday, March 31, 2010 6:13 PM
To: Subodh Nair
Cc: MySQL Cluster Mailing List
Subject: Re: MySQL cluster- migrating from WIndows to Linux
On Mar 31, 2010, at 14:35 , Subodh Nair wrote:
> ..
> 2010-03-31 13:06:38 [MgmSrvr] INFO -- Node 1: Node 1 Connected
> 2010-03-31 13:06:38 [MgmSrvr] INFO -- Id: 1, Command port: *:1186
> 2010-03-31 13:06:38 [MgmSrvr] INFO -- Starting initial configuration
> change
> 2010-03-31 13:06:38 [MgmSrvr] INFO -- Configuration 1 commited
> 2010-03-31 13:06:38 [MgmSrvr] INFO -- Config change completed! New
> generation: 1
You seem to have restarted the management node with a new configuration, or
at least using the --initial option for ndb_mgmd. Could it be that the
configuration is now different/incorrect?
Geert
--
Geert Vanderkelen, MySQL Senior Support Engineer
Sun Microsystems GmbH Sonnenallee 1, D-85551 Kirchheim-Heimstetten
Geschaeftsfuehrer: Thomas Schröder HRB MUC 161028
