MySQL Instance Manager is been deprecated in MySQL 5.1 and is removed in MySQL 5.5.
The Instance Manager stores its user information in a password
file. On Windows, the default is
mysqlmanager.passwd in the directory where
Instance Manager is installed. On Unix, the default file is
/etc/mysqlmanager.passwd. To specify a
different location for the password file, use the
If the password file does not exist or contains no password entries, you cannot connect to the Instance Manager.
Any Instance Manager process that is running to monitor server instances does not notice changes to the password file. You must stop it and restart it after making password entry changes.
Entries in the password file have the following format, where the two fields are the account user name and encrypted password, separated by a colon:
Instance Manager password encryption is the same as that used by MySQL Server. It is a one-way operation; no means are provided for decrypting encrypted passwords.
Instance Manager accounts differ somewhat from MySQL Server accounts:
MySQL Server accounts are associated with a host name, user name, and password (see Section 6.3.1, “User Names and Passwords”).
Instance Manager accounts are associated with a user name and password only.
This means that a client can connect to Instance Manager with a
given user name from any host. To limit connections so that
clients can connect only from the local host, start Instance
Manager with the
option so that it listens only to the local network interface.
Remote clients will not be able to connect. Local clients can
connect like this:
mysql -h 127.0.0.1 -P 2273
To generate a new entry, invoke Instance Manager with the
--passwd option and append
the output to the
file. Here is an example:
mysqlmanager --passwd >> /etc/mysqlmanager.passwdCreating record for new user. Enter user name:
At the prompts, enter the user name and password for the new Instance Manager user. You must enter the password twice. It does not echo to the screen, so double entry guards against entering a different password than you intend (if the two passwords do not match, no entry is generated).
The preceding command causes the following line to be added to
Use of the
fails if mysqlmanager is invoked directly
from an IBM 5250 terminal. To work around this, use a command
like the following from the command line to generate the
mysql -B --skip-column-name \
-e 'SELECT CONCAT("
The output from the command can be used an entry in the