[ntp:bugs] [Bug 327] New: constant "time reset 0.137329 s" in ntp4.2.0a and ntp 4.1.1 version

[bugzilla at ntp.org]

http://bugzilla.ntp.org/show_bug.cgi?id=327

           Summary: constant  "time reset 0.137329 s" in   ntp4.2.0a and ntp
                    4.1.1 version
           Product: ntp
           Version: stable
          Platform: DEC
        OS/Version: OSF/1
            Status: NEW
          Severity: normal
          Priority: P2
         Component: ntpd
        AssignedTo: stenn at ntp.org
        ReportedBy: balajisa at india.hp.com
                CC: bugs at ntp.org


Hi,


 Iam using ntp on tru64 machine... Iam getting log messages(time reset ) which
 i have pasted below.. I looked in to the ntp faq for these
 messages and could not come to proper conclusion what should
 i do for this to fix this problem.. NTP faq says these
 messages will come if my clock is too fast or too slow.
 It also says tickadj is absolute in V4 and  ntpd will
 correct if the error in the clock is less than 500ppm.
                                                                               
                                              
 From the log message ( and reading ntp faq), i found
 that for each secound , 10.016003 microseconds should have
 been added to tick. This value is less than 500pm and ntpv4
 doesnot correct the problem..
 
  I discussed this issue in the ntp mailing list and i
went for the upgrade from 4.1.1 to 4.2.0a and still found
this issue exist.. I tried xntpd v3 and found that this
problem does not exist.. 
 

  Please let me know if you need any further information
                                                                               
                                                regards,
Balaji


-------------Log message-----------------------
                                                                               
                                             
Jul 29 11:33:28 mgrspd01 xntpd[122425]: ntpd 4.1.1 Tue Jun 29 02:53:35
EDT 2004
Jul 29 11:33:29 mgrspd01 xntpd[122425]: precision = 976 usec
Jul 29 11:33:29 mgrspd01 xntpd[122425]: kernel time discipline status
0040
Jul 29 11:33:29 mgrspd01 xntpd[122425]: frequency initialized 10.814
from /etc/ntp.drift
Jul 29 11:33:33 mgrspd01 xntpd[122425]: too many recvbufs allocated (40)
Jul 29 11:42:06 mgrspd01 xntpd[122425]: too many recvbufs allocated (40)
Jul 29 11:52:05 mgrspd01 xntpd[122425]: too many recvbufs allocated (40)
Jul 29 13:00:08 mgrspd01 xntpd[122425]: too many recvbufs allocated (40)
Jul 29 13:00:21 mgrspd01 xntpd[122425]: too many recvbufs allocated (40)
Jul 29 15:03:41 mgrspd01 xntpd[122425]: too many recvbufs allocated (40)
Jul 29 15:03:52 mgrspd01 xntpd[122425]: too many recvbufs allocated (40)
Jul 29 15:12:02 mgrspd01 xntpd[122425]: too many recvbufs allocated (40)
Jul 29 15:19:01 mgrspd01 xntpd[122425]: too many recvbufs allocated (40)
Jul 29 15:22:13 mgrspd01 xntpd[122425]: too many recvbufs allocated (40)
Jul 29 15:24:00 mgrspd01 xntpd[122425]: too many recvbufs allocated (40)
Jul 29 15:27:02 mgrspd01 xntpd[122425]: time reset 0.136939 s
Jul 29 15:27:02 mgrspd01 xntpd[122425]: synchronisation lost
Jul 29 15:27:02 mgrspd01 xntpd[122425]: too many recvbufs allocated (40)
Jul 29 15:32:13 mgrspd01 xntpd[122425]: too many recvbufs allocated (40)
Jul 29 15:35:27 mgrspd01 xntpd[122425]: too many recvbufs allocated (40)
Jul 29 15:42:09 mgrspd01 xntpd[122425]: too many recvbufs allocated (40)
Jul 29 15:43:02 mgrspd01 xntpd[122425]: too many recvbufs allocated (40)
Jul 29 19:16:16 mgrspd01 xntpd[122425]: time reset 0.137329 s
Jul 29 19:16:16 mgrspd01 xntpd[122425]: synchronisation lost
.....................................................................
.....................................................................
.....................................................................
.....................................................................
.....................................................................
Jul 29 23:05:56 mgrspd01 xntpd[122425]: time reset 0.138053 s
Jul 29 23:05:56 mgrspd01 xntpd[122425]: synchronisation lost
.....................................................................
.....................................................................
.....................................................................
.....................................................................
.....................................................................
Jul 30 02:47:50 mgrspd01 xntpd[122425]: time reset 0.133474 s
Jul 30 02:47:50 mgrspd01 xntpd[122425]: synchronisation lost
Jul 30 06:36:47 mgrspd01 xntpd[122425]: time reset 0.136751 s



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.