[ Bonus PPS Pool - 130% PPS - OPEN ]

[Clipse]

UPDATE:

Datacentre reported they swapped out a bunch of core routers which were faulty, pool is behaving rather well right off the bat so I assume it was likely a huge part of the pool problems for weeks probably. I will let it run until tomorrow night and if all checks out then only will I send out the recent Signup requests.

[cuz0882]

It doesn't look like the reject issue was fixed. I'm getting about 100 rejects a hour right now. Which is a lot more then I normally get here.

[Clipse]

It doesn't look like the reject issue was fixed. I'm getting about 100 rejects a hour right now. Which is a lot more then I normally get here.

Mmm that doesnt seem completely right, your at 2.3% and constantly dropping from the first days 6-7% due to all the issues on that day. Im sure there is still some reject spamming left at new LP but it used to happen at every single LP and I dont see that being the case anymore. Its not perfect yet but its alot better and at the PPS rate we pay there is real value to mine here now, it will improve more as soon as I can drop the rejects more but for now I need to get it to run stable 24/7.

[Clipse]

PAYMENTS PROCESSED:

Pure PPS + Bonus PPS for 6 May 00:00:00 - 9 May 23:59:59 were processed.

[Clipse]

Ive just made few more changes to see about the rejects, need to see what happens over next couple of LP's from here on.

EDIT: Will soon be running new network library, in the meantime I will probably just let it avg out on reject rate of 3-4% for most but the 108% will atleast show some decent extra gains. There is however alot of users still sitting 1-2% or less, rejects are only occuring at LP and without drastic network changes I cant fix that right now, so for now I will leave it running without all these resets but there will be the usually LP rejects from time to time.

[ddd1]

Sent PM 2-3days ago was hoping to be able to mine on youre pool

[Clipse]

Sent PM 2-3days ago was hoping to be able to mine on youre pool

I will send out the signups now, just take note that you could be getting 3-4% rejects right now until I get the network sorted hopefully within next few days(sunday if Im lucky). If thats the case, you should still gain 4-5% above 100% PPS even with that reject count.

[Clipse]

UPDATE:

All queued signups send out.

[Clipse]

PAYMENTS PROCESSED:

All Pure PPS + Bonus PPS for 10 May 00:00:00 - 12 May 23:59:59 paid.

[ThiagoCMC]

Clipse,

 What is this:

 [2012-05-14 21:10:16] Started cgminer 2.4.1
 [2012-05-14 21:10:16] Loaded configuration file cgminer-user1.conf
 [2012-05-14 21:10:17] Found 0 ztex board(s)
 [2012-05-14 21:10:17] Probing for an alive pool
 [2012-05-14 21:10:18] Long-polling activated for http://pool.bonuspool.co.cc:80/LP
 [2012-05-14 21:10:18] Pool 0 http://pool.bonuspool.co.cc:80 alive
 [2012-05-14 21:10:19] Long-polling activated for http://gpumax.com:8332/listenChannel
 [2012-05-14 21:10:19] Pool 1 http://gpumax.com:8332 alive
 [2012-05-14 21:10:20] Pool 2 http://us.eclipsemc.com:8337 alive
 [2012-05-14 21:10:20] Long-polling activated for http://us.eclipsemc.com:8337/LP
 [2012-05-14 21:10:21] Long-polling activated for pool http://btcmine.com:8332 via http://pool.bonuspool.co.cc:80/LP  
 [2012-05-14 21:10:21] Pool 3 http://btcmine.com:8332 alive
 [2012-05-14 21:10:23] Accepted 186761f4.6e68efde GPU 0 pool 0
 [2012-05-14 21:10:23] API running in IP access mode

 My intention was:

 1- mine at Bonus Pool...;
 2- until GPUMax begin leasing...;
 3- if both down, go to EclipseMC...;
 4- if EclipseMC is down, mine at BTCMine.

 BUT, what that bold line means?!?! LP for pool btcmine activated via Bonus Pool?!?!

 I am very curious about what that CGMiner output means...

Thanks!
Thiago

[Clipse]

