I just started using this software to manage my miners. I switched out from using Ethos to this. One of the biggest issues I have with this software so far is that when it detects a failed miner it just gives up on trying to restart the miner and then the miner just sits there. There should be an option to restart the miner regardless of how many failures there are. I am constantly having to go in and restart the miners when the issue was a miner software crash with one particular miner software. This is the number one detractor from the software and is what will prevent people from using it full scale. I can manage this in alternative ways (power monitor resetting the computer) but then I have other issues because the services are not starting.
- Doesn't start the MSI After Burner Remote Server when restarting the machine
- Manager gives up trying to start the miner if there are several errors in a row.
- Fails to apply the GPU overclock profiles on restart or relaunch of Afterburner software
By default Awesome Miner tries to restart a process three times. If it fails three times within a short period of times, Awesome Miner actually gives up. If the mining software has been running for a few minutes, it will reset this counter and you will have another three times of restart available.
If you want to take further actions after three times, you can use the Rules (Options dialog, Rules section) for that. You have a trigger "Process failure" that will be triggered in this scenario. You can define define your actions - maybe to give you a notification and then try to start the miner again.
The MSI Afterburner Remote Server is a bit difficult to auto start because it requires Admin permissions and doesn't have any built-in concept for that. Awesome Miner can however setup this for you, so have you followed these steps? Please share more details on this if you already have and it isn't working.
http://www.awesomeminer.com/help/gpuclocking.aspxI'm not sure I fully understand the scenario with a restarted MSI Afterburner. If you simply restart that software (close it, then start it), how would that affect the GPU Clocking profiles? Sorry if I missed the point here.