controller.cfg wiped out, after rebuilding wasp is not starting

Document ID : KB000122734
Last Modified Date : 07/12/2018
Show Technical Document Details
Issue:
The controller.cfg got randomly wiped out due to server error and only contained one probe definition - controller itself.

After I have fixed this (re-defining missing probes, clearing magic keys and Validating probes in Infrastructure Manager), the wasp probe refuses to start:

Dec  7 03:02:21:879 [140072237500224] Controller: Max. restarts reached for probe 'wasp' (command = <startup java>) 
Resolution:
redeployed wasp probe