MySQL Bugs: #11331: "Warning: could not add log destination" message does not provide enough info

Bug #11331	"Warning: could not add log destination" message does not provide enough info
Submitted:	14 Jun 2005 21:54	Modified:	20 Jan 2006 14:34
Reporter:	Jonathan Miller	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S3 (Non-critical)
Version:	4.1->	OS:	Linux (Linux)
Assigned to:	Stewart Smith	CPU Architecture:	Any

Description:
Trying to setup log file parameters for the master cluster, I would recieve:

Warning: could not add log destination "FILE:filename=ndb_1_cluster.log, maxfiles=4,maxsize=134217728"

in the a ndb_1_out.log. This message does not provide enough information to allow for correction of the issue.

How to repeat:
add "FILE:filename=ndb_1_cluster.log, maxfiles=4,maxsize=134217728" to config.ini and start the cluster

Suggested fix:
Should tell the user what the issues is.

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/1008

Pushed to 4.1.18

Will appear in a 5.0 tree when people merge their csets.

at time of pushing to 4.1.18, 5.0 was at 5.0.19.

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 bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html

Additional info:

Documented in 4.1.18 and 5.1.19 changelogs.

Will this also be in 5.1.6?

Documented in changelog for 5.0.19, not 5.1.19.