@claymore:
1) Maybe I found a hint: Is it possible that it is some kind of IP address caching issue? It seems to happen to rigs which reboot and get another (dynamic) IP address. If I change the "IP" field in EthMan to the current numeric IP address or use an alternative DNS name which resolves to the same computer EthMan shows correct "up" state. If I change it to the old one its shown "down" again. Restarting EthMan seems to update these values and the rig ist shown online, even with the same old name ("IP" entry). Or it is some kind of update process which is only executed when adding/changing a rig entry. But maybe this helps...
2) Did you read my comment about retriggering above and understand my issue?
Please test this version:
https://mega.nz/#!C5xiUSYY!QY44OAExh5EQ2elGcH1DvfbkQMTkgMSwOEMLoG0lUCULet me know if you still have the issue.
DNS caching can cause some additional delays, but in a minute the lost rig must be found anyway.
I will add retriggering in next update.
Thank you, downloaded, running and watching.
Maybe another hint: even with this EthMan version and CDM 9.5 this procedure can produce an identical looking error: Use EthMan to send a "Restart Miner" command to a "read only management port" rig. After a few seconds it will be shown offline (although the client refuses the command because management interface is in read-only mode and just keeps mining) and can not be brought back until EthMan is restarted or the "IP" field was changed like in my post above.