Bitcoin Forum
December 08, 2016, 12:18:02 PM *
News: To be able to use the next phase of the beta forum software, please ensure that your email address is correct/functional.
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 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 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 ... 744 »
  Print  
Author Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool  (Read 2032749 times)
Richy_T
Legendary
*
Offline Offline

Activity: 1246


1RichyTrEwPYjZSeAYxeiFBNnKC9UjC5k


View Profile
October 21, 2015, 03:27:20 PM
 #13601

OK, think I'm done with this pool. My payout on the last block according to the graph should have been 0.012 but was actually around 0.005. Then I had to restart the pool and bitcoind and my shares dropped again. Something screwy, chaps.

I'm not sure what front end your running, but the predicted payout reported by p2pool is exact if a block is found "now". Perhaps you had some shares drop off from when you saw it and when the block was mined?



Nope. The block was mined at 08:59:53.

The graph shows 0.014 up until I had to kill the p2pool and bitcoind at 09:05 because it was interfering with my Cisco phone. (I blame the Cisco phone for this FWIW).

Payout was around 0.005 (Won't say the exact amount)

Then the graph shows a gap before I started bitcoind and p2pool again when my call was done.

Then the graph continues to show 0.014 for a few minutes then it drops to 0.005, apparently losing most of the shares I had taken the last 24 hours building up.

Someone suggested that maybe the payout address had changed for my earlier issue of losing shares. Besides the fact that I had been running p2pool without restarting from way before it happened so that couldn't have been the case, I also just changed my payout address (to one that I'm OK with sharing) and the payout dropped to 0 (as you would expect) whereas before when it happened, it didn't.



1RichyTrEwPYjZSeAYxeiFBNnKC9UjC5k
1481199482
Hero Member
*
Offline Offline

Posts: 1481199482

View Profile Personal Message (Offline)

Ignore
1481199482
Reply with quote  #2

1481199482
Report to moderator
1481199482
Hero Member
*
Offline Offline

Posts: 1481199482

View Profile Personal Message (Offline)

Ignore
1481199482
Reply with quote  #2

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

Posts: 1481199482

View Profile Personal Message (Offline)

Ignore
1481199482
Reply with quote  #2

1481199482
Report to moderator
yslyung
Legendary
*
Offline Offline

Activity: 1064


Mine Mine Mine


View Profile
October 21, 2015, 03:27:25 PM
 #13602

To anyone who has experiences in p2pool, for 2.3PH/s running 24x7 how many bitcoins would you estimate I would get/day?

Thanks

D = Difficulty
H = Mhash/s
C = Reward (currenctly 25 BTC, soon to be 12.5)

24 / (D * 2^32 / (H * 10^6) / 60 / 60) * C = BTC/day
Writing the formula another way:
Code:
25 / (2^32 * difficulty / hashrate / 86400)
For 2.3PH/s it's 18.99852101BTC expected per day.


Your calculation seems fairly accurate.

I get about 18.6 with PPS.

I might give it a shot. thanks man.


as i mentioned earlier, you'll need to be very patient with p2p. takes sometime to build up the payout. best is to run your own p2p next to your miners.

would love to see a boost in p2p
Richy_T
Legendary
*
Offline Offline

Activity: 1246


1RichyTrEwPYjZSeAYxeiFBNnKC9UjC5k


View Profile
October 21, 2015, 03:41:49 PM
 #13603

One thought on the dropping shares. I know that p2pool uses sharechains. Is it possible somehow that there is a fork going on in the background and one of the forks eventually gets orphaned. That could kind-of explain how my expected payout dropped to what the payout was in the block *after* the block had been mined. If I was on the shorter fork...

I am now collecting data about expected payouts for everyone listed in my instance of p2pool and I'll see if this looks like it's affecting anybody else.

1RichyTrEwPYjZSeAYxeiFBNnKC9UjC5k
Richy_T
Legendary
*
Offline Offline

Activity: 1246


1RichyTrEwPYjZSeAYxeiFBNnKC9UjC5k


View Profile
October 21, 2015, 04:24:26 PM
 #13604

