1 person found this helpful
The error indicates that client0 is not in sync with the primeclient and vcenter. Make sure that the VMware Tools option "Synchronize guest time with host" is checked for client0. Also be sure that all times all ESX hosts which are hosting client0, primeclient and vcenter are sync'd to the same ntp server.
i found that there are some problems on my ntp server so i changed to time.google.com
and i also discovered that my vcenter didn't sync up with host...
thanks again, the vmmark works now.
i have the same Problem "clients or vcserver out of sync: [u'client0']“",
i set up all esx nodes with the same ntp server (time.google.com) and activate the Option "Sync Time with HOST" but it still doesn't work!
I also tried already to put all three Machines (Prime, Client0 and VCenter) on the same ESX Node. Nothing...
The time is overall correct. What can it be? Different Timezone ? MEST <> CEST?
It could very well be a timezone issue -- you'll definitely want to make sure the timezones match up across the board.
If it's still an issue, please ZIP or tar up your most recent Results folder and attach it in your reply.
PS -- In the future, please start a new thread since the OP had his issue solved -- your post almost slipped through the cracks.
Thanks for your tip with the Logfiles. It was a different Timezone (MEST and CEST) on the Prime Client!
I'm trying to run vmmark3 benchmark job and getting same error message. I have verified that:
- VCenter server and all VMs including PrimeClient and CLient0 are in the same Time Zone.
- VCenter server and all VMs including PrimeClient and CLient0 has the same time, 1 or 2 sec difference the most.
- VCenter and ESXi hosts are set to the same NTP servers.
- All VMs including PrimeClient and Client0 are set to sync time with hosts.
I have checked everything multiple times and I'm out of ideas what can be wrong. Any suggestions would be greatly appreciated.
Your TimeChecks.txt shows this:
tileindex, PrimeTime, PrimeTimeZone, ClientName, ClientTime, ClientTimeZone,TimeErrors, Skew
0, 1583181332,GMT,Client0, 1583181331, CST, 1, 1
Note the disparity in time zones between the Prime Client's Time Zone (GMT) and Client0 Time Zone (CST).
Look in the User's Guide and find the text "Make sure the prime client is configured for the correct time zone" for more help on setting /etc/localtime correctly for primeclient, and let me know if you still have issues.
Thank you for quick response. It looks like changing Time Zone on PrimeClient doesn't happen without reboot. After reboot time check completes without errors.