bitHopper: Python Pool Hopper Proxy

[bitcoindaddy]

Anyone know why BTCPool24 json isn't working? The page looks correct and so does the pools.cfg config. I'm on the latest version.

Error in pool api for BTCPool24

sometimes a pool just lags for brief moment, remember you connect to pools located in various geographical areas

Well it's been like that for a couple days. And it doesn't lag when you look at it in the browser.

working fine here

Code:

[16:56:32] RPC request [c082b000] submitted to polmine.pl
[16:56:32] nofeemining: 3958709
[16:56:34] btcpool24: 95044
[16:56:47] triple: 1692301
[16:56:49] RPC request [getwork] submitted to polmine.pl
[16:56:51] slush: 82141

Are you using the latest master from c00w?

yes I do (ver.  a4fbacd), although it doesn't matter much to your problem, right now c00w is working on LP

edit: just had a lag error with them like yours, now is back up, but this tells me 1. they lack the internet connection to support high traffic or 2. my route over the internet to their server sucks and is not a good option to mine with them. Is only my case, for another person could work fine and lag some other pool that works fine with me.

Someone else was complaining earlier about the same thing.

It's odd, it seems to work just fine when I do:

Code:

curl http://www.btcpool24.com/json_stats.php
{"poolname":"BTCPool24","time":"03-08-11 17:13","hashrate":"30078","worker":"52","blocks_found":"1","round_started":"2011-08-03 13:30:23","round_duration_sec":13382,"shares_this_round":102092}

[EskimoBob]

Anyone know why BTCPool24 json isn't working? The page looks correct and so does the pools.cfg config. I'm on the latest version.

Error in pool api for BTCPool24

sometimes a pool just lags for brief moment, remember you connect to pools located in various geographical areas

Well it's been like that for a couple days. And it doesn't lag when you look at it in the browser.

Same problem here

[rampone]

Also have a btcpool24 error, but not the api error. after restart it stays at 100%.
 updated right now from i think the 6th or 7th oldest commit to the newest.

c00w and all other developers: u r faboulous

right now it went from full difficulty shares to zero shares, and surprise its the right value now (103663 shares)

mmmh, role: mine

anyone a hoppersden invite for the sickstarr in me , this thread is becoming spookingly BIG

[bitcoindaddy]

Also have the btcpool24 error, updated right now from i think the 6th or 7th oldest commit.

right now it went from full difficulty shares to zero shares, and surprise its the right value now (103663 shares)

mmmh, role: mine

anyone a hoppersden invite, this thread is becoming spookingly BIG

For me it was cause by a case mismatch between user.cfg and pools.cfg, specifically BTCPool24 vs. btcpool24.  The name must have been changed recently. A subtle problem that was staring me in the face.

[paraipan]

what's up with these guys ?    (http://btcworld.de/)

[rampone]

what's up with these guys ?    (http://btcworld.de/)

dunno, cant rememeber how much shares i laid in, was only 14 at the site (i think i did not ine a lot with them yet)

C00w: newest commit seems still to hang up and not accept new connections after hopping fastly.

Also the pools start to turn red really quick with me (therefore the fast hopping). Is "lag"detection really aggressive right now?

[muyoso]

IDK if the slicer is working correctly.  Just tried it again with bitclockers at 42% and polmine at around 38% and it would not switch off of bitclockers.

[EskimoBob]

Also have the btcpool24 error, updated right now from i think the 6th or 7th oldest commit.

right now it went from full difficulty shares to zero shares, and surprise its the right value now (103663 shares)

mmmh, role: mine

anyone a hoppersden invite, this thread is becoming spookingly BIG

For me it was cause by a case mismatch between user.cfg and pools.cfg, specifically BTCPool24 vs. btcpool24.  The name must have been changed recently. A subtle problem that was staring me in the face.

Thanx bitcoindaddy. Works now.
Because bithopper switches on even the slightest delay from the pools web server, it keeps hopping away.

[gtrrkicw]

Hi everyone, first of all I wanted to say thank you to c00w and company for making this awesome hopper. I've been using it for about a week now and it rocks.

Second, I've been trying to get the slice scheduler working and it doesn't seem to do anything. I'm running BH with --scheduler SliceScheduler and it seems to stick to just one pool even though there are several below 43.5% any thoughts?

[joulesbeef]

c00w did a lot of updating late last night.. not sure the status of the slicer. A lot of people were having problems at 4am eastern.

It IS expected to jump to some of those lower percent ones, but not very often.. we are trying to divide our work load between pools that are below 43% but not necessarily hop on and hop off immediately. I believe the last time he said it was around 3 minutes between hops. Mine is slicing


