IV64152: SECONDARY NODE CAN'T BIND TO THE NAME SERVER

7.1.0-TIV-NCI-ZLINUX-FP0006
7.1.0-TIV-NCI-WINDOWS-FP0006
7.1.0-TIV-NCI-SOLARIS-FP0006
7.1.0-TIV-NCI-LINUX-FP0006
7.1.0-TIV-NCI-AIX-FP0006
6.1.1-TIV-BSM-FP0004-windows
6.1.1-TIV-BSM-FP0004-zlinux
6.1.1-TIV-BSM-FP0004-solaris
6.1.1-TIV-BSM-FP0004-linux
6.1.1-TIV-BSM-FP0004-aix
6.1.1-TIV-NCI-FP0004-windows
6.1.1-TIV-NCI-FP0004-zlinux
6.1.1-TIV-NCI-FP0004-solaris
6.1.1-TIV-NCI-FP0004-aix
6.1.1-TIV-NCI-FP0004-linux
7.1.0-TIV-NCI-ZLINUX-FP0005
7.1.0-TIV-NCI-LINUX-FP0005
7.1.0-TIV-NCI-WINDOWS-FP0005
7.1.0-TIV-NCI-SOLARIS-FP0005
7.1.0-TIV-NCI-AIX-FP0005
6.1.1-TIV-BSM-FP0003-aix
6.1.1-TIV-NCI-FP0003-zlinux
6.1.1-TIV-NCI-FP0003-windows
6.1.1-TIV-NCI-FP0003-solaris
6.1.1-TIV-NCI-FP0003-linux
6.1.1-TIV-NCI-FP0003-aix
6.1.1-TIV-BSM-FP0003-zlinux
6.1.1-TIV-BSM-FP0003-windows
6.1.1-TIV-BSM-FP0003-solaris
6.1.1-TIV-BSM-FP0003-linux
6.1.1-TIV-BSM-FP0002-windows
6.1.1-TIV-BSM-FP0002-zlinux
6.1.1-TIV-BSM-FP0002-solaris
6.1.1-TIV-BSM-FP0002-aix
6.1.1-TIV-BSM-FP0002-linux
6.1.1-TIV-NCI-FP0002_zlinux
6.1.1-TIV-NCI-FP0002_windows
6.1.1-TIV-NCI-FP0002_solaris
6.1.1-TIV-NCI-FP0002_linux
6.1.1-TIV-NCI-FP0002_aix
IBM Tivoli Netcool/Impact V6.1.1 Fix Pack 2 (6.1.1-TIV-NCI-FP0002)
IBM Tivoli Netcool/Impact V7.1.0 Fix Pack 2(7.1.0-TIV-NCI-FP0002)
IBM Tivoli Business Service Manager V6.1.1 Fix Pack 3(6.1.1-TIV-BSM-FP0003)
IBM Tivoli Netcool/Impact V6.1.1 Fix Pack 3 (6.1.1-TIV-NCI-FP0003)
IBM Tivoli Netcool/Impact V7.1.0 Fix Pack 3(7.1.0-TIV-NCI-FP0003)
IBM Tivoli Netcool/Impact V7.1.0 Fix Pack 5(7.1.0-TIV-NCI-FP0005)
IBM Tivoli Netcool/Impact V6.1.1 Fix Pack 4 (6.1.1-TIV-NCI-FP0004)
IBM Tivoli Business Service Manager V6.1.1 Fix Pack 4(6.1.1-TIV-BSM-FP0004)
IBM Tivoli Netcool/Impact V7.1.0 Fix Pack 6(7.1.0-TIV-NCI-FP0006)
IBM Tivoli Netcool/Impact V7.1.0 Fix Pack 7(7.1.0-TIV-NCI-FP0007)
IBM Tivoli Netcool/Impact V7.1.0 Fix Pack 8(7.1.0-TIV-NCI-FP0008)
IBM Tivoli Netcool/Impact V7.1.0 Fix Pack 9(7.1.0-TIV-NCI-FP0009)
IBM Tivoli Netcool/Impact V7.1.0 Fix Pack 10(7.1.0-TIV-NCI-FP0010)
IBM Tivoli Netcool/Impact V7.1.0 Fix Pack 11(7.1.0-TIV-NCI-FP0011)
IBM Tivoli Netcool/Impact V6.1.1 Fix Pack 5 (6.1.1-TIV-NCI-FP0005)
IBM Tivoli Business Service Manager V6.1.1 Fix Pack 5(6.1.1-TIV-BSM-FP0005)
IBM Tivoli Netcool/Impact V7.1.0 Fix Pack 12 (7.1.0-TIV-NCI-FP0012)
IBM Tivoli Netcool/Impact V7.1.0 Fix Pack 13 (7.1.0-TIV-NCI-FP0013)

APAR status

• Closed as program error.

Error description

• During fail-over, secondary node is unable to lookup thenode
  table on the nameserver due to interrupted thread, resulting in
  error:
  
  07 Jul 2014 11:36:03,560 DEBUG [UddiClusterBootStrapper] The
  primary
  info for cluster 'NCICLUSTER' is available, hostInfo =
  172.31.120.77:57188
  07 Jul 2014 11:36:03,560 ERROR [UddiClusterBootStrapper] Unable
  to
  lookup the ClusterPrimaryIfc 'NCICLUSTER'
  java.lang.InterruptedException at
  java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquire
  SharedNa
  nos(AbstractQueuedSynchronizer.java:1313) at
  java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:23
  8)
  
  This condition is circunvented by enabling the following
  logging parameters:
  
  <context-param>
          <param-name>ENABLE_GENERAL_LOGGING</param-name>
          <param-value>true</param-value>
      </context-param>
  
      <context-param>
          <param-name>ENABLE_REQUEST_LOGGING</param-name>
          <param-value>true</param-value>
      </context-param>
  
      <context-param>
          <param-name>ENABLE_PING_LOGGING</param-name>
          <param-value>true</param-value>
      </context-param>
  

Local fix

• build 'nci201408272010v6110b512.jar' provided as workaround
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All Impact Users                                             *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * When the primary cluster member goes down, the secondary     *
  * member does not start processing events.                     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * None                                                         *
  ****************************************************************
  When the primary member goes down, the secondary member will try
  to become primary.  When the new secondary tries to register as
  the primary it can time out and not become primary.  This will
  cause events to not be processed since there is no running
  primary member.
  

Problem conclusion

• Changed the timeout so that the server will retry when trying to
  become primary if it fails.
  
  The fix for this APAR is contained in the following
  maintenance packages:
  |Fix Pack| 6.1.1-TIV-NCI-FP0002
  |Fix Pack| 7.1.0-TIV-NCI-FP0002
  

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:

Modules/Macros

• UNKNOWN
  

Fix information

• Fixed component name

  NETCOOL/IMPACT

• Fixed component ID

  5724O59IS

Applicable component levels

• R611 PSY

     UP

• R710 PSY

     UP