Hi, today i recognized a strange Pacemaker behavior at one of my Cluster-Server. I needed to do some work on the services so i just wanted to prevent the services from migrating to the other node and switched Pacemaker into the maintenance mode:
# crm configure property maintenance-mode=true After my work was done, i switched it back with the "false" value. Now i wanted to test Pacemaker and killed one of my services. But Pacemaker didn't recognized it and migrate nothing...the service was still listed as "Running", i tried it with two other services on the node, but the same result. The service was not listed in the process-list and the initscript-status returned a false value,, so the service was really dead. It looked like Pacemaker was still in maintenance mode, but it wasn't. In the crm-config the maintenance mode was set as "false". After a restart of Pacemaker and Corosync it works fine (restart or migration of service). Now i switched back to maintenance mode again, and turned it off again. Same result...Pacemaker recognize nothing. Now my question....is this how the maintenance mode should work and i misunderstood something? ;) Or is it a bug or something else? I use the ubuntu-server 12.04 LTS version, with updated Packages. thx chris
_______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
