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

[mdude77]

Hi,

Please who wants to help me setting up my p2pool?? I am gonna donate 0.05 BTC for the help.

Yesterday as soon as I started it was working great with a increasing predicted payout, later on, this payout has decreased, now it is half then when I started. There is something wrong here. DOA is low. I do not understand.

Thanks. Please help!!

What's your hash rate?  Sounds like a bad luck streak to me.  The lower your hashrate, the worse the luck can be.

M

[smooth]

It's a display issue. The displayed payout is per block. As the pool grows (as it has recently) we expect to get more blocks but your share of each block is lower. It doesn't mean you are getting paid less per day, just smaller amounts more often.

Also, what is your hash rate?

Hi,

Please who wants to help me setting up my p2pool?? I am gonna donate 0.05 BTC for the help.

Yesterday as soon as I started it was working great with a increasing predicted payout, later on, this payout has decreased, now it is half then when I started. There is something wrong here. DOA is low. I do not understand.

Thanks. Please help!!

[sciack]

no guys, there is something wrong, I put back the standard web-static and I see my efficiency al 0%!!!!

how come??

I have more than 1.5 TH/s

[jonnybravo0311]

no guys, there is something wrong, I put back the standard web-static and I see my efficiency al 0%!!!!

how come??

I have more than 1.5 TH/s

How many shares does your node report it has found (how many orphan, how many dead)?
What does your node report for current hash rate?

[sciack]

9 total (8 orphaned, 1 dead) Efficiency: 0.000%

But I don't understand why yesterday it was working ok.

I am trying to reinstall p2pool from 0

Or I suspect there is something wrong in bitcoind....

anyway the pool is p2poolthailand.com:9332

[mdude77]

9 total (8 orphaned, 1 dead) Efficiency: 0.000%

But I don't understand why yesterday it was working ok.

I am trying to reinstall p2pool from 0

Or I suspect there is something wrong in bitcoind....

anyway the pool is p2ptoolthailand.com:9332

Orphaned usually means it got to the p2pool alt chain after a competing share did, and yours lost out.  I think dead means it got there so late the pool doesn't know what it is or where it would go.

I'd say you have a connectivity issue.

M

[jonnybravo0311]

9 total (8 orphaned, 1 dead) Efficiency: 0.000%

But I don't understand why yesterday it was working ok.

I am trying to reinstall p2pool from 0

Or I suspect there is something wrong in bitcoind....

anyway the pool is p2ptoolthailand.com:9332

That's precisely your problem.  Your miners found 9 shares, all of which were lost.  The 8 orphaned mean they got to the p2pool network too late.  The dead one means it didn't even make it out to the network at all.

You've got a connectivity issue from your p2pool node, and possibly a miner configuration issue.  How many inbound/outbound connections do you have?  Are you running a fully synched Bitcoin node?  Have you setup some limits in your configuration files to limit the number of connections?

EDIT: I just looked at your stats page.  You made a typo in your link, but I figured you didn't really mean p2ptool

Anyway, looking at the stats from the past few minutes since you've fired up your node, you've got a 10% DOA.  That's about 9% too high.  What is the latency between your miners and the machine running the p2pool node?  Between the node and the bitcoind?

[sciack]

I am restarting, and installed a fresh copy of the p2pool, let's see what happen

But why yesterday I was expecting 0.06444 BTC and now 0.01, I mean why I did not change anything, at least in the miners.

bitcoin.conf has only

server=1
daemon=1
rpcuser=xxxxxxxx
rpcpassword=xxxxxxxxxx

(not xxx but I am just hiding the content)

[jonnybravo0311]

I am restarting, and installed a fresh copy of the p2pool, let's see what happen

But why yesterday I was expecting 0.06444 BTC and now 0.01, I mean why I did not change anything, at least in the miners.

bitcoin.conf has only

server=1
daemon=1
rpcuser=xxxxxxxx
rpcpassword=xxxxxxxxxx

(not xxx but I am just hiding the content)

I figured you weren't really using 'xxxxxxxxxx'

