enterprise-support team mailing list archive

[Matthew B <1361851@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

I created a 1M/2S setup with make_replication_sandbox. I'm testing out
MHA and so I did a kill -9 on the master's Pid and safe_mysqld pid.

I then did ~/sandboxes/status_all
This, incorrectly, reported that all 3 nodes were running:

[c_mboehm@test-db3 sandboxes]$ ./status_all
REPLICATION rsandbox_5_5_38
master on
node1 on
node2 on

I did a stop_all to shutdown the slaves and then did start_all to bring
them back up and got this:

[c_mboehm@test-db3 sandboxes]$ ./start_all
executing "start" on master
sandbox server already started (found pid file /home/c_mboehm/sandboxes/rsandbox_5_5_38/master/data/mysql_sandbox24193.pid)
 sandbox server started
executing "start" on slave 1
.. sandbox server started
executing "start" on slave 2
. sandbox server started

[c_mboehm@test-db3 sandboxes]$ cat /home/c_mboehm/sandboxes/rsandbox_5_5_38/master/data/mysql_sandbox24193.pid
29683

[c_mboehm@test-db3 sandboxes]$ ps -Af |grep 29683
c_mboehm 23778 10338  0 19:47 pts/0    00:00:00 grep 29683
[c_mboehm@test-db3 sandboxes]$

So seems the status scripts are just checking for the existence of a pid
file and not actually checking if that pid exists, or even better would
be that a connection to that mysql instance can be ping'd (SELECT 1
etc).

** Affects: mysql-sandbox
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server/Client Support Team, which is subscribed to MySQL.
Matching subscriptions: Ubuntu Server/Client Support Team
https://bugs.launchpad.net/bugs/1361851

Title:
  start/stop/status scripts don't actually check if running

To manage notifications about this bug go to:
https://bugs.launchpad.net/mysql-sandbox/+bug/1361851/+subscriptions