bitHopper: Python Pool Hopper Proxy

[paraipan]

damn sure, it gets stuck right after pressing enter

that means it is working.. you didnt tell me you wanted output to both file AND screen.

Code:

try bithopper.py --debug | tee >debuglog

thanks man, will try this way, and I didn't realize it's too different outputting to file or both, every day I learn something  

edit: launched it with

Code:

| tee > debuglog

and it selects the backup server (one line of output) after that it freezes

edit2: it freezes only in console, file is ok

[1713568791]

1713568791

[1713568791]

1713568791

[1713568791]

1713568791

[1713568791]

1713568791

[1713568791]

1713568791

[1713568791]

1713568791

[paraipan]

The error seems to have completely disabled my server, need to initiate a remote forced reboot

whhoaa, you got balls being on the edge in remote kudos to you

[joulesbeef]

Are Polmine stats screwy for anyone else? User page is showing 348,994 this round, pool stats page is showing 949,000.

fine here.. or what do you mean?

bithopper is reporting 975033 which is the same on the polmine server stats page.

thanks man, will try this way, and I didn't realize it's too different outputting to file or both, every day I learn something

 


hey me too.

for windows I am using

Code:

bitHopper.py  --scheduler AltSliceScheduler --startLP --debug > debugc00w.txt  2>debugc00werr.txt >con

first part gets main output and logs to file.. which is getting big quick.. second part 2> gets standard errors.. but misses a lot.. and the >con displays on console.. sans what goes into debugc00werr.txt.. to add that which doesnt seem like it catches a lot.. i need to add a 2>&1 at the very end of my code.

testings gnagets fix.. right now

ed64 will be glad to test your fork.. let me know

[c00w]

lp error?
I think I fixed it.
Website loading error?
I think I fixed it.
Too many sockets error?
Not sure where it is coming from. But i Have a sneaking suspicion what I added to client.py is causing it.

EDIT: So if you are on the bleeding edge: UPDATE!

[owowo]

Polmine is lagging out for me too.

and bitHopper is freking out with

Code:

[19:45:46] Error in pool api for slush
[19:45:46] Error in pool api for slush
[19:45:46] Error in pool api for slush
[19:45:46] Error in pool api for slush
.....a lot more of that here

but good thing is the stales are less. I'm using the latest version I DL an hour ago.

EDIT: i just (19:56 GMT+1) DL the one with updated "lp.py", I'll run it now with --debug.

EDIT2:(20:26 GMT+1) no major errs seen. seems ok.

[c00w]

Can you give me an error log with --debug?

[dribbits]

Are Polmine stats screwy for anyone else? User page is showing 348,994 this round, pool stats page is showing 949,000.

fine here.. or what do you mean?

bithopper is reporting 975033 which is the same on the polmine server stats page.

But look at your user stats for the current round, mine is showing ( 566 / 394763), yet bithopper/pool stats shows 988,000.

[joulesbeef]

when you say you downloaded the latest version.. it is probably better to paste in the actual file version.

c00w small error still on newest version, c00w-bitHopper-v0.1.3-35-g65b3a40.. dont think it matters much but am sharing.

Code:

011-08-08 13:55:31-0400 [-] 'Running Delager'
011-08-08 13:55:31-0400 [-] 'Caught, jsonrpc_call insides'
011-08-08 13:55:31-0400 [-] Unhandled Error
       Traceback (most recent call last):
       Failure: exceptions.KeyError: 'user'

011-08-08 13:55:32-0400 [HTTP11ClientProtocol,client] bithasher: 1175027

c00w I posted some debug logs for you on that error.

that was in version c00w-bitHopper-v0.1.3-19-g52db110

[joulesbeef]

Are Polmine stats screwy for anyone else? User page is showing 348,994 this round, pool stats page is showing 949,000.

fine here.. or what do you mean?

bithopper is reporting 975033 which is the same on the polmine server stats page.

But look at your user stats for the current round, mine is showing ( 566 / 394763), yet bithopper/pool stats shows 988,000.

OK i see it now.. you are right.

SO is polmine lying to us now? they were a great site to have


Hmm looking at their forums they might be lying.. good catch

The second important thing to do is to secure the mine against jumpers, just delay struck about a block of 30-60 minutes to pool hoppers have lost interest in the pool (and it is also enough to get the 4 receipts for payment).

we should probably grab that user stats number

[paraipan]

damn sure, it gets stuck right after pressing enter

