Paprika
Fri 15th Dec '06, 4:28am
I thought I'd post this here since the vbulletin community is so good about taking care of it's own:
Maybe this can sum my problem up real nicely:
root@server[~]# date
Thu Dec 14 23:44:07 EST 2006
root@server[~]# hwclock --show
Thu 14 Dec 2006 11:52:26 PM EST -0.072929 seconds
.. hwclock showing the actually correct real world time.
If I run rdate, it fixes the system time, but then because the system time *apparently* is running slow, it's wrong again within minutes.
I've setup a cron to run rdate every 2 minutes and the time still won't hold up for even that 2 minutes. Obviously after watching it for some time, that clock is running slower than it should be and I have no idea how to fix a problem like this.
This is a cpanel/WHM vps in question.
Any ideas?
I've already tried the ntpd service, it didn't seem to work. My rdate cronjob does it much better but still the problem is aparently and it's causing problems in my boards to i had to close them till i fix it.
Maybe this can sum my problem up real nicely:
root@server[~]# date
Thu Dec 14 23:44:07 EST 2006
root@server[~]# hwclock --show
Thu 14 Dec 2006 11:52:26 PM EST -0.072929 seconds
.. hwclock showing the actually correct real world time.
If I run rdate, it fixes the system time, but then because the system time *apparently* is running slow, it's wrong again within minutes.
I've setup a cron to run rdate every 2 minutes and the time still won't hold up for even that 2 minutes. Obviously after watching it for some time, that clock is running slower than it should be and I have no idea how to fix a problem like this.
This is a cpanel/WHM vps in question.
Any ideas?
I've already tried the ntpd service, it didn't seem to work. My rdate cronjob does it much better but still the problem is aparently and it's causing problems in my boards to i had to close them till i fix it.