Bug #4052 Mysqld does not read Ndb.cfg from directory where mysqld is started

• Submitted: 8 Jun 2004 8:56
• Modified: 15 Jun 2004 17:07
• Reporter: Tomas Ulin
• Status: Not a Bug
• Category: MySQL Cluster: Cluster (NDB) storage engine
• Severity: S3 (Non-critical)
• Version: 4.1.3 bk clone
• OS: Any (any)
• CPU Architecture: Any

[8 Jun 2004 8:56] Tomas Ulin

Description:
When ndb table handler is initiated, cwd has changed to mysql/var, hence ndb handler will not find Ndb.cfg, if it was located in the dir where mysqld was started.

How to repeat:
start mysqld --ndbcluster (anywhere but in mysql/var) with NDB_CONNECSTRING and NDB_HOME unset with Ndb.cfg in current working directory

Suggested fix:

Workaround:
1. put Ndb.cfg in mysql/var
2. set NDB_HOME to point to Ndb.cfg directory
3. use NDB_CONNECTSTRING instead

[8 Jun 2004 9:05] Jonas Oreland

I actually don't this is a bug.
You can specify in mycnf where /var/mysql should be.
And having the Ndb.cfg there is more logical the cwd.

imho

[15 Jun 2004 17:07] Jonas Oreland

This is only a bug in the documentation.