OK, here's some more oddness. Note the difference before and after the restart





Note that the previous drop in payout I had, I had over-restricted my bandwidth with tc.sh (because my upsteam was saturated) so I am wondering if I somehow disconnected from a "false" chain or possibly some kind of DOS (note the high in/out) or... Who knows? It's beyond me.

1RichyTrEwPYjZSeAYxeiFBNnKC9UjC5k
p3yot33at3r
Sr. Member
****
Offline Offline

Activity: 266



View Profile
October 21, 2015, 04:48:08 PM
 #13605

Just on the off chance, are you using the latest version of p2pool?

Saturation should never be a problem with p2pool - it uses minimal bandwidth, almost nothing. How many connections does your bitcoind have? I restrict mine to 14 to keep bandwidth down - I also use QOS for prioritizing traffic on ports 9332,9333,8332 & 8333.
jonnybravo0311
Legendary
*
Offline Offline

Activity: 1008


Mine at Jonny's Pool


View Profile WWW
October 21, 2015, 05:04:31 PM
 #13606

Just on the off chance, are you using the latest version of p2pool?

Saturation should never be a problem with p2pool - it uses minimal bandwidth, almost nothing. How many connections does your bitcoind have? I restrict mine to 14 to keep bandwidth down - I also use QOS for prioritizing traffic on ports 9332,9333,8332 & 8333.
That would have been my question as well, but using a version earlier than 14 would result in no shares submitted at all, and hence no expected or actual payouts.  To be honest, I've never seen the behavior Richy_T is reporting here.  Yes, I've seen shares drop off the chain; however, it is in proportion to when they were added.  For example, if I suddenly start mining with 1PH/s, I would see a very rapid increase in the number of shares I have on the chain, and then when I stopped, they would drop off at the same rate.

My calculated expected payouts provided by the node have always been spot on (give or take a few satoshi).  My actual payouts reflect the node's expectations.

I wish I had some better news or a solution I could offer, but unfortunately I'm at a loss, too.

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

Activity: 1246


1RichyTrEwPYjZSeAYxeiFBNnKC9UjC5k


View Profile
October 21, 2015, 05:04:45 PM
 #13607

Just on the off chance, are you using the latest version of p2pool?

Saturation should never be a problem with p2pool - it uses minimal bandwidth, almost nothing. How many connections does your bitcoind have? I restrict mine to 14 to keep bandwidth down - I also use QOS for prioritizing traffic on ports 9332,9333,8332 & 8333.

It shouldn't but see the graph posted above.

