IZ80108: PLINUX WITH NO DNS THROWS UNKNOWNHOSTEXCEPTION

IBM Tivoli Monitoring 6.2.2 Fix Pack 8 (6.2.2-TIV-ITM-FP0008)
IBM Tivoli Monitoring 6.2.2 Fix Pack 9 (6.2.2-TIV-ITM-FP0009)
IBM Tivoli Monitoring 6.2.2 Fix Pack 6 (6.2.2-TIV-ITM-FP0006)

APAR status

• Closed as program error.

Error description

• When remotely deploying, or locally configuring, agents using
  XML properties in the configuration, the cfg file is generated
  with an incorrect file name. The string "unknown" is included
  in the file name where the local host name should be.
  You will also notice messages like the following in the
  itm_install.trc and itm_config.trc log files:
  
  2010-07-02 14:41:13.138-05:00
  
  com.ibm.tivoli.monitoring.install.cmdline.KinCmdLineConfig
  KinCmdLineConfigConstructor __ERROR__  (traceKey:1278096073138)
  java.net.UnknownHostException: nyeste4: nyeste4
  at java.net.InetAddress.getLocalHost(InetAddress.java:1476)
  at com.ibm.tivoli.monitoring.install.cmdline.KinCmdLineConfig
     .KinCmdLineConfigConstructor(KinCmdLineConfig.java:127)
  at com.ibm.tivoli.monitoring.install.cmdline.KinCmdLineConfig
     .<init>(KinCmdLineConfig.java:93)
  at com.ibm.tivoli.monitoring.install.cmdline.KinCmdLineConfig
     .runConsole(KinCmdLineConfig.java:405)
  at com.ibm.tivoli.monitoring.install.KinPlugin.ttyConfig
     (KinPlugin.java:77)
  at ITMinstall.CandleConfigAgent.main(CandleConfigAgent.java:721)
  RECREATE INSTRUCTIONS:
  
  
  1) Login to a pLinux RH5 system as root.
     This problem has not been recreatable on other Linux RH5
     platforms with the same network configuration.
  2) Modify /etc/hosts
     Make a backup copy of the file before modifying it.
     Ensure that there is a valid entry for this system.
     Ensure that there are entries for all of the systems you will
     need to communicate with.
  3) Modify /etc/nsswitch.conf
     Make a backup copy of the file before modifying it.
     Ensure that the hosts entry is one of the following forms
     only:
     hosts:      files
  
      hosts:     files dns
  4) Modify /etc/resolv.conf
     Make a backup copy of the file before modifying it.
     Empty the file
  5) Run the following command to empty the name server cache:
     service nscd restart
  6) Run the following commands to verify that only the entries in
     /etc/hosts are being used for host resolution:
     getent hosts localhost
     getent hosts <thisHostName>
     getent hosts <thisHostIP>
     getent hosts builderbob   (assuming that builderbob in not
     defined)
  
  
  
  7) Install ITM 6.2.2 FP2 OS agent
  8) Install Agent Builder agent
  9) Install ITCAM for DB2 monitoring agent 6.2.2
  10) Configure the DB2 monitoring agent
  11) Notice a message similar to that mentioned above in the
      itm_config.trc log.
  

Local fix

• For any unknown_*.cfg files create correctly named symbolic
  links using the local hostname instead of "unknown".
  
  The following is an example of commands which will run in sh,
  bash, ksh:
  NOTE: CANDLEHOME must be set properly for the commands to work.
  
  cd $CANDLEHOME/config
  here=`pwd`
  lhost=`hostname | cut -d. -f1 | tr 'A-Z' 'a-z'`
  LHOST=`hostname | cut -d. -f1 | tr 'a-z' 'A-Z'`
  for file in unknown_*.cfg
  do
   suff=`echo $file | cut -d_ -f2-`
   nlink=${lhost}_$suff
   NLINK=${LHOST}_$suff
   ln -s $here/$file $nlink
   ln -s $here/$file $NLINK
  done
  

Problem summary

• On a Linux for System/P with no DNS configured, an
  UnknownHostException is thrown when attempting to configure an
  agent.
  
  
  When remotely deploying or locally configuring agents using XML
  properties in the configuration, the configuration file is
  generated with an incorrect file name.  The string "unknown" is
  included in the file name where the local host name should be.
  You will also notice messages like the following in the
  itm_install.trc and itm_config.trc log files:
  
  com.ibm.tivoli.monitoring.install.cmdline.KinCmdLineConfig
  KinCmdLineConfigConstructor __ERROR__  (traceKey:1278096073138)
  java.net.UnknownHostException: nyeste4: nyeste4
  at java.net.InetAddress.getLocalHost(InetAddress.java:1476)
  at
  com.ibm.tivoli.monitoring.install.cmdline.KinCmdLineConfig.KinCm
  dLineConfigConstructor(KinCmdLineConfig.java:127)
  at
  com.ibm.tivoli.monitoring.install.cmdline.KinCmdLineConfig.<init
  >(KinCmdLineConfig.java:93)
  at
  com.ibm.tivoli.monitoring.install.cmdline.KinCmdLineConfig.runCo
  nsole(KinCmdLineConfig.java:405)
  at
  com.ibm.tivoli.monitoring.install.KinPlugin.ttyConfig(KinPlugin.
  java:77)
  at ITMinstall.CandleConfigAgent.main(CandleConfigAgent.java:721)
  

Problem conclusion

• On machines that are not configured to use DNS to resolve
  hostnames, the Java API "InetAddress.getLocalHost" will throw an
  UnknownHostException.
  
  The code has been modified to use the system hostname command to
  configure the agent correctly.
  
  
  The fix for this APAR is contained in the following maintenance
  packages:
  
    | fix pack | 6.2.2-TIV-ITM-FP0003
  

Temporary fix

Comments

APAR Information

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

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

Fix information

• Fixed component name

  OMEG DIST INSTA

• Fixed component ID

  5608A41CI

Applicable component levels

• R622 PSY

     UP