Clipse,

 What is this:

 [2012-05-14 21:10:16] Started cgminer 2.4.1
 [2012-05-14 21:10:16] Loaded configuration file cgminer-user1.conf
 [2012-05-14 21:10:17] Found 0 ztex board(s)
 [2012-05-14 21:10:17] Probing for an alive pool
 [2012-05-14 21:10:18] Long-polling activated for http://pool.bonuspool.co.cc:80/LP
 [2012-05-14 21:10:18] Pool 0 http://pool.bonuspool.co.cc:80 alive
 [2012-05-14 21:10:19] Long-polling activated for http://gpumax.com:8332/listenChannel
 [2012-05-14 21:10:19] Pool 1 http://gpumax.com:8332 alive
 [2012-05-14 21:10:20] Pool 2 http://us.eclipsemc.com:8337 alive
 [2012-05-14 21:10:20] Long-polling activated for http://us.eclipsemc.com:8337/LP
 [2012-05-14 21:10:21] Long-polling activated for pool http://btcmine.com:8332 via http://pool.bonuspool.co.cc:80/LP  
 [2012-05-14 21:10:21] Pool 3 http://btcmine.com:8332 alive
 [2012-05-14 21:10:23] Accepted 186761f4.6e68efde GPU 0 pool 0
 [2012-05-14 21:10:23] API running in IP access mode

 My intention was:

 1- mine at Bonus Pool...;
 2- until GPUMax begin leasing...;
 3- if both down, go to EclipseMC...;
 4- if EclipseMC is down, mine at BTCMine.

 BUT, what that bold line means?!?! LP for pool btcmine activated via Bonus Pool?!?!

 I am very curious about what that CGMiner output means...

Thanks!
Thiago

Your guess is as good as mine, Ive never seen such output from cgminer:

[2012-05-14 21:10:21] Long-polling activated for pool http://btcmine.com:8332 via http://pool.bonuspool.co.cc:80/LP  


That said I also never run cgminer with so many pools, only usually 2 pools primary and backup.

[The00Dustin]

[2012-05-14 21:10:21] Long-polling activated for pool http://btcmine.com:8332 via http://pool.bonuspool.co.cc:80/LP

BUT, what that bold line means?!?! LP for pool btcmine activated via Bonus Pool?!?!

 I am very curious about what that CGMiner output means...

I think this started with the new version that keeps an LP connection open for each pool.  I didn't worry about it when I saw something similar for my fourth backup (solo mining) since I knew it didn't have its own LP.  If BTCMine is supposed to have its own LP, then it might be worrying about, but if it isn't, then I am guessing it will do one of two things:
1) Since BTCMine is your last backup, that LP will fail before you switch to that backup, and you will mine without LP
2) If BTCMine isn't your last backup, then even if that LP fails before you switch to BTCMine, an LP on a further-back backup would be used to avoid stales on BTCMine.

This is just a guess, but I don't think it's cause for alarm either way.  It may even be listed in the changelog, but I don't remember.

[Clipse]

UPDATE:

Planning to roll-out the last reject related updates by sunday, just running some remaining test rights now. This should be the end of LP stuffups and the pool will behave properly

[coblee]

Rejects around new blocks are the main reason why I'm getting around 3% rejects.
Here's what my miner just outputed:

Code:

