Solaris Cluster - HA-LDOM Resource Start Fails with "Failed to add the domain <domain_name> using /var/cluster/run/<ldom_res_name>.xml"
(Doc ID 2619728.1)
Last updated on DECEMBER 06, 2021
Applies to:
Solaris Cluster - Version 4.3 to 4.4 [Release 4.3 to 4.4]Information in this document applies to any platform.
Symptoms
HA-LDOM resource fails to go online and may enter STOP-FAILED (Faulted) state.
Node1 is the Cluster President and shows the 'state' changes:
Oct 23 17:25:40 Node1 Cluster.RGM.global.rgmd: [ID 529407 daemon.notice] resource group ldom2-rg state on node Node2 change to RG_PENDING_ONLINE
Oct 23 17:25:40 Node1 Cluster.RGM.global.rgmd: [ID 443746 daemon.notice] resource ldom2-rs state on node Node2 change to R_STARTING
Oct 23 17:25:40 Node1 Cluster.RGM.global.rgmd: [ID 922363 daemon.notice] resource ldom2-rs status msg on node Node2 change to <Starting>
Oct 23 17:26:19 Node1 Cluster.RGM.global.rgmd: [ID 443746 daemon.error] resource ldom2-rs state on node Node2 change to R_START_FAILED
Oct 23 17:26:19 Node1 Cluster.RGM.global.rgmd: [ID 529407 daemon.error] resource group ldom2-rg state on node Node2 change to RG_PENDING_OFF_START_FAILED
Oct 23 17:26:19 Node1 Cluster.RGM.global.rgmd: [ID 922363 daemon.notice] resource ldom2-rs status msg on node Node2 change to <Stopping>
Oct 23 17:26:19 Node1 Cluster.RGM.global.rgmd: [ID 443746 daemon.notice] resource ldom2-rs state on node Node2 change to R_STOPPING
Oct 23 17:26:25 Node1 Cluster.RGM.global.rgmd: [ID 443746 daemon.error] resource ldom2-rs state on node Node2 change to R_STOP_FAILED
Oct 23 17:26:25 Node1 Cluster.RGM.global.rgmd: [ID 529407 daemon.error] resource group ldom2-rg state on node Node2 change to RG_PENDING_OFF_STOP_FAILED
Oct 23 17:26:25 Node1 Cluster.RGM.global.rgmd: [ID 529407 daemon.error] resource group ldom2-rg state on node Node2 change to RG_ERROR_STOP_FAILED
Oct 23 17:26:25 Node1 Cluster.RGM.global.rgmd: [ID 870123 daemon.warning] Resource group <ldom2-rg> might require operator attention due to STOP failure
Oct 23 17:26:25 Node1 Cluster.RGM.global.rgmd: [ID 663692 daemon.error] failback attempt failed on resource group <ldom2-rg> with error <resource group in
ERROR_STOP_FAILED state requires operator attention>
--
Node2:
Oct 23 17:29:08 Node2 Cluster.RGM.global.rgmd: [ID 224900 daemon.notice] launching method <gds_start> for resource <ldom2-rs>, resource group
<ldom2-rg>, node <Node2>, timeout <300> seconds
Oct 23 17:29:47 Node2 SC[SUNW.ldom:11,ldom2-rg,ldom2-rs]: [ID 399534 daemon.error] Failed to add the domain ldom2-rg using
/var/cluster/run/ldom2-rs.xml.
Oct 23 17:29:47 Node2 SC[,SUNW.ldom:11,ldom2-rg,ldom2-rs,gds_start]: [ID 186822 daemon.error] /opt/SUNWscxvm/bin/start_xvm -R ldom2-rs
ldom2-rg -T SUNW.ldom:11 has failed rc=1
Oct 23 17:29:47 Node2 SC[,SUNW.ldom:11,ldom2-rg,ldom2-rs,gds_start]: [ID 475178 daemon.notice] Start_exit_on_error=true has been set. The
resource will enter a start failed state.
Oct 23 17:29:47 Node2 Cluster.RGM.global.rgmd: [ID 938318 daemon.error] Method <gds_start> failed on resource <ldom2-rs> in resource group
<ldom2-rg> [exit code <1>, time used: 13% of timeout <300 seconds>]
Oct 23 17:29:47 Node2 Cluster.RGM.global.rgmd: [ID 224900 daemon.notice] launching method <gds_stop> for resource <ldom2-rs>, resource group
<ldom2-rg>, node <Node2>, timeout <300> seconds
Oct 23 17:29:53 Node2 SC[,SUNW.ldom:11,ldom2-rg,ldom2-rs,gds_stop]: [ID 186822 daemon.error] /opt/SUNWscxvm/bin/stop_xvm -R ldom2-rs
-G ldom2-rg -T SUNW.ldom:11 has failed rc=1
Oct 23 17:29:53 Node2 SC[,SUNW.ldom:11,ldom2-rg,ldom2-rs,gds_stop]: [ID 943012 daemon.error] Stop_exit_on_error=true has been set. The re
source will enter a stop failed state.
Oct 23 17:29:53 Node2 Cluster.RGM.global.rgmd: [ID 938318 daemon.error] Method <gds_stop> failed on resource <ldom2-rs> in resource group
<ldom2-rg> [exit code <1>, time used: 2% of timeout <300 seconds>]
Oct 23 21:46:20 Node2 Cluster.RGM.global.rgmd: [ID 870123 daemon.warning] Resource group <ldom2-rg> might require operator attention due to STOP fa
ilure
Changes
The Cluster had been shutdown, powered-off and moved to another location.
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 |
Changes |
Cause |
Solution |