is something wrong with the stats?
According to blockchain.info, blocks 198917, 198923 and 198926 are mined by your pool, but stats still shows 198915 as the last mined block
Topic: [4+ EH] Slush Pool (slushpool.com); Overt AsicBoost; World First Mining Pool - page 887. (Read 4382653 times)
September 15, 2012, 01:21:55 PM
Hi Slush,
is something wrong with the stats?
According to blockchain.info, blocks 198917, 198923 and 198926 are mined by your pool, but stats still shows 198915 as the last mined block
is something wrong with the stats?
According to blockchain.info, blocks 198917, 198923 and 198926 are mined by your pool, but stats still shows 198915 as the last mined block
September 14, 2012, 05:55:31 PM
I have 4 cards on there now 
Here are the stats:
[397.47 Mhash/sec] [7714 Accepted] [8 Rejected] [RPC (+LP)]
[398.73 Mhash/sec] [7717 Accepted] [9 Rejected] [RPC (+LP)]
[383.78 Mhash/sec] [7205 Accepted] [3 Rejected] [RPC (+LP)]
[400.54 Mhash/sec] [7507 Accepted] [3 Rejected] [RPC (+LP)]
23/30,140 = .07631055%
vs.
[366.03 Mhash/sec] [114607 Accepted] [980 Rejected] [RPC (+LP)]
[401.11 Mhash/sec] [199204 Accepted] [1697 Rejected] [RPC (+LP)]
[398.42 Mhash/sec] [199115 Accepted] [1620 Rejected] [RPC (+LP)]
4,297/512,926 = .837742676%
So there's some real world data for everyone!
Edit: Make that 7!
Here are the stats:
[397.47 Mhash/sec] [7714 Accepted] [8 Rejected] [RPC (+LP)]
[398.73 Mhash/sec] [7717 Accepted] [9 Rejected] [RPC (+LP)]
[383.78 Mhash/sec] [7205 Accepted] [3 Rejected] [RPC (+LP)]
[400.54 Mhash/sec] [7507 Accepted] [3 Rejected] [RPC (+LP)]
23/30,140 = .07631055%
vs.
[366.03 Mhash/sec] [114607 Accepted] [980 Rejected] [RPC (+LP)]
[401.11 Mhash/sec] [199204 Accepted] [1697 Rejected] [RPC (+LP)]
[398.42 Mhash/sec] [199115 Accepted] [1620 Rejected] [RPC (+LP)]
4,297/512,926 = .837742676%
So there's some real world data for everyone!
Edit: Make that 7!
September 14, 2012, 06:58:12 AM
WhiteShum, honestly, I'm sure there're many bugs in Diablo. All rejected should be logged in proxy (although I agree that the proxy log is quite verbose at this moment). What do you see there? If you see accepted on the pool and accepted in the proxy, then it's definitely just Diablo failing in rejection reporting.
I've tested all stuff with cgminer, poclbm and ufasoft and no one of these miners have such problems.
I've tested all stuff with cgminer, poclbm and ufasoft and no one of these miners have such problems.
September 14, 2012, 05:31:50 AM
Question
in DiabloMiner i have accept 100 shares and redject 10 shares,BUT in my account i see "Current shares" 110 --Pool accept my redject?
p.s. now i have 500 accept and 10 redject, in other pool i have 0.5-0.01 % redject wtf?
in DiabloMiner i have accept 100 shares and redject 10 shares,BUT in my account i see "Current shares" 110 --Pool accept my redject?
p.s. now i have 500 accept and 10 redject, in other pool i have 0.5-0.01 % redject wtf?
September 14, 2012, 04:52:44 AM
So far 0 stales on the new proxy 
I'm not surprised
.Quote
We average about .8%. Is that normal?
Well, unfortunately, this is possible on some backends. That's why I want to switch to Stratum as soon as possible. Next week there'll be already native support in some miners, so I hope that more people switch transparently.
In the last phase, I'll switch off the old pool and start bunch of proxies to Stratum there instead.
Quote
PS Could not resist and have 2 cards on the new Stratum protocol now!
Excellent!
September 13, 2012, 05:29:33 PM
Go for it!
Looks like I just found a block! Brings our total to 10... any way of finding out which blocks were mine?
So far 0 stales on the new proxy We average about .8%. Is that normal?
PS Could not resist and have 2 cards on the new Stratum protocol now!
Looks like I just found a block! Brings our total to 10... any way of finding out which blocks were mine?
So far 0 stales on the new proxy
We average about .8%. Is that normal?PS Could not resist and have 2 cards on the new Stratum protocol now!
September 13, 2012, 03:56:41 PM
I just moved one rig outside and there's a tarp over it to deflect any rain so that is a bit of fun today...
Awesome.
I'm inspired to move my rigs to the garage. At least until it starts getting colder, lol.
September 13, 2012, 03:49:43 PM
Let's celebrate! Block of round #13852 has been finished by Stratum pool! And the founder iiiis.... no digital, it's not you :-(.
Blocks done by Stratum can be easily identified on blockchain.info; they're "Relayed by slush" and have "Version 2".
Blocks done by Stratum can be easily identified on blockchain.info; they're "Relayed by slush" and have "Version 2".
Congrats! I'm planning on trying it soon with about 2.8Ghash (I emailed yesterday with a bug which you are working on), but I am running phoenix miner. I think it is the latest of the 1.x branch. Should it work? (Also any reason to switch miners... I get about 400Mhash from each of my 5870s. It could be a pain cause I have a lot of custom scripts for temperature control although IIRC they should work with any miner as they just use aticonfig.)
Did you tried to install dependencies by "sudo easy_install twisted stratum" ? I'll have time to dig into and release some fix only on Monday. But this is quite specific bug happening on your system and that command above should help you.
Basically you can run any getwork miner towards stratum proxy, including phoenix. So there's no reason to move to other miner if you'll have some monitoring scripts. Also I'll work on stratum patch for Phoenix 2 soon.
It works! I had to install easy_install first naturally and run "sudo easy_install -U distribute" but it looks good!
I just moved one rig outside and there's a tarp over it to deflect any rain so that is a bit of fun today... 1 card on that rig is now on stratum! I'll compare the rejects over the next 24 hours or so and report back. Then I'll switch both cards to stratum. Next week I'll move over all 2.8 Ghash.
September 13, 2012, 03:20:54 PM
Let's celebrate! Block of round #13852 has been finished by Stratum pool! And the founder iiiis.... no digital, it's not you :-(.
Blocks done by Stratum can be easily identified on blockchain.info; they're "Relayed by slush" and have "Version 2".
Blocks done by Stratum can be easily identified on blockchain.info; they're "Relayed by slush" and have "Version 2".
Congrats! I'm planning on trying it soon with about 2.8Ghash (I emailed yesterday with a bug which you are working on), but I am running phoenix miner. I think it is the latest of the 1.x branch. Should it work? (Also any reason to switch miners... I get about 400Mhash from each of my 5870s. It could be a pain cause I have a lot of custom scripts for temperature control although IIRC they should work with any miner as they just use aticonfig.)
Did you tried to install dependencies by "sudo easy_install twisted stratum" ? I'll have time to dig into and release some fix only on Monday. But this is quite specific bug happening on your system and that command above should help you.
Basically you can run any getwork miner towards stratum proxy, including phoenix. So there's no reason to move to other miner if you'll have some monitoring scripts. Also I'll work on stratum patch for Phoenix 2 soon.
September 13, 2012, 12:09:48 PM
Let's celebrate! Block of round #13852 has been finished by Stratum pool! And the founder iiiis.... no digital, it's not you :-(.
Blocks done by Stratum can be easily identified on blockchain.info; they're "Relayed by slush" and have "Version 2".
Blocks done by Stratum can be easily identified on blockchain.info; they're "Relayed by slush" and have "Version 2".
Congrats! I'm planning on trying it soon with about 2.8Ghash (I emailed yesterday with a bug which you are working on), but I am running phoenix miner. I think it is the latest of the 1.x branch. Should it work? (Also any reason to switch miners... I get about 400Mhash from each of my 5870s. It could be a pain cause I have a lot of custom scripts for temperature control although IIRC they should work with any miner as they just use aticonfig.)
September 13, 2012, 12:48:21 AM
Let's celebrate! Block of round #13852 has been finished by Stratum pool! And the founder iiiis.... no digital, it's not you :-(.
Blocks done by Stratum can be easily identified on blockchain.info; they're "Relayed by slush" and have "Version 2".
Blocks done by Stratum can be easily identified on blockchain.info; they're "Relayed by slush" and have "Version 2".
September 12, 2012, 05:12:57 PM
I just released new version of mining proxy, version 0.5.0. Older versions still works nicely, this adds some few features:
* Implemented method client.reconnect(host, port), so pool can now easily balance clients between backends or gracefully shutdown a backend without a miner outage.
* Added "--no-midstate" parameter. When used, proxy won't generate "midstate" field in the getwork response. Some old miners and Diablo still requires this field, but modern miners like poclbm/cgminer can generate midstate ourselves and in much faster way. So if you're using these miners and want to save a bit of CPU time, this argument is just for you. It speeds up getwork creation twice.
digital: The luck of whole bitcoin network in the last hour is quite interesting.
* Implemented method client.reconnect(host, port), so pool can now easily balance clients between backends or gracefully shutdown a backend without a miner outage.
* Added "--no-midstate" parameter. When used, proxy won't generate "midstate" field in the getwork response. Some old miners and Diablo still requires this field, but modern miners like poclbm/cgminer can generate midstate ourselves and in much faster way. So if you're using these miners and want to save a bit of CPU time, this argument is just for you. It speeds up getwork creation twice.
digital: The luck of whole bitcoin network in the last hour is quite interesting
. September 12, 2012, 01:51:00 PM
175% luck!
Lets keep it up...
Lets keep it up...
September 12, 2012, 01:23:31 PM
Just have a test running to see, so easy to install - no errors, easy setup. Seems like great piece of work
September 12, 2012, 10:48:05 AM
I've got my full 2.4ghash using the proxy...
Im really hoping to be the one to find the first block. Bragging Rights! lol
Im really hoping to be the one to find the first block. Bragging Rights! lol
September 12, 2012, 10:43:29 AM
I just added Stratum hashrate indicator to Stats page. We're already on 20 Ghash/s and everything seems perfectly stable - few of these disconnections were caused by me, pushing new versions to live server.
I'm being pretty optimistic and I'd like to encourage more users to move to Stratum protocol, or current Stratum beta testers to move more hashpower to it.
I knocked up short page describing main advantages of using mining proxy for miners. There're also step-by-step instructions how to run mining proxy on your rig: http://mining.bitcoin.cz/mining-proxy-howto
Stratum submitted around 300k shares. We need much more power to find the block in some reasonable time to confirm that everything is working correctly. Of course I tested it on hundreds testnet blocks, but I'd like to see first livenet block mined by Stratum pool soon :-).
I'm being pretty optimistic and I'd like to encourage more users to move to Stratum protocol, or current Stratum beta testers to move more hashpower to it.
I knocked up short page describing main advantages of using mining proxy for miners. There're also step-by-step instructions how to run mining proxy on your rig: http://mining.bitcoin.cz/mining-proxy-howto
Stratum submitted around 300k shares. We need much more power to find the block in some reasonable time to confirm that everything is working correctly. Of course I tested it on hundreds testnet blocks, but I'd like to see first livenet block mined by Stratum pool soon :-).
September 12, 2012, 04:55:11 AM
"SocketTransportClientFactory connection timed out" - looks like firewall issue. Don't you have some ports blocked?
September 12, 2012, 12:53:28 AM
error:?
~/stratum-mining-proxy$ ./mining_proxy.py -gp 8899
2012-09-12 01:47:52,279 DEBUG stats logger.get_logger # Logging initialized
2012-09-12 01:47:52,282 DEBUG protocol logger.get_logger # Logging initialized
2012-09-12 01:47:52,282 DEBUG socket_transport logger.get_logger # Logging initialized
2012-09-12 01:47:52,282 DEBUG proxy logger.get_logger # Logging initialized
2012-09-12 01:47:52,284 INFO proxy mining_proxy.main # Trying to connect to Stratum pool at api-stratum.bitcoin.cz:3333
Unhandled error in Deferred:
Unhandled Error
Traceback (most recent call last):
Failure: stratum.custom_exceptions.TransportException: SocketTransportClientFactory connection timed out
2012-09-12 01:48:22,314 DEBUG socket_transport socket_transport.clientConnectionFailed # [Failure instance: Traceback (failure with no frames):: User timeout caused connection failure.
]
2012-09-12 01:48:54,790 DEBUG socket_transport socket_transport.clientConnectionFailed # [Failure instance: Traceback (failure with no frames):: User timeout caused connection failure.
]
2012-09-12 01:49:32,289 DEBUG socket_transport socket_transport.clientConnectionFailed # [Failure instance: Traceback (failure with no frames):: User timeout caused connection failure.
~/stratum-mining-proxy$ ./mining_proxy.py -gp 8899
2012-09-12 01:47:52,279 DEBUG stats logger.get_logger # Logging initialized
2012-09-12 01:47:52,282 DEBUG protocol logger.get_logger # Logging initialized
2012-09-12 01:47:52,282 DEBUG socket_transport logger.get_logger # Logging initialized
2012-09-12 01:47:52,282 DEBUG proxy logger.get_logger # Logging initialized
2012-09-12 01:47:52,284 INFO proxy mining_proxy.main # Trying to connect to Stratum pool at api-stratum.bitcoin.cz:3333
Unhandled error in Deferred:
Unhandled Error
Traceback (most recent call last):
Failure: stratum.custom_exceptions.TransportException: SocketTransportClientFactory connection timed out
2012-09-12 01:48:22,314 DEBUG socket_transport socket_transport.clientConnectionFailed # [Failure instance: Traceback (failure with no frames):
]
2012-09-12 01:48:54,790 DEBUG socket_transport socket_transport.clientConnectionFailed # [Failure instance: Traceback (failure with no frames):
]
2012-09-12 01:49:32,289 DEBUG socket_transport socket_transport.clientConnectionFailed # [Failure instance: Traceback (failure with no frames):
September 11, 2012, 06:35:03 PM
LOL, typo. It should be "There's basically NO reason why..." :-)
had me completely confused there for a bit
September 11, 2012, 06:34:17 PM
Fine, I just finished necessary maintenance on the stratum pool. Load balancing is now in use. Not that it's required for 30 connections, but it's better to tune it up early. Now I can add backends into the loadbancer without interrupting current connections (which is anyway great improvement over Nginx load balancing used on getwork pool).
Now I don't know about any issue with Stratum and I'll leave it running for some time, to collect some stats (and hopefully solve the first block!).
Now I don't know about any issue with Stratum and I'll leave it running for some time, to collect some stats (and hopefully solve the first block!).
Jump to: