Originally posted by: rakeshsinnya

Is it possible to find the reason for failed RG movement in power ha 5.5 with following logs:

****************************************************************************************************************************
"Mar 8 11:07:59 AMSDC1 user:notice HACMP for AIX: EVENT START: event_error 255 TE_RG_MOVE"

Mar 8 11:13:22 AMSDC1 user:notice HACMP for AIX: EVENT START: release_service_addr
Mar 8 11:13:24 AMSDC1 user:notice HACMP for AIX: EVENT COMPLETED: release_service_addr 0
Mar 8 11:13:24 AMSDC1 user:notice HACMP for AIX: EVENT COMPLETED: rg_move amsdc1 1 RELEASE 0
Mar 8 11:13:24 AMSDC1 user:notice HACMP for AIX: EVENT COMPLETED: rg_move_release amsdc1 1 0
Mar 8 11:13:59 AMSDC1 local0:crit clstrmgrES352484: Thu Mar 8 11:13:59 config_too_long: Timer type is 0
Mar 8 11:13:59 AMSDC1 local0:crit clstrmgrES352484: Thu Mar 8 11:13:59 config_too_long: Submitted event config_too_long, PID=1970380
Mar 8 11:13:59 AMSDC1 user:notice HACMP for AIX: EVENT START: config_too_long 360 TE_RG_MOVE_RELEASE
Mar 8 11:20:13 AMSDC1 user:notice HACMP for AIX: clexit.rc : Unexpected termination of clinfoES.
Mar 8 11:21:39 AMSDC1 user:notice HACMP for AIX: clexit.rc : Unexpected termination of clinfoES.
Mar 8 11:43:54 AMSDC1 daemon:notice RMCdaemon65872: (Recorded using libct_ffdc.a cv 2):::Error ID: 6eKora0Se2KD/e.I09s/e.1...................:::Reference ID: :::Template ID: a6df45aa:::Details File: :::Location: RSCT,rmcd.c,1.69,219 :::RMCD_INFO_0_ST The daemon is started.
Mar 8 12:05:23 AMSDC1 daemon:notice RMCdaemon295156: (Recorded using libct_ffdc.a cv 2):::Error ID: 6eKora0by2KD//RJ.9s/e.1...................:::Reference ID: :::Template ID: a6df45aa:::Details File: :::Location: RSCT,rmcd.c,1.69,219 :::RMCD_INFO_0_ST The daemon is started.
Mar 8 12:13:21 AMSDC1 daemon:notice topsvcs647310: (Recorded using libct_ffdc.a cv 2):::Error ID: 6UpNEL0343KD/Q2p09s/e.1...................:::Reference ID: :::Template ID: 97419d60:::Details File: :::Location: rsct,bootstrp.C,1.215.1.13,4956 :::TS_START_ST Topology Services daemon started Topology Services daemon started by: SRC Topology Services daemon log file location /var/ha/log/topsvcs.08.121321.mediation.en_US Topology Services daemon run directory /var/ha/run/topsvcs.mediation/
Mar 8 12:13:25 AMSDC1 daemon:notice grpsvcs630904: (Recorded using libct_ffdc.a cv 2):::Error ID: 63Y7ej0743KD/YnH.9s/e.1...................:::Reference ID: :::Template ID: afa89905:::Details File: :::Location: RSCT,pgsd.C,1.62.1.13,663 :::GS_START_ST Group Services daemon started DIAGNOSTIC EXPLANATION HAGS daemon started by SRC. Log file is /var/ha/log/grpsvcs_trace.
Mar 8 12:13:30 AMSDC1 local0:crit clstrmgrES466968: Thu Mar 8 12:13:30 HACMP: clstrmgrES: VRMF fix level in product ODM = 8
Mar 8 12:13:30 AMSDC1 local0:crit clstrmgrES466968: Thu Mar 8 12:13:30 CLSTR_JOIN_AUTO_START - This is the normal start request
Mar 8 12:13:39 AMSDC1 user:notice HACMP for AIX: clexit.rc : Unexpected termination of clinfoES.
*****************************************************************************************************************************
#PowerHA-(Formerly-known-as-HACMP)-Technical-Forum
#PowerHAforAIX

Originally posted by: Claudio

No, it is not possible.
To diagnose such problems it's necessary to collect and analyze a full set of log files from all cluster nodes.
You should place a call to your local IBM SW Support organization.
#PowerHA-(Formerly-known-as-HACMP)-Technical-Forum
#PowerHAforAIX