Commit 1b44fe61 authored by petr/cps@outpost.site's avatar petr/cps@outpost.site

Fix Bug #22494 Instance Manager: Inconsistent error message wording

Use better wording
parent 103e0d5e
...@@ -25,7 +25,7 @@ Success: the process has been stopped. ...@@ -25,7 +25,7 @@ Success: the process has been stopped.
-- 1.1.4. -- 1.1.4.
-------------------------------------------------------------------- --------------------------------------------------------------------
START INSTANCE mysqld3; START INSTANCE mysqld3;
ERROR HY000: Bad instance name. Check that the instance with such a name exists ERROR HY000: Unknown instance name
START INSTANCE mysqld1; START INSTANCE mysqld1;
ERROR HY000: The instance is already started ERROR HY000: The instance is already started
...@@ -33,7 +33,7 @@ ERROR HY000: The instance is already started ...@@ -33,7 +33,7 @@ ERROR HY000: The instance is already started
-- 1.1.5. -- 1.1.5.
-------------------------------------------------------------------- --------------------------------------------------------------------
STOP INSTANCE mysqld3; STOP INSTANCE mysqld3;
ERROR HY000: Bad instance name. Check that the instance with such a name exists ERROR HY000: Unknown instance name
-------------------------------------------------------------------- --------------------------------------------------------------------
-- 1.1.6. -- 1.1.6.
......
...@@ -45,7 +45,7 @@ static const char *mysqld_error_message(unsigned sql_errno) ...@@ -45,7 +45,7 @@ static const char *mysqld_error_message(unsigned sql_errno)
" corresponds to your MySQL Instance Manager version for the right" " corresponds to your MySQL Instance Manager version for the right"
" syntax to use"; " syntax to use";
case ER_BAD_INSTANCE_NAME: case ER_BAD_INSTANCE_NAME:
return "Bad instance name. Check that the instance with such a name exists"; return "Unknown instance name";
case ER_INSTANCE_IS_NOT_STARTED: case ER_INSTANCE_IS_NOT_STARTED:
return "Cannot stop instance. Perhaps the instance is not started, or was" return "Cannot stop instance. Perhaps the instance is not started, or was"
" started manually, so IM cannot find the pidfile."; " started manually, so IM cannot find the pidfile.";
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment