My Oracle Support Banner

Oracle VM Manager Failover failed with 'start for resource: xag.ovmm.wl 1 1 completed with status: TIMEDOUT' (Doc ID 2357121.1)

Last updated on DECEMBER 04, 2020

Applies to:

Oracle Cloud Infrastructure - Version N/A and later
Oracle VM - Version 3.4.4 and later
Information in this document applies to any platform.

Symptoms

Follow up document of  'Oracle VM 3:Using Oracle Clusterware to Protect Oracle VM Manager'
The resource xag.ovmm.wl is always in "UNKNOWN" status

/opt/12.1.0.1/grid/bin/crsctl stat res -t
--------------------------------------------------------------------------------
Name Target State Server State details
xag.ovmm.wl 1 ONLINE UNKNOWN b-cluster CHECK TIMED OUT,STABLE

Trying to stop the resource forcefully itself is failing with the error cleaning the resource "xag.ovmm.wl" and then it throws exception "Check timed out"

Logs with below:

2018-01-23 14:32:15.513: [ AGFW][1793705728] {1:52732:733} Preparing START command for: xag.ovmm.wl 1 1
2018-01-23 14:32:15.513: [ AGFW][1793705728] {1:52732:733} xag.ovmm.wl 1 1 state changed from: UNKNOWN to: STARTING>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
2018-01-23 14:32:15.515: [xag.ovmm.wl][1795806976] {1:52732:733} [start] Executing action script: /opt/xag/bin/agwlas[start]
2018-01-23 14:32:15.618: [xag.ovmm.wl][1795806976] {1:52732:733} [start] weblogic admin server agent running command 'start' on xag.ovmm.wl
2018-01-23 14:32:15.618: [xag.ovmm.wl][1795806976] {1:52732:733} [start] weblogic admin server agent running command 'start' on xag.ovmm.wl
2018-01-23 14:32:16.970: [xag.ovmm.wl][1795806976] {1:52732:733} [start] start weblogic admin server, rc=0>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>Not sure here weblogic admin server is started
2018-01-23 14:32:16.970: [xag.ovmm.wl][1795806976] {1:52732:733} [start] waiting for weblogic admin server to start...>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
2018-01-23 14:37:15.567: [ AGFW][1797908224] {1:52732:733} Created alert : (:CRSAGF00113:) : Aborting the command: start for resource: xag.ovmm.wl 1 1
2018-01-23 14:37:15.567: [xag.ovmm.wl][1797908224] {1:52732:733} [start] Killing action script: start>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
2018-01-23 14:37:15.567: [ AGFW][1797908224] {1:52732:733} Command: start for resource: xag.ovmm.wl 1 1 completed with status: TIMEDOUT
2018-01-23 14:38:15.569: [ AGFW][1793705728] {1:52732:733} xag.ovmm.wl 1 1 state details has changed from: to: CHECK TIMED OUT

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.