bitHopper: Python Pool Hopper Proxy

[kbsbtc]

Using the latest revision off the github (fa960e461cfa15afaf05) and it seems that after running it for 1 hour bithopper stops pushing out more work. It was running fine but just didnt have any RPC requests in the window and then it was kinda just sitting idle. Just restarted bithopper and it looks like its working. Any ideas on what happened?

[1713986745]

1713986745

[1713986745]

1713986745

[1713986745]

1713986745

[Clipse]

just started testing out latest version since quite a few versions back and I get this error in log every couple of minutes:

Code:

Unhandled error in Deferred:
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 361, in callback
    self._startRunCallbacks(result)
  File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 455, in _startRunCallbacks
    self._runCallbacks()
  File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 542, in _runCallbacks
    current.result = callback(current.result, *args, **kw)
  File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1076, in gotResult
    _inlineCallbacks(r, g, deferred)
--- <exception caught here> ---
  File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1020, in _inlineCallbacks
    result = g.send(result)
  File "/home/miner1/bitHopper/work.py", line 142, in jsonrpc_getwork
    server = bitHopper.get_new_server(server)
  File "./bitHopper.py", line 125, in get_new_server
    self.log_bdg('Lagging. :' + server)
exceptions.AttributeError: BitHopper instance has no attribute 'log_bdg'

[hawks5999]

just started testing out latest version since quite a few versions back and I get this error in log every couple of minutes:

Code:

Unhandled error in Deferred:
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 361, in callback
    self._startRunCallbacks(result)
  File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 455, in _startRunCallbacks
    self._runCallbacks()
  File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 542, in _runCallbacks
    current.result = callback(current.result, *args, **kw)
  File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1076, in gotResult
    _inlineCallbacks(r, g, deferred)
--- <exception caught here> ---
  File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1020, in _inlineCallbacks
    result = g.send(result)
  File "/home/miner1/bitHopper/work.py", line 142, in jsonrpc_getwork
    server = bitHopper.get_new_server(server)
  File "./bitHopper.py", line 125, in get_new_server
    self.log_bdg('Lagging. :' + server)
exceptions.AttributeError: BitHopper instance has no attribute 'log_bdg'

go into bithopper.py and search for log_bdg and change to log_dbg - there is one instance.

There is a patch pull request with the fix on github

[bitcoindaddy]

Using the latest revision off the github (fa960e461cfa15afaf05) and it seems that after running it for 1 hour bithopper stops pushing out more work. It was running fine but just didnt have any RPC requests in the window and then it was kinda just sitting idle. Just restarted bithopper and it looks like its working. Any ideas on what happened?

I'm having the same problem. Lots of miner idles and occasional RPC problems.  Edit - maybe it's because bitclockers is slow and can't keep the miners fed.  Edit2 - confirmed - when I disabled bitclockers, the problem went away.

Code:

