spooler
Oct 18 16:42:16:645 [0001] Controller: Probe 'spooler' FAILED to start, file check determines changes in the probe
Oct 18 17:15:01:068 [0001] Controller: Probe 'spooler' FAILED to start, file check determines changes in the probe
hdb
Oct 18 16:42:18:875 [0001] Controller: Probe 'hdb' FAILED to start, file check determines changes in the probe
Oct 18 17:07:07:400 [0001] Controller: Probe 'hdb' FAILED to start, file check determines changes in the probe
The controller continues to run - log shows no issues.
Release:
Component: ROBOT
You can usually alleviate this issue by right clicking on the probes and select Security - > Validate, Yes to all.
Security validate resets the security token on the probes, this issue is usually seen following a IP address change or a hardware change.
If for some reason you cannot do that via the Infrastructure Manager, it has to be done manually as per the steps below:
- Log into the Robot machine as root or administrator for windows
- cd to the the Nimsoft root directory
On Linux:
- run the command ./bin/niminit stop
On Windows:
Stop the robot watcher service
- cd to the /robot directory
- Copy the file controller.cfg from the /robot directory to the /changes directory using
On Linux:
cp -p
On windows:
copy command
- Delete the file controller.cfg from the /robot directory
- cd to /changes
- Edit controller.cfg and delete all of the lines that contain the key "magic-key"
Then run the command:
On Linux:
./bin/niminit start
On windows:
Start the robot watcher service
Then check that the Nimsoft robot processes (controller, hdb and spooler), are all up and running:
On Linux:
ps -ef | grep nim
On Windows:
Use task manager