Specifying incorrect node name causes mmm_control to think Daemon is not running.

What steps will reproduce the problem?
1. Issue the command "mmm_control set_online <typo'd servername here>"
2. Issue the "mmm_control show" command
3. See the error: "WARNING!!! DAEMON IS NOT RUNNING. INFORMATION MAY NOT BE
ACTUAL!!!"
4. A ps shows that mmmd_mon is still running.
5. Only way I have found to resolve is to restart the mmmd_mon agent.

What is the expected output? What do you see instead?
I would expect the control to produce an error that the node/server name
specified is not valid and not continue.

What version of the product are you using? On what operating system?
Version 1.0 on CentOS 5.2

Please provide any additional information below.
Copy of actual problem:

[root@www1 ~]# mmm_control show
Config file: mmm_mon.conf
Daemon is running!
Servers status:
  lbdb1(10.100.254.153): master/ADMIN_OFFLINE. Roles: None
  lbdb2(10.100.254.152): master/ONLINE. Roles: reader(10.100.254.120;),
reader(10.100.254.121;), writer(10.100.254.122;)

[root@www1 ~]# mmm_control set_online lbdb00
Config file: mmm_mon.conf
Daemon is running!
Command sent to monitoring host. Result: 

[root@www1 ~]# mmm_control show
Config file: mmm_mon.conf

WARNING!!! DAEMON IS NOT RUNNING. INFORMATION MAY NOT BE ACTUAL!!!

Servers status:
  lbdb1(10.100.254.153): master/ADMIN_OFFLINE. Roles: None
  lbdb2(10.100.254.152): master/ONLINE. Roles: reader(10.100.254.120;),
reader(10.100.254.121;), writer(10.100.254.122;)

[root@www1 var]# ps -ef|grep mmm
root     10977     1  2 07:38 ?        00:08:50 perl
/usr/local/mmm/sbin/mmmd_mon
root     32713 32613  0 13:33 pts/0    00:00:00 grep mmm

[root@www1 var]# service mmm_mon restart
Daemon bin: '/usr/local/mmm/sbin/mmmd_mon'
Daemon pid: '/usr/local/mmm/var/mmmd.pid'
Daemon bin: '/usr/local/mmm/sbin/mmmd_mon'
Daemon pid: '/usr/local/mmm/var/mmmd.pid'
Shutting down MMM Monitor daemon: Ok
Waiting 10 sec before restart...Ok
Daemon bin: '/usr/local/mmm/sbin/mmmd_mon'
Daemon pid: '/usr/local/mmm/var/mmmd.pid'
Starting MMM Monitor daemon: Reading config file: 'mmm_mon.conf'
$VAR1 = {
          'lbdb1' => {
                       'roles' => [],
                       'version' => '0',
                       'state' => 'ADMIN_OFFLINE'
                     },
          'lbdb2' => {
                       'roles' => [
                                    'reader(10.100.254.120;)',
                                    'reader(10.100.254.121;)',
                                    'writer(10.100.254.122;)'
                                  ],
                       'version' => '0',
                       'state' => 'ONLINE'
                     }
        };
Role: 'reader(10.100.254.120;)'
Adding role: 'reader' with ip '10.100.254.120'
Role: 'reader(10.100.254.121;)'
Adding role: 'reader' with ip '10.100.254.121'
Role: 'writer(10.100.254.122;)'
Adding role: 'writer' with ip '10.100.254.122'
Ok

[root@www1 var]# ps -ef|grep mmm
root     32736     1 12 13:34 ?        00:00:00 perl
/usr/local/mmm/sbin/mmmd_mon
root     32742 32736 11 13:34 ?        00:00:00 perl
/usr/local/mmm/bin/check/checker rep_backlog
root     32743 32736  8 13:34 ?        00:00:00 perl
/usr/local/mmm/bin/check/checker mysql
root     32744 32736  4 13:34 ?        00:00:00 perl
/usr/local/mmm/bin/check/checker ping
root     32745 32736  9 13:34 ?        00:00:00 perl
/usr/local/mmm/bin/check/checker rep_threads
root     32749 32613  0 13:34 pts/0    00:00:00 grep mmm

[root@www1 var]# mmm_control show
Config file: mmm_mon.conf
Daemon is running!
Servers status:
  lbdb1(10.100.254.153): master/ADMIN_OFFLINE. Roles: None
  lbdb2(10.100.254.152): master/ONLINE. Roles: reader(10.100.254.120;),
reader(10.100.254.121;), writer(10.100.254.122;)

[root@www1 var]# mmm_control set_online lbdb1
Config file: mmm_mon.conf
Daemon is running!
Command sent to monitoring host. Result: OK: State of 'lbdb1' changed to
ONLINE. Now you can wait some time and check its new roles!

[root@www1 var]# mmm_control show
Config file: mmm_mon.conf
Daemon is running!
Servers status:
  lbdb1(10.100.254.153): master/ONLINE. Roles: reader(10.100.254.120;)
  lbdb2(10.100.254.152): master/ONLINE. Roles: reader(10.100.254.121;),
writer(10.100.254.122;)
Original issue reported on code.google.com by asb.b...@gmail.com on 11 Oct 2008 at 1:59
chusiang / mysql-master-master

Specifying incorrect node name causes mmm_control to think Daemon is not running. #16
