Topic: bitHopper: Python Pool Hopper Proxy - page 85. (Read 355678 times)
Um we could set it up to use multiple accounts. currently you can hack it to use multiple pools with slightly different names. The issue is that we don't have work level slicing only time level slicing so we can't just send an even number of getworks per account. Thats the next goal once I figure out the DB issues.
bitclockers:
Yeah he's set us to be the lowest QOS. He did it a while ago. It looks like it was manual settings so get a new IP and User account and the latest version of bitHopper and you should be fine. We used to not masquerade very well and now we do.
Yeah he's set us to be the lowest QOS. He did it a while ago. It looks like it was manual settings so get a new IP and User account and the latest version of bitHopper and you should be fine. We used to not masquerade very well and now we do.
Ive done all this, read my previous post as I think that is more likely to be the issue here. Alot of non-bithoppers get same issues.
That is exactly the issue with bitclockers, for some reason it seems they restrict the maximum getwork per worker which is retarded and would affect any legit miner using one worker for all their gpu's, stupid by design.
If I mine <1gh I get no issues on bitclockers but when I route all my gpus through bithopper with one bitclockers account at ~30gh it fks out basicly immediately(anything more than 1gh per worker seems to go haywire) which brings me to another idea, cant we have bithopper login to multiple accounts and pull getwork across multiple accounts(perhaps we could preset with maximum getwork per account / no limit getwork per account)
If I mine <1gh I get no issues on bitclockers but when I route all my gpus through bithopper with one bitclockers account at ~30gh it fks out basicly immediately(anything more than 1gh per worker seems to go haywire) which brings me to another idea, cant we have bithopper login to multiple accounts and pull getwork across multiple accounts(perhaps we could preset with maximum getwork per account / no limit getwork per account)
bitclockers:
Yeah he's set us to be the lowest QOS. He did it a while ago. It looks like it was manual settings so get a new IP and User account and the latest version of bitHopper and you should be fine. We used to not masquerade very well and now we do.
Yeah he's set us to be the lowest QOS. He did it a while ago. It looks like it was manual settings so get a new IP and User account and the latest version of bitHopper and you should be fine. We used to not masquerade very well and now we do.
Found a few pools that seems hoppable not in the list.
Swepool.net looks to be a proportional again now as of recently and operating at around 5Gh~. And Digbtc.net is another pool that is a small proportional pool that can be added I think.
Could someone pls add these two pools to the pool.cfg/user.cfg list?
Swepool.net looks to be a proportional again now as of recently and operating at around 5Gh~. And Digbtc.net is another pool that is a small proportional pool that can be added I think.
Could someone pls add these two pools to the pool.cfg/user.cfg list?
thanks, digbtc is added, Swepoo would surely win the prize for the most simple and clean pool site ever, cant find nothing in there (shares for ex.)
edit: oops, now I see the shares, but not the actual round ones
Hey Para you can see the shares once you create the account and you are in the stats section while logged in.
edit: current round share that is.
This is a problem- swepool only shows you the share count if you're logged in - it won't work for bitHopper unless you're logged in on the same machine.
I take that back - you can't use swepool unless bitHopper itself can login and save a cookie, I don't see that happening soon.
Um, I am running 400mhash through bitclockers from a single machine. I did not make a new account or get a new ip. The latest version shouldn't have any obvious errors. When you are running a lot of Mhash's through them what happens? Do they just lag out a lot quicker? b/c we could have the delagger run more often. Or is it just an artificially high reject rate? and is bitclockers the only pool where it appears?
bitclocker is the only one.
and it's mainly connection errors (delagger works fine; maybe you could change the it to percentage - means: last 10 getworks, more than 2% conn error -> lag)
it is lagging really fast. it switches to bitclockers, stays for 3 secs (approx) and lag again.
with multiple bithoppers i saw way less connection errors (it stays for about 10-20secs), and the bitclocker-guy where talking about some traffic control - so i thought i could just be the amount of getworks
now i think i should make a new user and redirect my bitclockers traffic through a fresh ip
Um, I am running 400mhash through bitclockers from a single machine. I did not make a new account or get a new ip. The latest version shouldn't have any obvious errors. When you are running a lot of Mhash's through them what happens? Do they just lag out a lot quicker? b/c we could have the delagger run more often. Or is it just an artificially high reject rate? and is bitclockers the only pool where it appears?
Rejects are fine and pretty low. This is what happens:
Code:
[14:22:16] RPC request [getwork] submitted to rfcpool.com
[14:22:18] btcmonkey: 3134237
[14:22:19] triple: 2620852
[14:22:23] bitclockers: 169721
[14:22:27] RPC request [2dddd000] submitted to rfcpool.com
[14:22:28] RPC request [getwork] submitted to rfcpool.com
[14:22:35] slush: 10355371
[14:22:39] RPC request [503e8000] submitted to rfcpool.com
[14:22:40] RPC request [getwork] submitted to rfcpool.com
[14:22:42] RPC request [97826000] submitted to rfcpool.com
[14:22:46] btcmonkey: 3134253
[14:22:46] triple: 2621078
[14:22:47] nofeemining: 4307955
[14:22:52] RPC request [getwork] submitted to rfcpool.com
[14:22:53] Server change to bitclockers, telling client with LP
[14:22:53] LP triggered serving miner
[14:22:53] LP triggered serving miner
[14:22:54] rfc: 468991
[14:22:54] LP Call pool3.bitclockers.com:8332/LP
[14:23:03] btcpool24: 697559
[14:23:03] RPC request [getwork] submitted to bitclockers.com
[14:23:09] RPC request [b6976000] submitted to rfcpool.com
[14:23:12] writing to database
[14:23:13] triple: 2621292
[14:23:14] btcmonkey: 3134268
[14:23:23] bitclockers: 172216
[14:23:24] Server change to rfc, telling client with LP
[14:23:24] RPC request [3e8c1000] submitted to bitclockers.com
[14:23:24] LP triggered serving miner
[14:23:24] LP triggered serving miner
[14:23:24] LP Call pool.rfcpool.com:8332/LP
[14:23:27] RPC request [d0bdf000] submitted to bitclockers.com
[14:23:29] RPC request [getwork] submitted to rfcpool.com
[14:23:33] slush: 10370471
[14:23:33] RPC request [6b91d000] submitted to rfcpool.com
[14:23:36] polmine: 1060066
[14:23:37] RPC request [b54c2000] submitted to rfcpool.com
[14:23:41] triple: 2621511
[14:23:41] RPC request [getwork] submitted to rfcpool.com
[14:23:42] btcmonkey: 3134294
[14:23:46] RPC request [8aa82000] submitted to rfcpool.com
[14:23:48] nofeemining: 4308177
[14:23:51] RPC request [getwork] submitted to rfcpool.com
[14:23:57] rfc: 470617
[14:23:59] RPC request [85cae000] submitted to rfcpool.com
[14:24:02] RPC request [246cf000] submitted to rfcpool.com
[14:24:02] slush: 10387871
[14:24:03] btcpool24: 697751
[14:24:03] RPC request [getwork] submitted to rfcpool.com
[14:24:05] RPC request [6ddf8000] submitted to rfcpool.com
I can get like 3-4 shares to bitclockers before it lags and then hops away. 30 seconds on bitclockers and then the server is changed to RFC. No clue why it happens but its gutting my payments.
Um, I am running 400mhash through bitclockers from a single machine. I did not make a new account or get a new ip. The latest version shouldn't have any obvious errors. When you are running a lot of Mhash's through them what happens? Do they just lag out a lot quicker? b/c we could have the delagger run more often. Or is it just an artificially high reject rate? and is bitclockers the only pool where it appears?
I have bitclockers working fine for myself.
Did you create a new account, get a new IP or something like that? Did you used to have problems and then fix it in a newer version of bithopper? Are you running one instance of bithopper and having multiple miners connect to it from various rigs?
Found a few pools that seems hoppable not in the list.
Could someone pls add these two pools to the pool.cfg/user.cfg list?
btcmp.com Could someone pls add these two pools to the pool.cfg/user.cfg list?
I have bitclockers working fine for myself.
how much mhash are you pushing?
with everything above 300mh i get way more connection errors.
with different worker they all are doing fine (still some connection errors, but not that much)
I have bitclockers working fine for myself.
I am wondering how cherrypicker has bitclockers working. According to some its working flawlessly.
I wonder if its that cherrypicker is using poclbm to mine. Are we sending getworks faster than poclbm or doing anything else that would differentiate us from normal miners? If so, is there a way we could scale it back to blend in with the crowd?
I wonder if its that cherrypicker is using poclbm to mine. Are we sending getworks faster than poclbm or doing anything else that would differentiate us from normal miners? If so, is there a way we could scale it back to blend in with the crowd?
I think as soon as we can get bithopper to act directly with miners rather than feeding work back and forth as a proxy, any and all issues like this would be resolved. That said, I have the exact same issues with bitclockers using bithopper and not using it so I still think its bitclockers that hosts a shit server rather than them screwing with bithopper users.
I am wondering how cherrypicker has bitclockers working. According to some its working flawlessly.
I wonder if its that cherrypicker is using poclbm to mine. Are we sending getworks faster than poclbm or doing anything else that would differentiate us from normal miners? If so, is there a way we could scale it back to blend in with the crowd?
I wonder if its that cherrypicker is using poclbm to mine. Are we sending getworks faster than poclbm or doing anything else that would differentiate us from normal miners? If so, is there a way we could scale it back to blend in with the crowd?
Found a few pools that seems hoppable not in the list.
Swepool.net looks to be a proportional again now as of recently and operating at around 5Gh~. And Digbtc.net is another pool that is a small proportional pool that can be added I think.
Could someone pls add these two pools to the pool.cfg/user.cfg list?
Swepool.net looks to be a proportional again now as of recently and operating at around 5Gh~. And Digbtc.net is another pool that is a small proportional pool that can be added I think.
Could someone pls add these two pools to the pool.cfg/user.cfg list?
thanks, digbtc is added, Swepoo would surely win the prize for the most simple and clean pool site ever, cant find nothing in there (shares for ex.)
edit: oops, now I see the shares, but not the actual round ones
Hey Para you can see the shares once you create the account and you are in the stats section while logged in.
edit: current round share that is.
This is a problem- swepool only shows you the share count if you're logged in - it won't work for bitHopper unless you're logged in on the same machine.
Hardly worth all that for one pool
yep, its just a matter of principle
Feature request for stats page:
1) Please add a thousand separators to stat page (Shares, User shares etc).
2) Please add a button to force mining in selected pool and hop away only when another pool starts a new block
3) check pool once more, before it gets a status "api_disable"
4) remove "api_disable" after N seconds and return the pool back to its previous status (mine etc)
5) move move backup pool to the end of the mining pools list and before disabled pools
1) Please add a thousand separators to stat page (Shares, User shares etc).
2) Please add a button to force mining in selected pool and hop away only when another pool starts a new block
3) check pool once more, before it gets a status "api_disable"
4) remove "api_disable" after N seconds and return the pool back to its previous status (mine etc)
5) move move backup pool to the end of the mining pools list and before disabled pools
I have something for this list. For the miner stats at the bottom left of the page could you make it so the name is red or green according to its online status based off when they submitted shares last. For example:
After 10 min if shares have not changed for x miner then color name red for offline else color green for online.
I tried to code something like this in javascript but it's probably better off being handled with the back end rather than the stats page.
Done, issue posted on git
@litt, nice to know, thanks
i now have a working configuration for bitclockers (but it requires two different ip's)
first-ip: start a bithopper instance
second-ip: start a bithopper instance per worker on a different port (eg you have three workers just put them at ports 8000,8001,8002)
-> change pools.cfg to get stats from http:///data
format is always json, key is servers.#poolname#.shares
(poolname does not refer to its name, it the key inside [key] in pools.cfg)
-> change users.cfg to get a unique workername for bitclockers at each port
(as this file is always read in through bithopper start, you can write a script which starts the instances all from the same directory, just switches the users.cfg)
-> you could change the stat update interval in bitHopper.py (ONLY on your worker-hopper, not on stats hopper)
now connect your worker - each to a different bithopper port
now you can mine at bitclockers again.
^^ with this your stats will be a little messed up;
first-ip: start a bithopper instance
second-ip: start a bithopper instance per worker on a different port (eg you have three workers just put them at ports 8000,8001,8002)
-> change pools.cfg to get stats from http://
format is always json, key is servers.#poolname#.shares
(poolname does not refer to its name, it the key inside [key] in pools.cfg)
-> change users.cfg to get a unique workername for bitclockers at each port
(as this file is always read in through bithopper start, you can write a script which starts the instances all from the same directory, just switches the users.cfg)
-> you could change the stat update interval in bitHopper.py (ONLY on your worker-hopper, not on stats hopper)
now connect your worker - each to a different bithopper port
now you can mine at bitclockers again.
^^ with this your stats will be a little messed up;
Hardly worth all that for one pool
Found a few pools that seems hoppable not in the list.
Swepool.net looks to be a proportional again now as of recently and operating at around 5Gh~. And Digbtc.net is another pool that is a small proportional pool that can be added I think.
Could someone pls add these two pools to the pool.cfg/user.cfg list?
Swepool.net looks to be a proportional again now as of recently and operating at around 5Gh~. And Digbtc.net is another pool that is a small proportional pool that can be added I think.
Could someone pls add these two pools to the pool.cfg/user.cfg list?
thanks, digbtc is added, Swepoo would surely win the prize for the most simple and clean pool site ever, cant find nothing in there (shares for ex.)
edit: oops, now I see the shares, but not the actual round ones
Hey Para you can see the shares once you create the account and you are in the stats section while logged in.
edit: current round share that is.
Jump to: