Hi Andrew, > They were stopped because the imagepool resource failed to stop on > SERVER1 and SERVER2 is in standby (thus unable to run resources). > So there was nowhere left to run them.
So the "cannot run anywhere" messages were related to that...got it. > The reason it was asked to stop is probably due to a bug in the old version. Hmm... I looked at the logs many times but couldn't spot that info, THANKS. I am really getting upset now coz' I cannot go back to my SP1... These clusters were semi-production systems. Isn't the latest version 2.1.3? I thought SLES10SP2 caught up on HA versions? > > and reported all 3 VMs > > being stopped but the NFSVM I migrated from the standby one was still > > running!!! > > According to who? The cluster lists it as failed (due to the failed > start action). According to xen and since it was the NFSVM which holds my home directory I noticed as it was still available. (hb_gui and crm_mon reported all 3 VMs stopped at that time) I am unsure but looking at the logs make me feel that HA didn't realise that NFSVM runs on SERVER1 after the migration and HA thought that only PRINTVM and YUPVM ran so stopped those followed by imagepool (according to my order constraints) obviously failed because the NFSVM's image was running on it. What triggered the active resource to fail and not realising that there's new resource running on it? > Please use hb_report next time... it gathers all the info needed to > figure out what went wrong. Ohh it was emergency I didn't have time to do that but I'll move the VMs off the SAN and try replicating this. I'll submit the stuff next time if it happens...(hb_report) Thanks, Ivan _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
