Closed GoogleCodeExporter closed 8 years ago
> nohup masterha_manager --conf=/etc/app1.cnf < /dev/null >
/data/log/masterha/manager.log 2>&1 &;
>
> tail -f /data/log/masterha/manager.log
> Tue Dec 27 21:39:59 2011 - [info] Reading default configuratoins from
/etc/masterha_default.cnf..
> Tue Dec 27 21:39:59 2011 - [info] Reading application default configurations
from /etc/app1.cnf..
> Tue Dec 27 21:39:59 2011 - [info] Reading server configurations from
/etc/app1.cnf..
> Tue Dec 27 21:40:33 2011 - [info] Reading default configuratoins from
/etc/masterha_default.cnf..
> Tue Dec 27 21:40:33 2011 - [info] Reading application default configurations
from /etc/app1.cnf..
> Tue Dec 27 21:40:33 2011 - [info] Reading server configurations from
/etc/app1.cnf..
This is strange. When MHA monitors master successfully, masterha_manager should
print "waiting until MySQL doesn't respond.." message in the logs. What if you
set "log_lavel=debug" in the configuration file and simply run masterha_manager
(not using nohup, not running in backgrounds)?
Original comment by Yoshinor...@gmail.com
on 27 Dec 2011 at 2:58
[deleted comment]
Sorry, log_level=debug, not log_lavel.
Original comment by Yoshinor...@gmail.com
on 28 Dec 2011 at 2:22
thanks for replay, i change the below section in my app1.cnf, it works.
[server default]
user=root
password=
manager_workdir=/var/log/masterha/app1
#manager_log=/var/log/masterha/app1/app1.log
#remote_workdir=/var/log/masterha/app1
log_level=debug
But I have a place not sure , if the masterha_manager complete the
failover, the process will be aborted?
Original comment by r...@mkrss.com
on 28 Dec 2011 at 2:29
The masterha_manager process ends after it processes failover. Currently I
recommend using daemontools to run as a daemon.
http://code.google.com/p/mysql-master-ha/wiki/Runnning_Background
Original comment by Yoshinor...@gmail.com
on 28 Dec 2011 at 2:31
Original comment by Yoshinor...@gmail.com
on 28 Dec 2011 at 2:32
Original issue reported on code.google.com by
r...@mkrss.com
on 27 Dec 2011 at 2:43