Wasp probe not starting on OC ( Operator Console) - Max. restarts reached for probe 'wasp'
Article ID: 111655
Updated On:
Products
Issue/Introduction
Wasp is not starting and you can see the following log messages in the log files:
wasp.log ( set to level 3 or more):
Aug 10 14:30:21:222 DEBUG [main, com.nimsoft.nimbus.utils.FileUtils] local certificate store FileChecksum - be4ae3a1cc51fc7ae682e3b231f22e3c
Aug 10 14:30:22:310 INFO [main, com.nimsoft.nimbus.NimProbeBase] Login to NimBUS is OK
Aug 10 14:30:22:311 INFO [main, com.nimsoft.nimbus.probe.service.wasp.WaspNimProbe] WaspNimProbe login successful.
Aug 10 14:30:22:420 INFO [main, com.nimsoft.nimbus.probe.service.wasp.Probe] Connection String: xxxxxxxxxxxx==
Aug 10 14:30:22:435 DEBUG [main, com.nimsoft.nimbus.lookup.DataEngineLookup] Request to probe "/xxxxx/HUB1/data_engine" callback get_connection_string was successful.
Aug 10 14:30:24:794 DEBUG [main, com.nimsoft.nimbus.utils.FileUtils] In FileUtils.getFileChecksum
Aug 10 14:30:24:795 DEBUG [main, com.nimsoft.nimbus.utils.FileUtils] local certificate store FileChecksum - be4ae3a1cc51fc7ae682e3b231f22e3c
Aug 10 14:30:25:788 [140716923103040] Controller: Max. restarts reached for probe 'wasp' (command = <startup java>)
Aug 10 14:50:08:057 [140716923103040] Controller: Max. restarts reached for probe 'wasp' (command = <startup java>)
Aug 10 16:44:35:353 [140716923103040] Controller: Max. restarts reached for probe 'wasp' (command = <startup java>)
Environment
Release: DX UIM 20.4.x / 23.4.x
Component: OC & CABI wasp
Resolution
The UIM Server installer creates a .pem file (certificate.pem) in the <Nimsoft>\security folder.
The .pem file is a symmetric key that is shared with the required robots, which is then used for communication with the data_engine probe.
You need to copy this .pem file to the remote OC and CABI robots and provide the location of the file in the robot.cfg file (cryptkey = <.pem file location>). Furthermore, if any impacted probe is not on the same computer where data_engine is present, copy the generated .pem file to the robot computer (where data_engine is not available) and update the robot.cfg file with the .pem file location on that computer.
For more information about the robot.cfg file configuration, see Configure robot.cfg.
Follow these steps:
1. Navigate to the <uim_home>\nimsoft\robot folder.
2. Open the robot.cfg file in a text editor.
3. Add the following parameter to the file:
cryptkey = <location of the .pem file>
For example, cryptkey = c:\Certificate\certificate.pem
4. Save your changes.
Post replacing / overwriting the existing in-place certificate.pem file, UMP/OC wasp should be able to be started and work as expected.
- Deactivate wasp
Wait until the port and PID disappear
- Activate wasp
Note: You do not need to restart the robot.
You have successfully configured the robot.cfg file on the OC and CABI robots.
Additional Information
controller log
Aug 15 10:23:27:357 [4408] Controller: handle_probe_config_get: finding value of section=/controller, key=cryptkey
Aug 15 10:23:27:357 [4408] Controller: handle_probe_config_get : could not find value of section=/controller, key=cryptkey
Aug 15 10:23:27:357 [4408] Controller: nimSession:0000000001160080:xxxxxxxxxxxxxx/52487 - needs cross-thread locking
Aug 15 10:23:27:357 [4408] Controller: SREPLY: status = 4(not found) ->xxxxxxxxxx/52487
Aug 15 10:23:28:361 [1700] Controller: RREQUEST: _close <-xxxxxxxxxx/52487 h=292 d=0
Aug 15 10:23:29:361 [1700] Controller: Process stopped (probe=wasp, pid=4084) RET = 1
Note: The following error can also be caused by the folder that contains the certificate.pem does not have the correct permissions.
wasp log
Aug 15 10:23:27:341 DEBUG [main, com.nimsoft.nimbus.lookup.DataEngineLookup] Request to probe "/xxx/xxx/xxx/data_engine" callback get_connection_string was successful.
Aug 15 10:23:29:048 DEBUG [main, com.nimsoft.nimbus.lookup.DataEngineLookup] No crypt key
Aug 15 10:23:29:361 [1700] Controller: Max. restarts reached for probe 'wasp' (command = <startup java>)
Feedback
