Roberto C. Sanchez <[EMAIL PROTECTED]> wrote on Tuesday, October 17, 2006 2:25 PM -0500:
> $ ntpq -p > remote refid st t when poll reach delay offset jitter > ======================================================================== > yauco.connexer. .INIT. 16 u - 1024 0 0.000 0.000 4000.00 > maracaibo.conne .INIT. 16 u - 1024 0 0.000 0.000 4000.00 It looks like you can't reach your servers, or you reach it and then discard it (ntp determines it is a 'falseticker'). The first character on each server line is a space, which indicates its status as a server is 'reject'. Also, both servers show up as stratum 16, which is not reasonable since each of the two servers was configured to use three low stratum servers. If working, you would see a '+' in the first column, the 'stratum' column would show 2 or 3, the 'when' column would show a number less than the poll column, the 'reach' column would typically show 377, and the 'delay', 'offset' and 'jitter' columns would show non-zero values. When a machine can't reach any of its designated servers, it uses the local hardware clock, so that's probably why it's drifting. Once you resolve the reachability issue, you might check whether a drift file is declared in ntp.conf. The drift calculation takes about a day to stabilize and with no drift file declared, ntp doesn't write this out at shutdown and must start over each time the machines reboots. To do the peering that Henrique suggested, you declare the other server as a peer. Here's what ntp.conf would look like for yauco.connexer.com: driftfile /var/lib/ntp/ntp.drift server ntp2.usno.navy.mil server ntp-1.vt.edu server ntp-2.vt.edu peer maracaibo.connexer.com -- Seth Goodman -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
