12-06-2012 03:44 PM
I have two system cms-app-49-51 and cms-app-49-52 that I have been testing an ungraceful shutdown between systems (hard power off)
After failing over from cms-app-49-52 to cms-app-49-51 I brought cms-app-49-52 back up and cleared all error (or so I thought.)
I checked the system and everything looked to be fine all faults cleared.
[root@cms-app-49-52 ~]# hastatus -sum
-- SYSTEM STATE
-- System State Frozen
A cms-app-49-51 FAULTED 0
A cms-app-49-52 RUNNING 0
-- GROUP STATE
-- Group System Probed AutoDisabled State
B CMSApp_Cluster cms-app-49-52 Y N OFFLINE
B CMSApp_Notifier cms-app-49-52 Y N ONLINE
[root@cms-app-49-52 ~]# hagrp -display -attribute AutoDisabled
#Group Attribute System Value
CMSApp_Cluster AutoDisabled cms-app-49-51 0
CMSApp_Cluster AutoDisabled cms-app-49-52 0
CMSApp_Notifier AutoDisabled cms-app-49-51 0
CMSApp_Notifier AutoDisabled cms-app-49-52 0
However CMSApp_Cluster on cms-app-49-52 never started automatically until I "hagrp -online CMSApp_Cluster -sys cms-app-49-52"
Attached is the logfile from both systems, please look around 2012/12/06 14:58:38
Solved! Go to Solution.
12-07-2012 01:06 AM
If you down 49-51, then CMSApp_Cluster will only failover if:
There should never be a need to restart VCS after clearing any faults.
Mike
12-06-2012 04:33 PM
The engine log shows:
12-06-2012 05:08 PM
Mike
I cleared out the error. and VCS then showed eveythign was offline on 49.52 before faulting 49.51. So i guess the next questions is do i need to clear the error on 52 then restart vcs on 52 before tring to failover again?
12-07-2012 01:06 AM
If you down 49-51, then CMSApp_Cluster will only failover if:
There should never be a need to restart VCS after clearing any faults.
Mike