127.0.0.1:8337 10/08/2011 19:20:50, Setting server (miner1 @ 127.0.0.1:8337)
127.0.0.1:8337 10/08/2011 19:21:25, warning: job finished, miner is idle
127.0.0.1:8337 10/08/2011 19:22:17, No more backup pools left. Using primary and starting over.
127.0.0.1:8337 10/08/2011 19:22:17, Setting server (miner1 @ 127.0.0.1:8337)
127.0.0.1:8337 10/08/2011 19:22:56, warning: job finished, miner is idle
127.0.0.1:8337 10/08/2011 19:23:19, warning: job finished, miner is idle
127.0.0.1:8337 10/08/2011 19:23:56, No more backup pools left. Using primary and starting over.
127.0.0.1:8337 10/08/2011 19:23:56, Setting server (miner1 @ 127.0.0.1:8337)
127.0.0.1:8337 10/08/2011 19:24:42, No more backup pools left. Using primary and starting over.
127.0.0.1:8337 10/08/2011 19:24:42, Setting server (miner1 @ 127.0.0.1:8337)
127.0.0.1:8337 10/08/2011 19:24:59, warning: job finished, miner is idle
127.0.0.1:8337 10/08/2011 19:25:42, warning: job finished, miner is idle
127.0.0.1:8337 10/08/2011 19:25:56, No more backup pools left. Using primary and starting over.
127.0.0.1:8337 10/08/2011 19:25:56, Setting server (miner1 @ 127.0.0.1:8337)
127.0.0.1:8337 10/08/2011 19:26:19, warning: job finished, miner is idle
127.0.0.1:8337 10/08/2011 19:28:38, warning: job finished, miner is idle
127.0.0.1:8337 10/08/2011 19:29:02, warning: job finished, miner is idle
127.0.0.1:8337 10/08/2011 19:29:20, warning: job finished, miner is idle
127.0.0.1:8337 10/08/2011 19:30:02, warning: job finished, miner is idle
127.0.0.1:8337 10/08/2011 19:31:28, warning: job finished, miner is idle
127.0.0.1:8337 10/08/2011 19:31:46, No more backup pools left. Using primary and starting over.
127.0.0.1:8337 10/08/2011 19:31:46, Setting server (miner1 @ 127.0.0.1:8337)
127.0.0.1:8337 10/08/2011 19:32:10, No more backup pools left. Using primary and starting over.
127.0.0.1:8337 10/08/2011 19:32:10, Setting server (miner1 @ 127.0.0.1:8337)
127.0.0.1:8337 10/08/2011 19:34:07, No more backup pools left. Using primary and starting over.
127.0.0.1:8337 10/08/2011 19:34:07, Setting server (miner1 @ 127.0.0.1:8337)
127.0.0.1:8337 10/08/2011 19:34:26, warning: job finished, miner is idle
127.0.0.1:8337 10/08/2011 19:35:10, warning: job finished, miner is idle
127.0.0.1:8337 10/08/2011 19:35:21, No more backup pools left. Using primary and starting over.
127.0.0.1:8337 10/08/2011 19:35:21, Setting server (miner1 @ 127.0.0.1:8337)
127.0.0.1:8337 10/08/2011 19:37:05, warning: job finished, miner is idle
127.0.0.1:8337 10/08/2011 19:37:57, No more backup pools left. Using primary and starting over.
127.0.0.1:8337 10/08/2011 19:37:57, Setting server (miner1 @ 127.0.0.1:8337)
127.0.0.1:8337 10/08/2011 19:40:10, warning: job finished, miner is idle        

[bb]

Yep, bitclockers is no good right now.

[Clipse]

yeh bitclockers stay connected with latest hopper for me except it literally kills 75% of my gpu's that just remains idle.

Weird, definitely getwork limitations per account. Retards.

[c00w]

Hm... I guess we need to have a timeout on getwork requests...
Um and I figured out how to add it. But it only works with new versions of twisted. As in bleeding edge.

[Clipse]

Hm... I guess we need to have a timeout on getwork requests...
Um and I figured out how to add it. But it only works with new versions of twisted. As in bleeding edge.

I think easier would be to split traffic to bitclockers across multiple accounts. That would sove the problem aswell.

[c00w]

Either way we are currently timing out after 30 seconds instead of the more reasonable 5. So it works okay for smaller setups but not very well for people with lots of hashes.

[Endeavour79]

BTCWorld.de pool entry needs to be changed to:

Code:

[btcworld]
name: BTCWorld.de
mine_address: btcworld.de:8332
api_address: http://btcworld.de/statistics
api_method: re
api_key: Verifizierte Anteile der aktuellen Runde:</th><td>([,0-9]+)</td>
api_strip: ','
url: http://btcworld.de/dashboard

[Endeavour79]

Anyone mining on Bitminter??
http://bitcointalk.org/index.php?topic=27062.0

[r2edu]

Hi! this is my first post outside the newbie section..

I´ve using bitHopper for twelve days or so... everything ok unitl the lastests versions, I can´t make it mine on deepbit or any other pool with "mine_deepbit"

I´m using the latest 0.1.6.1-18 with --startLP (test it with --noLP & --scheduler=AltSliceScheduler and nothing), GUIminer 2011-07-01, Win7x64

