Bitcoin Forum
December 10, 2016, 10:57:23 AM *
News: To be able to use the next phase of the beta forum software, please ensure that your email address is correct/functional.
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 [121] 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 ... 205 »
  Print  
Author Topic: bitHopper: Python Pool Hopper Proxy  (Read 333185 times)
c00w
Full Member
***
Offline Offline

Activity: 196


View Profile
August 04, 2011, 06:12:49 PM
 #2401

I have bitclockers working fine for myself.

1HEmzeuVEKxBQkEenysV1yM8oAddQ4o2TX
1481367443
Hero Member
*
Offline Offline

Posts: 1481367443

View Profile Personal Message (Offline)

Ignore
1481367443
Reply with quote  #2

1481367443
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1481367443
Hero Member
*
Offline Offline

Posts: 1481367443

View Profile Personal Message (Offline)

Ignore
1481367443
Reply with quote  #2

1481367443
Report to moderator
1481367443
Hero Member
*
Offline Offline

Posts: 1481367443

View Profile Personal Message (Offline)

Ignore
1481367443
Reply with quote  #2

1481367443
Report to moderator
flower1024
Hero Member
*****
Offline Offline

Activity: 868


luck is just a share away


View Profile
August 04, 2011, 06:15:28 PM
 #2402

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)

ewibit
Legendary
*
Offline Offline

Activity: 1749


View Profile
August 04, 2011, 06:20:26 PM
 #2403

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
muyoso
Member
**
Offline Offline

Activity: 84



View Profile
August 04, 2011, 06:25:54 PM
 #2404

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?

I drink it up!
c00w
Full Member
***
Offline Offline

Activity: 196


View Profile
August 04, 2011, 06:28:10 PM
 #2405

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?

1HEmzeuVEKxBQkEenysV1yM8oAddQ4o2TX
muyoso
Member
**
Offline Offline

Activity: 84



View Profile
August 04, 2011, 06:31:27 PM
 #2406

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.

I drink it up!
flower1024
Hero Member
*****
Offline Offline

Activity: 868


luck is just a share away


View Profile
August 04, 2011, 06:33:56 PM
 #2407

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
bitcoindaddy
Hero Member
*****
Offline Offline

Activity: 481


View Profile
August 04, 2011, 06:34:08 PM
 #2408

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?


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.
c00w
Full Member
***
Offline Offline

Activity: 196


View Profile
August 04, 2011, 06:48:50 PM
 #2409

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.

1HEmzeuVEKxBQkEenysV1yM8oAddQ4o2TX
Clipse
Hero Member
*****
Offline Offline

Activity: 504


View Profile
August 04, 2011, 06:50:03 PM
 #2410

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)

...In the land of the stale, the man with one share is king... >> Clipse

We pay miners at 130% PPS | Signup here : Bonus PPS Pool (Please read OP to understand the current process)
Clipse
Hero Member
*****
Offline Offline

Activity: 504


View Profile
August 04, 2011, 06:51:23 PM
 #2411

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.

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.

...In the land of the stale, the man with one share is king... >> Clipse

We pay miners at 130% PPS | Signup here : Bonus PPS Pool (Please read OP to understand the current process)
c00w
Full Member
***
Offline Offline

Activity: 196


View Profile
August 04, 2011, 06:55:06 PM
 #2412

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.

1HEmzeuVEKxBQkEenysV1yM8oAddQ4o2TX
Clipse
Hero Member
*****
Offline Offline

Activity: 504


View Profile
August 04, 2011, 06:58:27 PM
 #2413

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.

Cool, I can wait. Im sure it will take care of bitclockers aswell as make other things possible like continues shares from PPLNS/score pools at lower hashrate equivelants based on getwork throttling, would nullify their whole design Wink

...In the land of the stale, the man with one share is king... >> Clipse

We pay miners at 130% PPS | Signup here : Bonus PPS Pool (Please read OP to understand the current process)
EskimoBob
Legendary
*
Offline Offline

Activity: 910


Quality Printing Services by Federal Reserve Bank


View Profile
August 04, 2011, 07:00:01 PM
 #2414

who removed/renamed index.html? Smiley
Code:
web.Server Traceback (most recent call last):

<type 'exceptions.IOError'>: [Errno 2] No such file or directory: 'index.html'
/usr/lib/python2.7/site-packages/twisted/web/server.py, line 127 in process
125    try:
126      resrc = self.site.getResourceFor(self)
127      self.render(resrc)
128    except:
Self
site
twisted.web.server.Site instance @ 0x9890acc <twisted.web.server.Site instance at 0x9890acc>
....

While reading what I wrote, use the most friendliest and relaxing voice in your head.
BTW, Things in BTC bubble universes are getting ugly....
flower1024
Hero Member
*****
Offline Offline

Activity: 868


luck is just a share away


View Profile
August 04, 2011, 07:02:34 PM
 #2415

bitclockers is working fine..
just make a new account, thats enough
c00w
Full Member
***
Offline Offline

Activity: 196


View Profile
August 04, 2011, 07:10:24 PM
 #2416

I moved it. I put a modified version back.

EDIT: How did you get it to try and load index.html. What scheduler were you using?

1HEmzeuVEKxBQkEenysV1yM8oAddQ4o2TX
Clipse
Hero Member
*****
Offline Offline

Activity: 504


View Profile
August 04, 2011, 07:11:26 PM
 #2417

bitclockers is working fine..
just make a new account, thats enough

flowers I have, issues still remain when going >1gh of traffic. Its quite reliable to test from my side.

...In the land of the stale, the man with one share is king... >> Clipse

We pay miners at 130% PPS | Signup here : Bonus PPS Pool (Please read OP to understand the current process)
flower1024
Hero Member
*****
Offline Offline

Activity: 868


luck is just a share away


View Profile
August 04, 2011, 07:16:49 PM
 #2418

have you tried it without bithopper as an immediate (and different worker names)?

i still get some connection errors, but not that much as before (atm 1 conn errorevery minute - which bh ignores) - maybe you get more (as you have more getworks in general) - and therefor bh disabled bclockers faster?.
muyoso
Member
**
Offline Offline

Activity: 84



View Profile
August 04, 2011, 07:17:40 PM
 #2419

bitclockers is working fine..
just make a new account, thats enough

Created a new account and its even worse for some reason.  Now I cannot even submit a share before bithopper hops away.

I drink it up!
Clipse
Hero Member
*****
Offline Offline

Activity: 504


View Profile
August 04, 2011, 07:23:43 PM
 #2420

have you tried it without bithopper as an immediate (and different worker names)?

i still get some connection errors, but not that much as before (atm 1 conn errorevery minute - which bh ignores) - maybe you get more (as you have more getworks in general) - and therefor bh disabled bclockers faster?.

Yep, no bithopper+new ip+new account = bitclockers work semi stable <1gh , total wackjob >1gh , with bithopper+new ip+new account = bitclockers exact same results.

Im still 99.9% sure its a getwork per worker issue. If you are really bored you can keep track on multiple refreshes on the bitclocks stats page showing the top hashers all dropping down and back up over and over, doesnt seem to be such an issue for low hashers of <1gh .

So in essence, it seems bitclockers idea of QOS is getwork throttling per worker, lame.

...In the land of the stale, the man with one share is king... >> Clipse

We pay miners at 130% PPS | Signup here : Bonus PPS Pool (Please read OP to understand the current process)
Pages: « 1 ... 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 [121] 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 ... 205 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!