wasp probe is down, would not restart

book

Article ID: 224742

calendar_today

Updated On:

Products

DX Infrastructure Management

Issue/Introduction

The Operator Console is currently down and the 'wasp' probe is red.

Max Restarts observed in the log along with the following:

Sep 24 14:57:56:034 INFO  [main, com.nimsoft.nimbus.NimProbeBase] Login to NimBUS is OK 
Sep 24 14:57:56:034 INFO  [main, com.nimsoft.nimbus.probe.service.wasp.WaspNimProbe] WaspNimProbe login successful. 
Sep 24 14:57:56:503 INFO  [main, com.nimsoft.nimbus.probe.service.wasp.Probe] Connection String: 7XtA/ZTvzjzxrq4YyYrcX4Jqpd470sVvEu9wAlp9cYChX31ICznlrWVmoNgSqKuFaeTdMxJGzZXuBkwWmFRJCw56EWxeG3A0rgXj6AsoeeHDs/DMLOdT+cs6MHzEQj3PRk4rdyzZYj3BSB53e3PgfDXYsrBF/yqUlk9Z0aMe4tVTZkuZgGoXEvs92pnry5rNjLzZl9vmPv8y2b/DvLvQgyuV+wGpeEVTjRvO8fDDT1E= 
Sep 24 14:57:56:503 WARN  [main, com.nimsoft.nimbus.probe.service.wasp.Probe] Cannot obtain connection string from data_engine 
Sep 24 14:57:56:503 WARN  [main, com.nimsoft.nimbus.probe.service.wasp.Probe] (4) not found, Received status (4) on response (for sendRcv) for cmd = 'nametoip' name = '/<domain>/<hub>/<robot>/data_engine' 
 at com.nimsoft.nimbus.NimSessionBase.sendRcv(NimSessionBase.java:622) 

Cause

The string used by the wasp probe to reach the data_engine probe is case sensitive.  When the incorrect case is used in the domain, hub, robot, or probe name, this issue will occur.

Environment

Release : 20.3

Component : UIM OPERATOR CONSOLE - WASP & CORE

Resolution

Make sure that the correct case is used in all UIM addresses.  With the correct case in the wasp configuration, the data_engine probe should be reachable to obtain the database connection string and the wasp probe should start.