that means it is working.. you didnt tell me you wanted output to both file AND screen.

Code:

try bithopper.py --debug | tee >debuglog

thanks man, will try this way, and I didn't realize it's too different outputting to file or both, every day I learn something  

edit: launched it with

Code:

| tee > debuglog

and it selects the backup server (one line of output) after that it freezes

edit2: it freezes only in console, file is ok

just managed to hack it like I want

Code:

python bitHopper.py --startLP --debug &> output

I open another console, change dirs, and put

Code:

tail -f output

to see it realtime

[djex]

Any one else having problems with digbtc api?

[paraipan]

Any one else having problems with digbtc api?

yes, it doesn't update here too  (edit: either)

[joulesbeef]

damn sure, it gets stuck right after pressing enter

that means it is working.. you didnt tell me you wanted output to both file AND screen.

Code:

try bithopper.py --debug | tee >debuglog

thanks man, will try this way, and I didn't realize it's too different outputting to file or both, every day I learn something  

edit: launched it with

Code:

| tee > debuglog

and it selects the backup server (one line of output) after that it freezes

edit2: it freezes only in console, file is ok

just managed to hack it like I want

Code:

python bitHopper.py --startLP --debug &> output

I open another console, change dirs, and put

Code:

tail -f output

to see it realtime

cool.. what works.. works.


yeah digbtc is having problems today... everyone get a PM from them? begging us to mine?

perhaps we need to info some of these small pools that with a dual prop/pps system.. makes it easier to come back for the long blocks.

and people good at regex
how do i grab the second number.. the first number not always there

Code:

<td>prediction</td><td> (308/ 443984)

something like

Code:

<td>prediction</td><td> ( */ ([0-9]+)

maybe?

[owowo]

I have just a slight diff between shares in BH and shares on Polmine site. But they are discussing delaying stats. But i think not yet in place.

[paraipan]

I have just a slight diff between shares in BH and shares on Polmine site. But they are discussing delaying stats. But i think not yet in place.

it's been delayed for a while but not too much

[owowo]

There seems something wrong with DIGbtc. On BH there are 1888786 shares 100.00%,.. on their site it's "Round Shares: 1133369".

[ed64]

If BH can't get the round shares, it defaults to current difficulty, which is 1888786

There seems something wrong with DIGbtc. On BH there are 1888786 shares 100.00%,.. on their site it's "Round Shares: 1133369".

[MaGNeT]

There seems something wrong with DIGbtc. On BH there are 1888786 shares 100.00%,.. on their site it's "Round Shares: 1133369".

Yup, saw it too.
Can't understand why, pool.cfg seems to be right, nothing changed...

[joulesbeef]

Can't understand why, pool.cfg seems to be right, nothing changed...

then it is on digbits end.. pretty sure they are having connection issues is all... that 100% number 1888786, is what BH defaults to when it cant get an API answer.

I have just a slight diff between shares in BH and shares on Polmine site. But they are discussing delaying stats. But i think not yet in place.

Go to polmine.. click on user stats.. look at the predicted block and how many shares it has and tell me their isnt a slight difference..

No I am not talking about the share count on "pool stats" page.. which is only slightly different than what BH reports.

Nope look at USER stats. It will say on predicted block you have

Code:

prediction	 ( 938/ 403674) * 50.13200000

that is way way way way different than what it says on pool stats which is

Code:

Valid round shares / total:   1 108 490

so is the right answer for total shares on the current block 403674 or 1108490?

get what we are asking now?

[ed64]

Try updating your user agent, looks like digbtc is messing around a little

Oddly a user agent like 'curl/7.21.0 (x86_64-pc-linux-gnu) libcurl/7.21.0 OpenSSL/0.9.8o zlib/1.2.3.4 libidn/1.18' works fine as well. wth...

Code:

diff --git a/work.py b/work.py
index bcac801..836ef1d 100644
--- a/work.py
+++ b/work.py
@@ -73,7 +73,7 @@ def jsonrpc_lpcall(agent,server, url, lp):
 
 @defer.inlineCallbacks
 def get(agent,url):
-    d = agent.request('GET', url, Headers({'User-Agent':['Mozilla/5.0 (Windows NT 5.1) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.107 Safari/535.1']}),None)
+    d = agent.request('GET', url, Headers({'User-Agent':['Mozilla/5.0 (Windows NT 5.1) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.109 Safari/535.1']}),None)
     response = yield d
     finish = Deferred()
     response.deliverBody(WorkProtocol(finish))