View
661
Download
6
Category
Preview:
DESCRIPTION
Timeout Waiting for Op HVctl_op_hello
Citation preview
1/10/2016 Document 2090597.1
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrlstate=jp3rwim23_65&id=2090597.1 1/3
ldmd Dumps Core With Error Message "timeout waiting for op HVctl_op_hello" (Doc ID2090597.1)
In this Document
SymptomsCauseSolutionReferences
APPLIES TO:
Solaris SPARC Operating System - Version 11 11/11 and laterOracle Solaris on SPARC (64-bit)
SYMPTOMS
ldmd dumps core error due to HV response timeout of op HVctl_op_hello
Typical messages in /var/svc/log/ldoms-ldmd:default.log:
Oct 26 20:01:13 timeout waiting for op HVctl_op_get_bulk_res_stat Oct 26 20:01:13 fatal error: waiting for hv response timeout
[ Oct 26 20:01:16 Stopping because process dumped core. ] [ Oct 26 20:01:16 Executing stop method (:kill). ]
[ Oct 26 20:01:16 Executing start method ("/opt/SUNWldm/bin/ldmd_start"). ] Oct 26 20:02:17 timeout waiting for op HVctl_op_hello
Oct 26 20:02:17 fatal error: waiting for hv response timeout [ Oct 26 20:02:19 Method "start" exited with status 95. ]
Possible fmadm faulty message:
TIME EVENTID MSGID SEVERITY Oct 26 09:48:39 0bfe9607f9b7cc19a8c88d1ec4c7b5ea SMF8000YX major
Problem Status : isolated Diag Engine : softwarediagnosis / 0.1
System Manufacturer : unknown
Name : ORCL,SPARCT42 Part_Number : unknown
Serial_Number : 1xxxxxxxx Host_ID : 8xxxxxxx
Suspect 1 of 1 :
Fault class : defect.sunos.smf.svc.maintenance Certainty : 100%
Affects : svc:///ldoms/ldmd:default Status : faulted and taken out of service
Description : A service failed a start, stop or refresh method failed.
Response : The service has been placed into the maintenance state.
Impact : svc:/ldoms/ldmd:default is unavailable.
1/10/2016 Document 2090597.1
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrlstate=jp3rwim23_65&id=2090597.1 2/3
Action : Run 'svcs xv svc:/ldoms/ldmd:default' to determine the generic reason why the service failed, the location of any logfiles, and a list of other services impacted. Please refer to the associated reference document at http://support.oracle.com/msg/SMF8000YX
for the latest service procedures and policies regarding this diagnosis.
CAUSE
Issue is caused by encountering fatal error due to timeout for op HVctl_op_hello, HV response timeout
SOLUTION
- The short-term solution is a power-cycle of the system
!! Please ensure that all Domains and resources of the system gets stopped ( shutdown ) *gracefully* !! before performing a power-cycle of the system ( e.g. "stop /SYS" && "start /SYS" in ILOM )
- The midterm/long-term solution is to update the System Firmware to a recent version ( HypV 1.14.2 orhigher ) You might consider to use the downtime for the power-cycle to also update the System Firmware in one step
To find recent System Firmware for the T4-x and T5-x system, please check this URL or the tables belowhttp://www.oracle.com/technetwork/systems/patches/firmware/index.html
Recent System Firmware for T4-x systems:
SysFW : MachType : Patch : Date : ILOM : HypV : OBP
8.7.2.b : T41 : 15174301 : 20150522 : 3.2.5.3.b : 1.14.2.a : 4.37.2 8.8.1.d : T41 : 15205903 : 20151002 : 3.2.5.6.c : 1.15.1.b : 4.38.1 8.8.1.e : T41 : 15205904 : 20151204 : 3.2.5.6.d : 1.15.1.b : 4.38.1
8.7.2.b : T42 : 15174401 : 20150522 : 3.2.5.3.b : 1.14.2.a : 4.37.2 8.8.1.d : T42 : 15206003 : 20151002 : 3.2.5.6.c : 1.15.1.b : 4.38.1
8.7.2.b : T44 : 15174501 : 20150522 : 3.2.5.3.b : 1.14.2.a : 4.37.2 8.8.1.d : T44 : 15206103 : 20151002 : 3.2.5.6.c : 1.15.1.b : 4.38.1
8.7.2.b : T41B : 15174601 : 20150522 : 3.2.5.3.b : 1.14.2.a : 4.37.2 8.8.1.d : T41B : 15206203 : 20151002 : 3.2.5.6.c : 1.15.1.b : 4.38.1
8.7.2.b : NT41 : 15174701 : 20150522 : 3.2.5.3.b : 1.14.2.a : 4.37.2 8.8.1.d : NT41 : 15206303 : 20151002 : 3.2.5.6.c : 1.15.1.b : 4.38.1
8.7.2.b : NT41B : 15174901 : 20150522 : 3.2.5.3.b : 1.14.2.a : 4.37.2 8.8.1.d : NT41B : 15206503 : 20151002 : 3.2.5.6.c : 1.15.1.b : 4.38.1
8.7.2.b : NT42 : 15174801 : 20150522 : 3.2.5.3.b : 1.14.2.a : 4.37.2 8.8.1.d : NT42 : 15206403 : 20151002 : 3.2.5.6.c : 1.15.1.b : 4.38.1
This issue has also been observed on T5-x systems with old SystemFirmware ( 9.0.X.X or Firmware 9.1.X.X )but not seen with newer versions. Hence, we recommend to upgrade the SystemFirmware to a recent version.e.g.:
SysFW : MachType : Patch : Date : ILOM : HypV : OBP
9.4.2.e : T52 : 21342652 : 20150630 : 3.2.5.3.e : 1.14.2.a : 4.37.2 9.5.1.b : T52 : 21911663 : 20151001 : 3.2.5.6.b : 1.15.1.a : 4.38.1
1/10/2016 Document 2090597.1
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrlstate=jp3rwim23_65&id=2090597.1 3/3
9.4.2.e : T54 : 21342653 : 20150630 : 3.2.5.3.e : 1.14.2.a : 4.37.2 9.5.1.b : T54 : 21911664 : 20151001 : 3.2.5.6.b : 1.15.1.a : 4.38.1
9.4.2.e : T58 : 21342653 : 20150630 : 3.2.5.3.e : 1.14.2.a : 4.37.2 9.5.1.b : T58 : 21911664 : 20151001 : 3.2.5.6.b : 1.15.1.a : 4.38.1
9.4.2.e : T51B : 21342654 : 20150630 : 3.2.5.3.e : 1.14.2.a : 4.37.2 9.5.1.b : T51B : 21911665 : 20151001 : 3.2.5.6.b : 1.15.1.a : 4.38.1
9.4.2.e : NT51B : 21342655 : 20150630 : 3.2.5.3.e : 1.14.2.a : 4.37.2 9.5.1.b : NT51B : 21911667 : 20151001 : 3.2.5.6.b : 1.15.1.a : 4.38.1
Note: Please bear in mind that you cannot save the latest LDom changes to SP due to the failing ldmd ldmd SMF service use to be in maintenance state in such cases State: maintenance since <some-date>, Reason: Restarting too quickly.
Hence, you might need to restore the latest auto-saved config from /var/opt/SUNWldm/autosave* directories. MOS Doc ID 1464421.1 contains steps and examples how to perform this. configuration, save & restore setup and troubleshooting of Oracle VM Server for SPARC (LDom) Document1464421.1
- If you see this issue on a bare-metal system without ldom configuration you might considerto temporarily disable ldmd ( # svcadm disable -t ldmd ) until you can schedule a downtime for the SystemFirmware upgrade
REFERENCES
NOTE:1464421.1 - Configuration, Save & Restore Setup and Troubleshooting of Oracle VM Server for SPARC(LDom)
Didn't find what you are looking for?
Recommended