Closed GoogleCodeExporter closed 9 years ago
Any help is greatly appreciated. Thanks. What is the expected output? What do you see instead? start of the monitor instead i receive > mmmd_mon Reading config file: 'mmm_mon.conf' $VAR1 = {}; Can't open pid file '' for writing! What version of the product are you using? On what operating system? 1.0 Please provide any additional information below. mmmd_conf #!/usr/bin/env perl # Master-Master Manager config (monitor) # # Debug mode debug no # Paths pid_path /u01/home/mysql/repmgr/var/mmmd.pid status_path /u01/home/mysql/repmgr/var/mmmd.status bin_path /u01/home/mysql/repmgr/sbin # Logging setup log mydebug file /u01/home/mysql/repmgr/var/mmm-debug.log level debug log mytraps file /u01/home/mysql/repmgr/var/mmm-traps.log level trap email xyz@xxx.com # MMMD command socket tcp-port bind_port 9988 agent_port 9989 monitor_ip 127.0.0.1 # Cluster interface cluster_interface eth0 # Cluster hosts addresses and access params host db01 ip 151.138.20.15 port 3306 user repl password repl mode master peer db02 host db02 ip 151.138.20.16 port 3306 user repl password repl mode master peer db01 # # Define roles # active_master_role writer # Mysql Reader role role reader mode balanced servers db01,db02 ip 151.138.20.35,151.138.20.36 # Mysql Writer role role writer mode exclusive servers db01,db02 ip 151.138.20.37 # # Checks parameters # # Ping checker check ping check_period 1 trap_period 5 timeout 2 # Mysql checker # (restarts after 10000 checks to prevent memory leaks) check mysql check_period 1 trap_period 2 timeout 2 restart_after 10000 # Mysql replication backlog checker # (restarts after 10000 checks to prevent memory leaks) check rep_backlog check_period 5 trap_period 10 max_backlog 60 timeout 2 restart_after 10000 # Mysql replication threads checker # (restarts after 10000 checks to prevent memory leaks) check rep_threads check_period 1 trap_period 5 timeout 2 restart_after 10000
Original issue reported on code.google.com by kuru...@gmail.com on 15 Oct 2008 at 8:48
kuru...@gmail.com
Issue was resolved on the mailing list. -> Bad named config file.
Original comment by m...@pascalhofmann.de on 26 Oct 2008 at 2:20
m...@pascalhofmann.de
Original issue reported on code.google.com by
kuru...@gmail.com
on 15 Oct 2008 at 8:48