MySQL Bugs: #11565: Not possible to trace config changes by customer

Bug #11565	Not possible to trace config changes by customer
Submitted:	25 Jun 2005 11:23	Modified:	13 Aug 2007 21:40
Reporter:	Mikael Ronström	Email Updates:
Status:	Won't fix	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S4 (Feature request)
Version:		OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
To get around another bug, the customer made several attempts in changing the config file
and restarting. In order to detect faulty config changes it is necessary to log what configuration
is used in the node and preferrably also which management node that sent this configuration
file.

To be able to trace this, it is necessary to be able to get this information even after a graceful
shutdown of a node since it is necessary in a system or node restart to be able to compare
with previous config used when running the node.

How to repeat:
Not a repeatable bug in that sense. More that it is not possible to find errors made by
customers in changing the config files

Suggested fix:
Add info to error.log at start-up of the node or possibly a new file that only contains a
config file description for the started instance, similar to trace.log.1 possibly a
config.log.1

I couldn't reproduce this bug with the provided information.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

This bug is not scheduled to be fixed at this time.