Quote from: GH on June 13, 2017, 03:18:12 PM

Quote from: Claymore on June 12, 2017, 09:40:46 PM

Quote from: GH on June 12, 2017, 08:49:54 PM

Claymore,
the problem with ETHMan 3.1 + Dualminer 9.5
If some rig go down, and then after some time goes up, it dosent restore in ETHMan, on screenshot you see that miner restarted and work, i launched web console and it works already 2 minutes, but ETHMan still show "lost ****". Even after 10 minutes ETHMan dosent see rig. So as it was with ETHMan 3.0, I need restart it to see all rigs stats again.

If you included cryptography and https, then maybe here some trouble with ssl? need to update certificate if connection was lost?

Can confirm this, same problem here.
The last update of EthMan improved the 100% lock after a warning, but a rig which was offline and comes back up is not (always?) shown as alive until EthMan is restarted.
Also the batch action is still not retriggered in case of a persisting failure.

I spent half a day in attempts to reproduce it, but it works fine for me, weird. If you can 100% reproduce this issue I can prepare debug version with logging and send it to you so I can get more info. PM me if you want to participate.
Retriggering: if a rig was lost, BAT file will be executed. If rig is back again and then again will be lost, BAT will be executed again. What's wrong exactly?

I can not 100% reproduce it. Just had the error again two hours ago. Rig already back online but shown as offline for 2+ hours. But it does not happen always, some additional aspect I don't see at the moment must play a role here. But of course I can try to help if you have a logging debug version for me.

Retriggering: as I already wrote - a single action may not be sufficient to bringt the rig back up. (i.e.: rig hangs - action triggered -> auto-reset rig - if windows boots into recovery mode because it is the x-th reset in a row you are ...... - the rig stays offline waiting for user input until infinity).
So: if an action did not bring the rig back up after the same delay time, it should trigger the same action again and again until the problem is resolved. (Leaving out luxury options like number of max. attempts or configurable follow up delay Grin

)

@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?