Hello everyone,
We're having trouble stopping a DMA server in order to make some configuration adjustments. Despite our attempts to stop it through various methods such as using the SLTaskbar utility, executing BAT files in CMD, etc., it keeps automatically restarting and entering into a loop, preventing it from remaining in a stopped state.
Does anyone have any suggestions or ideas on how to resolve this issue?
Thank you.
Hi Edson,
I have faced this issue in the past with another dataminer agent and what worked for me is the following (you require Administrator privileges):
- Open the services window (Win+r: services.msc)
- Look for SLWatchdog and change the run status to “Manual”. You can change other SL* processes, but with SLWatchdog should be enough.
- Stop Dataminer by any means. My preferred is to execute “Dataminer Stop Dataminer and SLNet.bat” (as Administrator).
- OPTIONAL: Restart the Server (To have a clean slate)
- Execute the upgrade.
- Change the service status to “Automatic (Delayed Start)”.
- OPTIONAL: Restart the Server (again, to have a clean slate)
After the upgrade, I've noticed that the issue no longer happens right away, so if you need to do some other configurations (or multiple upgrades) you can do it without having to change the status again.
Finally, the root cause of this issue is unknown to me, but this workaround has helped me to finish the upgrade successfully.
I hope it works!
As additional info, the main reason for the SLDataMiner service restarting automatically (in turn launching the rest of DataMiner) is the SLWatchDog service. This service will automatically trigger a restart about 2 minutes after seeing a (single) process disappearance of process crashdump for one of the tracked DataMiner processes.
SLWatchDog keeps running when stopping/restarting via Cube/TaskBarUtility/bat-files (and should not trigger the auto restart in these cases)
The SLWatchDog2.txt logfile can shed more light on when and why a DMA was automatically restarted.
Another possible reason for SLDataMiner restarting automatically would be to have Recovery options configured in the Windows Services configuration for SLDataMiner. This would be quite a custom and uncommon config and is most likely not the trigger here.
Thanks Arturo! I did the steps mentioned and it worked.