Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 164. (Read 2591920 times)

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.

Thx

A side note, wikileaks updated the "Hacking Team" files today, guess who was looking at p2pool:

https://wikileaks.org/hackingteam/emails/?q=p2pool

Great work windpath - well above my pay grade 

Been skipping around various p2pool node finders, there's still a massive amount of nodes still mining on outdated p2pool v13  I'm surprised there hasn't been a flood of complaints about missing payments from the last block....I'm seeing so many peers still getting banned......

So the original intent with the CoinCadence front end was to release the whole thing as open source...

As sometimes happens in development, the whole thing became a complicated mess

About a month ago I started working on a PHP interface to the Bitcoin API JSON-RPC with the hopes of it serving as the foundation for releasing the CoinCadence P2Pool front end, as well as about a hundred other projects I have in mind...

It's not done yet, but with the TX volume spiking I wanted to release it, particularly so folks could have web based easy access to estimatefee and getmempoolinfo.

There are 25 other commands supported in the Alpha, once I get them all integrated and the Chain Query source up on GitHub I'll re-work the CoinCadence front end to work with it and release that as well...

Check it out: http://ChainQuery.com/bitcoin-api

BTC Talk thread: https://bitcointalksearch.org/topic/chain-query-alpha-a-web-based-interface-to-the-bitcoin-api-json-rpc-1115048

Reddit Post: https://www.reddit.com/r/Bitcoin/comments/3cogxu/chain_query_alpha_a_web_based_interface_to_the/

I hope you like it so far, any questions or feedback are welcome and appreciated.

Yes, but with a system crash as soon as I started it......

Good news is I just compiled the latest release with only one warning & it's back up & running again   The amount of received transaction sizes of 1347 & 906 is staggering though, & I don't seem to be sending any back at all - which I'm putting down to the attack I think. At least it's running again.

Had my first bitcoind disconnect in nearly 20 hours a while ago too. Bummer. Back to the drawing board.......

Edit: Plenty of this too:

Oh you poor, poor soul.  Why would you torture yourself like that?

Anybody else have an issue connecting from a remote IP to the stats html pages?

It was working fine until last night, now all I get is garbled text with the only thing readable being the version number. This is when I connect from my android, no problems connecting locally however.

  well, it's the point ... i run a win32 engine.  

I'm pretty sure if p2pool was causing core to crash every 30 minutes to 1 hour, somebody would have reported it before now.  I have never seen the behavior you describe, and I run p2pool servers on Ubuntu and OS X - sometimes for months on end without a restart of either bitcoind or p2pool.

Were you able to get it compiled and built on your system?  I had no problem updating and building.  Of course, the relay isn't actually responding to anything at this point...

That's what I done - no go. Are you using 32bit or 64bit?

EDIT: Sorted, thanks kano 

It is running for me, ubuntu 14.x. compiled c++ from a clone off a github.

Hi nonnakip,

It's been nearly 12 hours since I implemented the bad IP block & I've had no bitcoind disconnects since doing so. I presume you've checked your logs for a similar repeat offender? Worth a try......

I just noticed Matt has released a new "dirty hack" relaynetworkclient for p2pool also - https://github.com/TheBlueMatt/RelayNode

gonna try & compile it now & see if it helps any......

EDIT: Nope, it still won't run on 14.04 64bit - anyone else had any luck?

I run a simple test of calling "bitcoin-cli getblocktemplate" in a loop. Normally this request is relative fast. But every 6 seconds it takes nearly 2 seconds to complete and causes 100% CPU load on a bitcoind thread during the 2 seconds. The bitcoind thread with the load changes each time so it is probably the bitcoind thread that happens to process the cli request.

I do not have time right now to profile bitcoind to isolate this issue. But I thought it was interesting that the requests take so long (busy waiting?) at nearly exact 6 second intervals.

I also continue to see bitcoind connection issues every hour or so. Connection is lost between 1 and 25 minutes! I need to make some time so I can debug the exact scenario. It occurs often enough.

Yes ... above 0.9.1 bitcoin core, RPC of Bitcoin Core (or bitcoind) crash because of the P2Pool server ...
It's not new.

I have an automated routine to restart Bitcoin Core every 30min~1h for this.

That node likely does not have the most recent update to block v13 nodes. So it will get bad shares from its bad peers and then try to pass them on.  For some reason this is creating a timeout within p2pool at times, which then causes a disconnect to bitcoind and the other [p2pool] peers.

The best course of action is to manually ban it, like you did.

With a bunch of nodes now updated to 14.0-6, the pool seems to be recovering.  Just a few hiccups here and there.  Even still, we managed to score a block tonight!

BLOCK!!

Phew.......

Yeah, I'm aware of the attack - been following it:

https://www.reddit.com/r/Bitcoin/comments/3cfext/bitcoin_under_attack/

&

https://www.reddit.com/r/Bitcoin/comments/3cg95d/bitcoin_is_resilient/

But I don't think that has anything to do with the IP flooding my node.

BTW - love this quote:


QFT. 

Here is an article which could explain what your seeing
https://bitcoinmagazine.com/21125/bitcoin-network-still-backlogged-tens-thousands-unconfirmed-transactions-causing-delays/

I dunno. It might be nothing, but I was going through my p2pool logs earlier & noticed the same IP over & over again that was connecting, submitting dodgy hash, getting banned for it then reconnecting again on a different port & doing the same thing all over again, constantly & repeatedly using a different port every time. My logs are full of the same IP, namely 219.239.31.11 - it's in China:


Then reconnect on different port, request shares, submit bad hash, get banned again:


Over & over, closely followed by a bitcoind disconnect.

Note that whoever this is is using v14, so isn't getting banned by p2pool straight away. My logs are full of this IP using a different port every connection, submitting bad hash, requesting good then getting banned - so instead of waiting for 65535 banned connections to get through, I figured I'd just get rid, so I banned it at the router level firewall too.

Since I did that a few hours ago I haven't had a single disconnect. Yet. Maybe I'm clutching at straws, but it just seems a bit weird that some China IP keeps flooding my node with shit so close to losing contact with bitcoind. I'd be interested to hear if anyone else has this IP in their logs........

Or any other ideas of course, but check your logs anyway - see if you have the same IP as in my logs.......

EDIT: Still getting this though  :

I had the problem of bitcoin core freezing (I would only notice it on p2pool log "lost connection" or through email saying my node has stalled) since i upgraded from 10.0 to 10.2 i thought it was my linksys router so i bought a switch should be arriving any day now. Could still be a coincidence but more and more people are speaking out about it. Bitcoin has been more stable now but does drop at peeks. Bitcoin uses a about 4 g ram which is 51% of a little under 8 g's and a quater to half my cpu on my intel 2 Quad CPU (Q6700 @ 2.66GHz). That's bitcoin alone. Once the switch comes in ill put p2pool back online and put out stats I should be getting 100mb/s but running a speedtest i was getting 7.5 which is slow so it could have been the connection timing out.