search

pengmingde / mysql-master-ha

Automatically exported from code.google.com/p/mysql-master-ha
0 stars 0 forks source link

master_ip_online_change Fails when called by masterha_master_switch (manual failover) 0.55 MHA manager #75

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1.execute /usr/bin/masterha_master_switch --master_state=alive 
--conf=/home/mysql/.mha_itm_prod.cnf --new_master_host=lsitm304d
2.
3. Additionally, I get the following problem when trying to set the mandatory 
parameter --dead_master_host=lsitm303d  in the script masterha_master_switch, 
says it is an unknown option, see below: 

[mysql@VM:lsmql300a ~]$ /usr/bin/masterha_master_switch --master_state=alive 
--conf=/home/mysql/.mha_itm_prod.cnf --dead_master_host=lsitm303d 
--new_master_host=lsitm304d 
Unknown options: --dead_master_host=lsitm303d

What is the expected output? What do you see instead?

Manual Failover happens as expected.

The following errors when running the script:

Wed Feb 12 01:18:22 2014 521607 Set read_only on the new master.. ok. 
 Wed Feb 12 01:18:22 2014 526489 Drpping app user on the orig master.. 
Got Error: Undefined subroutine &main::FIXME_xxx_drop_app_user called at 
/home/mysql/MHA/scripts/master_ip_online_change line 148. 

 Wed Feb 12 01:18:22 2014 - [error][/usr/lib/perl5/vendor_perl/MHA/ManagerUtil.pm, ln178] Got ERROR:  at /usr/bin/masterha_master_switch line 53

What version of the product are you using? On what operating system?

RHEL 5.8 and MySQL Enterprise Edition 5.5.25a
mha4mysql-manager-0.55-1.el5.noarch.rpm 
mha4mysql-node-0.54-1.el5.noarch.rpm 
mha4mysql-manager-0.55.tar.gz (only un-compressed for 2 sample scripts we 
needed which were not included in manager RPM these were 
master_ip_online_change and send_report scripts)

Please provide any additional information below.

