Re: Bad File Descriptor



At about the time of 8/6/2005 8:26 AM, mike stated the following:

> Daniel Rudy wrote:
>
>>Hello,
>>
>> I'm having an issue with ntp 4.2.0-a on FreeBSD 5.4-p4 system. It
>>seems that ntpd is recording bad file descriptor errors in the system
>>log. This seems to happen every 9-10 minutes or so. I have a copy of
>>the logs below as well as my /etc/ntp.conf file. This has been going on
>>for awhile now, and I'm not sure when it started. Any idea as to what
>>is causing this problem?
>>
>>Any help is appriciated. Thank you.
>>
>
>
> I have not checked the code, but you appear to have a very
> pesssimistic list of servers. As this is just something that appears
> intermittently it may be related to the number you have defined.
> Five should be enough even for the purists. Try that and see if it fixes
> the issue.

New Config File:

wildfire:/etc 1033 ### ->cat ntp.conf
#server time.windows.com iburst
#server clepsydra.dec.com iburst
#server time.xmission.com iburst
#server ntp2.sth.netnod.se iburst
#server ntp2.sp.se iburst
server bitsy.mit.edu iburst
server clock.via.net iburst
server clock.isc.org iburst
server us.pool.ntp.org iburst

restrict 192.168.0.0 mask 255.255.255.0 nopeer nomodify notrap kod
restrict 127.0.0.1 mask 255.0.0.0



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.

wildfire:/etc 1034 ### ->/usr/sbin/ntpd --version
/usr/sbin/ntpd: ntpd 4.2.0-a Tue Jul 19 00:50:14 PDT 2005 (1)

wildfire:/etc 1035 ### ->uname -a
FreeBSD wildfire..org 5.4-RELEASE-p4 FreeBSD 5.4-RELEASE-p4 #4: Tue Jul
19 02:29:40 PDT 2005 root@strata:/usr/obj/usr/src/sys/WILDFIRE i386


--
Daniel Rudy

Email address has been encoded to reduce spam.
Remove all numbers, then remove invalid, email, no, and spam to reply.
.



Relevant Pages

  • Re: Bad File Descriptor
    ... seems that ntpd is recording bad file descriptor errors in the system log. ... #server clepsydra.dec.com iburst ...
    (comp.protocols.time.ntp)
  • Bad File Descriptor
    ... seems that ntpd is recording bad file descriptor errors in the system ... server clepsydra.dec.com iburst ...
    (comp.protocols.time.ntp)
  • Re: Bad File Descriptor
    ... seems that ntpd is recording bad file descriptor errors in the system log. ... server clepsydra.dec.com iburst ...
    (comp.protocols.time.ntp)
  • Re: Meinberg NTP Software--Time Accuracy
    ... I would guess that possible server locations can be found ... server 0.us.pool.ntp.org preempt iburst ... you can use the pool commands. ...
    (comp.protocols.time.ntp)
  • Are these Windows XP clients beyond hope?
    ... It's OK to use iburst. ... I administer 2 small networks, both consisting of a mix of Fedora Linux ... servers and Windows 2K/XP workstations, ... server kermit.local iburst ...
    (comp.protocols.time.ntp)