top of page

Business Monitor Support Cluster Will Not Start Due to Initialization Failure on Linux

If you are running your Business Monitor installation on Redhat Linux 6.x, you may encounter the following issue when trying to start your Support cluster members:

WSVR0501E: Error creating component com.ibm.ws.channelfw.secure.FirstChannelActions

java.lang.NoClassDefFoundError: com.ibmws.process.linuxutil.ThreadUtil (initialization failure)

Caused by: java.lang.NoClassDefFoundError: com.ibm.ws.process.linuxutil.ThreadUtil (initialization failure) at java.lang.J9VMInternals.initialize(J9VMInternals.java:168)


and see this in your FFDC logs:


FFDC Exception:java.lang.NoClassDefFoundError SourceId:null ProbeId:1011 Reporter:com.ibm.ws.runtime.component.ContainerHelper@81c1141 java.lang.NoClassDefFoundError: com.ibm.ws.process.linuxutil.ThreadUtil (initialization failure) Caused by: java.lang.UnsatisfiedLinkError: Ws60ProcessManagement (/opt/IBM/MonV8/cognos/bin64/libfreebl3.so: version `NSSRAWHASH_3.12.3′ not found (required by /lib64/libcrypt.so.1))

Fortunately, there is a fairly easy fix. It turns out that the libfreebl3.so file that is shipped with COGNOS 10.1.1 is not compatible with Redhat Linux 6.x. To resolve, you need to edit your .bashrc or .profile for the user id you are running Monitor under to include the following:


export LD_PRELOAD=/lib64/libfreebl3.so

Please see the following IBM Support document outlining the issue and the resolution:

http://www-01.ibm.com/support/docview.wss?uid=swg21612810

Share this:

  1. Facebook

  2. LinkedIn

  3. Twitter

  4. Email

#monitor #Supportcluster #initializationfailure #linux #businessmonitor #websphere

8 views0 comments
bottom of page