List:Cluster« Previous MessageNext Message »
From:Tomas Ulin Date:November 12 2004 7:21am
Subject:Re: Can't connect MGM after server down
View as plain text  
For now you can just restart the management server... this has no impact 
on the database service.

And since it seems you use fixed nodeid's you can start it again with 
"ndb_mgmd --no-nodeid-checks" and then you will not run into the problem 
again.

T

NiCK wrote:

>Thank you for your answer. 
>Waiting for 4.1.8 release.......
>
>-----Original Message-----
>From: Tomas Ulin [mailto:tomas@stripped] 
>Sent: 2004?11?12? 13:46
>To: NiCK
>Cc: cluster@stripped
>Subject: Re: Can't connect MGM after server down
>
>This is a recently "fixed" bug.  Even though it is not fixed properly, a new
>workaround is provided (and some existed before). See last comment at:
>
>http://bugs.mysql.com/bug.php?id=6328
>
>T
>
>NiCK wrote:
>
>  
>
>>Hi:
>>
>>I have a mysql cluster that include 1 MGM ,2 NDB and 2 API. 3 boxes .
>>Config.ini setting as follows:
>>[NDBD DEFAULT]
>>NoOfReplicas= 2
>>DataDir= /var/lib/mysql-cluster
>>
>>[NDB_MGMD]
>>Hostname= 192.168.8.92
>>DataDir= /var/lib/mysql-cluster
>>
>>[NDBD]
>>HostName= 192.168.8.94
>>
>>[NDBD]
>>HostName= 192.168.8.93
>>
>>[MYSQLD]
>>HostName= 192.168.8.94
>>
>>[MYSQLD]
>>HostName= 192.168.8.93
>>
>>The problem is:
>>
>>192.168.8.94 server down ,then reboot it. NDB and Mysql can't connect MGM. 
>>I use command that ndbd --connect-string="nodeid=2;host=192.168.8.92:2200"
>>and mysqld_safe --ndb-connectstring="nodeid=4;192.168.8.92:2200"
>>--user=mysql &
>>watch log error messages as follows:
>>cat  ndb_pid1284_error.log 
>>Current byte-offset of file-pointer is: 468                       
>>
>>
>>Date/Time: Friday 12 November 2004 - 10:24:50 Type of error: error
>>Message: Invalid Configuration fetched from Management Server Fault ID: 
>>2350 Problem data: Unable to alloc node id Object of reference: Could 
>>not alloc node id at 192.168.8.92 port 2200: Id 2 already allocated by 
>>another node.
>>ProgramName: NDB Kernel
>>ProcessID: 1284
>>TraceFile: <no tracefile>
>>***EOM***
>>
>>tail localhost.localdomain.err
>>041112 11:07:03  InnoDB: Started; log sequence number 0 43829 
>>Configuration error: Could not alloc node id at 192.168.8.92 port 2200: 
>>Id 4 already allocated by another node.
>>041112 11:07:18 [ERROR] Can't init databases
>>041112 11:07:18 [ERROR] Aborting
>>
>>041112 11:07:18  InnoDB: Starting shutdown...
>>041112 11:07:21  InnoDB: Shutdown completed; log sequence number 0 
>>43829
>>041112 11:07:21 [Note] /usr/local/mysql/bin/mysqld: Shutdown complete
>>
>>041112 11:07:21  mysqld ended
>>
>>
>>MGM server status as follows:
>>NDB> show
>>Cluster Configuration
>>---------------------
>>[ndbd(NDB)]     2 node(s)
>>id=2 (not connected, accepting connect from 192.168.8.94)
>>id=3    @192.168.8.93  (Version: 3.5.3, Nodegroup: 0)
>>
>>[ndb_mgmd(MGM)] 1 node(s)
>>id=1    @192.168.8.92  (Version: 3.5.3)
>>
>>[mysqld(API)]   2 node(s)
>>id=4 (not connected, accepting connect from 192.168.8.94)
>>id=5    @192.168.8.93  (Version: 3.5.3)
>>
>>
>>why?
>>
>>
>> 
>>
>>    
>>
>
>
>  
>

Thread
Can't connect MGM after server downNiCK12 Nov
Re: Can't connect MGM after server downTomas Ulin12 Nov
  • RE: Can't connect MGM after server downNiCK12 Nov
Re: Can't connect MGM after server downTomas Ulin12 Nov