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

[Automatic Monkey]

Hi all, having some trouble with my p2pool node.

After the BTCGuild shutdown I decided to play my own game and run my own p2pool node. Got it up and running (Linux), bitcoind is running, miners are connecting and finding shares at the expected rate, but even after a week online I still get "Current Payout=0" and no payments to the address.

Quick help would be appreciated, because others might be connecting to my node and it's one thing to waste my own hash, but worse to waste someone else's. Thanks in advance.

Wow BTCGuild a casualty of centralized pools. You are running 14.0. Whats you log look like when you run p2pool?

Here's a sample of the log:
2015-07-09 19:58:35.462721 P2Pool: 17388 shares in chain (17393 verified/17393 total) Peers: 6 (0 incoming)
2015-07-09 19:58:35.462788  Local: 0H/s in last 10.0 minutes Local dead on arrival: Expected time to share:
2015-07-09 19:58:35.462852  Shares: 6 (1 orphan, 1 dead) Stale rate: ~33.3% (9-71%) Efficiency: ~78.9% (35-107%) Current payout: (0.0000)=0.0000 BTC
2015-07-09 19:58:35.462925  Pool: 1641TH/s Stale rate: 15.5% Expected time to block: 1.5 days

This is after I took my hash off of it (I had 5 TH on it) which is why there is no hash, but you can see it found shares.

Startup string is:
run_p2pool.py --give-author 0.5 --net bitcoin -f 0.5 --address 1MyAddress

[1715211105]

1715211105

[1715211105]

1715211105

[1715211105]

1715211105

[Duce]

Hi all, having some trouble with my p2pool node.

After the BTCGuild shutdown I decided to play my own game and run my own p2pool node. Got it up and running (Linux), bitcoind is running, miners are connecting and finding shares at the expected rate, but even after a week online I still get "Current Payout=0" and no payments to the address.

Quick help would be appreciated, because others might be connecting to my node and it's one thing to waste my own hash, but worse to waste someone else's. Thanks in advance.

Wow BTCGuild a casualty of centralized pools. You are running 14.0. Whats you log look like when you run p2pool?

Here's a sample of the log:
2015-07-09 19:58:35.462721 P2Pool: 17388 shares in chain (17393 verified/17393 total) Peers: 6 (0 incoming)
2015-07-09 19:58:35.462788  Local: 0H/s in last 10.0 minutes Local dead on arrival: Expected time to share:
2015-07-09 19:58:35.462852  Shares: 6 (1 orphan, 1 dead) Stale rate: ~33.3% (9-71%) Efficiency: ~78.9% (35-107%) Current payout: (0.0000)=0.0000 BTC
2015-07-09 19:58:35.462925  Pool: 1641TH/s Stale rate: 15.5% Expected time to block: 1.5 days

This is after I took my hash off of it (I had 5 TH on it) which is why there is no hash, but you can see it found shares.

Startup string is:
run_p2pool.py --give-author 0.5 --net bitcoin -f 0.5 --address 1MyAddress

Did you open up ports 8333 (Bitcoin peer to peer), 9333 (p2p peer to peer) and optional 9332 (for connections and web interface). I only ask because you do not have an incoming connections. This would not answer your original question which JB may have hit on the right direction already.

[qumqats]

I've been mining on p2pool for well over a year without any problems.
Then came the hard upgrade and I've been having problems ever since

I've upgraded to bitcoind to 0.10.2
I've upgraded to p2pool 14.0

BUT . . .

my local p2pool status says:

P2Pool: 11391 shares in chain (2750 verified/11391 total) Peers: 7 (1 incoming)
 Local: 4285GH/s in last 10.0 minutes Local dead on arrival: ~0.0% (0-1%) Expected time to share: 50.9 minutes
 Shares: 18 (0 orphan, 0 dead) Stale rate: ~0.0% (0-18%) Efficiency: ~112.5% (92-113%) Current payout: (0.0365)=0.0365 BTC
 Pool: 689TH/s Stale rate: 11.1% Expected time to block: 3.6 days


but it's WRONG

Coin Cadence says my payout is now zero, and that the Pool rate is 1.5PH/s

*** I deleted the data directory yesterday, either the shares download has failed, or it's taking forever ***
*** the local p2pool global pool rate started higher and has been slowly going down **
*** the local p2pool payout started low and has been going up, while the Coin Cadence payout has been doing the opposite, it started high and worked it's way down to zero! ***

suggestions?
What have I done to break it and how can I fix it?

ADVthaAnksNCE

[Automatic Monkey]

Hi all, having some trouble with my p2pool node.

After the BTCGuild shutdown I decided to play my own game and run my own p2pool node. Got it up and running (Linux), bitcoind is running, miners are connecting and finding shares at the expected rate, but even after a week online I still get "Current Payout=0" and no payments to the address.

Quick help would be appreciated, because others might be connecting to my node and it's one thing to waste my own hash, but worse to waste someone else's. Thanks in advance.

Wow BTCGuild a casualty of centralized pools. You are running 14.0. Whats you log look like when you run p2pool?