In BCLC, i change the pool.cfg to the old one (without the re_rate) and set it to "mine" and works ok, i recive ~0.06 per "short" rounds, ok with my 1.05 Gh/s..

This is my set-up right now:



I got some others questions but for the moment those are the more relevants..

Thanks c00w for all the great work you´re doing with this app, and sorry me for presenting with some many questions!!

BTW, my english is not the best  

[lueo]

Using the latest revision off the github (fa960e461cfa15afaf05) and it seems that after running it for 1 hour bithopper stops pushing out more work. It was running fine but just didnt have any RPC requests in the window and then it was kinda just sitting idle. Just restarted bithopper and it looks like its working. Any ideas on what happened?

I met the same problem yesterday. Then I download the release version 1.6.1, it runs well. No more crashes.

[joulesbeef]

r2edu

get rid of polmine.. they have gone anti hopper and I'm not sure if it is just stats, they were talking about manipulating our payouts as well.

some folks had trouble jumping to deepbit with bitclockers active..(they are fixed over the past few hours for me)

You dont need --startLP anymore


I use --scheduler OldDefaultScheduler

and I mine btcguild bitcoin.lc and deepbit with mine_deepbit

and I am sending shares to all 3.

and so far the accuracy has been nearly spot on..(not so good for btcguild) going back and checking when blocks have actually been found, BH is only off by a few seconds for me, most of the time.

[r2edu]

@joulesbeef: thanks for your response

I get rid off Polmine, I give it some last chance because it pays me very good the last week... done

I set Bitclockers to "info" and in an hour or so i was able to mine deepbit , but... past some rounds BH jump again to DB and my workers stop working. I see the bitHopper DOS window and i was having RPC requests but the miner doesn´t start working. Set it to "info" cause it still active (yellow) on bh and didn´t jump to other pool

It is posible that the LP take some time to start working? I was running BH for about 2-3hs and in the last 30min. starts to mine DB..

BTW, anybody knows what happens with BitMinersUnion? They change the web and it does´t seem to be a pool anymore, I have to register again... and I have 0.54 in "unconfirmed" when was working

[kbsbtc]

@joulesbeef: thanks for your response

I get rid off Polmine, I give it some last chance because it pays me very good the last week... done

I set Bitclockers to "info" and in an hour or so i was able to mine deepbit , but... past some rounds BH jump again to DB and my workers stop working. I see the bitHopper DOS window and i was having RPC requests but the miner doesn´t start working. Set it to "info" cause it still active (yellow) on bh and didn´t jump to other pool

It is posible that the LP take some time to start working? I was running BH for about 2-3hs and in the last 30min. starts to mine DB..

BTW, anybody knows what happens with BitMinersUnion? They change the web and it does´t seem to be a pool anymore, I have to register again... and I have 0.54 in "unconfirmed" when was working

I was getting the same issue with the RPC requests but the miner not working, pushed out the new revision and hopefully it will go away.

[user7516]

How I see lag compensation system:
pic

[Sukrim]

How I see lag compensation system:
pic

As Deepbit is hosted in Germany, it could on the other hand be very likely that the "de" Client predicts deepbit correctly and the "us" client predicts btcguild correctly...

Also I'm personally not sure if everyone wants to be in an IRC channel with other hoppers/miners.

You could however release a special version that does something like this and then provide a web service for everyone else to get the results of the consensus (as you don't need ~1000 samples).

[ewibit]

You could however release a special version that does something like this and then provide a web service for everyone else to get the results of the consensus (as you don't need ~1000 samples).

perhaps can we use this:
http://miner.k1024.de/#

[user7516]

As Deepbit is hosted in Germany, it could on the other hand be very likely that the "de" Client predicts deepbit correctly and the "us" client predicts btcguild correctly...

Also I'm personally not sure if everyone wants to be in an IRC channel with other hoppers/miners.

You could however release a special version that does something like this and then provide a web service for everyone else to get the results of the consensus (as you don't need ~1000 samples).

It was an example. I want to say that we can use information from bitHopper programs with the highest number of correct guesses. The channel will be only for bitHopper program, not for people.