bitcoind is left as the default (I believe Cool and is on QOS (which I also have to switch off when I am using the dumb Cisco phone). P2pool is unrestricted and is normally fine for bandwidth. Version is 14.0 which is the latest afaik.

1RichyTrEwPYjZSeAYxeiFBNnKC9UjC5k
p3yot33at3r
Sr. Member
****
Offline Offline

Activity: 266



View Profile
October 21, 2015, 05:12:57 PM
 #13608

Just on the off chance, are you using the latest version of p2pool?

Saturation should never be a problem with p2pool - it uses minimal bandwidth, almost nothing. How many connections does your bitcoind have? I restrict mine to 14 to keep bandwidth down - I also use QOS for prioritizing traffic on ports 9332,9333,8332 & 8333.

It shouldn't but see the graph posted above.

bitcoind is left as the default (I believe Cool and is on QOS (which I also have to switch off when I am using the dumb Cisco phone). P2pool is unrestricted and is normally fine for bandwidth. Version is 14.0 which is the latest afaik.

It's a tricky one. Try limiting your bitcoind connections with:

Code:
maxconnections=14

..in your conf file, even if it doesn't help, it will ensure that your bandwidth stays free. It might also be that your p2pool sharechain is corrupted somehow - have you tried deleting it & redownloading?
Richy_T
Legendary
*
Offline Offline

Activity: 1246


1RichyTrEwPYjZSeAYxeiFBNnKC9UjC5k


View Profile
October 21, 2015, 05:16:51 PM
 #13609

Here's the thing that should be concerning to others: Look at the pool rate. That was hanging out at slightly below 1.0PH for a while and then climbs jumpily back up to over 2.0. Now, because that happened *after* I restarted, more than likely that is just something my p2pool instance is seeing but possibly that represents hashing power that wasn't being applied to the longest chain. Unfortunately, the fact we got a block at the same time may have affected things. But again, I'm not even sure if this fork idea is even credible so I'm getting into very infirm territory now. My instance was getting that 1.0PH from somewhere (I know I wasn't generating it Smiley )

Anyway, I will keep monitoring the stats and I should be able to see if others also lose shares if it happens to me again. Also, it looks like I can use the outbound traffic as a trigger to let me know I need to pay attention. Of course, I will likely lose shares then as well but I'll give it a go for another block or 3.

If anyone is interested, I'll be using the address in my signature for the mining.

Edit: Another interesting point is that before two of the "Resets" my share was climbing to way more (0.035 and 0.025) than what it typically has been (0.02) which would potentially indicate a fork type scenario.

1RichyTrEwPYjZSeAYxeiFBNnKC9UjC5k
p3yot33at3r
Sr. Member
****
Offline Offline

Activity: 266



View Profile
October 21, 2015, 05:20:05 PM
 #13610

The pool rate is always jumping about - it's normal. failovers, restarts, miners coming & going etc.
Richy_T
Legendary
*
Offline Offline

Activity: 1246


1RichyTrEwPYjZSeAYxeiFBNnKC9UjC5k


View Profile
October 21, 2015, 05:39:11 PM
 #13611

The pool rate is always jumping about - it's normal. failovers, restarts, miners coming & going etc.

Sure. But look at my graph. smooth and steady at 0.9something for many hours then jumpily climbing... That's not what you would expect to see.

Edit: you would expect to see some climb after we found two blocks so quickly but it still doesn't look correct.

Edit2: Check this monthly chart, especially the circled areas. Looking at this one makes me think it doesn't support the fork hypothesis as much as I had thought though.


1RichyTrEwPYjZSeAYxeiFBNnKC9UjC5k
p3yot33at3r
Sr. Member
****
Offline Offline

Activity: 266



View Profile
October 21, 2015, 05:56:12 PM
 #13612

Yeah, that looks nothing like my monthly chart at all.  Huh  Did you redownload the p2pool sharechain yet?



Edit: Here's mine (click for larger)

Edit1: It might even be a dodgy SSD?
jonnybravo0311
Legendary
*
Offline Offline

Activity: 1008


Mine at Jonny's Pool


View Profile WWW
October 21, 2015, 05:57:25 PM
 #13613

The pool rate is always jumping about - it's normal. failovers, restarts, miners coming & going etc.

Sure. But look at my graph. smooth and steady at 0.9something for many hours then jumpily climbing... That's not what you would expect to see.

Edit: you would expect to see some climb after we found two blocks so quickly but it still doesn't look correct.

Edit2: Check this monthly chart, especially the circled areas. Looking at this one makes me think it doesn't support the fork hypothesis as much as I had thought though.


Huh... here's that same graph from windpath's node:


The blank spot is where his node was down.  I see some differences...

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



View Profile
October 21, 2015, 05:57:42 PM
 #13614

To anyone who has experiences in p2pool, for 2.3PH/s running 24x7 how many bitcoins would you estimate I would get/day?

https://bitcoinwisdom.com/bitcoin/difficulty (top-right) : 19 BTC/day.

P2Pool only pay if you have participate at the sidechain (sharechain of the P2Pool) an amount of time AND if a block is find.

No time, No chocolate.  Grin

French ... but not so much   ---===---   P2P ... it's people at the end   ---===---   P2Pool (10,9 GH/s).
Comment miner des bitcoins ? Un tutoriel est là : https://bitcointalk.org/index.php?topic=1114415.0
Bitcoin change everything ... an explain of this fact : https://www.youtube.com/watch?v=joITmEr4SjY
Meuh6879
Legendary
*
Offline Offline

Activity: 1092



View Profile
October 21, 2015, 05:59:50 PM
 #13615



this flat section is a freeze of bitcoind process (freeze of bitcoin deamon server RPC-JSON).
you have this, too ... when sharechain of P2Pool (local files) have a problem ... (remember this : 17500 shares valid v14 but 20650 shares available ...).

XT node with maxmempooltx purge system draw this :

No offline section.

French ... but not so much   ---===---   P2P ... it's people at the end   ---===---   P2Pool (10,9 GH/s).
Comment miner des bitcoins ? Un tutoriel est là : https://bitcointalk.org/index.php?topic=1114415.0
Bitcoin change everything ... an explain of this fact : https://www.youtube.com/watch?v=joITmEr4SjY
jonnybravo0311
Legendary
*
Offline Offline

Activity: 1008


Mine at Jonny's Pool


View Profile WWW
October 21, 2015, 06:12:03 PM
 #13616

That would explain things... if the bitcoind process was frozen and you were still mining to that node that actually explains everything.  Because bitcoind wasn't fetching new blocks, p2pool was always mining to an old block.  You were submitting shares just fine on your node.  The rest of the network was rejecting your shares (since they were from old blocks).  Then when things came back to life on your node, things caught back up, the shares you submitted were immediately dropped and your expected payment went to what the network thought it should be.

In effect, even though your miners were mining, they weren't doing anything useful because they were solving shares for blocks that were already on the chain.

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



View Profile
October 21, 2015, 06:20:39 PM
 #13617

Yes - that sounds like the problem to me too - well spotted Meuh6879  Wink
Richy_T
Legendary
*
Offline Offline

Activity: 1246


1RichyTrEwPYjZSeAYxeiFBNnKC9UjC5k


View Profile
October 21, 2015, 07:46:48 PM
 #13618

Yeah, that looks nothing like my monthly chart at all.  Huh  Did you redownload the p2pool sharechain yet?



Edit: Here's mine (click for larger)

Edit1: It might even be a dodgy SSD?

Yep. Restarted this morning at 9:10am. That system is using spinning-disk media.

1RichyTrEwPYjZSeAYxeiFBNnKC9UjC5k
Richy_T
Legendary
*
Offline Offline

Activity: 1246


1RichyTrEwPYjZSeAYxeiFBNnKC9UjC5k


View Profile
October 21, 2015, 07:51:23 PM
 #13619



this flat section is a freeze of bitcoind process (freeze of bitcoin deamon server RPC-JSON).
you have this, too ... when sharechain of P2Pool (local files) have a problem ... (remember this : 17500 shares valid v14 but 20650 shares available ...).

XT node with maxmempooltx purge system draw this :

No offline section.

That would explain things... if the bitcoind process was frozen and you were still mining to that node that actually explains everything.  Because bitcoind wasn't fetching new blocks, p2pool was always mining to an old block.  You were submitting shares just fine on your node.  The rest of the network was rejecting your shares (since they were from old blocks).  Then when things came back to life on your node, things caught back up, the shares you submitted were immediately dropped and your expected payment went to what the network thought it should be.

In effect, even though your miners were mining, they weren't doing anything useful because they were solving shares for blocks that were already on the chain.

Yes - that sounds like the problem to me too - well spotted Meuh6879  Wink

Looks like that's my answer then. Thanks guys.

I guess the increased bandwidth was probably because I kept spewing shitty info to other nodes and they kept re-requesting it (or however that bit works).

I guess the question is how best to prevent this going forward. I don't have any objection to XT (I'm already running the BIP101 patch) so that may be the way to go.

1RichyTrEwPYjZSeAYxeiFBNnKC9UjC5k
p3yot33at3r
Sr. Member
****
Offline Offline

Activity: 266



View Profile
October 21, 2015, 08:04:57 PM
 #13620

That system is using spinning-disk media.

A HDD? Do people still use them?  Cheesy

I'd ditch that if I were you - they're terrible for Bitcoin wallet, p2pool & mining in general. Only good for servers now.

Glad we got to the bottom of this, it was a head banger for me, so I'm sure it was doing your nut in!  Cheesy Wink
Pages: « 1 ... 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 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 ... 744 »
  Print  
 
Jump to:  

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!