Monitor your node for a while.  Like I wrote, when I looked at it, you had a 10% DOA rate.  Now, you're up to 23%.  You have a problem with your network connectivity between your miners and your node, or your miners are configured incorrectly.

[sciack]

9 total (8 orphaned, 1 dead) Efficiency: 0.000%

But I don't understand why yesterday it was working ok.

I am trying to reinstall p2pool from 0

Or I suspect there is something wrong in bitcoind....

anyway the pool is p2ptoolthailand.com:9332

That's precisely your problem.  Your miners found 9 shares, all of which were lost.  The 8 orphaned mean they got to the p2pool network too late.  The dead one means it didn't even make it out to the network at all.

You've got a connectivity issue from your p2pool node, and possibly a miner configuration issue.  How many inbound/outbound connections do you have?  Are you running a fully synched Bitcoin node?  Have you setup some limits in your configuration files to limit the number of connections?

EDIT: I just looked at your stats page.  You made a typo in your link, but I figured you didn't really mean p2ptool

Anyway, looking at the stats from the past few minutes since you've fired up your node, you've got a 10% DOA.  That's about 9% too high.  What is the latency between your miners and the machine running the p2pool node?  Between the node and the bitcoind?

Yes, sorry for the typo, I corrected it...

Yes, but 10% DOA is because is just started, usually it settle around 1-3% max.

Ping from here to my node is 25ms

from the node to bitcoind I do not know how to do it....

Should I disable the wallet on the node??

[sciack]

9 total (8 orphaned, 1 dead) Efficiency: 0.000%

But I don't understand why yesterday it was working ok.

I am trying to reinstall p2pool from 0

Or I suspect there is something wrong in bitcoind....

anyway the pool is p2ptoolthailand.com:9332

That's precisely your problem.  Your miners found 9 shares, all of which were lost.  The 8 orphaned mean they got to the p2pool network too late.  The dead one means it didn't even make it out to the network at all.

You've got a connectivity issue from your p2pool node, and possibly a miner configuration issue.  How many inbound/outbound connections do you have?  Are you running a fully synched Bitcoin node?  Have you setup some limits in your configuration files to limit the number of connections?

EDIT: I just looked at your stats page.  You made a typo in your link, but I figured you didn't really mean p2ptool

Anyway, looking at the stats from the past few minutes since you've fired up your node, you've got a 10% DOA.  That's about 9% too high.  What is the latency between your miners and the machine running the p2pool node?  Between the node and the bitcoind?

Yes, sorry for the typo, I corrected it...

Yes, but 10% DOA is because is just started, usually it settle around 1-3% max.

Ping from here to my node is 25ms

from the node to bitcoind I do not know how to do it....

Should I disable the wallet on the node??

miners are perfect, if I switch to another node I go up to 0.06 BTC expected payout immediately. The problem seems to be in some configuration.

how can I check latency from the node to bitocoind?

check now DOA is 1%

[norgan]

Hi All,

I am struggling to work out why I don't see any incoming peers when I've been up for a few days now and so far as I can tell I have all ports forwarded and opened.

9332, 9333, 8333

Any ideas?

http://pool.norgzpool.net.au:9332

Sorry to be pushy but I think my question got lost in the next lol anyway just trying to figure out how to get incoming peers and why I would be seeing no incoming peers with 6 outgoing. Any help would be appreciated. 

[sciack]

Hi All,

I am struggling to work out why I don't see any incoming peers when I've been up for a few days now and so far as I can tell I have all ports forwarded and opened.

9332, 9333, 8333

Any ideas?

http://pool.norgzpool.net.au:9332

Sorry to be pushy but I think my question got lost in the next lol anyway just trying to figure out how to get incoming peers and why I would be seeing no incoming peers with 6 outgoing. Any help would be appreciated. 

I have the same problem...

[norgan]

I have the same problem...

It's always somehow reassuring that someone else is experiencing the same problem. Lets see if we can figure out why. haha

[mdude77]

I have the same problem...

It's always somehow reassuring that someone else is experiencing the same problem. Lets see if we can figure out why. haha

Incoming connections not happening are usually caused by firewalls or port forwarding snafus.  I had that problem with my local node for ages until I figured out my DSL modem had its own firewall so they were never reaching my router to forward on.

