MySQL Bugs: #27207: Missing parameters in [TCP] section cause ndb

Bug #27207	Missing parameters in [TCP] section cause ndb_mgmd start failure
Submitted:	16 Mar 2007 11:31	Modified:	15 May 2007 6:32
Reporter:	Oli Sennhauser	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S3 (Non-critical)
Version:	5.1.16	OS:	Any
Assigned to:	li zhou	CPU Architecture:	Any

Description:
When I start ndb_mgmd with the attached config ini. it does NOT start and returns -1.

How to repeat:
mysql@bobcat:cluster> /opt/mysql/mysql/bin/ndb_mgmd
mysql@bobcat:cluster> echo $?
255

config file and diff follows.

Suggested fix:
mgmd must be able to handle these kind of user errors...

this config works

Attachment: config.ini.works (application/octet-stream, text), 2.79 KiB.

This is wrong

[TCP DEFAULT]

[TCP]
SendBufferMemory            = 2M

This should work:

[TCP DEFAULT]

#[TCP]
SendBufferMemory            = 2M

usually ndb_mgmd prints error messages on invalid config files before terminating, e.g.:

  Error line 6: [TCP] Unknown parameter: IndexMemory
  Error line 6: Could not parse name-value pair in config file.
  Invalid configuration file: /usr/local/mysql-5.1/config.ini

here it fails silently which is indeed a bug

If I move the TCP section's at the end (which should more clrearly be commented in the docu) it works.

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/23377

ChangeSet@1.2488, 2007-03-30 09:47:11+00:00, lzhou@dev3-63.(none) +1 -0
  BUG#27207 Return correct error message when ndb_mgmd start with wrong config.ini parameter

stewart's improved patch

Attachment: bug27207.patch (text/x-patch), 1.67 KiB.

Please have a look at my patch here and see what you think.

also try a few more things with the TCP section to see if you can cause any other crashes.

Rule of [TCP] section:
1: Only 2 connections can set between data node and other nodes. 
2: NodeId1 and NodeId2 must be set if [TCP] section is set.

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/25365

ChangeSet@1.2488, 2007-04-25 14:39:16+00:00, lzhou@dev3-63.(none) +1 -0
  BUG#27207 Return correct error message when ndb_mgmd start with wrong config.ini parameter in TCP section

new patch approved.

merge into mysql-5.1-new-ndb tree

Pushed into 5.1.19-beta

Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release.

If necessary, you can access the source repository and build the latest available version, including the bug fix. More information about accessing the source trees is available at

    http://dev.mysql.com/doc/en/installing-source.html

Documented bugfix in 5.1.19 changelog.

(Already documented info about placement of [TCP] sections in config file per discussion with Oli.)