[ntp:questions] Re: Is ntp working?

Richard B. Gilbert rgilbert88 at comcast.net
Thu Oct 20 13:53:58 UTC 2005


Steven Meres wrote:

>I'm using a debian sarge dist of linux on a dual opteron file server named
>'fserver'.
>
>Ultimately I would like to have fserver to supply the time to all the other
>machines on the LAN.
>
>Currently this is the results of my /var/log/ntpd.log file. Something tells
>me something is not right.
>
> 
>
>19 Oct 08:20:50 ntpd[4226]: synchronized to LOCAL(0), stratum 13
>
>19 Oct 08:20:50 ntpd[4226]: kernel time sync disabled 0041
>
>19 Oct 08:21:05 ntpd[3985]: sendto(69.37.143.241): Bad file descriptor
>
>19 Oct 08:21:07 ntpd[3985]: sendto(131.211.80.155): Bad file descriptor
>
>19 Oct 08:21:48 ntpd[4226]: sendto(131.211.80.155): Bad file descriptor
>
>19 Oct 08:21:52 ntpd[4226]: sendto(84.16.227.206): Bad file descriptor
>
>19 Oct 08:21:55 ntpd[4226]: kernel time sync enabled 0001
>
>19 Oct 08:22:09 ntpd[3985]: sendto(69.37.143.241): Bad file descriptor
>
>19 Oct 08:22:10 ntpd[3985]: sendto(131.211.80.155): Bad file descriptor
>
>19 Oct 08:22:52 ntpd[4226]: sendto(131.211.80.155): Bad file descriptor
>
>19 Oct 08:22:56 ntpd[4226]: sendto(84.16.227.206): Bad file descriptor
>
>19 Oct 08:23:55 ntpd[4226]: sendto(131.211.80.155): Bad file descriptor
>
>19 Oct 08:24:00 ntpd[4226]: sendto(84.16.227.206): Bad file descriptor
>
>19 Oct 08:24:16 ntpd[3985]: sendto(131.211.80.155): Bad file descriptor
>
>19 Oct 08:24:18 ntpd[3985]: sendto(69.37.143.241): Bad file descriptor
>
>19 Oct 08:24:40 ntpd[3881]: sendto(132.236.56.250): Bad file descriptor
>
>19 Oct 08:24:44 ntpd[3881]: sendto(140.162.8.3): Bad file descriptor
>
>19 Oct 08:24:46 ntpd[3881]: sendto(199.212.17.20): Bad file descriptor
>
>  
>
<snip>

Well, through bad luck or poor design,  you have servers in the 
Netherlands, Australia and, I think, in the US.
It is highly desirable to have servers relatively close to you and these 
don't look as if they are close.  I believe that there is a syntax for 
specifying pool servers in the US which should get better results if you 
are in the US.  You can specify other general areas of the world; e.g. 
Europe, as well.

The log output doesn't suggest what the problem is or what to do about it.

Try posting your ntp.conf file and the output of ntpq -p after ntp has 
been running for at least fifteen or twenty minutes (more is better).   
Also post the output of ntpq -c version which should tell us what 
version of ntpd we are dealing with.




More information about the questions mailing list