[ntp:questions] Re: Bad File Descriptor

Danny Mayer mayer at gis.net
Mon Aug 8 03:40:25 UTC 2005


Daniel Rudy wrote:
> At about the time of 8/6/2005 8:26 AM, mike stated the following:
> 
> 
> Aug  7 13:01:06 wildfire ntpd[8337]: sendto(209.81.9.7): Bad file descriptor
> Aug  7 13:01:06 wildfire ntpd[8337]: sendto(24.130.207.189): Bad file
> descriptor
> Aug  7 13:01:07 wildfire ntpd[8337]: sendto(204.152.184.72): Bad file
> descriptor
> Aug  7 13:01:07 wildfire ntpd[8337]: sendto(18.72.0.3): Bad file descriptor
> Aug  7 13:01:08 wildfire ntpd[8337]: sendto(209.81.9.7): Bad file descriptor
> Aug  7 13:01:08 wildfire ntpd[8337]: sendto(24.130.207.189): Bad file
> descriptor
> Aug  7 13:01:09 wildfire ntpd[8337]: sendto(204.152.184.72): Bad file
> descriptor
> Aug  7 13:01:09 wildfire ntpd[8337]: sendto(18.72.0.3): Bad file descriptor
> Aug  7 13:01:10 wildfire ntpd[8337]: sendto(209.81.9.7): Bad file descriptor
> Aug  7 13:01:10 wildfire ntpd[8337]: sendto(24.130.207.189): Bad file
> descriptor
> 
> 
> Same problem with only 4 servers.  And as someone else suggested, I did
> remove the iburst option to no avail.
> 
None of this has anything to do with the servers. It's all about your 
local server and it's  attempt to send packets. Bad file descriptor 
means that the file descriptor you are attempting to use is bad. Someone 
else has pointed out you may have another instance running. 
Alternatively your IP address changed and the socket that was opened on 
the port is no longer valid and you need to restart ntpd.

Danny



More information about the questions mailing list