IV37515: XNTPD NOT SYNCHRONIZING, LEAVING UNKILLABLE CHILD APPLIES TO AIX 6100-09

Fix pending

APAR status

• Closed as program error.

Error description

• When xntpd is delayed during its configuration phase (e.
  g.
  when DNS servers are not reachable) the child process it
  spawned may become unresponsive and unkillable. The
  parent
  process can be stopped, and another instance of xntpd can
  be started but the existing child will remain with init
  as parent.
  The process stack of the child shows that it is in
  pause()
  function.
  

Local fix

Problem summary

• xntpd may not syncronize with the host machine configured on
  ntp.conf file.  The process stack of the child process created
  by xntpd, will show it is waiting in pause() for ever.  -> ps
  -ef | grep xntpd
      root 4587552 6094944   0 00:45:10  pts/3  0:00 grep xntpd
      root 6226168 1310746   0 00:45:03      -  0:00
      /usr/sbin/xntpd root 6881392 6226168   0 00:45:03      -
      0:00 /usr/sbin/xntpd
  
  ->  procstack 6881392 6881392: /usr/sbin/xntpd 0xd01374d0
  pause() + 0x1f0 0x1003aecc  ntp_intres() + 0x16c 0x10001c04
  do_resolve_internal() + 0x144 0x10002d78  getconfig(??, ??) +
  0x318 0x10000638  main(??, ??) + 0x238 0x10000168  __start() +
  0x68
  

Problem conclusion

• Code modified to receive alarm signal.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

  IV33998

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  AIX 610 STD EDI

• Fixed component ID

  5765G6200

Applicable component levels

• R610 PSY U855283

     UP13/11/21 I 1000

PTF to Fileset Mapping

• U855283 bos.net.tcp.client 6.1.9.0