Link to home
Start Free TrialLog in
Avatar of snoopaloop
snoopaloopFlag for United States of America

asked on

syncing hardware clock to system time (failed)

When I reboot I noticed "syncing hardware clock to system time (failed)"   The time was off on the virtual OSs and I have no idea how to fix the failed service.
Avatar of Paul Solovyovsky
Paul Solovyovsky
Flag of United States of America image

check this out

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1001827


Details
When I shutdown the ESX server using shutdown -h now , the ESX host displays the following message:
Syncing hardware clock to system time [FAILED]
In the date command it is showing the correct time but VMware Infrastructure Client was showing wrong time.
Solution
This message can Be Safely Ignored

The message, Syncing Hardware Clock to System Time [Failed], is displayed during the ESX Server shutdown.
This has no impact on system availability or performance.
 
This happens when the hardware clock and system clock are not synchronised.
You can synchronize them using following two commands:

hwclock --show
(Shows you BIOS hardware clock time)

hwclock --systohc
(Sync the system time to the hardware clock)
Avatar of snoopaloop

ASKER

Alright, I inputted those two commands and loaded up the system.  However, the virtual OS installed still says the wrong time.
do you have ntp setup on the ESX hosts?
I tried to set it up but it looks like it's not making a difference
If NTP is not running it is picking up time from the server BIOS which is most likely causing this issue.

What NTP Servers are you pointing to? Internal or External?
Here's some Infrastructure Client snapshots...
esx1.jpg
esx2.jpg
ASKER CERTIFIED SOLUTION
Avatar of Paul Solovyovsky
Paul Solovyovsky
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
the one you're using seems to be the local time, here's what I found, most likely the issue

To access its own system clock, also called the local clock, NTP uses the pseudo IP address 127.127.1.0. This IP address must not be mixed up with 127.0.0.1, which is the IP of the localhost, i.e. the computer's loopback interface.
sorry for the delay.  I entered the time.  I will reboot to confirm the time sticks later today,  thanks
Check to see if NTP date and time are red, if yes than it's not syncing, if normal color than you should be ok (hopefully)
It's normal and rebooted with the correct time thanks