Hi, I know this is an FAQ, but I have a situation where the normal method (bind monitoring templates directly to the server the app lives on) doesn't work.
Say I have two servers, with a DRBD replicated volume. MySQL runs on one, and the other monitors it with heartbeat. Should the first fail, the IP used for MySQL moves along with daemon. I can't add MySQL monitoring using the virtual IP, because Zenoss detects it already exists on server #1. If I monitor MySQL directly on server #1 and for some reason (purposeful or otherwise) MySQL is suddenly running on server #2, then... fail. Suggestions? -Charlie _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
