Hi All,
I am having little trouble with my ntp 4.2.0 in Linux.
I have having a problem with my ntpd. I have configured only local server
127.127.1.0 as my default server and later configure any server using ntpdc
program.
Here is my configuration :
Now after my ntpd syncs up with local clock, it creates drift file and store
the drift as 0.000
Now I configure a valid ntp stratum 1 server using ntpdc addserver command.
What I observe is, it starts the poll from 64 and after 3 packet exchange only
it goes to 1024. As a result it is taking lot of time to sync up. Even after
syncup I see it goes back and forth between local and the server and does clock
reset evry 30 min or so.
This situation is improved with adding burst flag while configuring the server.
Now, sometime after reach value goes to 3 or 7 , it selects the server for sync
( earlier it was not even doing that ) but again it reaches to sometime 128 or
256 or 1024. In these cases I see pstats shows that it has exchanged 9 packets.
But since the poll interval is increased, it takes longer time to reset the
clock to correct the offset and change the refid and stratum value. This is
inconsistent behavior.
If I restart the ntpd and then confiture the server ( while it is not yet
synced to local) it works fine.
Is this the right behavior or a bug. The end result is that it takes unusually
long time to sync.
Also, doing multiple reset of clock every hour seems pointing to a bug in ntpd
or probably the hardware clock is slipping continuously. Usually I would expect
after one time clock reset ( step ) the server should be doing slew. But I see
the offset reported even after first or second reset is more than 250 mSec.
Below is some captures:
with burst setup:
Please let me know if any one has any clue.
I am having little trouble with my ntp 4.2.0 in Linux.
I have having a problem with my ntpd. I have configured only local server
127.127.1.0 as my default server and later configure any server using ntpdc
program.
Here is my configuration :
Code:
restrict default nomodify
restrict 127.0.0.1
authenticate no
server 127.127.1.0 # local clock
fudge 127.127.1.0 stratum 10
broadcastclient
Now after my ntpd syncs up with local clock, it creates drift file and store
the drift as 0.000
Now I configure a valid ntp stratum 1 server using ntpdc addserver command.
What I observe is, it starts the poll from 64 and after 3 packet exchange only
it goes to 1024. As a result it is taking lot of time to sync up. Even after
syncup I see it goes back and forth between local and the server and does clock
reset evry 30 min or so.
This situation is improved with adding burst flag while configuring the server.
Now, sometime after reach value goes to 3 or 7 , it selects the server for sync
( earlier it was not even doing that ) but again it reaches to sometime 128 or
256 or 1024. In these cases I see pstats shows that it has exchanged 9 packets.
But since the poll interval is increased, it takes longer time to reset the
clock to correct the offset and change the refid and stratum value. This is
inconsistent behavior.
If I restart the ntpd and then confiture the server ( while it is not yet
synced to local) it works fine.
Is this the right behavior or a bug. The end result is that it takes unusually
long time to sync.
Also, doing multiple reset of clock every hour seems pointing to a bug in ntpd
or probably the hardware clock is slipping continuously. Usually I would expect
after one time clock reset ( step ) the server should be doing slew. But I see
the offset reported even after first or second reset is more than 250 mSec.
Below is some captures:
with burst setup:
Code:
* - selected for sync, + - peer mode(active),
- - peer mode(passive), = - polled in client mode
remote local st poll reach delay offset disp
---------------------------------------------------------------------------
=127.127.1.0 127.0.0.1 10 64 377 0.00000 0.000000 0.03078
*10.81.254.131 10.194.60.72 1 128 3 0.07545 -0.063021 0.01147
ntpdc> peers
remote local st poll reach delay offset disp
=======================================================================
=LOCAL(0) 127.0.0.1 10 64 377 0.00000 0.000000 0.03036
*10.81.254.131 10.194.60.72 1 1024 3 0.07544 -0.280085 0.00662
ntpdc> pstats 10.81.254.131
remote host: 10.81.254.131
local interface: 10.194.60.72
time last received: 278s
time until next send: 732s
reachability change: 356s
packets sent: 9
packets received: 9
bad authentication: 0
bogus origin: 0
duplicate: 0
bad dispersion: 0
bad reference time: 0
candidate order: 6
Please let me know if any one has any clue.