I have just setup MHA, but we want to do manual failover only (not automated), 
we do not want to run masterha_manager. I have check masterha_manager running 
and it runs OK no error, but we do not want to run automated failover. When 
performing masterha_check_repl everything is fine, see below: 

 [mysql@VM:lsmql300a ~]$ /usr/bin/masterha_check_repl --conf=/home/mysql/.mha_itm_prod.cnf 
 Wed Feb 12 00:04:53 2014 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping. 
 Wed Feb 12 00:04:53 2014 - [info] Reading application default configurations from /home/mysql/.mha_itm_prod.cnf.. 
 Wed Feb 12 00:04:53 2014 - [info] Reading server configurations from /home/mysql/.mha_itm_prod.cnf.. 
 Wed Feb 12 00:04:53 2014 - [info] MHA::MasterMonitor version 0.55. 
 Wed Feb 12 00:04:53 2014 - [debug] Connecting to servers.. 
 Wed Feb 12 00:04:53 2014 - [debug]  Connected to: lsitm303d(10.132.60.168:3306), user=radmin 
 Wed Feb 12 00:04:53 2014 - [debug]  Connected to: lsitm304d(10.132.60.167:3306), user=radmin 
 Wed Feb 12 00:04:53 2014 - [debug]  Connected to: lcitm308d(10.12.60.190:3306), user=radmin 
 Wed Feb 12 00:04:54 2014 - [debug]  Connected to: lcitm309d(10.12.60.189:3306), user=radmin 
 Wed Feb 12 00:04:54 2014 - [debug]  Comparing MySQL versions.. 
 Wed Feb 12 00:04:54 2014 - [debug]   Comparing MySQL versions done. 
 Wed Feb 12 00:04:54 2014 - [debug] Connecting to servers done. 
 Wed Feb 12 00:04:54 2014 - [info] Multi-master configuration is detected. Current primary(writable) master is lsitm303d(10.132.60.168:3306) 
 Wed Feb 12 00:04:54 2014 - [info] Master configurations are as below: 
 Master lsitm304d(10.132.60.167:3306), replicating from 10.132.60.168(10.132.60.168:3306), read-only 
 Master lsitm303d(10.132.60.168:3306), replicating from 10.132.60.167(10.132.60.167:3306) 

 Wed Feb 12 00:04:54 2014 - [info] Dead Servers: 
 Wed Feb 12 00:04:54 2014 - [info] Alive Servers: 
 Wed Feb 12 00:04:54 2014 - [info]   lsitm303d(10.132.60.168:3306) 
 Wed Feb 12 00:04:54 2014 - [info]   lsitm304d(10.132.60.167:3306) 
 Wed Feb 12 00:04:54 2014 - [info]   lcitm308d(10.12.60.190:3306) 
 Wed Feb 12 00:04:54 2014 - [info]   lcitm309d(10.12.60.189:3306) 
 Wed Feb 12 00:04:54 2014 - [info] Alive Slaves: 
 Wed Feb 12 00:04:54 2014 - [info]   lsitm304d(10.132.60.167:3306)  Version=5.5.25a-enterprise-commercial-advanced-log (oldest major version between slaves) log-bin:enabled 
 Wed Feb 12 00:04:54 2014 - [debug]    Relay log info repository: FILE 
 Wed Feb 12 00:04:54 2014 - [info]     Replicating from 10.132.60.168(10.132.60.168:3306) 
 Wed Feb 12 00:04:54 2014 - [info]     Primary candidate for the new Master (candidate_master is set) 
 Wed Feb 12 00:04:54 2014 - [info]   lcitm308d(10.12.60.190:3306)  Version=5.5.25a-enterprise-commercial-advanced-log (oldest major version between slaves) log-bin:enabled 
 Wed Feb 12 00:04:54 2014 - [debug]    Relay log info repository: FILE 
 Wed Feb 12 00:04:54 2014 - [info]     Replicating from 10.132.60.168(10.132.60.168:3306) 
 Wed Feb 12 00:04:54 2014 - [info]     Primary candidate for the new Master (candidate_master is set) 
 Wed Feb 12 00:04:54 2014 - [info]   lcitm309d(10.12.60.189:3306)  Version=5.5.25a-enterprise-commercial-advanced-log (oldest major version between slaves) log-bin:enabled 
 Wed Feb 12 00:04:54 2014 - [debug]    Relay log info repository: FILE 
 Wed Feb 12 00:04:54 2014 - [info]     Replicating from 10.132.60.168(10.132.60.168:3306) 
 Wed Feb 12 00:04:54 2014 - [info]     Primary candidate for the new Master (candidate_master is set) 
 Wed Feb 12 00:04:54 2014 - [info] Current Alive Master: lsitm303d(10.132.60.168:3306) 
 Wed Feb 12 00:04:54 2014 - [info] Checking slave configurations.. 
 Wed Feb 12 00:04:54 2014 - [warning]  relay_log_purge=0 is not set on slave lsitm304d(10.132.60.167:3306). 
 Wed Feb 12 00:04:54 2014 - [info] Starting SSH connection tests.. 
 Wed Feb 12 00:04:55 2014 - [debug] 
 Wed Feb 12 00:04:54 2014 - [debug]  Connecting via SSH from mysql@lsitm303d(10.132.60.168:22) to mysql@lsitm304d(10.132.60.167:22).. 
 Wed Feb 12 00:04:54 2014 - [debug]   ok. 
 Wed Feb 12 00:04:54 2014 - [debug]  Connecting via SSH from mysql@lsitm303d(10.132.60.168:22) to mysql@lcitm308d(10.12.60.190:22).. 
 Wed Feb 12 00:04:54 2014 - [debug]   ok. 
 Wed Feb 12 00:04:54 2014 - [debug]  Connecting via SSH from mysql@lsitm303d(10.132.60.168:22) to mysql@lcitm309d(10.12.60.189:22).. 
 Wed Feb 12 00:04:55 2014 - [debug]   ok. 
 Wed Feb 12 00:04:55 2014 - [debug] 
 Wed Feb 12 00:04:54 2014 - [debug]  Connecting via SSH from mysql@lsitm304d(10.132.60.167:22) to mysql@lsitm303d(10.132.60.168:22).. 
 Wed Feb 12 00:04:54 2014 - [debug]   ok. 
 Wed Feb 12 00:04:54 2014 - [debug]  Connecting via SSH from mysql@lsitm304d(10.132.60.167:22) to mysql@lcitm308d(10.12.60.190:22).. 
 Wed Feb 12 00:04:55 2014 - [debug]   ok. 
 Wed Feb 12 00:04:55 2014 - [debug]  Connecting via SSH from mysql@lsitm304d(10.132.60.167:22) to mysql@lcitm309d(10.12.60.189:22).. 
 Wed Feb 12 00:04:55 2014 - [debug]   ok. 
 Wed Feb 12 00:04:56 2014 - [debug] 
 Wed Feb 12 00:04:55 2014 - [debug]  Connecting via SSH from mysql@lcitm308d(10.12.60.190:22) to mysql@lsitm303d(10.132.60.168:22).. 
 Wed Feb 12 00:04:55 2014 - [debug]   ok. 
 Wed Feb 12 00:04:55 2014 - [debug]  Connecting via SSH from mysql@lcitm308d(10.12.60.190:22) to mysql@lsitm304d(10.132.60.167:22).. 
 Wed Feb 12 00:04:56 2014 - [debug]   ok. 
 Wed Feb 12 00:04:56 2014 - [debug]  Connecting via SSH from mysql@lcitm308d(10.12.60.190:22) to mysql@lcitm309d(10.12.60.189:22).. 
 Wed Feb 12 00:04:56 2014 - [debug]   ok. 
 Wed Feb 12 00:04:57 2014 - [debug] 
 Wed Feb 12 00:04:55 2014 - [debug]  Connecting via SSH from mysql@lcitm309d(10.12.60.189:22) to mysql@lsitm303d(10.132.60.168:22).. 
 Wed Feb 12 00:04:56 2014 - [debug]   ok. 
 Wed Feb 12 00:04:56 2014 - [debug]  Connecting via SSH from mysql@lcitm309d(10.12.60.189:22) to mysql@lsitm304d(10.132.60.167:22).. 
 Wed Feb 12 00:04:56 2014 - [debug]   ok. 
 Wed Feb 12 00:04:56 2014 - [debug]  Connecting via SSH from mysql@lcitm309d(10.12.60.189:22) to mysql@lcitm308d(10.12.60.190:22).. 
 Wed Feb 12 00:04:57 2014 - [debug]   ok. 
 Wed Feb 12 00:04:57 2014 - [info] All SSH connection tests passed successfully. 
 Wed Feb 12 00:04:57 2014 - [info] Checking MHA Node version.. 
 Wed Feb 12 00:04:57 2014 - [info]  Version check ok. 
 Wed Feb 12 00:04:57 2014 - [info] Checking SSH publickey authentication settings on the current master.. 
 Wed Feb 12 00:04:57 2014 - [debug] SSH connection test to lsitm303d, option -o StrictHostKeyChecking=no -o PasswordAuthentication=no -o BatchMode=yes -o ConnectTimeout=5, timeout 5 
 Wed Feb 12 00:04:58 2014 - [info] HealthCheck: SSH to lsitm303d is reachable. 
 Wed Feb 12 00:04:58 2014 - [info] Master MHA Node version is 0.54. 
 Wed Feb 12 00:04:58 2014 - [info] Checking recovery script configurations on the current master.. 
 Wed Feb 12 00:04:58 2014 - [info]   Executing command: save_binary_logs --command=test --start_pos=4 --binlog_dir=/mydb/itm01/binlogs --output_file=/home/mysql/MHA/log/save_binary_logs_test --manager_version=0.55 --start_file=mysql-bin.000009 --debug 
 Wed Feb 12 00:04:58 2014 - [info]   Connecting to mysql@lsitm303d(lsitm303d).. 
  Creating /home/mysql/MHA/log if not exists..    ok. 
  Checking output directory is accessible or not.. 
   ok. 
  Binlog found at /mydb/itm01/binlogs, up to mysql-bin.000009 
 Wed Feb 12 00:04:58 2014 - [info] Master setting check done. 
 Wed Feb 12 00:04:58 2014 - [info] Checking SSH publickey authentication and checking recovery script configurations on all alive slave servers.. 
 Wed Feb 12 00:04:58 2014 - [info]   Executing command : apply_diff_relay_logs --command=test --slave_user='radmin' --slave_host=lsitm304d --slave_ip=10.132.60.167 --slave_port=3306 --workdir=/home/mysql/MHA/log --target_version=5.5.25a-enterprise-commercial-advanced-log --manager_version=0.55 --relay_log_info=/mydb/itm04/data/relay-log.info  --relay_dir=/mydb/itm04/data/  --debug  --slave_pass=xxx 
 Wed Feb 12 00:04:58 2014 - [info]   Connecting to mysql@10.132.60.167(lsitm304d:22).. 
  Checking slave recovery environment settings.. 
    Opening /mydb/itm04/data/relay-log.info ... ok. 
    Relay log found at /mydb/itm04/admin/relay, up to mysql-relay-bin.000002 
    Temporary relay log file is /mydb/itm04/admin/relay/mysql-relay-bin.000002 
    Testing mysql connection and privileges.. done. 
    Testing mysqlbinlog output.. done. 
    Cleaning up test file(s).. done. 
 Wed Feb 12 00:04:58 2014 - [info]   Executing command : apply_diff_relay_logs --command=test --slave_user='radmin' --slave_host=lcitm308d --slave_ip=10.12.60.190 --slave_port=3306 --workdir=/home/mysql/MHA/log --target_version=5.5.25a-enterprise-commercial-advanced-log --manager_version=0.55 --relay_log_info=/mydb/itm07/data/relay-log.info  --relay_dir=/mydb/itm07/data/  --debug  --slave_pass=xxx 
 Wed Feb 12 00:04:58 2014 - [info]   Connecting to mysql@10.12.60.190(lcitm308d:22).. 
  Checking slave recovery environment settings.. 
    Opening /mydb/itm07/data/relay-log.info ... ok. 
    Relay log found at /mydb/itm07/admin/relay, up to mysql-relay-bin.000002 
    Temporary relay log file is /mydb/itm07/admin/relay/mysql-relay-bin.000002 
    Testing mysql connection and privileges.. done. 
    Testing mysqlbinlog output.. done. 
    Cleaning up test file(s).. done. 
 Wed Feb 12 00:04:59 2014 - [info]   Executing command : apply_diff_relay_logs --command=test --slave_user='radmin' --slave_host=lcitm309d --slave_ip=10.12.60.189 --slave_port=3306 --workdir=/home/mysql/MHA/log --target_version=5.5.25a-enterprise-commercial-advanced-log --manager_version=0.55 --relay_log_info=/mydb/itm10/data/relay-log.info  --relay_dir=/mydb/itm10/data/  --debug  --slave_pass=xxx 
 Wed Feb 12 00:04:59 2014 - [info]   Connecting to mysql@10.12.60.189(lcitm309d:22).. 
  Checking slave recovery environment settings.. 
    Opening /mydb/itm10/data/relay-log.info ... ok. 
    Relay log found at /mydb/itm10/admin/relay, up to mysql-relay-bin.000002 
    Temporary relay log file is /mydb/itm10/admin/relay/mysql-relay-bin.000002 
    Testing mysql connection and privileges.. done. 
    Testing mysqlbinlog output.. done. 
    Cleaning up test file(s).. done. 
 Wed Feb 12 00:04:59 2014 - [info] Slaves settings check done. 
 Wed Feb 12 00:04:59 2014 - [info] 
 lsitm303d (current master) 
 +--lsitm304d 
 +--lcitm308d 
 +--lcitm309d 

 Wed Feb 12 00:04:59 2014 - [info] Checking replication health on lsitm304d.. 
 Wed Feb 12 00:04:59 2014 - [info]  ok. 
 Wed Feb 12 00:04:59 2014 - [info] Checking replication health on lcitm308d.. 
 Wed Feb 12 00:04:59 2014 - [info]  ok. 
 Wed Feb 12 00:04:59 2014 - [info] Checking replication health on lcitm309d.. 
 Wed Feb 12 00:04:59 2014 - [info]  ok. 
 Wed Feb 12 00:04:59 2014 - [warning] master_ip_failover_script is not defined. 
 Wed Feb 12 00:04:59 2014 - [warning] shutdown_script is not defined. 
 Wed Feb 12 00:04:59 2014 - [debug]  Disconnected from lsitm303d(10.132.60.168:3306) 
 Wed Feb 12 00:04:59 2014 - [debug]  Disconnected from lsitm304d(10.132.60.167:3306) 
 Wed Feb 12 00:04:59 2014 - [debug]  Disconnected from lcitm308d(10.12.60.190:3306) 
 Wed Feb 12 00:04:59 2014 - [debug]  Disconnected from lcitm309d(10.12.60.189:3306) 
 Wed Feb 12 00:04:59 2014 - [info] Got exit code 0 (Not master dead). 

 MySQL Replication Health is OK. 

