Percona-Lab/pacemaker-replication-agents

Monitor doesn't really work

Closed this issue · 3 comments

After issuing command
kill pidof mysqld; nc -l -p 3306 > /dev/null &
crm_mon shows me that mysql is still running. Also on a slave:
I killed mysql then pacemaker tried to start, but not successful. After I started mysql slave by hand, but it still show's me that it is not running

Maybe the #3 patch helps

Hi,
without details about your configuration, it is hard to draw
conclusions. The monitor op runs a query so the nc fake 3306 port will
not fool it. Remember also that a graceful kill is not instaneous with
MySQL (-9 is). If nc was still running, then it is normal pacemaker
failed to restart mysql since 3306 was already used. What's the logic
of using nc like that, seems pathological to me.

Regards,

Yves

Le 2013-07-12 00:51, Samat Toibazarov a écrit :

After issuing command
kill |pidof mysqld|; nc -l -p 3306 > /dev/null &
crm_mon shows me that mysql is still running. Also on a slave:
I killed mysql then pacemaker tried to start, but not successful. After
I started mysql slave by hand, but it still show's me that it is not running


Reply to this email directly or view it on GitHub
#2.

Just tried this:

kill pidof mysqld; nc -l -p 3306 > /dev/null &

and quickly, I got:

Failed actions:
p_mysql:0_start_0 (node=pacemaker-1, call=64, rc=1, status=complete): unkown error

Without more details, I'll consider this as a non-issue