Topic: [ Bonus PPS Pool - 130% PPS - OPEN ] - page 32. (Read 94062 times)

Quote from: DutchBrat on May 30, 2012, 05:01:24 PM

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

Well that sucks, i thought ckvolas resolved that since whats the purpose of backup pool when primary pool dies but it stays connected to it and just dump shares Sad

It was resolved for everybody else and all other pools. I can testify to this.

It is just your sucky proxy pool that has very high rejects and it keeps getting disabled.

No need to ask ckolivas to change cgminer. 2.4.1 has no bugs AFAIK.

Tell your miners to use the --no-pool-disable switch when at your pool and turn the switch off when at other normal / non-proxying / low reject pools Wink

Good luck !

if it was specific to this pool, all my mining rigs would stay connected to my backup pool.... they don't.... sometimes 1 or 2 of them keep hashing away at the backup pool, while the others happily switch back to Clipse.... seems clear enough to me !

Clipse

hero member

Activity: 504

Merit: 502

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

Well that sucks, i thought ckvolas resolved that since whats the purpose of backup pool when primary pool dies but it stays connected to it and just dump shares Sad

The only reason I could see is that I restart the pool too fast and it never actually lost connection except dumps invalid shares indefinitely on restart. I will time the restarts better even tho Im aiming better or worse to keep the pool continously running until sunday.

Think it is a flaw in CGMiner.... Pool goes in reject state after 3 mins of rejects, then on next LP it looks to see if the main pool is back online

In most instances it works perfectly, but in sometimes it doesn't see the pool back alive... strange thing is, on one rig it does see the pool and on another it doesn't, even on the same IP address....

strange !

Well lets see the next run, as stated Im going to leave it on continously and see the results. Im making some progress on my side juggling between this and real life heh.

EDIT: Ok busy calculating the final shares for payment history, pool back up, lets see how clean run goes.

DutchBrat

hero member

Activity: 868

Merit: 1000

Quote from: bulanula on May 30, 2012, 04:59:01 PM

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

Well that sucks, i thought ckvolas resolved that since whats the purpose of backup pool when primary pool dies but it stays connected to it and just dump shares Sad

The only reason I could see is that I restart the pool too fast and it never actually lost connection except dumps invalid shares indefinitely on restart. I will time the restarts better even tho Im aiming better or worse to keep the pool continously running until sunday.

Think it is a flaw in CGMiner.... Pool goes in reject state after 3 mins of rejects, then on next LP it looks to see if the main pool is back online

In most instances it works perfectly, but in sometimes it doesn't see the pool back alive... strange thing is, on one rig it does see the pool and on another it doesn't, even on the same IP address....

strange !

Clipse

hero member

Activity: 504

Merit: 502

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

Well that sucks, i thought ckvolas resolved that since whats the purpose of backup pool when primary pool dies but it stays connected to it and just dump shares Sad

It was resolved for everybody else and all other pools. I can testify to this.

It is just your sucky proxy pool that has very high rejects and it keeps getting disabled.

No need to ask ckolivas to change cgminer. 2.4.1 has no bugs AFAIK.

Tell your miners to use the --no-pool-disable switch when at your pool and turn the switch off when at other normal / non-proxying / low reject pools Wink

Good luck !

Your useless comments have no value in this thread. Also do you feel hated that I didnt want to let you back on this pool since you are constantly starting shit all over the forum. I understand why you stole the 25BTC from that user considering you want to cry over me initially not sending you 0.01 or less than that.

Good bye troll.

bulanula

hero member

Activity: 518

Merit: 500

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

Well that sucks, i thought ckvolas resolved that since whats the purpose of backup pool when primary pool dies but it stays connected to it and just dump shares Sad

It was resolved for everybody else and all other pools. I can testify to this.

It is just your sucky proxy pool that has very high rejects and it keeps getting disabled.

No need to ask ckolivas to change cgminer. 2.4.1 has no bugs AFAIK.

Tell your miners to use the --no-pool-disable switch when at your pool and turn the switch off when at other normal / non-proxying / low reject pools Wink

Good luck !

Clipse

hero member

Activity: 504

Merit: 502

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

Well that sucks, i thought ckvolas resolved that since whats the purpose of backup pool when primary pool dies but it stays connected to it and just dump shares Sad

The only reason I could see is that I restart the pool too fast and it never actually lost connection except dumps invalid shares indefinitely on restart. I will time the restarts better even tho Im aiming better or worse to keep the pool continously running until sunday.

DutchBrat

hero member

Activity: 868

Merit: 1000