But when I attempt to perform manual failover with masterha_master_switch it 
fails when master_ip_online_change is setup in my configuration file, which, I 
have been told is required for manual failover, it seems that there is a bug 
below in either the master_ip_online_change and associate helper perl module 
ManagerUtil.pm, as show below:

[mysql@VM:lsmql300a scripts]$ /usr/bin/masterha_master_switch 
--master_state=alive --conf=/home/mysql/.mha_itm_prod.cnf 
--new_master_host=lsitm304d 
 Wed Feb 12 01:18:15 2014 - [info] MHA::MasterRotate version 0.55. 
 Wed Feb 12 01:18:15 2014 - [info] Starting online master switch.. 
 Wed Feb 12 01:18:15 2014 - [info] 
 Wed Feb 12 01:18:15 2014 - [info] * Phase 1: Configuration Check Phase.. 
 Wed Feb 12 01:18:15 2014 - [info] 
 Wed Feb 12 01:18:15 2014 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping. 
 Wed Feb 12 01:18:15 2014 - [info] Reading application default configurations from /home/mysql/.mha_itm_prod.cnf.. 
 Wed Feb 12 01:18:15 2014 - [info] Reading server configurations from /home/mysql/.mha_itm_prod.cnf.. 
 Wed Feb 12 01:18:15 2014 - [debug] Connecting to servers.. 
 Wed Feb 12 01:18:16 2014 - [debug]  Connected to: lsitm303d(10.132.60.168:3306), user=radmin 
 Wed Feb 12 01:18:16 2014 - [debug]  Connected to: lsitm304d(10.132.60.167:3306), user=radmin 
 Wed Feb 12 01:18:16 2014 - [debug]  Connected to: lcitm308d(10.12.60.190:3306), user=radmin 
 Wed Feb 12 01:18:16 2014 - [debug]  Connected to: lcitm309d(10.12.60.189:3306), user=radmin 
 Wed Feb 12 01:18:16 2014 - [debug]  Comparing MySQL versions.. 
 Wed Feb 12 01:18:16 2014 - [debug]   Comparing MySQL versions done. 
 Wed Feb 12 01:18:16 2014 - [debug] Connecting to servers done. 
 Wed Feb 12 01:18:16 2014 - [info] Multi-master configuration is detected. Current primary(writable) master is lsitm303d(10.132.60.168:3306) 
 Wed Feb 12 01:18:16 2014 - [info] Master configurations are as below: 
 Master lsitm304d(10.132.60.167:3306), replicating from 10.132.60.168(10.132.60.168:3306), read-only 
 Master lsitm303d(10.132.60.168:3306), replicating from 10.132.60.167(10.132.60.167:3306) 

 Wed Feb 12 01:18:16 2014 - [info] Current Alive Master: lsitm303d(10.132.60.168:3306) 
 Wed Feb 12 01:18:16 2014 - [info] Alive Slaves: 
 Wed Feb 12 01:18:16 2014 - [info]   lsitm304d(10.132.60.167:3306)  Version=5.5.25a-enterprise-commercial-advanced-log (oldest major version between slaves) log-bin:enabled 
 Wed Feb 12 01:18:16 2014 - [debug]    Relay log info repository: FILE 
 Wed Feb 12 01:18:16 2014 - [info]     Replicating from 10.132.60.168(10.132.60.168:3306) 
 Wed Feb 12 01:18:16 2014 - [info]     Primary candidate for the new Master (candidate_master is set) 
 Wed Feb 12 01:18:16 2014 - [info]   lcitm308d(10.12.60.190:3306)  Version=5.5.25a-enterprise-commercial-advanced-log (oldest major version between slaves) log-bin:enabled 
 Wed Feb 12 01:18:16 2014 - [debug]    Relay log info repository: FILE 
 Wed Feb 12 01:18:16 2014 - [info]     Replicating from 10.132.60.168(10.132.60.168:3306) 
 Wed Feb 12 01:18:16 2014 - [info]     Primary candidate for the new Master (candidate_master is set) 
 Wed Feb 12 01:18:16 2014 - [info]   lcitm309d(10.12.60.189:3306)  Version=5.5.25a-enterprise-commercial-advanced-log (oldest major version between slaves) log-bin:enabled 
 Wed Feb 12 01:18:16 2014 - [debug]    Relay log info repository: FILE 
 Wed Feb 12 01:18:16 2014 - [info]     Replicating from 10.132.60.168(10.132.60.168:3306) 
 Wed Feb 12 01:18:16 2014 - [info]     Primary candidate for the new Master (candidate_master is set) 

 It is better to execute FLUSH NO_WRITE_TO_BINLOG TABLES on the master before switching. Is it ok to execute on lsitm303d(10.132.60.168:3306)? (YES/no): YES 
 Wed Feb 12 01:18:19 2014 - [info] Executing FLUSH NO_WRITE_TO_BINLOG TABLES. This may take long time.. 
 Wed Feb 12 01:18:19 2014 - [info]  ok. 
 Wed Feb 12 01:18:19 2014 - [info] Checking MHA is not monitoring or doing failover.. 
 Wed Feb 12 01:18:19 2014 - [info] Checking replication health on lsitm304d.. 
 Wed Feb 12 01:18:19 2014 - [info]  ok. 
 Wed Feb 12 01:18:19 2014 - [info] Checking replication health on lcitm308d.. 
 Wed Feb 12 01:18:19 2014 - [info]  ok. 
 Wed Feb 12 01:18:19 2014 - [info] Checking replication health on lcitm309d.. 
 Wed Feb 12 01:18:19 2014 - [info]  ok. 
 Wed Feb 12 01:18:19 2014 - [info] lsitm304d can be new master. 
 Wed Feb 12 01:18:19 2014 - [info] 
 From: 
 lsitm303d (current master) 
 +--lsitm304d 
 +--lcitm308d 
 +--lcitm309d 

 To: 
 lsitm304d (new master) 
 +--lcitm308d 
 +--lcitm309d 

 Starting master switch from lsitm303d(10.132.60.168:3306) to lsitm304d(10.132.60.167:3306)? (yes/NO): yes 
 Wed Feb 12 01:18:22 2014 - [info] Checking whether lsitm304d(10.132.60.167:3306) is ok for the new master.. 
 Wed Feb 12 01:18:22 2014 - [info]  ok. 
 Wed Feb 12 01:18:22 2014 - [info] ** Phase 1: Configuration Check Phase completed. 
 Wed Feb 12 01:18:22 2014 - [info] 
 Wed Feb 12 01:18:22 2014 - [debug]  Disconnected from lsitm303d(10.132.60.168:3306) 
 Wed Feb 12 01:18:22 2014 - [info] * Phase 2: Rejecting updates Phase.. 
 Wed Feb 12 01:18:22 2014 - [info] 
 Wed Feb 12 01:18:22 2014 - [info] Executing master ip online change script to disable write on the current master: 
 Wed Feb 12 01:18:22 2014 - [info]   /home/mysql/MHA/scripts/master_ip_online_change --command=stop --orig_master_host=lsitm303d --orig_master_ip=10.132.60.168 --orig_master_port=3306 --orig_master_user='radmin' --orig_master_password='radmin-pw' --new_master_host=lsitm304d --new_master_ip=10.132.60.167 --new_master_port=3306 --new_master_user='radmin' --new_master_password='XXXXXXX' 
 Wed Feb 12 01:18:22 2014 521607 Set read_only on the new master.. ok. 
 Wed Feb 12 01:18:22 2014 526489 Drpping app user on the orig master.. 
 Got Error: Undefined subroutine &main::FIXME_xxx_drop_app_user called at /home/mysql/MHA/scripts/master_ip_online_change line 148. 

 Wed Feb 12 01:18:22 2014 - [error][/usr/lib/perl5/vendor_perl/MHA/ManagerUtil.pm, ln178] Got ERROR:  at /usr/bin/masterha_master_switch line 53 
 Wed Feb 12 01:18:22 2014 - [debug]  Already disconnected from lsitm303d(10.132.60.168:3306) 
 Wed Feb 12 01:18:22 2014 - [debug]  Disconnected from lsitm304d(10.132.60.167:3306) 
 Wed Feb 12 01:18:22 2014 - [debug]  Disconnected from lcitm308d(10.12.60.190:3306) 
 Wed Feb 12 01:18:22 2014 - [debug]  Disconnected from lcitm309d(10.12.60.189:3306) 
 [mysql@VM:lsmql300a scripts]$ 

Please any help on your end is appreciated, we are basically dead in the water 
on a failover solution, and we cannot upgrade to 5.6, because the vendor we are 
using for the application will not support it for another year.

--James Adams

Original issue reported on code.google.com by jbenjami...@gmail.com on 12 Feb 2014 at 9:01

GoogleCodeExporter commented 9 years ago 
Additionally, I am running this application as the user mysql, standard user 
with no special privileges.  I am not sure if that could be an issue related to 
this problem.

Original comment by jbenjami...@gmail.com on 12 Feb 2014 at 11:24