Here's a sample of the log:
2015-07-09 19:58:35.462721 P2Pool: 17388 shares in chain (17393 verified/17393 total) Peers: 6 (0 incoming)
2015-07-09 19:58:35.462788  Local: 0H/s in last 10.0 minutes Local dead on arrival: Expected time to share:
2015-07-09 19:58:35.462852  Shares: 6 (1 orphan, 1 dead) Stale rate: ~33.3% (9-71%) Efficiency: ~78.9% (35-107%) Current payout: (0.0000)=0.0000 BTC
2015-07-09 19:58:35.462925  Pool: 1641TH/s Stale rate: 15.5% Expected time to block: 1.5 days

This is after I took my hash off of it (I had 5 TH on it) which is why there is no hash, but you can see it found shares.

Startup string is:
run_p2pool.py --give-author 0.5 --net bitcoin -f 0.5 --address 1MyAddress

Did you open up ports 8333 (Bitcoin peer to peer), 9333 (p2p peer to peer) and optional 9332 (for connections and web interface). I only ask because you do not have an incoming connections. This would not answer your original question which JB may have hit on the right direction already.

OK I think I see the problem now. I actually was getting paid for the shares, and because I could not have bitcoind and bitcoin-qt open at the same time I couldn't see it. That problem was solved by installing an Electrum wallet on the machine that can be open with bitcoind.

Just two other questions- 1) the address I used in the startup command was not the same one the miners use, it's one in my phone wallet with a low balance. I assumed the only thing going to that one would be the fees from the p2pool node. But nothing showed up there. Is there something else I have to do to collect fees?

2) Is it a security risk to run a public p2pool off a machine? It's running on a machine with a few staking wallets on it.

[Duce]

Tell him to leave the entrances of his
house wide open while your at it man.

What has opening ports got to do with
not getting paid for share chain block
solves.

Simple, you run a Bitcoind just for your P2P Node, you never have any coins there so it is not at risk (8333). My comment about no peers covers 9333. 9332 if you want others to use your node for mining. My answer was only directed at the 0 peers as indicated. Now in the present condition, yes 0 peers could have been indicative of an increase in traffic saturating your connection which could cause an interrupt and thus you just lost all of your peers.

As I said, JB was probably on the right track for his answer. The port information is common knowledge in the P2P community but I put it out there in case he was not aware.

[MiningSev0]

Hey Guys thank you for your good work.
A Friend of Mine is Running a p2pool node in his Server.
Since the Last 3 days we got every hour a short 'lost contact to bitcoind'-period is it beacuse of the blockchain spamming?

It's realy frustrating...
Any ideas?

[Meuh6879]

shutdown are regulary ... it's not a P2Pool issue but an restarting job like every hour with a job plan manager.

BEFORE (job plan manager restart every 1 hour)


AFTER (serverdoc survey and restart when needed)

[luthermarcus]

I've been mining on p2pool for well over a year without any problems.
Then came the hard upgrade and I've been having problems ever since

I've upgraded to bitcoind to 0.10.2
I've upgraded to p2pool 14.0

BUT . . .

my local p2pool status says:

P2Pool: 11391 shares in chain (2750 verified/11391 total) Peers: 7 (1 incoming)
 Local: 4285GH/s in last 10.0 minutes Local dead on arrival: ~0.0% (0-1%) Expected time to share: 50.9 minutes
 Shares: 18 (0 orphan, 0 dead) Stale rate: ~0.0% (0-18%) Efficiency: ~112.5% (92-113%) Current payout: (0.0365)=0.0365 BTC
 Pool: 689TH/s Stale rate: 11.1% Expected time to block: 3.6 days


but it's WRONG

Coin Cadence says my payout is now zero, and that the Pool rate is 1.5PH/s

*** I deleted the data directory yesterday, either the shares download has failed, or it's taking forever ***
*** the local p2pool global pool rate started higher and has been slowly going down **
*** the local p2pool payout started low and has been going up, while the Coin Cadence payout has been doing the opposite, it started high and worked it's way down to zero! ***

suggestions?
What have I done to break it and how can I fix it?

ADVthaAnksNCE

(2750 verified/11391 total) once this is caught up you should see an improvement

[luthermarcus]

Hi all, having some trouble with my p2pool node.

After the BTCGuild shutdown I decided to play my own game and run my own p2pool node. Got it up and running (Linux), bitcoind is running, miners are connecting and finding shares at the expected rate, but even after a week online I still get "Current Payout=0" and no payments to the address.

Quick help would be appreciated, because others might be connecting to my node and it's one thing to waste my own hash, but worse to waste someone else's. Thanks in advance.

Wow BTCGuild a casualty of centralized pools. You are running 14.0. Whats you log look like when you run p2pool?

Here's a sample of the log:
2015-07-09 19:58:35.462721 P2Pool: 17388 shares in chain (17393 verified/17393 total) Peers: 6 (0 incoming)
2015-07-09 19:58:35.462788  Local: 0H/s in last 10.0 minutes Local dead on arrival: Expected time to share:
2015-07-09 19:58:35.462852  Shares: 6 (1 orphan, 1 dead) Stale rate: ~33.3% (9-71%) Efficiency: ~78.9% (35-107%) Current payout: (0.0000)=0.0000 BTC
2015-07-09 19:58:35.462925  Pool: 1641TH/s Stale rate: 15.5% Expected time to block: 1.5 days

