Bad/ Wrong behaviour of mmmd_mon when status-file is missing

[GoogleCodeExporter]

What steps will reproduce the problem?

1. Stop mmmd_mon
2. Delete mmmd.status file
3. Start mmmd_mon -> all hosts will go into state HARD_OFFLINE. This will
not change(!) until you ...
4. ... restart mmmd_mon -> all hosts will switch from HARD_OFFLINE to
AWAITING_RECOVERY. Very strange.

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

Perfect behavior would be, to ask agents for thier current status on
startup and recover the status information on this way.

Original issue reported on code.google.com by m...@pascalhofmann.de on 4 Nov 2008 at 9:21

[GoogleCodeExporter]

This are two bugs. The first is fixed in r137. For the second see Issue 22.

Original comment by m...@pascalhofmann.de on 4 Nov 2008 at 6:41

• Changed state: Fixed