Also Know one thing, if you are on the latest and greatest you are on alpha untested software.

the slicing thing is new on c00ws, there might be some issues getting it to where we and he wants it.

[ewibit]

is btcserv not going till now or in my config an error?
-------------------------------------------------
 DB Verson: 0.2
Traceback (most recent call last):
  File "bitHopper.py", line 224, in <module>
    bithopper_global = BitHopper()
  File "bitHopper.py", line 44, in __init__
    self.db = database.Database(self)
  File "/home/ewi/bitHopper/database.py", line 29, in __init__
    self.check_database()
  File "/home/ewi/bitHopper/database.py", line 130, in check_database
    self.curs.execute(sql)
sqlite3.OperationalError: unknown database btcserv
-------------------------------------------------
TIA

[muyoso]

c00w did a lot of updating late last night.. not sure the status of the slicer. A lot of people were having problems at 4am eastern.

It IS expected to jump to some of those lower percent ones, but not very often.. we are trying to divide our work load between pools that are below 43% but not necessarily hop on and hop off immediately. I believe the last time he said it was around 3 minutes between hops. Mine is slicing


Also Know one thing, if you are on the latest and greatest you are on alpha untested software.

the slicing thing is new on c00ws, there might be some issues getting it to where we and he wants it.

Yea, thats why I reverted to an older build for now.  The cool thing about bitclockers is that their crappyness causes the old builds to "slice" in a way.  Mining on bitclockers and polmine right now.  When bitclockers lags about once a minute it switches to polmine.

[ewibit]

IDK if the slicer is working correctly.  Just tried it again with bitclockers at 42% and polmine at around 38% and it would not switch off of bitclockers.

now polmine is at around 1,8% and next BtcPool24 at around 9,6% and it does not switch...

edit: and now bitclockers  at 2,3%

[ed64]

Ahh, good to know I'm not the only one. I'll see if I can fix it up, not sure how c00w intended to trigger a switch, let me try a quick hack.

IDK if the slicer is working correctly.  Just tried it again with bitclockers at 42% and polmine at around 38% and it would not switch off of bitclockers.

now polmine is at around 1,8% and next BtcPool24 at around 9,6% and it does not switch...

edit: and now bitclockers  at 2,3%

[ed64]

This seems to be an issue:

Code:

min_slice = self.sliceinfo[valid_servers[0]]
	      server = valid_servers[0]
	      for server in valid_servers:
	        if self.sliceinfo[server] < min_slice:
	            min_slice = self.sliceinfo[server]
	            server = valid_servers[0]

Although, not sure how this related to server_update and this:

Code:

if self.sliceinfo[self.bh.pool.get_current()] > 10:
            return True

Not sure what the 10 is about, after a few rounds of slicing, that should always be true, which doesn't sound ideal...

[ewibit]

Ahh, good to know I'm not the only one. I'll see if I can fix it up, not sure how c00w intended to trigger a switch, let me try a quick hack.

now it was very long from BtcPool24
------------------------
[17:02:02] Error in pool api for btcpool24
[17:02:02] Error in pool api for btcpool24
[17:02:02] Error in pool api for btcpool24
[17:02:02] Error in pool api for btcpool24
------------------------
and then
BtcPool24 and polmine changed to
api_disable
I have it manually changed back to mine - if I have not done this, does this stay at api_disable or sometimes changing back?

[joulesbeef]

I believe it always stays api_disabled right now. When it actually says api_disabled.

BTCworld.. didnt we give up on them for faking stats? I have them disabled.. pretty sure it was due to screwing with us.

[hawks5999]

I hope everybody isn't completely sworn off Bitclockers - they've found 4 blocks today.

And look who one of their top workers has been:
gnaget are you hopping them or riding 247?
Hasn't been a bad time to be 247, tbh.
Also, I've been running with Cherry Picker on more and more rigs for the last day or so. BitClockers doesn't seem to block, delay, QOS, etc. using CP. Interesting data point.

I've been hopping them with mine_friendly.

Well, I don't really believe in mine_friendly_charity_at-a-loss
But I make my friendly contributions in my own way

[ewibit]

can it be worth to force mine at slush when we see someting like this:

[url]


there have been some very short rounds...

[paraipan]

I believe it always stays api_disabled right now. When it actually says api_disabled.

BTCworld.. didnt we give up on them for faking stats? I have them disabled.. pretty sure it was due to screwing with us.

hehe lots of btc[any] pools here,