I have the same problem. I have an open bug report here: http://bugs.mysql.com/?id=4761
I can't figure out why my management server can not see my ndb servers. Perhaps I should try to down the secondary interface on all the servers? On Tue, 17 Aug 2004 15:54:29 -0400, Wheeler, Alex <[EMAIL PROTECTED]> wrote: > Yes, now I remember. This happens when I have either 2 interfaces or a > disagreement on hostname. If the clients don't see the server or > themselves by the same hostname as the server, this type of error can be > seen. > I've been setup with a node that did the initial communication via eth1 > but then tried the remainder via eth0 which corresponded with the > hostname, and which obviously didn't work. > I ended up temporarily changing the hostname to reference the eth1 ip. > > -- > Alex Wheeler > > -----Original Message----- > From: IHLING, CHRIS G (CHRIS) [mailto:[EMAIL PROTECTED] > Sent: Tuesday, August 17, 2004 3:43 PM > To: IHLING, CHRIS G (CHRIS) > Cc: [EMAIL PROTECTED] > Subject: RE: Problem with management server communication. > > I have no problem pinging either box from both. There is one other > strange thing. If I try to use a fully qualified hostname or ip address > in the config file I get an error when I try to start the ndbd. > > -----Original Message----- > From: Jonas Oreland [mailto:[EMAIL PROTECTED] > Sent: Tuesday, August 17, 2004 11:42 AM > To: IHLING, CHRIS G (CHRIS) > Cc: [EMAIL PROTECTED] > Subject: Re: Problem with management server communication. > > Hi, > > Also make sure that both hostnames are accessible from both computers. > I.e. that you can ping both lpsdev3-n1 & lpsdev3-n2 from both lpsdev3-n1 > > & lpsdev3-n2 > > /Jonas > > IHLING, CHRIS G (CHRIS) wrote: > > I have removed the [TCP] section from my config file and I am still > > seeing the same "no contact" message. Here is the config file I am > > using: > > > > [COMPUTER] > > Id:1 > > ByteOrder: Little > > HostName: lpsdev3-n2 > > > > [COMPUTER] > > Id:2 > > ByteOrder: Little > > HostName: lpsdev3-n1 > > > > [MGM] > > Id:1 > > ExecuteOnComputer: 1 > > PortNumber: 2200 > > ArbitrationRank: 1 > > > > [DB DEFAULT] > > NoOfReplicas:2 > > FileSystemPath: /usr/lps/mysql/data1 > > > > [DB] > > Id:2 > > ExecuteOnComputer:1 > > > > [DB] > > Id:3 > > ExecuteOnComputer:2 > > > > [API] > > Id:4 > > ExecuteOnComputer:1 > > > > [API] > > Id:5 > > ExecuteOnComputer:2 > > > > Is there any way to turn on tracing or check logs to find out more > > info? > > > > -----Original Message----- > > From: Wheeler, Alex [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, August 17, 2004 10:08 AM > > To: [EMAIL PROTECTED] > > Subject: RE: Problem with management server communication. > > > > > > I've seen this kind of error before, and if I recall correctly it's > > due to a misconfiguration of the TCP information. So, if you have any > > > TCP entries in the config.ini file such as [TCP]NodeId1:..., remove > > them as they are automatically configured anyway. Then stop the nodes, > > > and start again. Make sure you use the -i when starting the clients. > > > > -- > > Alex Wheeler > > > > -----Original Message----- > > From: IHLING, CHRIS G (CHRIS) [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, August 17, 2004 12:27 PM > > To: '[EMAIL PROTECTED]' > > Subject: Problem with management server communication. > > > > I am having a problem with the management server getting status from a > > > ndbd started on another machine. > > > > > > > > The ndbd server will start and report status fine if it is running on > > the same machine as the management server. > > > > The ndbd server will start on a different machine but no status is > > reported. > > > > If the management server is not running ndbd will not start so there > > must be some kind of communication just no status. > > > > > > > > Any suggestions on what to try? > > > > > > -- > Jonas Oreland, Software Engineer > MySQL AB, www.mysql.com > > -- > MySQL Cluster Mailing List > For list archives: http://lists.mysql.com/cluster > To unsubscribe: > http://lists.mysql.com/[EMAIL PROTECTED] > > > > > -- > MySQL Cluster Mailing List > For list archives: http://lists.mysql.com/cluster > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] > > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
