Common Error Messages
This section provides a list of messages that you may encounter while creating and extending a LifeKeeper MySQL resource hierarchy or removing and restoring a resource. Where appropriate, it provides an additional explanation of the cause of an error and necessary action to resolve the error condition.
Messages from other LifeKeeper components are also possible.
In these cases, please refer to the Message Catalog which provides a listing of all error codes, including operational, administrative and GUI, that may be encountered while using LifeKeeper for Linux and, where appropriate, provides additional explanation of the cause of the error code and necessary action to resolve the issue. This full listing may be searched for any error code received, or you may go directly to one of the individual Message Catalogs for the appropriate LifeKeeper component.
MySQL Specific Error Messages
Note: In the Error Message column, a word in quotations and all capital letters refers to the name of a resource on the server (for example, “SERVER” might actually be a server named “Server1”).
| Error Number | Error Message |
|---|---|
| 102001 | Usage: “SCRIPT NAME” sysname dbvarname cnfpath exepath instance |
| 102002 | Usage: “SCRIPT NAME” cnfpath |
| 102003 | Usage: “SCRIPT NAME” exepath cnfpath |
| 102004 | Unable to obtain a valid value for the “socket” variable in “PATH”/my.cnf Action: There must be an entry for the “socket” in the ‘mysqld’ section of the my.cnf configuration file |
| 102005 | Unable to obtain a valid value for the “port” in “PATH”/my.cnf Action: There must be an entry for the “port” in the ‘mysqld’ section of the my.cnf configuration file |
| 102006 | Unable to obtain the data directory location “PATH” Action: Please make sure that the database is running using the socket and port specified. |
| 102007 | Must specify the absolute path to the my.cnf configuration file |
| 102008 | Must specify the absolute path to the MySQL executables |
| 102009 | The file my.cnf does not exist in the path specified |
| 102010 | The MySQL executables do not exist in the path specified |
| 102011 | LifeKeeper was unable to start the MySQL database server |
| 102012 | LifeKeeper successfully started the MySQL database server |
| 102013 | LifeKeeper was unable to stop the MySQL database server |
| 102014 | LifeKeeper successfully stopped the MySQL database server |
| 102015 | The port “PORT NUMBER” is in use on the target server “SERVER” |
| 102016 | The MySQL database server is not running on server “SERVER” |
| 102017 | Unable to open the configuration file “PATH”/my.cnf |
| 102018 | Unable to get the Data Directory information for resource “TAG” on server “SERVER” |
| 102019 | Unable to get the configuration file location information for resource “TAG” on server “SERVER” |
| 102020 | Unable to get the executable location information for resource “TAG” on server “SERVER” |
| 102021 | The argument for the configuration file path is empty |
| 102022 | The argument for the executable path is empty |
| 102023 | The path “PATH” for directive “DIRECTIVE” is not on a shared filesystem |
| 102024 | Unable to get the information for resource “TAG” on system “SYSTEM” |
| 102025 | The MySQL data directory “DATADIR” is already under LifeKeeper protection |
| 102026 | The port variables in the file /etc/my.cnf on “SERVER1” and “SERVER2” do not match |
| 102027 | The socket variables in the file /etc/my.cnf on “SERVER1” and “SERVER2” do not match |
| 102028 | The MySQL database server is not running on server “SERVER” Action: There must be a valid entry for the “user” variable in the ‘client’ section of the my.cnf configuration file |
| 102029 | Unable to obtain a valid value for the “password“ variable in “PATH”/my.cnf Action: There must be a valid entry for the “password” variable in the ‘client’ section of the my.cnf configuration file |
| 102030 | The user variables in the file /etc/my.cnf on “SERVER1” and “SERVER2” do not match |
| 102031 | The password variables in the file /etc/my.cnf on “SERVER1” and “SERVER2” do not match |
| 102032 | Unable to obtain the pid file location Action: There must be an entry for the “pid-file” variable in the ‘mysqld’ section of the my.cnf configuration file |
| 102033 | Unable to obtain a valid value for the “user” variable in “PATH”/my.cnf Action: The OS user must be specified using the “user” variable in the ‘mysqld’ section of the my.cnf configuration file |
| 102034 | WARNING: A my.cnf file exists at “PATH”, which may override the values specified in the file at “PATH”/my.cnf. |
| 102035 | The mysql system user “USER” does not exist on target server “SERVER” |
| 102036 | The mysql system user “USER” uids are different on target server “SERVER1” and template server “SERVER2” |
| 102037 | The mysql system user “USER” gids are different on target server “SERVER1” and template server “SERVER2” |
| 102038 | LifeKeeper was unable to stop the MySQL database server using a graceful shutdown. Issuing kill for pid(s): “PROCESS ID LIST”. |
| 102039 | LifeKeeper will ignore failed connection as possible max connections error, due to existence of process pid “PROCESS ID”. |
| 102040 | The mysql action for resource tag :TAG” returned: “COMMAND OUTPUT”. |
| 102041 | LifeKeeper was unable to start the MySQL database server using the defaults-file option. Retrying with individual options. |
| 102042 | The LifeKeeper “ACTION” action detected the flag “FLAG”, and will exit. |
| 102043 | END of “ACTION” action on due to a(n) “SIGNAL” signal. |
| 102044 | The file my.cnf does not exist in the stored path “PATH”. |
| 102045 | “DIRECTIVE” path “PATH” is on a shared filesystem. |
| 102046 | Starting mysqld daemon with databases from “PATH”. |
Post your comment on this topic.