This is after I took my hash off of it (I had 5 TH on it) which is why there is no hash, but you can see it found shares.

Startup string is:
run_p2pool.py --give-author 0.5 --net bitcoin -f 0.5 --address 1MyAddress

Check your bitcoin if you dont have a green bar with a check mark on the bottom of your bitcoin core wallet you need to port forward 8333(bitcoin) and 9332(p2pool) through your modem and let the ports through your firewall. There should be directions at bitcoin core website on how to run a full node.

[MiningSev0]

shutdown are regulary ... it's not a P2Pool issu but an restarting job like every hour with a job plan manager.

BEFORE (job plan manager restart every 1 hour)


AFTER (serverdoc survey and restart when needed)

But we didn't changed anything - only the Update to 14
Any sugesstions where to search?

[Meuh6879]

But we didn't changed anything - only the Update to 14
Any sugesstions where to search?

the problem is not P2Pool ... it's the bitcoind or bitcoin core.

[MiningSev0]

But we didn't changed anything - only the Update to 14
Any sugesstions where to search?

the problem is not P2Pool ... it's the bitcoind or bitcoin core.

Ok, than everything i could Do is waiting   
Or do you know a Workaround?

[Meuh6879]

Request send now ... but this bug in since the 0.9.2    : https://bitcointalk.org/index.php?topic=1116851.msg11840984#msg11840984

[p3yot33at3r]

Another yummy block  

A proper one too, that contributes to the network. Unlike some other pools empty blocks........

A few more would be super nice.......

[mdude77]

OK I think I see the problem now. I actually was getting paid for the shares, and because I could not have bitcoind and bitcoin-qt open at the same time I couldn't see it. That problem was solved by installing an Electrum wallet on the machine that can be open with bitcoind.

I'm pretty sure you don't have to run bitcoind to use p2pool.  bitcoin-qt works just fine for that purpose.  At least that's how I did it when I was running p2pool on windows.

M

[notbatman]

OK I think I see the problem now. I actually was getting paid for the shares, and because I could not have bitcoind and bitcoin-qt open at the same time I couldn't see it. That problem was solved by installing an Electrum wallet on the machine that can be open with bitcoind.

I'm pretty sure you don't have to run bitcoind to use p2pool.  bitcoin-qt works just fine for that purpose.  At least that's how I did it when I was running p2pool on windows.

M

You need to run bitcoind now, bitcoin-core no longer supports mining. It's located in the bitcoin\daemon directory.

[rav3n_pl]

OK I think I see the problem now. I actually was getting paid for the shares, and because I could not have bitcoind and bitcoin-qt open at the same time I couldn't see it. That problem was solved by installing an Electrum wallet on the machine that can be open with bitcoind.

I'm pretty sure you don't have to run bitcoind to use p2pool.  bitcoin-qt works just fine for that purpose.  At least that's how I did it when I was running p2pool on windows.

M

You need to run bitcoind now, bitcoin-core no longer supports mining. It's located in the bitcoin\daemon directory.

Add

Code:

server=1
daemon=1
rpcuser=something
rpcpassword=somethingmore

to bitcoin.conf in %appdata%/bitcoin directory

[Meuh6879]

... you reference to this ? http://bitcoin.stackexchange.com/questions/2640/p2pool-crashes-the-bitcoin-client

... 0.5.0 version of Bitcoin-QT ?

  i can espect that developpers (of bitcoin) have solve this issue since a long time ...

no ? (it's a real and dumb question)

[jtoomim]

I had an issue like the above on my two p2pool nodes as well. It appears to be due to bitcoind getting overloaded from the stress test. I added this to my .bitcoin/bitcoin.conf file:

Code:

minrelaytxfee=0.0001
mintxfee=0.0001

After that, performance improved and the periodic bitcoind dropouts stopped.

I don't know what the threshold is for getting it to work. It's possible that 0.00005 or lower might work as well. Anyone want to play around with different values? I've got over 350 TH/s on my nodes, so I don't want to do anything with them that would cause unnecessary downtime.

[squidicuz]

http://imagize[Suspicious link removed]ageshack.us/a/img537/4057/vs3mqb.jpg

I had an issue like the above on my two p2pool nodes as well. It appears to be due to bitcoind getting overloaded from the stress test. I added this to my .bitcoin/bitcoin.conf file:

Code:

minrelaytxfee=0.0001
mintxfee=0.0001

After that, performance improved and the periodic bitcoind dropouts stopped.

I don't know what the threshold is for getting it to work. It's possible that 0.00005 or lower might work as well. Anyone want to play around with different values? I've got over 350 TH/s on my nodes, so I don't want to do anything with them that would cause unnecessary downtime.

I am using a min relay fee of .12 mBTC at the moment, at least until this spam clears out.  A higher fee results in less transactions you are trying to mine with your node.  I guess your node was hanging due to the large mempool when doing getblocktemplate.

Anyone else that is still experiencing bitcoind hangouts, please try increasing your minrelaytxfee?