ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Wasp probe for UMP system will not start


Article ID: 102855


Updated On:


DX Unified Infrastructure Management (Nimsoft / UIM) NIMSOFT PROBES


The UMP wasp was restarted due to some issues with unresponsiveness.

The probe would not restart, so it was deactivated and reactivated.

The probe never fully restarted (meaning it never gets a port assignment)

Followed instructions in

KB000007118 : WASP module don't start

and configured all portlets except usm and ROOT to not start automatically, but the wasp probe still does not start.
No errors are reported in either the portal.log or wasp,.log during the probe startup.

The last lines recorded in the wasp.log file at loglevel 5 are:

INFO  [localhost-startStop-1, org.apache.catalina.core.ContainerBase.[wasp-engine].[localhost].[/]] Initializing Spring root WebApplicationContext
INFO  [localhost-startStop-1, org.apache.catalina.core.ContainerBase.[wasp-engine].[localhost].[/]] Initializing Spring FrameworkServlet 'Remoting Servlet'


Prior to the initial restart of the UMP wasp probe, the portal.log file was filled with errors similar to the following:

Received status (120) on response (for sendRcv) for cmd = 'get_next_fire_time_for_schedules'

This indicates that the UMP wasp probe was failing to execute this callback command in the maintenance_mode probe on the primary hub.
There were no outward indications that this probe was having problems when viewed in Infrastructure Manager or Admin Console.


UIM/UMP 8.51


Deactivated the UMP wasp probe.
Rebooted the primary hub server and verified that all of the core probes successfully started (show green status and values for both the PID and port when viewed in Infrastructure Manager or Admin Console)
Activated the UMP wasp probe.