Before starting the MySQL Cluster Manager agent, you should make any necessary
changes to the
[mcmd] section of the agent
configuration file, supplied with MySQL Cluster Manager as
etc/mcmd.ini in the installation directory.
On Linux and similar operating systems, you can edit this file in
place; on Windows, it is recommended that you save a copy of this
file to a convenient location for which the path does not contain
any spaces, such as
# character in the MySQL Cluster Manager configuration file
indicates the beginning of a comment; the comment continues to the
end of the line.
The version of this file that is supplied with MySQL Cluster Manager reads similarly to what is shown here:
[mcmd] plugins=manager ##manager-port=1862 ##agent-uuid= log-file=mcmd.log log-level=message ##pid-file= ## Username and password for manager plugin ##manager-username= ##manager-password= ## Top-level directory for manager plugins information stored on disk ##manager-directory=
Prior to MySQL Cluster Manager 1.1.1, the
[mcmd] section of
the configuration file used the heading
[mysql-proxy]. The old name is still
supported for backward compatibility, but is now deprecated and
is thus subject to removal in a future release of MySQL Cluster Manager. For
this reason, you should change any
[mysql-proxy] section headings in existing
configuration files to
[mcmd], when upgrading
to MySQL Cluster Manager 1.2.4.
A minimal agent configuration file as used in production might look like this:
[mcmd] plugins=manager manager-port=1862 manager-directory=/var/opt/mcm-1.2.4 log-file=/var/opt/mcm/mcmd.log log-level=warning
For more information about these and other options which can be set in the agent configuration file, see Section 3.1, “mcmd, the MySQL Cluster Manager Agent”.