Bitcoin Forum
February 23, 2019, 12:27:08 PM *
News: Latest Bitcoin Core release: 0.17.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 [651] 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 ... 814 »
  Print  
Author Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool  (Read 2570728 times)
jonnybravo0311
Legendary
*
Offline Offline

Activity: 1344
Merit: 1015


Mine at Jonny's Pool


View Profile WWW
July 07, 2015, 05:04:28 PM
 #13001

You are welcome... and welcome to p2pool Smiley.

Jonny's Pool - Mine with us and help us grow!  Support a pool that supports Bitcoin, not a hardware manufacturer's pockets!  No SPV cheats.  No empty blocks.
1550924828
Hero Member
*
Offline Offline

Posts: 1550924828

View Profile Personal Message (Offline)

Ignore
1550924828
Reply with quote  #2

1550924828
Report to moderator
1550924828
Hero Member
*
Offline Offline

Posts: 1550924828

View Profile Personal Message (Offline)

Ignore
1550924828
Reply with quote  #2

1550924828
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1550924828
Hero Member
*
Offline Offline

Posts: 1550924828

View Profile Personal Message (Offline)

Ignore
1550924828
Reply with quote  #2

1550924828
Report to moderator
jonnybravo0311
Legendary
*
Offline Offline

Activity: 1344
Merit: 1015


Mine at Jonny's Pool


View Profile WWW
July 07, 2015, 10:21:14 PM
 #13002

So it appears the problems continue... my node has been effectively offline for the majority of the day today.  P2Pool is pegging my CPU at 100% and I'm consistently seeing the "lost contact with bitcoind" message in the logs.  Is this solely because of the ridiculous number of unconfirmed transactions that are still flooding the network (nearly 13k at this point)?  Granted, my VPS isn't exactly a monster (but not horrible as a dual core droplet).

I'm on the latest version of p2pool and bitcoin core 0.10.2 compiled from source.

To the miners who are on my node, I apologize for the inconvenience this is likely causing you.  On the bright side, my miners fall back to ck.'s solo pool, so maybe I'll be lucky and they'll solve a block for me Tongue.

EDIT: when my node does appear online, and the miners are connected, they're reporting huge rejected hash percentages (25% or more).

Jonny's Pool - Mine with us and help us grow!  Support a pool that supports Bitcoin, not a hardware manufacturer's pockets!  No SPV cheats.  No empty blocks.
luthermarcus
Full Member
***
Offline Offline

Activity: 213
Merit: 100



View Profile
July 07, 2015, 10:40:29 PM
Last edit: July 07, 2015, 10:57:22 PM by luthermarcus
 #13003

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.

Donate Bitcoin
1Mz7ZHxPhoH1ZK2yQvo62NdHvvsS2quhzc
Donate TRX
TB3WiLEj6iuSBU5tGUKyZkjB4vqrBDvoYM
p3yot33at3r
Sr. Member
****
Offline Offline

Activity: 266
Merit: 250



View Profile
July 07, 2015, 11:37:54 PM
Last edit: July 07, 2015, 11:53:19 PM by p3yot33at3r
 #13004

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:

Code:
2015-07-06 06:14:57.151757 invalid hash for 219.239.31.11 'remember_tx' 748990 a9117513
2015-07-06 06:14:57.151874 Bad peer banned: ('219.239.31.11', 64888)
2015-07-06 06:14:57.155612 Lost peer 219.239.31.11:64888 - Connection was aborted locally, using.
2015-07-06 06:14:57.156126 > in download_shares:
2015-07-06 06:14:57.156218 > Traceback (most recent call last):
2015-07-06 06:14:57.156259 > Failure: twisted.internet.error.ConnectionAborted: Connection was aborted locally, using.

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

