MySQL Bugs: #12673: Instance Manager: allows to stop the instance many times

Bug #12673	Instance Manager: allows to stop the instance many times
Submitted:	19 Aug 2005 12:38	Modified:	17 Aug 2006 10:54
Reporter:	Alexander Nozdrin	Email Updates:
Status:	Closed	Impact on me:	None
Category:	Instance Manager	Severity:	S3 (Non-critical)
Version:	5.0	OS:	Linux (Linux)
Assigned to:	Jim Winstead	CPU Architecture:	Any

Description:
The command 'STOP INSTANCE' can be applied to the already stopped instances.

How to repeat:
1. Start Instance Manager;
2. Start 'mysql' and connect to the Instance Manager;
3. Execute any command (SHOW INSTANCES, for one);
4. Wait some time (5 minutes is absolutely enough);
5. Execute the following:
mysql> SHOW INSTANCES;
+---------------+---------+
| instance_name | status  |
+---------------+---------+
| mysqld        | online  |
| mysqld2       | offline |
+---------------+---------+
2 rows in set (0.00 sec)

mysql> STOP INSTANCE mysqld;
Query OK, 0 rows affected (0.00 sec)

mysql> SHOW INSTANCES;
+---------------+---------+
| instance_name | status  |
+---------------+---------+
| mysqld        | offline |
| mysqld2       | offline |
+---------------+---------+
2 rows in set (0.00 sec)

mysql> STOP INSTANCE mysqld;
Query OK, 0 rows affected (0.00 sec)

Thank you for a bug report. I was able to get inconsistent behaviour from IM with a single instance in the latest 5.0.16-BK build:

[openxs@Fedora 5.0]$ libexec/mysqlmanager >/dev/null 2>&1 &
[1] 15888
[openxs@Fedora 5.0]$ ps -ef | grep mysql
openxs   15888 15813 99 14:23 pts/1    00:00:05 libexec/mysqlmanager
openxs   15895 15894  6 14:23 pts/1    00:00:00 /home/openxs/dbs/5.0/libexec/mysqld --no-defaults --pid-file=Fedora.pid
openxs   15906 15813  0 14:23 pts/1    00:00:00 grep mysql
[openxs@Fedora 5.0]$ netstat -a
...
unix  2      [ ACC ]     STREAM     LISTENING     61578  /tmp/mysqlmanager.sock

[openxs@Fedora 5.0]$ bin/mysql -uvk -p --socket=/tmp/mysqlmanager.sock
Enter password:
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 1 to server version: 0.2-alpha

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

mysql> show instances;
+---------------+---------+
| instance_name | status  |
+---------------+---------+
| mysqld        | offline |
+---------------+---------+
1 row in set (0,00 sec)

mysql> stop instance mysqld;
Query OK, 0 rows affected (0,00 sec)

mysql> show instances;
+---------------+---------+
| instance_name | status  |
+---------------+---------+
| mysqld        | offline |
+---------------+---------+
1 row in set (0,00 sec)

mysql> stop instance mysqld;
Query OK, 0 rows affected (0,00 sec)

mysql> show instances;
+---------------+---------+
| instance_name | status  |
+---------------+---------+
| mysqld        | offline |
+---------------+---------+
1 row in set (0,00 sec)

mysql> start instance mysqld;
Query OK, 0 rows affected (0,02 sec)
Instance started

mysql> show instances;
+---------------+---------+
| instance_name | status  |
+---------------+---------+
| mysqld        | offline |
+---------------+---------+
1 row in set (0,00 sec)

So, it looks like status is displayed/processed incorrect even in a simple case.

Stealing this bug.

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/9096

Pushed to 5.0.25

Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release.

If necessary, you can access the source repository and build the latest available version, including the bug fix. More information about accessing the source trees is available at

    http://dev.mysql.com/doc/en/installing-source.html

Documented bugfix in 5.0.25 changelog.