MintCondition, with DiabloMiner is a lot better now: [8/19/11 10:42:54 PM] pool.abcpool.co accepted block 20 from Cypress (#1)
[8/19/11 10:42:55 PM] pool.abcpool.co accepted block 21 from Cypress (#1)
There still is the 50 seconds LP socket close. I think 50 seconds is too little given that you need to communicate a new block every 10 minutes on average. Did you try a very short keep-alive, like a couple of minutes so that the socket gets closed faster if the client pc does not answer fast enough? spiccioli No, it simply took longer, miner looping, no more share submitted, my stats have invalid shares increasing steadly. [8/19/11 11:42:47 PM] ERROR: Cannot connect to pool.abcpool.co: Bitcoin disconnected during response: 200 ok
[8/19/11 11:43:37 PM] ERROR: Cannot connect to pool.abcpool.co: Bitcoin disconnected during response: 200 ok
[8/19/11 11:44:27 PM] ERROR: Cannot connect to pool.abcpool.co: Bitcoin disconnected during response: 200 ok
[8/19/11 11:45:17 PM] ERROR: Cannot connect to pool.abcpool.co: Bitcoin disconnected during response: 200 ok
[8/19/11 11:46:07 PM] ERROR: Cannot connect to pool.abcpool.co: Bitcoin disconnected during response: 200 ok
[8/19/11 11:46:57 PM] ERROR: Cannot connect to pool.abcpool.co: Bitcoin disconnected during response: 200 ok
[8/19/11 11:47:47 PM] ERROR: Cannot connect to pool.abcpool.co: Bitcoin disconnected during response: 200 ok
[8/19/11 11:48:37 PM] ERROR: Cannot connect to pool.abcpool.co: Bitcoin disconnected during response: 200 ok
[8/19/11 11:49:27 PM] ERROR: Cannot connect to pool.abcpool.co: Bitcoin disconnected during response: 200 ok
[8/19/11 11:50:17 PM] ERROR: Cannot connect to pool.abcpool.co: Bitcoin disconnected during response: 200 ok
mhash: 654.7/654.1 | accept: 170 | reject: 0 | hw error: 0
|
|
|
|
All I meant to point out is that if one would like to pool hop with a big proportional pool and is having difficulty with the LP aspect then they can at least make some gains by using the information on the bitcoin network (if the pool is sufficiently large). cool with out a doubt it is a strategy that can work on pools the size of deepbit. Pident is ok.. but does have high error rate as well. Higher for some pools than others but it is an option. The only truely effective anti hopping technique is a fair payout system. The rest can be gotten around by means of varying difficulty... derpbit being one of the hardest. not every pool hates us.. which is nice. IMO the best payout method that keeps us happy and their users happy, is to have a choice between prop and pps.WE could then hop them on prop, and use pps for backup and set back up to jump to the poll with the most shares over all. This way when they are on a really long block(and hate us the most at this time, mainly cause we are not there), we can come back and help them finish it out.(which we do on occasion anyways for pools we like even if they dont have pps) And we can be quite effective at ending blocks from hell. An extra 150gh is a welcome site when you are on a 5 million plus share drought. joulesbeef, what about "hopping" the same pool (like abcpool mtred) which has both payment methods. ? you just need to create two accounts on them, one set to prop and the other to PPS and, from the pool perspective, the total GHs never change. am I wrong? spiccioli. |
|
|
|
UPDATE: We are currently investigating the high invalid counts for non-Phoenix clients. Going through the logs, the high invalid rate is for the most part due to 'invalid-time' submissions. We were seeing some of these before, that's why a few days back we added the HTTP header to all getworks. This header indicates explicitly that time-rolling is not allowed. It seems that some clients are taking the presence of this header as a sign to enable time-rolling instead of disabling it. That's why we've just turned the header off again. At first glance it seems to have eliminated the bulk of time-invalid submissions. MintCondition, with DiabloMiner is a lot better now: [8/19/11 10:42:54 PM] pool.abcpool.co accepted block 20 from Cypress (#1)
[8/19/11 10:42:55 PM] pool.abcpool.co accepted block 21 from Cypress (#1)
[8/19/11 10:43:01 PM] pool.abcpool.co accepted block 22 from Cypress (#2)
[8/19/11 10:43:03 PM] ERROR: Cannot connect to pool.abcpool.co: Bitcoin disconnected during response: 200 ok
[8/19/11 10:43:09 PM] pool.abcpool.co accepted block 23 from Cypress (#1)
[8/19/11 10:43:21 PM] pool.abcpool.co accepted block 24 from Cypress (#1)
[8/19/11 10:43:27 PM] pool.abcpool.co accepted block 25 from Cypress (#2)
[8/19/11 10:43:32 PM] pool.abcpool.co accepted block 26 from Cypress (#1)
[8/19/11 10:43:53 PM] ERROR: Cannot connect to pool.abcpool.co: Bitcoin disconnected during response: 200 ok
[8/19/11 10:44:08 PM] pool.abcpool.co accepted block 27 from Cypress (#2)
[8/19/11 10:44:25 PM] pool.abcpool.co accepted block 28 from Cypress (#1)
[8/19/11 10:44:43 PM] ERROR: Cannot connect to pool.abcpool.co: Bitcoin disconnected during response: 200 ok
[8/19/11 10:44:46 PM] pool.abcpool.co accepted block 29 from Cypress (#1)
[8/19/11 10:44:46 PM] pool.abcpool.co accepted block 30 from Cypress (#1)
[8/19/11 10:44:58 PM] pool.abcpool.co accepted block 31 from Cypress (#1)
[8/19/11 10:45:00 PM] pool.abcpool.co accepted block 32 from Cypress (#2)
[8/19/11 10:45:06 PM] pool.abcpool.co accepted block 33 from Cypress (#2)
mhash: 658.4/644.0 | accept: 33 | reject: 0 | hw error: 0
There still is the 50 seconds LP socket close. I think 50 seconds is too little given that you need to communicate a new block every 10 minutes on average. Did you try a very short keep-alive, like a couple of minutes so that the socket gets closed faster if the client pc does not answer fast enough? spiccioli |
|
|
|
Thank you spiccioli for bringing this up. The very least I can do now it to make sure that "vis in numeris" is on bitcoin.org.uk's logo.
And next time I go to an Uni I'll make sure that I take some Latin classes.
You're welcome. spiccioli. btw, I did write, a couple of months ago, to RSantana maker of the coinedbits coin, since he used the same motto for his coins, telling him the same thing about vis/vires! This whole Latin g thing is something that keeps returning and I'm starting to think that it keeps returning because it really is a beatiful motto, which clearly states something about bitcoins which so unique to them... but being "wrong" it cannot settle down like those ghosts in ancient castles  |
|
|
|
A peek at a Latin dictionary confirms what spiccioli is saying about vires meaning "forces" in the military sense.
Just out of curiosity, how would one say, "you flourish (vireo) in numbers?"
If you mean 'I grow thanks to the numbers' I'd say 'numeris augeo'. spiccioli |
|
|
|
Forto En Numeros... that's it in Esperanto, I think.
Actually, that would be "Forto En Nombroj" (strength in numbers [of things]) or "Forto En Ciferoj" (strength in figures / digits). Even if it's dog Latin that I originally used internet groupthink to translate, I'm thrilled that my "Vires in Numeris" motto has caught on as well as it has.  Oh yes, and there is even another coin which uses it! http://www.coinedbits.com/but I saw it too late to 'fix' it spiccioli. |
|
|
|
Really, --edit-- big bad G --edit-- it's freightening... spiccioli. |
|
|
|
This sucks! Now I'm totally confused. No wonder the Roman Empire fell. They couldn't even agree on defining a simple phrase. Lucky for US we have...  Haha... spiccioli |
|
|
|
My INTP's intuition tells me that there is something right about
in numeris vires
Sorry but, what follows is what you can find googling for "vis in numeris" De numeris: MS Hannover, Landeskirchlichen Archiv D 10 Nr. 1 (PfA Bissendorf HS 20) ff. 186r-195v [inc: Quanta sit vis in numeris noverant hii…The beginning ('incipit' in latin, which is 'inc:' in the reference above) says: Those (they?) were aware of how much strength (how much value) is in numbers... spiccioli. |
|
|
|
Heh... I'm trying to delve into the recesses of my mind to find the drawer where I keep my high school Latin. And yet, part of me thinks that for a group that doesn't seem to know the difference between "except" and "accept", or between "affect" and "effect", this thread might just be a tad precious, no?
Piper67, if it is as you say then such a group should not use Latin  spiccioli. |
|
|
|
Vladimir, as I said in the other thread, big bad G doesn't know Latin spiccioli. |
|
|
|
Google is not able to correctly translate Latin I've studied Latin in high school (5 years) here in Italy and my wife teaches Latin in high school. 'Vires' means 'soldiers', 'armed forces'. When used in its plural form 'vires', it may mean 'strength', but only in sentences like 'vires defiunt' which means 'I'm becoming dizzy' (my 'forces' are going away, literally). If you want to correctly translate 'strength (is) in numbers' the Latin for it is: 'vis in numeris'. It was even used before, see: http://articles.latimes.com/2000/dec/17/news/ss-5286or a manuscript De numeris: MS Hannover, Landeskirchlichen Archiv D 10 Nr. 1 (PfA Bissendorf HS 20) ff. 186r-195v [inc: Quanta sit vis in numeris noverant... "How much strength is in numbers ... " spiccioli. |
|
|
|
jedi, this is what I got as soon as latest phoenix tried to connect to backup pool self.mainLoop()
File "/usr/lib/python2.6/dist-packages/twisted/internet/base.py", line 1171, in mainLoop
self.runUntilCurrent()
--- <exception caught here> ---
File "/usr/lib/python2.6/dist-packages/twisted/internet/base.py", line 793, in runUntilCurrent
call.func(*call.args, **call.kw)
File "/home/user/phoenix/minerutil/RPCProtocol.py", line 117, in errback
self.root._failure()
File "/home/user/phoenix/minerutil/RPCProtocol.py", line 408, in _failure
self.runCallback('failure')
File "/home/user/phoenix/minerutil/ClientBase.py", line 43, in runCallback
func(*args)
File "/home/user/phoenix/Miner.py", line 55, in onFailure
self.failoverCheck()
File "/home/user/phoenix/Miner.py", line 109, in failoverCheck
self.connection = self.options.makeConnection(self, True)
File "./phoenix.py", line 101, in makeConnection
exit()
exceptions.SystemExit:
I had to kill the program. TIA spiccioli |
|
|
|
I have decided to create some real physical Bitcoins. Here's what's to come. Cost: 1.15 BTC + shipping, with bulk discounts available.
casascius, the correct Latin phrase is 'vis in numeris' (not vires). my 2 satoshis spiccioli. |
|
|
|
I've tested your pool with poclbm and DiabloMiner and both have problems staying connected, while phoenix, on the same rig, works ok.
What is different between your pool and most others?
Thanks for letting us know about this. We did heavy modifications of pushpool to obtain low stale rates. We've only tested these mods with Phoenix, that's why we recommend it on our site. It now appears that some other clients may experience problems. This is DiabloMiner [8/18/11 10:22:18 AM] ERROR: Cannot connect to pool.abcpool.co: Bitcoin disconnected during response: 200 ok
I looked through the Diablo code, and I'm fairly certain this is caused by ABCPool timing out the LP connection with a '200 OK' after 50 seconds to get rid of disconnected clients. Most pools don't do this, but it is one of the reasons ABCPool can keep the stalerate low. Phoenix handles this excellently by silently reconnecting; just what we want. Diablominer might expect a different response than 200 OK. I've posted the issue in their forum. poclbm keeps disconnecting, I don't have a log, but I can give one if you need it.
That would be most helpful. Can you PM them? Hi MintCondition, here it is poclbm: pool.abcpool.co:8332 19/08/2011 09:45:59, warning: job finished, miner is idle
pool.abcpool.co:8332 19/08/2011 09:46:32, warning: job finished, miner is idle
pool.abcpool.co:8332 19/08/2011 09:46:53, warning: job finished, miner is idle
pool.abcpool.co:8332 19/08/2011 09:47:10, long poll: IO error
pool.abcpool.co:8332 19/08/2011 09:47:11, LP connected to pool.abcpool.co:8332
pool.abcpool.co:8332 19/08/2011 09:47:27, warning: job finished, miner is idle
pool.abcpool.co:8332 19/08/2011 09:47:40, warning: job finished, miner is idle
pool.abcpool.co:8332 19/08/2011 09:47:54, warning: job finished, miner is idle
pool.abcpool.co:8332 19/08/2011 09:48:06, long poll: IO error
pool.abcpool.co:8332 19/08/2011 09:48:14, LP connected to pool.abcpool.co:8332
pool.abcpool.co:8332 19/08/2011 09:48:27, warning: job finished, miner is idle
pool.abcpool.co:8332 19/08/2011 09:48:39, warning: job finished, miner is idle
pool.abcpool.co:8332 19/08/2011 09:49:04, warning: job finished, miner is idle
pool.abcpool.co:8332 19/08/2011 09:49:09, long poll: IO error
pool.abcpool.co:8332 19/08/2011 09:49:12, LP connected to pool.abcpool.co:8332
pool.abcpool.co:8332 19/08/2011 09:49:27, warning: job finished, miner is idle
pool.abcpool.co:8332 19/08/2011 09:49:49, warning: job finished, miner is idle
pool.abcpool.co:8332 19/08/2011 09:50:08, long poll: IO error
pool.abcpool.co:8332 19/08/2011 09:50:11, warning: job finished, miner is idle
pool.abcpool.co:8332 19/08/2011 09:50:12, LP connected to pool.abcpool.co:8332
pool.abcpool.co:8332 19/08/2011 09:50:25, warning: job finished, miner is idle
pool.abcpool.co:8332 19/08/2011 09:50:37, warning: job finished, miner is idle
pool.abcpool.co:8332 19/08/2011 09:50:49, warning: job finished, miner is idle
best regards. spiccioli |
|
|
|
Hi MintCondition, I've tested your pool with poclbm and DiabloMiner and both have problems staying connected, while phoenix, on the same rig, works ok. What is different between your pool and most others? This is DiabloMiner [8/18/11 10:22:18 AM] ERROR: Cannot connect to pool.abcpool.co: Bitcoin disconnected during response: 200 ok
[8/18/11 10:22:27 AM] pool.abcpool.co accepted block 342 from Cypress (#1)
[8/18/11 10:22:28 AM] pool.abcpool.co accepted block 343 from Cypress (#2)
[8/18/11 10:22:30 AM] pool.abcpool.co accepted block 344 from Cypress (#1)
[8/18/11 10:22:30 AM] pool.abcpool.co accepted block 345 from Cypress (#1)
[8/18/11 10:22:32 AM] pool.abcpool.co accepted block 346 from Cypress (#2)
[8/18/11 10:22:46 AM] pool.abcpool.co accepted block 347 from Cypress (#1)
[8/18/11 10:22:47 AM] pool.abcpool.co accepted block 348 from Cypress (#2)
[8/18/11 10:23:08 AM] ERROR: Cannot connect to pool.abcpool.co: Bitcoin disconnected during response: 200 ok
and so on and so on till it goes out of sync and invalid shares in my account go to the roof. poclbm keeps disconnecting, I don't have a log, but I can give one if you need it. TIA spiccioli. |
|
|
|
Diablo,
I've opened an account on ABCpool, I get lots of disconnection errors:
Is this an issue of the pool or something you can look at?
TIA
spiccioli.
If you haven't noticed, it appears to happen every 50 min. It could also be your network connection settings to disconnect and create a new connection after 50 min. Could be in your router if not the pool. it happens every 50 seconds, and no, it is not my router. Anyway it has problems with poclbm as well while it works ok with phoenix. spiccioli. |
|
|
|
Diablo,
I've opened an account on ABCpool, I get lots of disconnection errors:
Is this an issue of the pool or something you can look at?
TIA
spiccioli.
I've got tons of them with another miner, so it is something in the pool. Sorry for bothering. spiccioli |
|
|
|
Truly, its one of the best ones, even without hopping spiccioli |
|
|
|
Diablo, I've opened an account on ABCpool, I get lots of disconnection errors: [8/18/11 10:22:18 AM] ERROR: Cannot connect to pool.abcpool.co: Bitcoin disconnected during response: 200 ok
[8/18/11 10:22:27 AM] pool.abcpool.co accepted block 342 from Cypress (#1)
[8/18/11 10:22:28 AM] pool.abcpool.co accepted block 343 from Cypress (#2)
[8/18/11 10:22:30 AM] pool.abcpool.co accepted block 344 from Cypress (#1)
[8/18/11 10:22:30 AM] pool.abcpool.co accepted block 345 from Cypress (#1)
[8/18/11 10:22:32 AM] pool.abcpool.co accepted block 346 from Cypress (#2)
[8/18/11 10:22:46 AM] pool.abcpool.co accepted block 347 from Cypress (#1)
[8/18/11 10:22:47 AM] pool.abcpool.co accepted block 348 from Cypress (#2)
[8/18/11 10:23:08 AM] ERROR: Cannot connect to pool.abcpool.co: Bitcoin disconnected during response: 200 ok
[8/18/11 10:23:15 AM] pool.abcpool.co accepted block 349 from Cypress (#1)
[8/18/11 10:23:15 AM] pool.abcpool.co accepted block 350 from Cypress (#1)
[8/18/11 10:23:27 AM] pool.abcpool.co accepted block 351 from Cypress (#2)
[8/18/11 10:23:32 AM] pool.abcpool.co accepted block 352 from Cypress (#1)
[8/18/11 10:23:36 AM] pool.abcpool.co accepted block 353 from Cypress (#2)
[8/18/11 10:23:41 AM] pool.abcpool.co accepted block 354 from Cypress (#1)
[8/18/11 10:23:45 AM] pool.abcpool.co accepted block 355 from Cypress (#1)
[8/18/11 10:23:46 AM] pool.abcpool.co accepted block 356 from Cypress (#2)
[8/18/11 10:23:58 AM] ERROR: Cannot connect to pool.abcpool.co: Bitcoin disconnected during response: 200 ok
Is this an issue of the pool or something you can look at? TIA spiccioli. |
|
|
|
|
Show Posts
