Getting error "Bad file descriptor" and "no reply; clock not set" in /var/log/messages on ntp server

Solution Verified - Updated -

Issue

  • Getting error "Bad file descriptor" messages in /var/log/messages for ntpd.

  • Getting error "no reply; clock not set" in /var/log/messages for ntpd.

    17 Nov 17:18:48 ntpd[13215]: ntpd exiting on signal 15
17 Nov 17:23:08 ntpd[13238]: synchronized to 203.200.188.4, stratum 2
17 Nov 17:23:08 ntpd[13238]: kernel time sync enabled 0001
17 Nov 17:23:09 ntpd[13416]: sendto(203.200.188.4) (fd=-1): Bad file descriptor
17 Nov 17:23:11 ntpd[13416]: sendto(203.200.188.4) (fd=-1): Bad file descriptor
17 Nov 17:23:13 ntpd[13416]: sendto(203.200.188.4) (fd=-1): Bad file descriptor
17 Nov 17:23:15 ntpd[13416]: sendto(203.200.188.4) (fd=-1): Bad file descriptor
17 Nov 17:23:17 ntpd[13416]: sendto(203.200.188.4) (fd=-1): Bad file descriptor
17 Nov 17:23:19 ntpd[13416]: sendto(203.200.188.4) (fd=-1): Bad file descriptor
17 Nov 17:23:21 ntpd[13416]: sendto(203.200.188.4) (fd=-1): Bad file descriptor
17 Nov 17:23:23 ntpd[13416]: sendto(203.200.188.4) (fd=-1): Bad file descriptor
17 Nov 17:23:25 ntpd[13416]: no reply; clock not set

Environment

  • Red Hat Enterprise Linux
  • ntp-4.2.2p1-9.el5_4.1
  • ntp-4.2.2p1-8.el5-x86_64

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content