M

[norgan]

I have the same problem...

It's always somehow reassuring that someone else is experiencing the same problem. Lets see if we can figure out why. haha

Incoming connections not happening are usually caused by firewalls or port forwarding snafus.  I had that problem with my local node for ages until I figured out my DSL modem had its own firewall so they were never reaching my router to forward on.

M

I have port 9332 forwarded and allowed and my miners can connect no problems at all. What other ports need to be allowed/forwarded?

[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?

Code:

2014-05-05 05:36:18.007167 > Error getting work from bitcoind:
2014-05-05 05:36:18.007236 > Traceback (most recent call last):
2014-05-05 05:36:18.007280 >   File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 545, in _runCallbacks
2014-05-05 05:36:18.007321 >     current.result = callback(current.result, *args, **kw)
2014-05-05 05:36:18.007361 >   File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1095, in gotResult
2014-05-05 05:36:18.007400 >     _inlineCallbacks(r, g, deferred)
2014-05-05 05:36:18.007439 >   File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1037, in _inlineCallbacks
2014-05-05 05:36:18.007478 >     result = result.throwExceptionIntoGenerator(g)
2014-05-05 05:36:18.007517 >   File "/usr/lib/python2.7/dist-packages/twisted/python/failure.py", line 382, in throwExceptionIntoGenerator
2014-05-05 05:36:18.007558 >     return g.throw(self.type, self.value, self.tb)
2014-05-05 05:36:18.007596 > --- <exception caught here> ---
2014-05-05 05:36:18.007634 >   File "/root/p2pool/p2pool/util/deferral.py", line 41, in f
2014-05-05 05:36:18.007673 >     result = yield func(*args, **kwargs)
2014-05-05 05:36:18.007711 >   File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1037, in _inlineCallbacks
2014-05-05 05:36:18.007750 >     result = result.throwExceptionIntoGenerator(g)
2014-05-05 05:36:18.007789 >   File "/usr/lib/python2.7/dist-packages/twisted/python/failure.py", line 382, in throwExceptionIntoGenerator
2014-05-05 05:36:18.007829 >     return g.throw(self.type, self.value, self.tb)
2014-05-05 05:36:18.007917 >   File "/root/p2pool/p2pool/bitcoin/helper.py", line 30, in getwork
2014-05-05 05:36:18.007961 >     work = yield go()
2014-05-05 05:36:18.008001 >   File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1037, in _inlineCallbacks
2014-05-05 05:36:18.008040 >     result = result.throwExceptionIntoGenerator(g)
2014-05-05 05:36:18.008079 >   File "/usr/lib/python2.7/dist-packages/twisted/python/failure.py", line 382, in throwExceptionIntoGenerator
2014-05-05 05:36:18.008118 >     return g.throw(self.type, self.value, self.tb)
2014-05-05 05:36:18.008205 >   File "/root/p2pool/p2pool/util/jsonrpc.py", line 133, in _http_do
2014-05-05 05:36:18.008269 >     raise Error_for_code(resp['error']['code'])(resp['error']['message'], resp['error'].get('data', None))
2014-05-05 05:36:18.008351 > p2pool.util.jsonrpc.NarrowError: -10 Bitcoin is downloading blocks...
2014-05-05 05:36:20.704794 Punishing share for 'Block-stale detected! height(3c7eaeb19823d40472686cb6002e40c292517b85ca8ea7d9) < height(1660ca5f092c9d130b94976ad8caffb6f44bc32eca3037243) or 1900896c != 1901a36e'! Jumping from 5a780513 to 03616349!
2014-05-05 05:36:20.708269 Punishing share for 'Block-stale detected! height(3c7eaeb19823d40472686cb6002e40c292517b85ca8ea7d9) < height(1660ca5f092c9d130b94976ad8caffb6f44bc32eca3037243) or 1900896c != 1901a36e'! Jumping from 5a780513 to 03616349!
2014-05-05 05:36:21.060108 Punishing share for 'Block-stale detected! height(3c7eaeb19823d40472686cb6002e40c292517b85ca8ea7d9) < height(1311ef70540180aadcb389237a5cf86090cc9481755ebc4d4) or 1900896c != 1901a36e'! Jumping from 5a780513 to 03616349!
2014-05-05 05:36:21.080853 New work for worker! Difficulty: 0.999985 Share difficulty: 1144679.946779 Total block value: 25.012906 BTC including 58 transactions
2014-05-05 05:36:21.129526 Punishing share for 'Block-stale detected! height(3c7eaeb19823d40472686cb6002e40c292517b85ca8ea7d9) < height(1311ef70540180aadcb389237a5cf86090cc9481755ebc4d4) or 1900896c != 1901a36e'! Jumping from 5a780513 to 03616349!
2014-05-05 05:36:25.728015 Punishing share for 'Block-stale detected! height(3c7eaeb19823d40472686cb6002e40c292517b85ca8ea7d9) < height(1311ef70540180aadcb389237a5cf86090cc9481755ebc4d4) or 1900896c != 1901a36e'! Jumping from 5a780513 to 03616349!
2014-05-05 05:36:25.731520 Punishing share for 'Block-stale detected! height(3c7eaeb19823d40472686cb6002e40c292517b85ca8ea7d9) < height(1311ef70540180aadcb389237a5cf86090cc9481755ebc4d4) or 1900896c != 1901a36e'! Jumping from 5a780513 to 03616349!
2014-05-05 05:36:28.190391 P2Pool: 17288 shares in chain (8740 verified/17330 total) Peers: 6 (0 incoming)
2014-05-05 05:36:28.190458  Local: 0H/s in last 0.0 seconds Local dead on arrival: ??? Expected time to share: ???
2014-05-05 05:36:28.190497  Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: 0.0113 BTC
2014-05-05 05:36:28.190539  Pool: 586TH/s Stale rate: 14.3% Expected time to block: 5.3 hours
2014-05-05 05:36:30.750547 Punishing share for 'Block-stale detected! height(3c7eaeb19823d40472686cb6002e40c292517b85ca8ea7d9) < height(1311ef70540180aadcb389237a5cf86090cc9481755ebc4d4) or 1900896c != 1901a36e'! Jumping from 5a780513 to 03616349!
2014-05-05 05:36:30.756221 Punishing share for 'Block-stale detected! height(3c7eaeb19823d40472686cb6002e40c292517b85ca8ea7d9) < height(1311ef70540180aadcb389237a5cf86090cc9481755ebc4d4) or 1900896c != 1901a36e'! Jumping from 5a780513 to 03616349!
2014-05-05 05:36:35.773332 Punishing share for 'Block-stale detected! height(3c7eaeb19823d40472686cb6002e40c292517b85ca8ea7d9) < height(1311ef70540180aadcb389237a5cf86090cc9481755ebc4d4) or 1900896c != 1901a36e'! Jumping from 5a780513 to 03616349!
2014-05-05 05:36:35.776844 Punishing share for 'Block-stale detected! height(3c7eaeb19823d40472686cb6002e40c292517b85ca8ea7d9) < height(1311ef70540180aadcb389237a5cf86090cc9481755ebc4d4) or 1900896c != 1901a36e'! Jumping from 5a780513 to 03616349!
2014-05-05 05:36:36.158103 Punishing share for 'Block-stale detected! height(3c7eaeb19823d40472686cb6002e40c292517b85ca8ea7d9) < height(1311ef70540180aadcb389237a5cf86090cc9481755ebc4d4) or 1900896c != 1901a36e'! Jumping from 5a780513 to 03616349!
2014-05-05 05:36:40.797246 Punishing share for 'Block-stale detected! height(3c7eaeb19823d40472686cb6002e40c292517b85ca8ea7d9) < height(1311ef70540180aadcb389237a5cf86090cc9481755ebc4d4) or 1900896c != 1901a36e'! Jumping from 5a780513 to 03616349!
2014-05-05 05:36:40.800768 Punishing share for 'Block-stale detected! height(3c7eaeb19823d40472686cb6002e40c292517b85ca8ea7d9) < height(1311ef70540180aadcb389237a5cf86090cc9481755ebc4d4) or 1900896c != 1901a36e'! Jumping from 5a780513 to 03616349!
2014-05-05 05:36:41.147421 Punishing share for 'Block-stale detected! height(3c7eaeb19823d40472686cb6002e40c292517b85ca8ea7d9) < height(1311ef70540180aadcb389237a5cf86090cc9481755ebc4d4) or 1900896c != 1901a36e'! Jumping from 246d54cf to 5a780513!
2014-05-05 05:36:41.180041 New work for worker! Difficulty: 0.999985 Share difficulty: 1137283.364926 Total block value: 25.012906 BTC including 58 transactions
2014-05-05 05:36:43.199075 P2Pool: 17289 shares in chain (8741 verified/17331 total) Peers: 6 (0 incoming)
2014-05-05 05:36:43.199172  Local: 0H/s in last 0.0 seconds Local dead on arrival: ??? Expected time to share: ???
2014-05-05 05:36:43.207837  Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: 0.0113 BTC
2014-05-05 05:36:43.207907  Pool: 594TH/s Stale rate: 14.3% Expected time to block: 5.3 hours
2014-05-05 05:36:44.717041 > Error getting work from bitcoind:
2014-05-05 05:36:44.717131 > Traceback (most recent call last):
2014-05-05 05:36:44.717215 >   File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 545, in _runCallbacks
2014-05-05 05:36:44.717288 >     current.result = callback(current.result, *args, **kw)
2014-05-05 05:36:44.717335 >   File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1095, in gotResult
2014-05-05 05:36:44.717375 >     _inlineCallbacks(r, g, deferred)
2014-05-05 05:36:44.717413 >   File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1037, in _inlineCallbacks
2014-05-05 05:36:44.717452 >     result = result.throwExceptionIntoGenerator(g)
2014-05-05 05:36:44.717492 >   File "/usr/lib/python2.7/dist-packages/twisted/python/failure.py", line 382, in throwExceptionIntoGenerator
2014-05-05 05:36:44.717533 >     return g.throw(self.type, self.value, self.tb)
2014-05-05 05:36:44.717572 > --- <exception caught here> ---
2014-05-05 05:36:44.717609 >   File "/root/p2pool/p2pool/util/deferral.py", line 41, in f
2014-05-05 05:36:44.717647 >     result = yield func(*args, **kwargs)
2014-05-05 05:36:44.717685 >   File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1037, in _inlineCallbacks
2014-05-05 05:36:44.717724 >     result = result.throwExceptionIntoGenerator(g)
2014-05-05 05:36:44.717762 >   File "/usr/lib/python2.7/dist-packages/twisted/python/failure.py", line 382, in throwExceptionIntoGenerator
2014-05-05 05:36:44.717802 >     return g.throw(self.type, self.value, self.tb)
2014-05-05 05:36:44.717840 >   File "/root/p2pool/p2pool/bitcoin/helper.py", line 30, in getwork
2014-05-05 05:36:44.717879 >     work = yield go()
2014-05-05 05:36:44.717916 >   File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1037, in _inlineCallbacks
2014-05-05 05:36:44.717955 >     result = result.throwExceptionIntoGenerator(g)
2014-05-05 05:36:44.717993 >   File "/usr/lib/python2.7/dist-packages/twisted/python/failure.py", line 382, in throwExceptionIntoGenerator
2014-05-05 05:36:44.718033 >

[mdude77]

I have the same problem...

It's always somehow reassuring that someone else is experiencing the same problem. Lets see if we can figure out why. haha

Incoming connections not happening are usually caused by firewalls or port forwarding snafus.  I had that problem with my local node for ages until I figured out my DSL modem had its own firewall so they were never reaching my router to forward on.

M

I have port 9332 forwarded and allowed and my miners can connect no problems at all. What other ports need to be allowed/forwarded?

9332 is the worker port.  That's not the one for incoming connections from other nodes.  9333 is.

From https://en.bitcoin.it/wiki/P2Pool:

If you are behind a NAT, you should enable TCP port forwarding on your router. Forward port 9333 to the host running P2Pool.

M

[mdude77]

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

[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.