NOTICE:
Im aware that some users actually permanently stayed on their backup pools, all I can think is that their backup pool configuration in their miners stuffed up or they didnt update to cgminer 2.4.1
CGMiner 2.4.1. did not resolve this issue, sometimes the pool stays on 'rejecting' state even though it is working fine again
Has anyone been dealing with this as well? I have one machine that was connected, fell to my backup pool, and now I cannot reconnect it. The machine has been restarted multiple times, but still won't connect. The rest of my rigs are connecting just fine. Anyone have anything? I'll give any suggestions a test run in the morning.
I am having a similar problem:
woke up and 1 of my rigs (separate IP from the others) was discarding every share as being stale.... Restarted the rig and now it won't connect to Bonuspool anymore
CGMiner reports it as being dead, while my other rigs are hashing away
My guess is that Clipse banned my IP for submitting too many rejects or smtg
Using 2.4.2.
Clipse: I'll IM you my IP that's giving the problems
Negative, all of mine are coming from the same IP as well. I'm missing around 1657ish from my normal stats. I just reset one machine and it connected fine, but that other one will not accept this pool as being valid. It says it's credentials are either invalid or the pool is down.
I switched back to 2.4.1 that didn't help....still the "share became stale before submitting, discarding" message, I let it run on another pool for a while.... Clipse came back to me, saying he had NOT banned my IP
I restarted 2.4.2 and now it works again, there was NO reason for it NOT to work and there is NO real reason why it is working again now
I'd suggest keep trying to reconnect