Code:
2015-07-06 05:13:49.929600 Incoming connection to peer 219.239.31.11:33919 established. p2pool version: 1400 '14.0'
2015-07-06 05:13:54.675766 invalid hash for 219.239.31.11 'remember_tx' 292502 69c836d4
2015-07-06 05:13:54.675885 Bad peer banned: ('219.239.31.11', 33919)
2015-07-06 05:13:54.676322 Lost peer 219.239.31.11:33919 - Connection was aborted locally, using.

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

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  Sad:

luthermarcus
Full Member
***
Offline Offline

Activity: 213
Merit: 100



View Profile
July 08, 2015, 12:04:35 AM
 #13005

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:

Code:
2015-07-06 06:14:57.151757 invalid hash for 219.239.31.11 'remember_tx' 748990 a9117513
2015-07-06 06:14:57.151874 Bad peer banned: ('219.239.31.11', 64888)
2015-07-06 06:14:57.155612 Lost peer 219.239.31.11:64888 - Connection was aborted locally, using.
2015-07-06 06:14:57.156126 > in download_shares:
2015-07-06 06:14:57.156218 > Traceback (most recent call last):
2015-07-06 06:14:57.156259 > Failure: twisted.internet.error.ConnectionAborted: Connection was aborted locally, using.

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

Code:
2015-07-06 05:13:49.929600 Incoming connection to peer 219.239.31.11:33919 established. p2pool version: 1400 '14.0'
2015-07-06 05:13:54.675766 invalid hash for 219.239.31.11 'remember_tx' 292502 69c836d4
2015-07-06 05:13:54.675885 Bad peer banned: ('219.239.31.11', 33919)
2015-07-06 05:13:54.676322 Lost peer 219.239.31.11:33919 - Connection was aborted locally, using.

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

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  Sad:



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

Donate Bitcoin
1Mz7ZHxPhoH1ZK2yQvo62NdHvvsS2quhzc
Donate TRX
TB3WiLEj6iuSBU5tGUKyZkjB4vqrBDvoYM
p3yot33at3r
Sr. Member
****
Offline Offline

Activity: 266
Merit: 250



View Profile
July 08, 2015, 12:11:39 AM
 #13006

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:

Quote
Now the interesting thing is that some core devs (paging Peter Todd, Luke-Jr, Gregory Maxwell) (some with notable direct conflicts of interest by working at Blockstream) do not wish to allow bitcoin to grow......

QFT.  Grin
p3yot33at3r
Sr. Member
****
Offline Offline

Activity: 266
Merit: 250



View Profile
July 08, 2015, 02:53:39 AM
 #13007

BLOCK!!

Phew....... Tongue
squidicuz
Newbie
*
Offline Offline

Activity: 58
Merit: 0


View Profile
July 08, 2015, 03:44:33 AM
 #13008

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:

Code:
2015-07-06 06:14:57.151757 invalid hash for 219.239.31.11 'remember_tx' 748990 a9117513
2015-07-06 06:14:57.151874 Bad peer banned: ('219.239.31.11', 64888)
2015-07-06 06:14:57.155612 Lost peer 219.239.31.11:64888 - Connection was aborted locally, using.
2015-07-06 06:14:57.156126 > in download_shares:
2015-07-06 06:14:57.156218 > Traceback (most recent call last):
2015-07-06 06:14:57.156259 > Failure: twisted.internet.error.ConnectionAborted: Connection was aborted locally, using.

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

Code:
2015-07-06 05:13:49.929600 Incoming connection to peer 219.239.31.11:33919 established. p2pool version: 1400 '14.0'
2015-07-06 05:13:54.675766 invalid hash for 219.239.31.11 'remember_tx' 292502 69c836d4
2015-07-06 05:13:54.675885 Bad peer banned: ('219.239.31.11', 33919)
2015-07-06 05:13:54.676322 Lost peer 219.239.31.11:33919 - Connection was aborted locally, using.

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

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  Sad:

http://i.imgur.com/4r7ElJH.png

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!
Meuh6879
Legendary
*
Offline Offline

Activity: 1512
Merit: 1000



