[SOLVED] Mysql server doesnot connect to management server.

tom6_uk · 03-06-2010, 06:25 AM

I have installed two data nodes , one management node and one mysql server on different machines. I have a problem that server node doesn't get connected to management node. When using shell>ndb_mgm -e show. It shows data and management node connected except server node.
Please help me.

Thanks.

zhjim · 04-06-2010, 04:33 AM

Hi Tom,

dunno if your problem still exists? Anyway here are some ideas.

How did you configure the sql server? Please provide the my.cnf file.

Did you check out this site? It's the official mysql site for configuring a cluster.
http://dev.mysql.com/doc/refman/5.0/...ti-config.html

tom6_uk · 04-12-2010, 07:35 AM

Thnx 4 reply.

Following is ('my.cnf') configuration file for server.

[mysqld]
ndbcluster #run NDB storage engine
ndb-connectstring=172.18.21.106 #location of management server

This is stored in /etc. I start server using /etc/init.d/mysqld start.

zhjim · 04-12-2010, 08:33 AM

Try adding this to your my.cnf

Code:

# Options for ndbd process:
[mysql_cluster]
ndb-connectstring=172.18.21.106  # location of management server

Heres the complete my.cnf as per the mysql.com website. (link I provided in my previous post)

Code:

# Options for mysqld process:
[mysqld]
ndbcluster                      # run NDB storage engine
ndb-connectstring=192.168.0.10  # location of management server

# Options for ndbd process:
[mysql_cluster]
ndb-connectstring=192.168.0.10  # location of management server

tom6_uk · 04-16-2010, 08:22 AM

one doubt can we install mysql server and data nodes on different machines?

tom6_uk · 04-24-2010, 01:53 PM

Following is mysql cluser server log.

Quote:

100421 16:32:18 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
100421 16:32:18 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The first specified data file ./ibdata1 did not exist:
InnoDB: a new database to be created!
100421 16:32:18 InnoDB: Setting file ./ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
100421 16:32:19 InnoDB: Log file ./ib_logfile0 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile0 size to 5 MB
InnoDB: Database physically writes the file full: wait...
100421 16:32:20 InnoDB: Log file ./ib_logfile1 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile1 size to 5 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
100421 16:32:20 InnoDB: Started; log sequence number 0 0
100421 16:32:20 [Note] NDB: NodeID is 3, management server '172.18.21.11:1186'
100421 16:32:21 [Note] NDB[0]: NodeID: 3, no storage nodes connected (timed out)
100421 16:32:21 [Warning] NDB: server id set to zero will cause any other mysqld with bin log to log with wrong server id
100421 16:32:21 [Note] Starting Cluster Binlog Thread
100421 16:32:21 [Note] Event Scheduler: Loaded 0 events
100421 16:32:37 [Warning] NDB : Tables not available after 15 seconds. Consider increasing --ndb-wait-setup value
100421 16:32:37 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.44-ndb-7.1.3-cluster-gpl' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Cluster Server (GPL)
2010-04-21 16:33:31 [NdbApi] INFO -- Management server closed connection early. It is probably being shut down (or has problems). We will retry the connection. 1006 Illegal reply from server line: 2883
2010-04-21 16:33:36 [NdbApi] INFO -- Management server closed connection early. It is probably being shut down (or has problems). We will retry the connection. 110 Time out talking to management server Error line: 454
2010-04-21 16:33:41 [NdbApi] INFO -- Management server closed connection early. It is probably being shut down (or has problems). We will retry the connection. 110 Time out talking to management server Error line: 454
100421 16:33:45 [Note] /usr/sbin/mysqld: Normal shutdown

100421 16:33:45 [Note] Event Scheduler: Purging the queue. 0 events
100421 16:33:45 [Note] Stopping Cluster Utility thread
100421 16:33:45 [Note] Stopping Cluster Binlog
2010-04-21 16:33:46 [NdbApi] INFO -- Management server closed connection early. It is probably being shut down (or has problems). We will retry the connection. 110 Time out talking to management server Error line: 454
100421 16:33:46 InnoDB: Starting shutdown...
100421 16:33:50 InnoDB: Shutdown completed; log sequence number 0 44233
100421 16:33:50 [Note] /usr/sbin/mysqld: Shutdown complete

100421 16:33:50 mysqld_safe mysqld from pid file /var/lib/mysql/cloud.cluster1.pid ended

tom6_uk · 04-24-2010, 01:53 PM

plz help me.

tom6_uk · 07-15-2012, 09:29 AM

This issue resolved. Its problem of firewall. In firewall i opened this port 1186.

dloghis · 10-06-2012, 04:16 AM

Beware MySQL Cluster is not using only 1186!
If you have a firewall you must consider that when it starts (default settings) every node is seeking the other in a random “hight port” , port is allocated dynamically in such a way as to ensure that no two nodes on the same host computer receive the same port number, so if you start the cluster without firewall and then you enable it is going to be ok but... if you are going to restart the cluster from ndb_mgm or stop and start it you are going to have an error like:

Management server closed connection early. It is probably being shut down (or has problems). We will retry the connection.

I did not test if you are going to have other problems but the right thing here is to setup your config.ini under [ndbd default] ServerPort=37650 or some port, or in my opinion to setup your firewall to open the high ports (above 1024) I hope this helped, dimitrios.