To start the MySQL Cluster Manager agent manually on a Windows host, you should
invoke mcmd.exe, found in the
bin directory under the manager
installation directory on that host. By default, the agent uses
etc/mcmd.ini in the MySQL Cluster Manager installation directory as its
configuration file; this can be overridden by passing the
desired file's location as the value of the
Typical options for mcmd are shown here:
mcmd[.exe] [--defaults-file | --bootstrap] [--log-file] [--log-level]
For information about additional options that can be used with mcmd on the command line or in an option file, see Section 3.1, “mcmd, the MySQL Cluster Manager Agent”.
By default, the agent assumes that the agent configuration file
etc/mcmd.ini, in the MySQL Cluster Manager installation
directory. You can tell the agent to use a different
configuration file by passing the path to this file to the
--defaults-file option, as shown
C:\Program Files (x86)\MySQL\MySQL Cluster Manager 1.1.4\bin> mcmd --defaults-file="C:\Program Files (x86)\MySQL\MySQL Cluster Manager 1.4.3\etc\mcmd.ini"
--bootstrap option causes the
agent to start with default configuration values, create a
default one-machine cluster named
and start it. The use of this option with
mcmd is shown here on a system having the
torsk, where MySQL Cluster Manager has been
installed to the default location:
C:\Program Files (x86)\MySQL\MySQL Cluster Manager 1.4.3\bin>mcmd --bootstrap MySQL Cluster Manager 1.4.3 started Connect to MySQL Cluster Manager by running "C:\Program Files (x86)\MySQL\MySQL Cluster Manager 1.4.3\bin\mcm" -a TORSK:1862 Configuring default cluster 'mycluster'... Starting default cluster 'mycluster'... Cluster 'mycluster' started successfully ndb_mgmd TORSK:1186 ndbd TORSK ndbd TORSK mysqld TORSK:3306 mysqld TORSK:3307 ndbapi * Connect to the database by running "C:\Program Files (x86)\MySQL\MySQL Cluster Manager 1.4.3\cluster\bin\mysql" -h TORSK -P 3306 -u root
You can then connect to the agent using the mcm client (see Section 3.3, “Starting the MySQL Cluster Manager Client”), and to either of the MySQL Servers running on ports 3306 and 3307 using mysql or another MySQL client application.
When starting the MySQL Cluster Manager agent for the first time, you may see one or more Windows Security Alert dialogs, such as the one shown here:
You should grant permission to connect to private networks for any of the programs mcmd.exe, ndb_mgmd.exe, ndbd.exe, ndbmtd.exe, or mysqld.exe. To do so, check the Private Networks... box and then click the button. It is generally not necessary to grant MySQL Cluster Manager or MySQL NDB Cluster access to public networks such as the Internet.
--log-file option allows you to
override the default location for the agent log file (normally
mcmd.log, in the MySQL Cluster Manager installation
You can use
--log-level option to
log-level set in the agent
See Section 3.1, “mcmd, the MySQL Cluster Manager Agent”, for more information about options that can be used with mcmd.
The MySQL Cluster Manager agent must be started on each host in the MySQL NDB Cluster to be managed.
It is possible to install MySQL Cluster Manager as a Windows service, so that it is started automatically each time Windows starts. See Section 184.108.40.206, “Installing the MySQL Cluster Manager Agent as a Windows Service”.
To stop one or more instances of the MySQL Cluster Manager agent, use the
stop agents command in the
MySQL Cluster Manager client. You can also stop an agent process using the
Windows Task Manager. In addition, if you have installed MySQL Cluster Manager
as a Windows service, you can stop (and start) the agent using
the Windows Service Manager,
CTRL-C, or the
NET STOP (or
START) command. See
Starting and stopping the MySQL Cluster Manager agent Windows service,
for more information about each of these options.