Troubleshooting
Problem
When a VM is deployed by PowerVC with a custom compute template that enables the virtual machine for remote restart, the deployed VM has the date incorrectly set to epoch (1st January 1970). This also has side effect that the crond daemon runs continuously.
Symptom
- Incorrect time set on a deployed virtual machine.
- High CPU utilization seen on the virtual machine for almost a day after deployment.
Cause
The PHYP function tries to set the initial date on the SRR partition, but incorrectly sets it to epoch(1st January 1970).
Environment
- Express (IVM) or Standard (HMC): HMC
- Any other environmental information you deem relevant
Release impacted :
PowerVC 1.2.3, 1.2.3 FP1, 1.2.3 FP2, 1.3.0, 1.3.0 FP1, 1.3.0 FP2, 1.3.1
Diagnosing The Problem
Log in to the VM. Check if the year on the VM is incorrectly set to the year 1970.
Resolving The Problem
Users can do either of the following:
- Upgrade or update the Server firmware. This is fixed in 840.20 released 5/27/2016. A fix is planned for 830.30 fixpack targeted for 3 quarter 2016.
- If firmware upgrade is not possible, then set the correct time on the VM manually after the VM is deployed. For example, to set the date on the VM to 2nd May 2016 6 PM, run the command “date --set="2 MAY 2016 18:00:00"
- Perhaps the best way to protect against this kind of problem is to make sure to use NTP in your environment so the correct time would then "sync" automatically even if it were wrong at create/deploy time.
[{"Product":{"code":"SSXK2N","label":"PowerVC Standard Edition"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"Not Applicable","Platform":[{"code":"PF016","label":"Linux"}],"Version":"1.2.3;1.3;1.3.1","Edition":"","Line of Business":{"code":"LOB57","label":"Power"}}]
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
nas8N1021369