You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Update: (ignore stale shares - will test WAN faking from other thread):
Running 9.6 - testing it out, I have noticed that I am getting a marked increase of stale shares (see screenshot)
I get the warning (as per the other issue and the doc about a local address/proxy) and ignored it, but
there is a 10% stale share in a few places - see screenshot (the empty spot in the middle is the changeover to proxy)
This may be early days, I will watch and see - this may be dag file swap related or perhaps a connection issue to ethermine - I found I had connection issues to ethermine with the "may be temporary" message.
Also, are you averse to a pull request that will allow failovers (e.g. eu1 or eu2 if main fails to connect?) in the section where it has the "may be temporary" message?
The text was updated successfully, but these errors were encountered:
Thanks. I realised #7 and had updated the issue. I am about 85% done on a pull request that has simple failover for same pool. Should finish it in the next 8 hours (afk atm)
Update: (ignore stale shares - will test WAN faking from other thread):
Running 9.6 - testing it out, I have noticed that I am getting a marked increase of stale shares (see screenshot)
I get the warning (as per the other issue and the doc about a local address/proxy) and ignored it, but
there is a 10% stale share in a few places - see screenshot (the empty spot in the middle is the changeover to proxy)
This may be early days, I will watch and see - this may be dag file swap related or perhaps a connection issue to ethermine - I found I had connection issues to ethermine with the "may be temporary" message.
Also, are you averse to a pull request that will allow failovers (e.g. eu1 or eu2 if main fails to connect?) in the section where it has the "may be temporary" message?
The text was updated successfully, but these errors were encountered: