Max restarts error for processes probe on Solaris

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

Processes probe does not start on Solaris server and errors as below in the porcesses log

Oct 29 21:29:45:928 [0001] Controller: Max. restarts reached for probe 'processes' (command = processes)
Oct 29 21:32:24:183 processes: ****************[ Starting ]****************
Oct 29 21:32:24:183 processes: processes 3.92, Mar 24 2015
Oct 29 21:32:24:183 processes: Nimsoft Corporation, Copyright @ 1998-2010
Oct 29 21:32:25:255 processes: port=48007 PID=14771
Oct 29 21:32:25:257 processes: CheckFile -  /usr/ucb/ps (No such file or directory)
Oct 29 21:32:25:257 processes: ProcLibStart - can't run without ucb ps

Environment

Release: CNMSPP99000-7.6-Unified Infrastructure Mgmt-Server Pack-- On Prem
Component:

Cause

Earlier versions of the Solaris ps command were limited to 80 columns and those versions of Solaris installed the ucb library by default.  The ucb library contained a BSD-style ps command that allowed wider column output.

The processes probe was written with the ability to take advantage of this additional library.

At some point, Solaris stopped installing the ucb library and therefore, if the processes probe is configured to rely on it, it may fail to start if the library doesn't exist.

 

Resolution

One of two solutions will need to be implemented:

• Install the ucb library
• Reconfigure the probe to not require the library

 

Installing the ucb library

If the probe is installed on an older version of Solaris, it may be necessary to use and install the ucb library.

First, add the Oracle library to the publisher list

# pkg set-publisher -G '*' -M '*' -g http://pkg.oracle.com/solaris/release solaris

Next install the compatibility library

# pkg install compatibility/ucb

Restart the processes probe and it should launch successfully.

 

Reconfiguring the probe

If the probe is installed on a newer version of Solaris which does not have the ucb library,  then it may be possible to remove that requirement from the probe

1. Open the Raw Configure window by highlighting the probe and holding the Shift key while Right Clicking on the probe.
2. Choose Raw Configure
3. Click "Edit Configuration File" if the window appears that gives the option
4. Click the setup section
5. Click the extended_cmdline key
6. Click Edit Key
7. Change the value to no
8. Click OK
9. Click OK

Restart the processes probe and it should launch successfully.