Bill et al,

Ntp.hep.wisc.edu just jumped 28801 seconds into the past.  I stopped
ntpd, and ntpdate tried to adjust it's clock 29297 seconds into the
future and failed.  And now I'm watching ntpd report wildly differing
offsets.  So clearly the system is sick and this is our problem.

Sorry for the bother.

steve
--

 > ---- Original Message ----
 > From: Hostmaster <hostmaster@doit.wisc.edu>
 > Steve,
 > 
 >   Is ntp.hep.wisc.edu still experiencing syncing problems?  Due to a 
 > logging issue we don't have historical data that we can look at right 
 > now.  We are working with the POST sysadmins to correct this.  That 
 > being said we don't see any problems at the host level and it seems to 
 > be in sync with outside sources as shown below:
 > 
 > ntpdate -q 128.104.30.17
 >  
 > server 128.104.30.17, stratum 2, offset -0.004851, delay 0.02597
 > 14 Feb 11:48:09 ntpdate[11550]: adjust time server 128.104.30.17 offset 
 > -0.004851 sec
 > 
 > 
 > [from 128.104.30.17]
 > ntpq> peer
 >      remote           refid      st t when poll reach   delay   offset 
 >  jitter
 > ============================================================================== 
 > 
 > -starfish.doit.w clock.xmission.  2 u   32  128   36    0.790  -21.757 
 >  0.326
 >  tang.doit.wisc. clock.via.net    2 u   12  128    3    0.749    5.539   
 > 0.372
 > -ntp.okstate.edu .USNO.           1 u   22  128  377   49.716  -10.423 
 >  0.373
 > *time-B.timefreq .ACTS.           1 u   90  128  377   77.397   -2.261 
 >  0.171
 > +time.nist.gov   .ACTS.           1 u   22  128  377   76.858   -2.488 
 >  1.334
 > +rrcs-64-183-55- .GPS.            1 u   18  128  377   89.275   -6.993 
 >  1.328
 > 
 > We will continue to look into the situation, if there is anything else 
 > we can do to assist you please let us know. 
 > 
 > Thanks,
 > DoIT Hostmasters (Bill Foster)