We have a custom probe running on a hub server which runs custom powershell scripts to gather QoS data for Zerto.
It has been working fine but apparently it stopped working since last week. There has been no change in the environment and we are unable to restart the probe. It fails after 10 times and we get error message "  Controller: Max. restarts reached for probe 'power_probe' (command = power_probe.exe) "
We have tried restarting the controller probe , robot as well as the server it doesnt turn on. The probe runs a .exe file. if we run it manually then .exe runs without any issues but controller should be able to manage the start/stop of the probe.
We have checked the controller logs and it shows that the probe turns on gets the port and PID but then it stops . It keeps checking for available port but then it reverts back to port 48003 and then it stops.
We are unable to understand why this is happening. Has anyone got any thoughts on this?
try adding first_probe_port = 48000 to the robot.cfg if not there and see if that helps.
your developer may need to put some code in the .exe to find out what is going on with it.
can try setting loglevel 5 and logsize 15000 on the controller and see if it provides anything else.
But sounds like something in the environment is causing an issue.
Might also check your system path and see if something changed there.
We were able to resolve the issue. The problem was the server itself causing the custom probe to fail.