2012-05-16 02:25:51.577	[250]	Clipse accepted share e5b69207 (difficulty 4.28280)
2012-05-16 02:25:51.991	[250]	Clipse accepted share eecaee31 (difficulty 10.76513)
2012-05-16 02:25:56.036	[250]	Clipse accepted share 688faa49 (difficulty 1.22878)
2012-05-16 02:25:56.498	[250]	Clipse accepted share 6c789255 (difficulty 8.18930)
2012-05-16 02:25:56.920	[250]	Clipse accepted share c1623623 (difficulty 4.65397)
2012-05-16 02:25:58.174	[250]	Clipse accepted share cb888b17 (difficulty 1.32570)
2012-05-16 02:26:01.311	[250]	Clipse accepted share 2adcf6ac (difficulty 2.55784)
2012-05-16 02:26:01.769	[200]	Clipse rejected share 5d1f9d26 (difficulty 1.51925): Unknown reason
2012-05-16 02:26:02.521	[200]	Clipse rejected share 911e8e31 (difficulty 1.04542): Unknown reason
2012-05-16 02:26:03.771	[300]	ABC: New block detected
2012-05-16 02:26:04.020	[200]	Clipse rejected share b087c79e (difficulty 1.28250): Unknown reason
2012-05-16 02:26:05.766	[200]	Clipse rejected share 1ec57622 (difficulty 1.38823): Unknown reason
2012-05-16 02:26:06.494	[200]	Clipse rejected share a6fe4149 (difficulty 1.69221): Unknown reason
2012-05-16 02:26:06.955	[200]	Clipse rejected share e7ae1459 (difficulty 4.45217): Unknown reason
2012-05-16 02:26:07.374	[200]	Clipse rejected share 349552b8 (difficulty 1.97132): Unknown reason
2012-05-16 02:26:07.849	[200]	Clipse rejected share 0983e6c4 (difficulty 2.47662): Unknown reason
2012-05-16 02:26:10.267	[200]	Clipse rejected share 16cd5134 (difficulty 1.28337): Unknown reason
2012-05-16 02:26:11.523	[200]	Clipse rejected share 52d7335c (difficulty 1.90752): Unknown reason
2012-05-16 02:26:11.947	[200]	Clipse rejected share d7c1c332 (difficulty 1.44645): Unknown reason
2012-05-16 02:26:12.373	[200]	Clipse rejected share 40fc533c (difficulty 1.71028): Unknown reason
2012-05-16 02:26:12.808	[200]	Clipse rejected share 7550f915 (difficulty 1.69678): Unknown reason
2012-05-16 02:26:13.232	[200]	Clipse rejected share 31cf7a16 (difficulty 1.20066): Unknown reason
2012-05-16 02:26:13.674	[200]	Clipse rejected share a3b2fe37 (difficulty 24.76243): Unknown reason
2012-05-16 02:26:14.118	[200]	Clipse rejected share b061de2a (difficulty 20.04860): Unknown reason
2012-05-16 02:26:15.179	[200]	Clipse rejected share 49069220 (difficulty 15.76314): Unknown reason
2012-05-16 02:26:16.446	[200]	Clipse rejected share ab3fc58d (difficulty 1.31017): Unknown reason
2012-05-16 02:26:16.877	[200]	Clipse rejected share c3e36d55 (difficulty 1.13255): Unknown reason
2012-05-16 02:26:21.560	[200]	Clipse rejected share b17d9afb (difficulty 2.42865): Unknown reason
2012-05-16 02:26:21.998	[200]	Clipse rejected share 4e113b47 (difficulty 1.10127): Unknown reason
2012-05-16 02:26:22.428	[200]	Clipse rejected share d6f1d5ac (difficulty 3.13094): Unknown reason
2012-05-16 02:26:23.721	[200]	Clipse rejected share 87156851 (difficulty 2.25289): Unknown reason
2012-05-16 02:26:30.011	[200]	Clipse rejected share 8b793547 (difficulty 2.46976): Unknown reason
2012-05-16 02:26:30.375	[300]	Clipse: New block detected
2012-05-16 02:26:35.757	[250]	ABC accepted share dfa3be61 (difficulty 2.21424)
2012-05-16 02:26:35.921	[250]	Clipse accepted share 3888ee00 (difficulty 12.64119)
2012-05-16 02:26:37.617	[250]	Clipse accepted share 5ad3e24b (difficulty 1.08846)
2012-05-16 02:26:41.019	[250]	Clipse accepted share c68044c6 (difficulty 3.82569)
2012-05-16 02:26:41.453	[250]	Clipse accepted share 48bd2582 (difficulty 4.11564)

As you can see, ABC reported a new block a lot earlier than your pool. And it seems like the pool just rejects these shares after the new block is found but the LP doesn't notify me of the new block until much later. So my miners wastes a lot of time mining on an old block which gets rejected.

[Clipse]

Im well aware of the issue around LP, and that is indeed the only reason anyone is getting more than 0.1% rejects. Im still testing the new setup to replace the current LP system that is sporatic in its LP publishing, sometimes its on time and sometimes it takes a 30 seconds longer than it should.

Its still on track to get it going by Sunday.

That said, the reject spam you posted looks extremely bad, seems you are getting among the worst of it right now. Let me see if I can tweak the current system a bit still to try lower that solong.

[Clipse]

I made a few changes to try lower the response for LP's, let me know if you notice any improvement over the next 20+ blocks.

[Clipse]

Hopefully this keeps up, 18 LPs(new blocks) 4400 accepted / 2 rejected. LP's also seem to push extremely fast now unlike before.

[MrTeal]

Hopefully this keeps up, 18 LPs(new blocks) 4400 accepted / 2 rejected. LP's also seem to push extremely fast now unlike before.

I restarted mine 5 hours ago, and have about 1.5% stales in the intervening time. Generally it's been pretty good, with a couple blocks that spewed dozens of rejects. All the machines are running 2.4.0/2.4.1, other than one that was running 2.3.2 to see if there's a difference in stales (there isn't).

[Clipse]

Hopefully this keeps up, 18 LPs(new blocks) 4400 accepted / 2 rejected. LP's also seem to push extremely fast now unlike before.

I restarted mine 5 hours ago, and have about 1.5% stales in the intervening time. Generally it's been pretty good, with a couple blocks that spewed dozens of rejects. All the machines are running 2.4.0/2.4.1, other than one that was running 2.3.2 to see if there's a difference in stales (there isn't).

Yep, sounds about right. There is still reject spewing, worlds apart from the rejects/instability we all saw just a week ago. Its definitely in a stable-usable form right now, I will have the last reject stuffups resolved so everyone can stay <1% rejects barring any local miner/connection issues of course

[DutchBrat]

For the  last 9 1/2 hours I have been running just a bit below <1%

Compared with last week that is a massive improvement already (from 4%+), can't wait for the new code that will bring the rejects down even further

W00t W00t