Bug #5027 mysqld reporting old cluster info for lacking Ndb.cfg
Submitted: 13 Aug 2004 9:59 Modified: 16 Aug 2004 8:29
Reporter: Arjen Lentz Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:4.1.3 OS:Any (Any)
Assigned to: Jonas Oreland CPU Architecture:Any

[13 Aug 2004 9:59] Arjen Lentz
Description:
Local configuration error
Line: 0,

This node needs information on how to connect
to the NDB Management Server.
The information can be supplied in one of the following ways:
1. Put a Ndb.cfg file in the directory where you start
   the node.
   Ex: Ndb.cfg
   | nodeid=11;host=localhost:2200

2. Use the environment variable NDB_CONNECTSTRING to
   provide this information.
   Ex:
   >export NDB_CONNECTSTRING="nodeid=11;host=localhost:2200"

Configuration error: error in retrieving contact info for mgmtsrvr

How to repeat:
Start mysqld with ndbcluster enabled, but without a Ndb.cfg

Suggested fix:
- The nodeid can be removed as it is no longer necessary
- The text talks about mgmtsrvr which should be ndb_mgmd
- Change example port number to 28000 (as in config)
[16 Aug 2004 8:29] Jonas Oreland
Suggested fix:
- The nodeid can be removed as it is no longer necessary
done

- The text talks about mgmtsrvr which should be ndb_mgmd
done