websphere probe will not start and throws Max. restarts error
search cancel

websphere probe will not start and throws Max. restarts error

book

Article ID: 377977

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM) CA Unified Infrastructure Management On-Premise (Nimsoft / UIM) CA Unified Infrastructure Management SaaS (Nimsoft / UIM)

Issue/Introduction

Need some assistance setting up the websphere probe on 2 AIX servers. I keep getting Max. restarts reached for probe 'websphere' (command = runprobe.sh) 

Error in the websphere log when the websphere probe is activated:

Controller: Max. restarts reached for probe 'websphere' (command = runprobe.sh)

Environment

  • DX UIM 20.4 or higher
  • AIX 7.2
  • websphere probe v1.85
  • WAS 8.5
  • Robot 9.40

Cause

  • Java configuration on the robot and the IBM WAS server

Resolution

Verify Java Installation

Install Java version 6 or higher from IBM on the computer running the probe and include the java executable in the probe path. You can also copy the Java folder from the WebSphere server directory to the remote Windows computer on which the websphere probe is installed.

Java JRE 6 and above is available with WAS 7.0 and above and you can use the same path for java_home.

Search for -> libjava.so

You can configure the JVM and Java Home settings to install the probe on a UNIX OS, in this case, AIX.


Follow these steps on the robot where the websphere probe is installed:

Set the JAVA_HOME environment variable to the directory in which IBM JVM is installed and export JAVA_HOME.

For example,

   export JAVA_HOME=/usr/lib/jvm/ibm-java2-i386-50/jre/bin

Ensure that the PATH variable includes $JAVA_HOME. For example,

   export PATH=$JAVA_HOME:$PATH

Open a shell as a root user and run the command java -version. The output shows the IBM JVM installed.

Setup Java Home and PATH variable, for example:

   export JAVA_HOME=/usr/lib/jvm/ibm-java2-i386-50/jre/bin

   export PATH=$JAVA_HOME:$PATH

Check this file in the websphere folder-> runprobe.err

   $NIM_ROOT/$NIM_JRE_HOME = $JAVA_HOME

On the websphere server:

There were different folders for each hosted application on the WAS server, so when we created a resource we referenced/used the following app from the list of many apps:

   /opt/was85/base/crm/java_1.8_64/bin 

A resource is a WAS instance to be monitored, and is identified with either the host name or the IP address. You can also add a cluster of the WAS as a resource to monitor.

You can create separate resources for each cluster node to achieve a systematic monitoring environment. Note that if it’s a WAS ‘cluster’ you normally have to use a different default port.

Set PMI to High on the WAS server

Activate Statistic Set Automatically on PMI: sets the Performance Monitoring Infrastructure (PMI) to a level so that the probe can access all the monitors. By default, the PMI level that the WebSphere server administrator defines might deny the probe access to some monitors.

Configuring the PMI

On the AIX system where WAS is running:

/usr/java8_64/jre

cd lib

Look for the libjava.so file, e.g., find . -name libjava.so

Setup JAVA home and provide the right path to the JRE on the machine

   JAVA_HOME=/usr/java8_64/jre/bin

   export PATH=$JAVA_HOME:$PATH

Then run->java –version to recheck the version.

Note:

There will be JAVA installed on the robot/machine where the websphere probe is deployed AND on the Websphere Application Server (WAS) to be monitored and they may have different paths.

After configuring java on the robot where the websphere probe is deployed,

LIB and JAVA HOME paths will need to be entered when configuring the probe using the websphere probe wizard.

In the websphere probe folder,e.g., at /opt/nimsoft/probes/application/websphere open the runprobe.err file to view the error log.

 

Edit runprobe.sh

Set Java Home in runprobe.sh if the error log shows that the java is 'not found.'

For example, add the following lines:

   export JAVA_HOME=/usr/java8_64/jre

   export PATH=$JAVA_HOME:$PATH

and change the $NIM_JRE_HOME to the related path, e.g., /usr/java8_64/jre

#!/bin/sh
CLASSPATH=jar/websphere.jar
export CLASSPATH
echo NIM_ROOT=$NIM_ROOT > .properties
echo NIM_DEVICE_ID=$NIM_DEVICE_ID >> .properties
$NIM_ROOT/$NIM_JRE_HOME/bin/java -DNIMV_CONTIP=$NIM_ROBOT_IP -DMY_NAME=websphere -DNIMCPRID=$NIMCPRID -DNIM_PROBE_KEY=$NIM_PROBE_KEY -DNIMPROBEPORT=$NIMPROBEPORT com.nimsoft.nimbus.probe.application.extractbase.Bootstrap $1 $2 $3 $4 $5 2>runprobe.err
cat runprobe.err >> $2.log

The path for the Nimsoft java jre in this case should be pointing to the IBM java configured on the system (path for JAVA_HOME on the Unix system). So, replace...

$NIM_ROOT/$NIM_JRE_HOME

with

${JAVA_HOME}/bin/java


and save the updated runprobe.sh file.

Then using the Infrastructure Manager (IM), rt-click and Activate the websphere probe, and rt-click to view the log. The log should now recover from the Max. restarts error and show that it is starting...

*****************Starting*****************

[main, websphere] 1.85 - base: 2.0.4
[main, websphere] Nimsoft
[main, websphere] port=48011
[main, websphere] Login to NimBUS is OK

Make sure the probe is green and has a port and a PID.

Then double-click the websphere probe to open the GUI and begin the configuration using the wizard.

Remote Monitoring

If the probe is not on the same systems as the WAS, copy the lib folder path into the window otherwise you can Browse to the folder(s) to add the paths.

If WAS is on a different machine/server, login to the WAS and look for and document the location of those two folders.

When prompted by the websphere wizard, select the WAS version.

Then identify the location of the WAS profiles for different applications – they may be in different folders so check.

Library folder:
/opt/was85/base/crm

Java home folder:
/opt/was85/base/crm/java_1.8_64/bin

Click Next.

If it’s misconfigured the font will turn red within the wizard window which shows the results. If it’s successfully configured, the font will remain black and java home and lib references will finish as ‘Ok’

Click Finish.

Then click Ok.

The websphere probe will restart.

Create a Resource

Then double-click the websphere probe to open it and create a resource, enter the hostname or IP address and port for the WAS server.

Add the username and password. (Administrative privileges are required)

If the username and password are incorrect, an error will occur.

Also contact your WAS admin to check and make sure PMI is set to High to allow all WAS metrics to be enabled and monitoring.

Note: If Illumio is installed: it is a security/whitelisting app which may require whitelisting the WAS app.

websphere Release Notes

Websphere monitoring configuration (via Admin Console versus IM)

Additional Information

Techdoc updated:

Setting the Java Path On UNIX/AIX 7.1/7.2

You can configure the probe to use OS specific JVM instead of jre shipped with Nimsoft 

Follow these steps:

  1. Deactivate the websphere probe

  2. Set the JAVA_HOME environment variable to the directory in which IBM JVM is installed and export JAVA_HOME.
    For example->     export JAVA_HOME=/usr/lib/jvm/ibm-java2-i386-50/jre/bin

  3. Ensure that the PATH variable includes $JAVA_HOME. For example,

    export PATH=$JAVA_HOME:$PATH

  4. Open a shell as a root user and run the command java - version.

  5. The output shows the IBM JVM version installed.

  6. Change the java path on the runprobe.sh

  7. Got to Nimsoft_home/probes/application/webshere

  8. Edit runprobe.sh 

Replace $NIM_ROOT/$NIM_JRE_HOME with  ${JAVA_HOME}

Save the runprobe.sh and activate the probe 

Powered by Wolken Software