ntpd struggling to keep up - how to fix?

Torfinn Ingolfsen torfinn.ingolfsen at broadpark.no
Fri Feb 12 12:26:09 UTC 2010


On Thu, 11 Feb 2010 10:25:59 -0800
Chuck Swiger <cswiger at mac.com> wrote:

> The rate at which this machine is losing time is probably exceeding the ~50 seconds per day that NTPd is willing to correct without extreme measures (ie, it has to step time rather than drift-correct).  > You might help it maintain a more sane idea of time by using at least 4 timeservers.

Hmm, ok that iis something I can try.

> You might take a look at 'vmstat -i' and look out for an interrupt storm, but it's possible your hardware's clock is simply busted.  

AFAICT, vmstat -i looks ok:
root at kg-f2# uptime
 1:23PM  up 18:31, 3 users, load averages: 0.00, 0.00, 0.00
root at kg-f2# vmstat -i
interrupt                          total       rate
irq1: atkbd0                          36          0
irq6: fdc0                             1          0
irq16: siis0 ohci0+                  408          0
irq22: atapci0                    856338         12
cpu0: timer                    133347678       1999
irq256: re0                       234087          3
cpu1: timer                    133337654       1999
Total                          267776202       4016


-- 
Regards,
Torfinn



More information about the freebsd-stable mailing list