[1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool

[mdude77]

M

Thanks mdude, I do have 9333 forwarded and allowed also. They are all TCP ports right?

if I telnet to 9333 on pool.norgzpool.net.au I see a response also.

Everything sounds right to me.  It's probably just a matter of time.

Although I have 1 incoming connection on my node now... and it's been up for 5 hours.

M

[1714278606]

1714278606

[1714278606]

1714278606

[norgan]

M

Thanks mdude, I do have 9333 forwarded and allowed also. They are all TCP ports right?

if I telnet to 9333 on pool.norgzpool.net.au I see a response also.

Everything sounds right to me.  It's probably just a matter of time.

Although I have 1 incoming connection on my node now... and it's been up for 5 hours.

M

ok thanks, I've just restarted it with logging and max conns set to 20. maybe that will make it do something lol will see how it goes.

[sciack]

I have a VPS not at home.

Anyway I believe other ports are 8333 and 9333

by the way, my run_p2pool.py gives me lots of these errors, what it can be?

This line here explains your issues:

Code:

p2pool.util.jsonrpc.NarrowError: -10 Bitcoin is downloading blocks...

Something is up with your bitcoin daemon.  It will say this if it's really downloading, or if it's reindexing.  Do a "getinfo" to see what block it's on.  If using bitcoind directly, run "bitcoind getinfo".  If using the qt version, go to the debug console and type "getinfo".

M

Yes, I have a bad feeling, maybe it is still downloading the chain???

I did this:

bitcoind getmininginfo
{
    "blocks" : 285045,
    "currentblocksize" : 7276,
    "currentblocktx" : 14,
    "difficulty" : 2621404453.06461525,
    "errors" : "",
    "genproclimit" : -1,
    "networkhashps" : 17699612012185874,
    "pooledtx" : 14,
    "testnet" : false,
    "generate" : false,
    "hashespersec" : 0
}
 

is it up to date or not yet?? thank you

[mdude77]

Yes, I have a bad feeling, maybe it is still downloading the chain???

I did this:

bitcoind getmininginfo
{
    "blocks" : 285045,
    "currentblocksize" : 7276,
    "currentblocktx" : 14,
    "difficulty" : 2621404453.06461525,
    "errors" : "",
    "genproclimit" : -1,
    "networkhashps" : 17699612012185874,
    "pooledtx" : 14,
    "testnet" : false,
    "generate" : false,
    "hashespersec" : 0
}
 
is it up to date or not yet?? thank you

It's close, but not there yet.  Check blockchain.info, the last block is 299153.

M

[sciack]

Yes, I have a bad feeling, maybe it is still downloading the chain???

I did this:

bitcoind getmininginfo
{
    "blocks" : 285045,
    "currentblocksize" : 7276,
    "currentblocktx" : 14,
    "difficulty" : 2621404453.06461525,
    "errors" : "",
    "genproclimit" : -1,
    "networkhashps" : 17699612012185874,
    "pooledtx" : 14,
    "testnet" : false,
    "generate" : false,
    "hashespersec" : 0
}
 
is it up to date or not yet?? thank you

It's close, but not there yet.  Check blockchain.info, the last block is 299153.

M

what a dumb I am!!! I thought it was finished downloading...

Thank God, now at least I have an explanation. In the meanwhile I move my 1.5TH/s on another node so I stop wasting my time.

Thanks for help.

[mdude77]

Yes, I have a bad feeling, maybe it is still downloading the chain???

I did this:

bitcoind getmininginfo
{
    "blocks" : 285045,
    "currentblocksize" : 7276,
    "currentblocktx" : 14,
    "difficulty" : 2621404453.06461525,
    "errors" : "",
    "genproclimit" : -1,
    "networkhashps" : 17699612012185874,
    "pooledtx" : 14,
    "testnet" : false,
    "generate" : false,
    "hashespersec" : 0
}
 
is it up to date or not yet?? thank you

It's close, but not there yet.  Check blockchain.info, the last block is 299153.

M

what a dumb I am!!! I thought it was finished downloading...

Thank God, now at least I have an explanation. In the meanwhile I move my 1.5TH/s on another node so I stop wasting my time.

Thanks for help.

Maybe use my node?   http://96.44.166.190:9332

M

[ceslick]

Hi all,

Busy setting up a p2pool and this guide helped a lot.

If anyone would like to test, details are:-


Pool URL: http://p2pool.integratedideas.net:9332
User: Your BTC address
Pass: x

It will improve and get better as it goes, more details and dashboard can be found here: - http://www.integratedideas.net/p2pool-btc/

Cheers

[sciack]

Yes, I have a bad feeling, maybe it is still downloading the chain???

I did this:

bitcoind getmininginfo
{
    "blocks" : 285045,
    "currentblocksize" : 7276,
    "currentblocktx" : 14,
    "difficulty" : 2621404453.06461525,
    "errors" : "",
    "genproclimit" : -1,
    "networkhashps" : 17699612012185874,
    "pooledtx" : 14,
    "testnet" : false,
    "generate" : false,
    "hashespersec" : 0
}
 
is it up to date or not yet?? thank you

It's close, but not there yet.  Check blockchain.info, the last block is 299153.

M

what a dumb I am!!! I thought it was finished downloading...

Thank God, now at least I have an explanation. In the meanwhile I move my 1.5TH/s on another node so I stop wasting my time.

Thanks for help.

Maybe use my node?   http://96.44.166.190:9332

M

I would but from thailand I have a higher latency to your node, I am sorry!

[norgan]

ok so I have caught an error. Wondering if you could assist in working out what it may be:

Code:

Error in DeferredResource handler:
2014-05-05 03:12:27.717000 > Traceback (most recent call last):
2014-05-05 03:12:27.717000 >   File "p2pool\util\deferred_resource.pyc", line 24, in render
2014-05-05 03:12:27.717000 >     
2014-05-05 03:12:27.717000 >   File "twisted\internet\defer.pyc", line 134, in maybeDeferred
2014-05-05 03:12:27.717000 >     
2014-05-05 03:12:27.717000 >   File "twisted\web\resource.pyc", line 216, in render
2014-05-05 03:12:27.717000 >     
2014-05-05 03:12:27.717000 >   File "twisted\internet\defer.pyc", line 1187, in unwindGenerator
2014-05-05 03:12:27.717000 >     
2014-05-05 03:12:27.717000 > --- <exception caught here> ---
2014-05-05 03:12:27.717000 >   File "twisted\internet\defer.pyc", line 1045, in _inlineCallbacks
2014-05-05 03:12:27.717000 >     
2014-05-05 03:12:27.717000 >   File "p2pool\web.pyc", line 189, in render_GET
2014-05-05 03:12:27.717000 >     
2014-05-05 03:12:27.717000 >   File "p2pool\web.pyc", line 444, in <lambda>
2014-05-05 03:12:27.717000 >     
2014-05-05 03:12:27.733000 > exceptions.KeyError: 'last_'
2014-05-05 03:12:28.264000

[sciack]

Yes, I have a bad feeling, maybe it is still downloading the chain???

I did this:

bitcoind getmininginfo
{
    "blocks" : 285045,
    "currentblocksize" : 7276,
    "currentblocktx" : 14,
    "difficulty" : 2621404453.06461525,
    "errors" : "",
    "genproclimit" : -1,
    "networkhashps" : 17699612012185874,
    "pooledtx" : 14,
    "testnet" : false,
    "generate" : false,
    "hashespersec" : 0
}
 
is it up to date or not yet?? thank you

It's close, but not there yet.  Check blockchain.info, the last block is 299153.

M

Now it is up and running perfectly, efficiency 110%, DOA 1-2%

p2poolthailand.com
or p2pool.asia

[jonnybravo0311]

Yes, I have a bad feeling, maybe it is still downloading the chain???

I did this:

bitcoind getmininginfo
{
    "blocks" : 285045,
    "currentblocksize" : 7276,
    "currentblocktx" : 14,
    "difficulty" : 2621404453.06461525,
    "errors" : "",
    "genproclimit" : -1,
    "networkhashps" : 17699612012185874,
    "pooledtx" : 14,
    "testnet" : false,
    "generate" : false,
    "hashespersec" : 0
}
 
is it up to date or not yet?? thank you

It's close, but not there yet.  Check blockchain.info, the last block is 299153.

M

Now it is up and running perfectly, efficiency 110%, DOA 1-2%

p2poolthailand.com
or p2pool.asia

Glad to see you got everything resolved!  The problem was that you had not completed downloading the block chain, so your miners were finding and submitting shares that could not be rectified.

Learning experience for everyone who wants to setup their own node - absolutely ensure that you've completed synchronizing the block chain before mining on your p2pool node

[sciack]

Yes, I have a bad feeling, maybe it is still downloading the chain???

I did this:

bitcoind getmininginfo
{
    "blocks" : 285045,
    "currentblocksize" : 7276,
    "currentblocktx" : 14,
    "difficulty" : 2621404453.06461525,
    "errors" : "",
    "genproclimit" : -1,
    "networkhashps" : 17699612012185874,
    "pooledtx" : 14,
    "testnet" : false,
    "generate" : false,
    "hashespersec" : 0
}
 
is it up to date or not yet?? thank you

It's close, but not there yet.  Check blockchain.info, the last block is 299153.

M

Now it is up and running perfectly, efficiency 110%, DOA 1-2%

p2poolthailand.com
or p2pool.asia

Glad to see you got everything resolved!  The problem was that you had not completed downloading the block chain, so your miners were finding and submitting shares that could not be rectified.

Learning experience for everyone who wants to setup their own node - absolutely ensure that you've completed synchronizing the block chain before mining on your p2pool node

Yes, I agree!!

Should I add to my username +1024 for each of my miners? I am using several AntMinerS1 all with the same wallet address. What do you think?

[windpath]

Yes, I agree!!

Should I add to my username +1024 for each of my miners? I am using several AntMinerS1 all with the same wallet address. What do you think?

I'd like to see some more informed members reply to this, however it is my understanding that allowing P2Pool to dynamically set your difficulty is a more efficient choice.

[sciack]

Yes, I agree!!

Should I add to my username +1024 for each of my miners? I am using several AntMinerS1 all with the same wallet address. What do you think?

I'd like to see some more informed members reply to this, however it is my understanding that allowing P2Pool to dynamically set your difficulty is a more efficient choice.

You're probably right, since I have changed it to +1024 my predicted payout has dropped...

[jonnybravo0311]

Yes, I agree!!

Should I add to my username +1024 for each of my miners? I am using several AntMinerS1 all with the same wallet address. What do you think?

I'd like to see some more informed members reply to this, however it is my understanding that allowing P2Pool to dynamically set your difficulty is a more efficient choice.

The p2pool code looks at the node's total hash rate and assigns difficulty based upon that.  There are forks of the code that address the issue of trying to assign difficulties by address/miner.  See here: https://bitcointalk.org/index.php?topic=269042.280.

[sciack]

Yes, I agree!!

Should I add to my username +1024 for each of my miners? I am using several AntMinerS1 all with the same wallet address. What do you think?

I'd like to see some more informed members reply to this, however it is my understanding that allowing P2Pool to dynamically set your difficulty is a more efficient choice.

The p2pool code looks at the node's total hash rate and assigns difficulty based upon that.  There are forks of the code that address the issue of trying to assign difficulties by address/miner.  See here: https://bitcointalk.org/index.php?topic=269042.280.

Thank you. Interesting reading.

I have noticed I am getting messages like this every 4 seconds about:

Code:

Peer sent entire transaction ff16175d4884dc428616e8f2d447e5fe34966d0af527bd9b73c3bc4d3994fcec that was already received

Is that bad bad??

[roy7]

You're probably right, since I have changed it to +1024 my predicted payout has dropped...

+DIFF only affects the pseudo shares you send in for logging/graphing purposes, it has no effect on your earnings. Using /DIFF changes the minimum shares you'll submit, in case vardiff is setting your target difficulty above the network minimum. If you are already at the network minimum, then /DIFF lower than that again has no effect. On some alt coins, /DIFF can be useful if you don't care about dust and want more (but smaller) shares. On Bitcoin, /DIFF is mostly only useful to very large miners who want to reduce the # of shares they find (finding bigger shared instead) to help keep network difficulty down for everyone else.

[roy7]

The p2pool code looks at the node's total hash rate and assigns difficulty based upon that.  There are forks of the code that address the issue of trying to assign difficulties by address/miner.  See here: https://bitcointalk.org/index.php?topic=269042.280.

For someone running their own node I guess it doesn't matter much, but I made this simple patch for public nodes so that small miners won't have their difficulty target pushed higher by large miners on the same public node. The pull request to the normal repo is:

https://github.com/forrestv/p2pool/pull/174

A much more advanced patch is by iongchun (also a pull request to the main repo) in handling pseudo share difficulties:

https://github.com/forrestv/p2pool/pull/187

iongchun folded in his own fix for alt coins serving DIFF 0 work, so I removed my prior mini fix. People running native p2pool repo from forrest for alt coins should at least pull in iongchun's patch for the DIFF 0 fix.

[cathoderay]

Excuse my Linux noobness, but what's the command line syntax used to integrate this fix into p2pool? I've tried the "git pull" request using the link above from within the p2pool folder but I get an error - so I presume I'm doing it wrong.......

Thanks.

[roy7]

Excuse my Linux noobness, but what's the command line syntax used to integrate this fix into p2pool? I've tried the "git pull" request using the link above from within the p2pool folder but I get an error - so I presume I'm doing it wrong.......

Thanks.

I've not done it this way often, but I think you'd use:

git pull https://github.com/roy7/p2pool vardiffbyaddress

or

git pull https://github.com/iongchun/p2pool auto-worker-diff

Depending on which you wanted to pull in.