Topic: [ Bonus PPS Pool - 130% PPS - OPEN ] - page 29. (Read 94062 times)
pool alive?
UPDATE:
Before anyone wonder why the connection problems, I just had to reset pool to increase caching due to increase users. All back up was about 5minutes of juggling. Should be able to do most of these adjustment without any resets soon.
Before anyone wonder why the connection problems, I just had to reset pool to increase caching due to increase users. All back up was about 5minutes of juggling. Should be able to do most of these adjustment without any resets soon.
UPDATE:
I will be away tonight so will only be able to process payment history for payment cycle tomorrow. I will include all extra shares at the time that I process it so everyone will be getting an extra early payment on shares submitted during the next payment cycle tomorrow.
I will be away tonight so will only be able to process payment history for payment cycle tomorrow. I will include all extra shares at the time that I process it so everyone will be getting an extra early payment on shares submitted during the next payment cycle tomorrow.
UPDATE:
Ok, I got the packetloss on the server related to corrupted driver resolved and pool is back up. Now to see what happens around LP's and in general so I can move on to the things that really needs fixing.
Ok, I got the packetloss on the server related to corrupted driver resolved and pool is back up. Now to see what happens around LP's and in general so I can move on to the things that really needs fixing.
Pool is down for a few minutes, trying to resolve the huge rx packetloss that I noticed occurring. It may very well be related to the random rejects.
EDIT: Its back up.
EDIT: In about an hour I will have the packetloss sorted out so we can check if or by how much it resolves rejects.
EDIT: Ok resolved the packetloss issue, stupid vm drivers that was faulty since the start but still worked sporaticly. Now to see what is breaking since it wont be packetloss related from here on.
EDIT: Busy with one more issue before pool will come back up, this one is bit trickier
EDIT: Its back up.
EDIT: In about an hour I will have the packetloss sorted out so we can check if or by how much it resolves rejects.
EDIT: Ok resolved the packetloss issue, stupid vm drivers that was faulty since the start but still worked sporaticly. Now to see what is breaking since it wont be packetloss related from here on.
EDIT: Busy with one more issue before pool will come back up, this one is bit trickier
Can you reset a miner and check now if its still happening, just trying to isolate where the problem may be just in case it is related to the pool only.
Done
Can you send me email while we figure this out, I dont want to clutter this thread with a bunch of short communications
Can you reset a miner and check now if its still happening, just trying to isolate where the problem may be just in case it is related to the pool only.
Done...
only a few rejects after connecting everything alright now, 12 minutes and no more rejects.
Seem to me that there is a flood when the miner first connects and the server does not handle well the initial burst
but is doing fine right now.
Can you reset a miner and check now if its still happening, just trying to isolate where the problem may be just in case it is related to the pool only.
At worse you should be seeing 4% rejects atm after a atleast 1000 shares, avg right now is 2-3% but 10% or more is by far not normal right now.
At worse you should be seeing 4% rejects atm after a atleast 1000 shares, avg right now is 2-3% but 10% or more is by far not normal right now.
almost 10% rejects, whats wrong? 
Eh? No way, everyones rejects is dropping and your overall is also dropping which is at 3.25% for this payment cycle, it was at 3.5% earlier.
If you had some miners reset a few hours ago it will look out of proportion on your local miner stats since I had a few resets in that duration which would have dumped rejects locally and that wont show on official pool stats since it never actually were send to the pool.
Now I see what happened!
But now I had reset the miner and look:
Elapsed MHS av Found Blocks Getworks Accepted Rejected Hardware Errors Utility Discarded
SUMMARY 2m 26s 7,323.48 0 106 155 116 0 63.60/m 9
Ok thats unique, I dont see anything like that here on my gpus or other connected miners. I just saw that dump from you(and only you) however for some strange reason, let me see if its something my side since it could also be some random network issues between you and the pool.
almost 10% rejects, whats wrong?
Eh? No way, everyones rejects is dropping and your overall is also dropping which is at 3.25% for this payment cycle, it was at 3.5% earlier.
If you had some miners reset a few hours ago it will look out of proportion on your local miner stats since I had a few resets in that duration which would have dumped rejects locally and that wont show on official pool stats since it never actually were send to the pool.
Now I see what happened!
But now I had reset the miner and look:
Elapsed MHS av Found Blocks Getworks Accepted Rejected Hardware Errors Utility Discarded
SUMMARY 2m 26s 7,323.48 0 106 155 116 0 63.60/m 9
almost 10% rejects, whats wrong?
Eh? No way, everyones rejects is dropping and your overall is also dropping which is at 3.25% for this payment cycle, it was at 3.5% earlier. If it really bothers you please let me know over how big samplesize you are seeing this 10% rejects on your local miners since you are clearly not refering to the actual webstats.
If you had some miners reset a few hours ago it will look out of proportion on your local miner stats since I had a few resets in that duration which would have dumped rejects locally and that wont show on official pool stats since it never actually were send to the pool.
almost 10% rejects, whats wrong?
Fixed and reconnected.
Yeh sorry about that, it was part of testing load balancing setup along with being far too tired and then not doublechecking everything before I go to bed.
Thanks, for the quick fix!
UPDATE:
Pool will be up in a few minutes, just needed a few OS updates that cant be done with live session.
EDIT: ITS BACK
Pool will be up in a few minutes, just needed a few OS updates that cant be done with live session.
EDIT: ITS BACK
Fixed and reconnected.
Yeh sorry about that, it was part of testing load balancing setup along with being far too tired and then not doublechecking everything before I go to bed.
Fixed and reconnected.
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
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
hehe, as I stated twice and in PM, it wasnt anyones fault other than myself overlooking a crucial setting on the pool side just before I went to bed. It will working correct now
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
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
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
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.
It will start to connect now, please confirm.
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
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.
Jump to: