Vmware - Diskless Time Error

[EvilAlchemist]

I have setup VMware Server and running the diskless ISO.

It is running well, but the time in the log if -4 behind my local time.

This casuse FAHMON to show the client is hung.

Anyone know how to correct this?

I am able to set the time zone manully to +0, but this causes all other clients to show as async but fixes the VMware clients.

 

[BillR]

There have been numerous fixes that have been recommended for this anomaly but by far the easiest is to go into the client config. On advanced settings say yes and move on down to the next of the last commands and you will see one that says something to the effect of ignore client deadlines.

At that point the Linux times won’t matter and all will be well.

If you are totally anal and hell bent on matching times Google has several work arounds that sometimes work, and sometimes don’t.


Luck

 

[EvilAlchemist]

I think the clients are fine, just a visual problem.

I don't mind having most of my clients show up as aysnc in fahmon ...as long as i have a way to monitor this progress, i am fine.

 

[rmdashrrootsplat]

It's a known problem with VMWare and Linux. I have the same problem with it in ESX. I get around it by installing the VMWare Tools or by just running an NTP daemon. Here's the VMWare white paper on it:

http://www.vmware.com/pdf/vmware_timekeeping.pdf

Don't know if any of those will work for the diskless image.

 

[Xilikon]

Yeah, I solved the problem myself by setting up all instances to use NTP to synchronise time periodically. Like that, it will seldom show as hung but like EA said, it's just cosmetic (A trick to differentiate a real hung and a fake hung is to look at the time of the last entry, if the 2 last digits is a bit more than the host time, it will show as hung (fahmon thought it didn't crunch for 23h59 mins). If the time is really different (like 21:22 on the monitored box and 22:59 on your main box), it's really hung.

With time, you will get used to this cosmetic bug

 

[EvilAlchemist]

Yeah, I solved the problem myself by setting up all instances to use NTP to synchronise time periodically.

Is this setup in the Vmware or in the guest OS?

Since I am running notfred's iso, it disables NTP in the OS since it is running in the VMware.

 

[Xilikon]

Is this setup in the Vmware or in the guest OS?

Since I am running notfred's iso, it disables NTP in the OS since it is running in the VMware.

It's done in Xubuntu OS. It's unfortunate VMWare itself have no way to synchronise time With notfred's, it's not possible but you can do a feature request to include a ntp package in it since it's very easy.