I do have this problem on all my rigs, so I would appreciate any idea that might help.
It would also be an option if Awesome Miner could monitor the miner if it is still hashing and, if it is not, reboot the whole Rig (since this seems to be the only way to solve this I think). Currently I am rebooting manually, up to 10 times until all cards are hashing and I do not get a watchdog restart due to the watchdog.
When looking at the statistics reported to Awesome Miner, how do you see that Claymore isn't operating as it should? Is it only that the hashrate is lower than it should?
thank you for your response. Unfortunately I have not found a good way yet, so let me describe more detailed what happened.
I do start Claymore Miner (CM) using Awesome Miner (AM), I did this without additional parameters (set by me).
Normally the software starts hashing, but often not all GPUs can be initiated and fail on OpenCL initialization. Since CM has a watchdog by default it restarts the software.
When this happens it comes to the screen posted before, it gets stuck on starting CM even before one single package has been submitted. Actually I do not think that this is a state I can access the rules with, right? If there is a way please let me know, this would be my preferred way.
If the API is up, you should be able to use rules like "Accept progress" to detect that Accepted shares doesn't increase.
If the API isn't running (Interface offline), you have a rule for "Offline detection". That one should be able to detect disconnected API's on a Managed Miner that is indicating "Mining - Interface offline". If the interface is offline for more than 2 minutes - it could be a sign that the miner isn't working as it should.