This article provides a solution to an issue where the wasp probe ends up in a failed state when it fails to locate the data_engine probe or throws a Max. restarts error and does not start up successfully.
The wasp.log, and/or _wasp.log files will show similar errors to the below snippet:
[main, com.nimsoft.nimbus.NimProbeBase] Login to NimBUS is OK
[main, com.nimsoft.nimbus.probe.service.wasp.WaspNimProbe] WaspNimProbe login successful.
[main, com.nimsoft.nimbus.probe.service.wasp.Probe] Connection String: null
[main, com.nimsoft.nimbus.probe.service.wasp.Probe] Cannot obtain connection string from data_engine
[main, com.nimsoft.nimbus.probe.service.wasp.Probe] (4) not found, Received status (4) on response (for sendRcv) for cmd = 'nametoip' name = 'data_engine'
at com.nimsoft.nimbus.NimSessionBase.sendRcv(NimSessionBase.java:610)
at com.nimsoft.nimbus.NimSessionBase.sendRcv(NimSessionBase.java:561)
The wasp probe will be in an error state (no PORT, no PID and in red status)
or you will see errors such as:
ERROR [main, com.nimsoft.nimbus.probe.service.wasp.Probe] main() Fatal error!
ERROR [main, com.nimsoft.nimbus.probe.service.wasp.Probe] main() (1) error, Database Information is null
ERROR [main, com.nimsoft.nimbus.probe.service.wasp.Probe] (1) error, Database Information is null
at com.nimsoft.nimbus.probe.service.wasp.Probe.doit(Probe.java:327)
at com.nimsoft.nimbus.probe.service.wasp.Probe.main(Probe.java:119)
[5976] Controller: Max. restarts reached for probe 'wasp' (command = <startup java>)
or
INFO [main, com.nimsoft.nimbus.NimProbeBase] Login to NimBUS is OK
INFO [main, com.nimsoft.nimbus.probe.service.wasp.WaspNimProbe] WaspNimProbe login successful.
INFO [main, com.nimsoft.nimbus.probe.service.wasp.Probe] Connection String:
DEBUG [main, com.nimsoft.nimbus.lookup.DataEngineLookup] Request to probe "/<domain>/<hub>/<robot>/data_engine" callback get_connection_string was successful.
DEBUG [main, com.nimsoft.nimbus.utils.FileUtils] In FileUtils.getFileChecksum
DEBUG [main, com.nimsoft.nimbus.utils.FileUtils] local certificate store FileChecksum - 561c2ed21da6f084266d3c3b67950e09
[7096] Controller: Max. restarts reached for probe 'wasp' (command = <startup java>)
Upon review of the wasp.cfg, either the probe is pointing to the following location to locate the probe:
data_engine = data_engine
or there is no data_engine parameter and value defined in the wasp.cfg.
This is incorrect. The wasp is usually deployed to a separate robot which attaches to and is under the Primary hub system and in this use case the key should contain the full NimBUS address of the data_engine, for example here is the syntax:
data_engine = /<uim_domain>/<primary_hub_name>/<primary_hub_robot_name>/data_engine
1. Go to the Primary hub server, right click on the data_engine probe, go to the bottom line for "Edit" and select "Copy to Clipboard"
2. Open a notepad file and paste the contents. Locate the data_engine probe string.
e.g., "/<uim_domain>/<primary_hub_name>/<primary_hub_robot_name>/data_engine"
3. Copy the probe connection string
4. Open the wasp probe in Raw Configure mode, and under the setup section, locate the data_engine key and edit the key
5. Enter the data_engine NimBUS address:
e.g., "data_engine = /<domain>/<hub>/<robot>/data_engine"
6. Click Apply to apply the changes and Save.
7. Restart the robot service of the OC robot system/Deactivate-Activate the wasp probe.
8. Check the wasp log at loglevel 5 to see if the issue is resolved.