Quantcast
Channel: MySQL Forums - NDB clusters
Viewing all articles
Browse latest Browse all 1560

Cannot start ndbd with error message: Unable to connect with connect string: nodeid=0,172.21.6.61:1186 (no replies)

$
0
0
Doing MySQL Cluster 7.2.5 on 6 VM CentOS v5.8/Linux machines with IP 172.21.6.61-66.

-------------------------------------------------------
MySQL Cluster evaluation package used:
mysql-cluster-gpl-7.2.5-linux2.6-x86_64.tar.gz

Unzip and untared to each VM machine under /usr/local
and
$ ln -s /usr/local/mysql-cluster-gpl-7.2.5-linux2.6-x86_64 /usr/local/mysql


-------------------------------------------------------

On all vm machines set /etc/my.cnf:

/etc/my.cnf
"[mysqld]
# Options for mysqld process:
ndbcluster # run NDB storage engine
ndb-connectstring=172.21.6.61 # location of management server

datadir = /ysi/data/evaldb
basedir = /usr/local/mysql
socket=/tmp/mysql.sock

connect_timeout = 60
max_connect_errors = 50
max_connections = 600

log-error=/ysi/logs/error/mysqld.err
pid-file=/ysi/logs/pid/mysqld.pid
slow-query-log=1
slow-query-log-files=/ysi/logs/slow/slow.log
long-query-time=1
log_queries_not_using_indexes
log-bin=/ysi/logs/binlog/bin-log

user = mysql
log-slave-updates
sync-binlog=1
server-id=602

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

-------------------------------------------------------

and set /etc/init.d/mysql.server on all 6 vm machines with
......
datadir = /ysi/data/evaldb
basedir = /usr/local/mysql
......


-------------------------------------------------------

On each ndb and sql node (172.21.6.62-66), install db servers
[/usr/local/mysql] $ scripts/mysql_install_db --user=mysql



-------------------------------------------------------

On management node, 172.21.6.61 create /ysi/data/config.ini:

"[ndbd default]
# Options affecting ndbd processes on all data nodes:
NoOfReplicas=2 # Number of replicas
DataMemory=800M # How much memory to allocate for data storage
IndexMemory=180M # How much memory to allocate for index storage
# For DataMemory and IndexMemory, we have used the
# default values. Since the "world" database takes up
# only about 500KB, this should be more than enough for
# this example Cluster setup.

[tcp default]
# TCP/IP options:
portnumber=2202 # This the default; however, you can use any
# port that is free for all the hosts in the cluster
# Note: It is recommended that you do not specify the port
# number at all and simply allow the default value to be used
# instead

[ndb_mgmd]
# Management process options:
#nodeid=1 # (one [ndbd] section per data node)
hostname=172.21.6.61 # Hostname or IP address of MGM node
datadir=/ysi/logs/mgmdlog # Directory for MGM node log files

[ndbd]
#nodeid=2 # (one [ndbd] section per data node)
hostname=172.21.6.62 # Hostname or IP address
#datadir=/usr/local/mysql/data/evaldb # Directory for this data node's data files
datadir=/ysi/data/evaldb # Directory for this data node's data files

[ndbd]
#nodeid=3 # (one [ndbd] section per data node)
hostname=172.21.6.63 # Hostname or IP address
datadir=/ysi/data/evaldb # Directory for this data node's data files

[ndbd]
#nodeid=4 # (one [ndbd] section per data node)
hostname=172.21.6.64 # Hostname or IP address
datadir=/ysi/data/evaldb # Directory for this data node's data files

[ndbd]
#nodeid=5 # (one [ndbd] section per data node)
hostname=172.21.6.65 # Hostname or IP address
datadir=/ysi/data/evaldb # Directory for this data node's data files

[mysqld]
# SQL node options:
#nodeid=6 # (one [ndbd] section per data node)
hostname=172.21.6.66 # Hostname or IP address
#datadir=/ysi/data/evaldb # Directory for this data node's data files
# (additional mysqld connections can be # specified for this node for various # purposes such as running ndb_restore)

[mysqld]
# SQL node options:
#nodeid=7 # (one [ndbd] section per data node)
#hostname=172.21.6.61 # Hostname or IP address
#datadir=/ysi/data/ysieval # Directory for this data node's data files
# (additional mysqld connections can be # specified for this node for various # purposes such as running ndb_restore)

"


-------------------------------------------------------

On management node, 172.21.6.61, start ndb_mgmd as user 'mysql"(tried "root" as well. The same result)

[/ysi/data] $ ndb_mgmd -f config.ini -v
MySQL Cluster Management Server mysql-5.5.20 ndb-7.2.5
2012-04-05 13:25:43 [MgmtSrvr] DEBUG -- Got nodeid: 1 from searching in configdir

[/ysi/data] $ ps -ef|grep ndb
mysql 12207 1 0 13:25 ? 00:00:00 ndb_mgmd -f config.ini -v



-------------------------------------------------------

On any ndb node and sql node, 172.21.6..62-66, start ndbd as user "mysql" (tried "root" as well. The same result):

On 172.21.6.62:

$ ndbd
Unable to connect with connect string: nodeid=0,172.21.6.61:1186
Retrying every 5 seconds. Attempts left: 12 11 10 9 8 7 6 5 4 3 2 1, failed.
2012-04-05 12:48:08 [ndbd] ERROR -- Could not connect to management server, error: ''


On 172.21.6.63:

$ ndbd
Unable to connect with connect string: nodeid=0,172.21.6.61:1186
Retrying every 5 seconds. Attempts left: 12 11 10 9 8 7 6 5 4 3 2 1, failed.
2012-04-05 12:48:08 [ndbd] ERROR -- Could not connect to management server, error: ''


......


On 172.21.6.66:

$ ndbd
Unable to connect with connect string: nodeid=0,172.21.6.61:1186
Retrying every 5 seconds. Attempts left: 12 11 10 9 8 7 6 5 4 3 2 1, failed.
2012-04-05 12:48:08 [ndbd] ERROR -- Could not connect to management server, error: ''
-------------------------------------------------------


Anybody came accross the same or similar issues? What and where did I do wrong or what and where to look?

Any responses are greatly appreciated.

Thank you in advance.


Jason

Viewing all articles
Browse latest Browse all 1560

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>