ntpdate[25856]: no server suitable for synchronization found -- Help needed

  • Follow


Hi,

 

I'm facing  NTP server synchronization issues  with my local reference
clock. Here is the description of my problem.

 

I 've used the latest NTP released version i.e. NTP-4.2.6p3  and tried
for the NTP synchronization with the local reference clock. But, I  only
end up with the below errors without any synchronization.

 

Here with the my ntp.conf file : 

 

# NTP Configuration File

logfile /XXX/ntp.log

statsdir /XXX/ntpstats/

driftfile /XXX/ntp.drift

 

 

#Sync Input

 

# NTP Input Disabled

#Sync Output

 

# NTP Server enabled

#Using Local Clock as NTP sync source

server 127.127.1.0 

fudge 127.127.1.0 stratum 10 

#restrict 127.0.0.1 nomodify

 

I  even couldn't get the association with the local reference clock as
shown by ntpq.

 

 

ntpq> v

ntpq 4.2.6p3@1.2290-o Wed Feb 16 14:46:20 UTC 2011 (1)

 

ntpq> pe

No association ID's returned

 

ntpq> as

No association ID's returned

 

ntpq> rv

associd=0 status=c012 leap_alarm, sync_unspec, 1 event, freq_set,

version="ntpd 4.2.6p3@1.2290-o Wed Feb 16 14:46:11 UTC 2011 (1)",

processor="i686", system="Linux/2.6.13.4.XXX-LEAF", leap=11, stratum=16,

precision=-18, rootdelay=0.000, rootdisp=10.185, refid=INIT,

reftime=00000000.00000000  Thu, Feb  7 2036  6:28:16.000,

clock=d10611f0.c00c62e8  Wed, Feb 16 2011  9:05:52.750, peer=0, tc=3,

mintc=3, offset=0.000, frequency=0.000, sys_jitter=0.000,

clk_jitter=0.004, clk_wander=0.000

 

 

The ntp.log shows as follows :

 

16 Feb 08:54:33 ntpd[12066]: attempt to configure invalid address
127.127.1.0

16 Feb 08:54:33 ntpd[12066]: inappropriate address 127.127.1.0 for the
fudge command, line ignored

 

 

However, I tried to get the executable ( ntpd, ntpq etc.. )  of  the
build  4.2.0a@1:4.2.0a+stable-8-r <mailto:4.2.0a@1:4.2.0a+stable-8-r>
and after copying them into my machine ( a typical linux machine ) , I
could get the synchronization with the local reference clock
successfully. Please see the below ntp.log statements :

 

16 Feb 08:54:33 ntpd[12066]: attempt to configure invalid address
127.127.1.0

16 Feb 08:54:33 ntpd[12066]: inappropriate address 127.127.1.0 for the
fudge command, line ignored

16 Feb 09:09:10 ntpd[12066]: ntpd exiting on signal 15

16 Feb 09:10:04 ntpd[12180]: frequency initialized 0.000 PPM from
/XXX/ntp.drift

16 Feb 09:13:18 ntpd[12180]: synchronized to LOCAL(0), stratum 10

16 Feb 09:13:18 ntpd[12180]: kernel time sync disabled 0041

16 Feb 09:14:24 ntpd[12180]: kernel time sync enabled 0001

 

So, I got the synchronization with the local reference clock after ~3.14
mins ( i.e. ~ 4 polls delay ) !!!!

 

 

Then, I walked into the source code of ntpd/ ntp-4.2.6p3 , I found that
the macro REFCLOCK is not defined. My question here is when and where
this macro REFCLOCK is defined ..??

 

I've  tried to define the  macro REFCLOCK in the Makefile of ntpd , I
could end up with below errors in ntp.log only without any
synchronization to the local reference clock.

 

16 Feb 07:42:00 ntpd[11518]: refclock_newpeer: clock type 1 invalid

16 Feb 07:42:00 ntpd[11518]: 127.127.1.0 interface 127.0.0.1 -> (none)

 

I 've even tried with the release version of 4.2.0a, still I couldn't
get the synchronization with the local reference clock ( However, I
could get the synchronization with the 4.2.0a@1:4.2.0a+stable-8-r
<mailto:4.2.0a@1:4.2.0a+stable-8-r>   !!!! ).

 

I would need your help in solving the above issue on the latest release
i.e. 4.2.6p3 or even on the 4.2. 0a release version. 

 

Note : I've made sure that RTC of the local clock is in sync with the
system time always.

 

 

Regards,

Gayatri Prasad
0
Reply Kovvali 2/18/2011 12:06:00 PM

At 07:06 AM 2/18/2011, Kovvali, Gayatri P (GE Energy) wrote...
>I'm facing  NTP server synchronization issues  with my local reference
>clock...
>  #Using Local Clock as NTP sync source
>server 127.127.1.0
>fudge 127.127.1.0 stratum 10

You do know that your PC's clock isn't a very good reference, at all. 
You would do much better syncing to a public server.

>16 Feb 08:54:33 ntpd[12066]: attempt to configure invalid address
>127.127.1.0
>
>16 Feb 08:54:33 ntpd[12066]: inappropriate address 127.127.1.0 for the
>fudge command, line ignored...
>Then, I walked into the source code of ntpd/ ntp-4.2.6p3 , I found 
>that
>the macro REFCLOCK is not defined. My question here is when and where
>this macro REFCLOCK is defined ..??

../configure --help 
0
Reply mikes 2/18/2011 2:34:37 PM


1 Replies
980 Views

(page loaded in 7.935 seconds)

Similiar Articles:













7/20/2012 4:58:39 PM


Reply: