time drift

[ScottLClement]

I have a GL580 with 4 xeon proc running RHEL 4 AS. The system clock is unable to maintain it's time correctly. It actually runs really fast. Without ntpd resyncing the time frequently we have a 5 minute drift every 1 hour give or take. Does anyone have a solution for this?

[Andrew Cowan]

Scott,

The normal cause of this is when the battery on your motherboard needs replacing, or in extreme cases it can be down to a corrupt BIOS.

[ScottLClement]

This motherboard was recently replaced for a problem with a onboard nic. So I would think that the Bio and battery are good. How do I validate if this is the issue?

[Andrew Cowan]

I think you need to talk to the people that did the work. The only way I know to test a battery is to completely detach your computer from the mains overnight, then boot up to BIOS level and see whether the clock has kept time.

[Steven E. Protter]

Shalom,

Dirty little secret. System clocks are useless. They can't tell time.

Unless they are totally broken they should be ignored.

ntp.con or xntp.conf or whatever they call it this week should be configured to point to a valid time server inside or outside your network if firewall permits.

chkconfig ntpd on
# sets it to auto start at boot
service ntpd on
service ntpd status
# check that its running.

You need to have system time adjusted to within an hour of reality before doing the above steps.

SEP

[ScottLClement]

I agree about having ntpd running and do have it. But to have a 5 minute per hour drift is rediculous.