weird time latency

jonaskellens · 06-25-2009, 10:42 AM

Code:

[root@asterisk asterisk]# date
Thu Jun 25 17:16:27 CEST 2009
[root@asterisk asterisk]# ntpdate 192.168.2.1
25 Jun 17:39:28 ntpdate[796]: step time server 192.168.2.1 offset 1362.400014 sec
[root@asterisk asterisk]# date
Thu Jun 25 17:39:31 CEST 2009

So now and then I need to do a ntpdate to adjust the time. If not then the clock of my server runs behind...

Can someone explain me why time seems to go much slower on my server then in the real world ??

neo009 · 06-25-2009, 11:36 AM

Set your BIOS time as same as your system time from command line..
# date
Sun May 24 04:16:07 MDT 2009

date -s "25 May 2009 14:31:00"

jonaskellens · 06-25-2009, 12:56 PM

Quote:

Originally Posted by neo009

Set your BIOS time as same as your system time from command line..
# date
Sun May 24 04:16:07 MDT 2009

date -s "25 May 2009 14:31:00"

The cause is my BIOS-time ??

This is a server that runs in a VirtualBox virtual machine...
Other virtual servers do not have this problem...

Code:

[root@asterisk ~]# date
Thu Jun 25 19:56:37 CEST 2009
[root@asterisk ~]# date -s "25 May 2009 19:57:00"

nothing happens...

neo009 · 06-26-2009, 07:03 AM

Often-times, it happens that when you reboot, your clock does not reflect the correct date and time. You may be forgetting to sync the hardware clock with the current system time. Here is how:

First check and set the current system date and time.

# date
# date -s 'Wed May 28 11:35:00 EST 2003'

Then sync your hardware clock with the system time.

# hwclock --show
# hwclock --systohc

neo009 · 06-26-2009, 07:07 AM

I think in your case you should do ntpdate update and then sync hw with sys time

# hwclock --show
# hwclock --hctosys

Also set your base OS for vmware time right with hw..are you using vmware vz???