ntpd process bind() cannot assign requested address

Solution In Progress - Updated -

Environment

  • Red Hat Enterprise Linux 5

Issue

investigate a matter of the following log messages;

ntpd[3439]: bind() fd 19, family 10, port 123, scope 2, addr [ipv6 Addr], in6_is_addr_multicast=0 flags=1 fails: Cannot assign requested address

Resolution

The contents of the message were going to do the same period at the time using an address that a target address was not assigned or does not exist on a current machine when it perform synchronization of the time on a part equivalent to [ipv6 Addr], but it is in a message saying that it was impossible.

In other words it is judged that an applicable message was output because host received EADDRNOTAVAIL of error code 99 from bind() function when it was going to do string charge account (bind) to port 123 using an address of ipv6.
※ ntpd goes to refer to both ipv4, ipv6 addresses as synchronization at the time in specifications.

When there is not it and measures do not use ipv6 address on the network where an applicable host supports ipv6, it is thought that it does't carry out the map with the ipv6 address by ntp service with an effective method by unloading ipv6 module.

When there is not an applicable host in ipv6 address band and when it's going to map ipv6 address, for a cause, it occurs.

Ex.

With /etc/sysconfig/network file

NETWORKING_IPV6=yes is changed to NETWORKING_IPV6=no

or

With /etc/modprobe.conf file

alias net-pf-10 off
options ipv6 disable=1
  • Component
  • ntp

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Comments