View Profile
July 08, 2015, 07:24:33 AM
 #13009

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.
nonnakip
Hero Member
*****
Offline Offline

Activity: 594
Merit: 547



View Profile
July 08, 2015, 08:38:40 AM
 #13010

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.

p3yot33at3r
Sr. Member
****
Offline Offline

Activity: 266
Merit: 250



View Profile
July 08, 2015, 09:15:50 AM
 #13011

I also continue to see bitcoind connection issues every hour or so

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?
squidicuz
Newbie
*
Offline Offline

Activity: 58
Merit: 0


View Profile
July 08, 2015, 11:37:07 AM
 #13012

I also continue to see bitcoind connection issues every hour or so
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?

It is running for me, ubuntu 14.x. compiled c++ from a clone off a github.
p3yot33at3r
Sr. Member
****
Offline Offline

Activity: 266
Merit: 250



View Profile
July 08, 2015, 12:04:18 PM
Last edit: July 08, 2015, 12:48:33 PM by p3yot33at3r
 #13013

I also continue to see bitcoind connection issues every hour or so
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?

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

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

EDIT: Sorted, thanks kano  Smiley
jonnybravo0311
Legendary
*
Offline Offline

Activity: 1344
Merit: 1015


Mine at Jonny's Pool


View Profile WWW
July 08, 2015, 01:13:46 PM
 #13014

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

I also continue to see bitcoind connection issues every hour or so
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?

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

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

EDIT: Sorted, thanks kano  Smiley
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...

Jonny's Pool - Mine with us and help us grow!  Support a pool that supports Bitcoin, not a hardware manufacturer's pockets!  No SPV cheats.  No empty blocks.
Meuh6879
Legendary
*
Offline Offline

Activity: 1512
Merit: 1000



View Profile
July 08, 2015, 09:41:20 PM
 #13015

and I run p2pool servers on Ubuntu and OS X

 Grin well, it's the point ... i run a win32 engine.  Wink
notbatman
Legendary
*
Offline Offline

Activity: 1848
Merit: 1013



View Profile
July 08, 2015, 10:16:13 PM
 #13016

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.
jonnybravo0311
Legendary
*
Offline Offline

Activity: 1344
Merit: 1015


Mine at Jonny's Pool


View Profile WWW
July 08, 2015, 10:34:51 PM
 #13017

and I run p2pool servers on Ubuntu and OS X

 Grin well, it's the point ... i run a win32 engine.  Wink
Oh you poor, poor soul.  Why would you torture yourself like that? Tongue

Jonny's Pool - Mine with us and help us grow!  Support a pool that supports Bitcoin, not a hardware manufacturer's pockets!  No SPV cheats.  No empty blocks.
p3yot33at3r
Sr. Member
****
Offline Offline

Activity: 266
Merit: 250



View Profile
July 09, 2015, 12:08:58 AM
 #13018

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

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

Good news is I just compiled the latest release with only one warning & it's back up & running again  Smiley 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....... Tongue

Edit: Plenty of this too:

Code:
127.0.0.1 Disconnect: failed to read message header (Transport endpoint is not connected)
127.0.0.1 Disconnect: failed to read message header (Transport endpoint is not connected)
windpath
Legendary
*
Offline Offline

Activity: 1235
Merit: 1001


View Profile WWW
July 09, 2015, 02:35:43 PM
 #13019

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 Smiley

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://bitcointalk.org/index.php?topic=1115048.0

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.
p3yot33at3r
Sr. Member
****
Offline Offline

Activity: 266
Merit: 250



View Profile
July 09, 2015, 05:19:25 PM
 #13020

Great work windpath - well above my pay grade  Wink

Been skipping around various p2pool node finders, there's still a massive amount of nodes still mining on outdated p2pool v13  Shocked 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...... Sad
Pages: « 1 ... 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 [651] 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 ... 814 »
  Print  
 
Jump to:  

Bitcointalk.org is not available or authorized for sale. Do not believe any fake listings.
Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!