err is that an internal ip, there reserved.
I'm thinking it should be ok to not hide them.
Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 134. (Read 2591928 times)
October 22, 2015, 08:16:54 PM
October 22, 2015, 08:03:50 PM
More of a clue?
2015-10-22 19:08:36.403770 Peer xx.xx.xx.xx:9333 misbehaving, will drop and ban. Reason: was connected to self
2015-10-22 19:08:36.403893 Bad peer banned: (u'xx.xx.xx.xx', 9333)
Where this is my IP in the logs.
I also see this for other IP addresses so maybe I was somehow connected to myself and other nodes saw it and have banned me? How can this be avoided in future?
2015-10-22 19:08:36.403770 Peer xx.xx.xx.xx:9333 misbehaving, will drop and ban. Reason: was connected to self
2015-10-22 19:08:36.403893 Bad peer banned: (u'xx.xx.xx.xx', 9333)
Where this is my IP in the logs.
I also see this for other IP addresses so maybe I was somehow connected to myself and other nodes saw it and have banned me? How can this be avoided in future?
October 22, 2015, 07:43:50 PM
OK, The issue has now been affecting me since 9am this morning I have tried restarting bitcoind and p2pool both separately and together and the problem persists. I have actually tried copying the p2pool directory and cleaning out the data/bitcoin directory. When I did this, I noticed p2pool was not able to stay connected to peers to download shares. I copied the "addresses" file into the directory again and a few shares are downloading but I am still getting a lot of disconnects. The error is this:
I am beginning to think that I am getting blocked by p2pool on other hosts. Is there any way to check this?
Quote
2015-10-22 19:43:23.180634 Lost peer xx.xx.xx.xx:9333 - Connection was aborted locally, using.
I am beginning to think that I am getting blocked by p2pool on other hosts. Is there any way to check this?
October 22, 2015, 06:43:12 PM
[Deleted] Want to do some more research before jumping on this one.
October 22, 2015, 12:43:01 AM
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.
would this happen if data directory is deleted/corrupted?
October 21, 2015, 05:25:10 PM
I couldn't do this with HDD's. No way. So yeah, SSD's are the way to go - but use quality ones. I'm a huge fan of the HyperX - I run one in my PC too, and my Netbook.
I had good lock with the Sandisk in 125 so I stuck with the make when I went to 250 but stepped up to Ultra II. I like it so far and I've bought a couple more to throw in laptops when I get time to do the imaging...
Looking at my server where I also run the bitcoind, it looks like the system partitions would fit on with room to spare so I may go with bitcoind and p2pool on there. That's if I can remember how to get through the nightmare that is setting up a drive to work with UEFI on my motherboard.
October 21, 2015, 04:57:10 PM
That system is using spinning-disk media.
A HDD? Do people still use them?
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!
Haha, yeah. It's pretty OK for Bitcoind as mostly you're just storing 60GB of history and they are great for long-term storage of bulky data that is not speed sensitive. I do have a 125G SSD that I just upgraded from from my workstation so I may throw that in as the boot disk but I doubt I'd put the blockchain on it.
Now, if someone want to tell me it would really benefit to have p2pool use one, I'm willing to listen.
My rig, running 64bit Xubuntu, runs a 60GB Corsair system SSD. I use a 256GB HyperX SSD for the 13 wallet data directories that I'm merge mining with p2pool - plus 7 other coin wallets that I mine with another p2pool instance on occasion, ie: when I'm playing
The speed is faster than my crappy internet, which I believe to be the cause of most of my orphans/doa's - of which there are few, my node very rarely goes below 105% efficiency & sometimes, when my internet is stable, it goes up to 125%.I couldn't do this with HDD's. No way. So yeah, SSD's are the way to go - but use quality ones. I'm a huge fan of the HyperX - I run one in my PC too, and my Netbook.
October 21, 2015, 04:45:15 PM
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.
the following post indicate somes values for the maxmempooltx that you can try : https://github.com/bitcoinxt/bitcoinxt/issues/82
I use 800-1200 (mempool = 3Mb to 6Mb for 0 minfee and 0,00001 relayfee).
Daily modified to ensure the fluidity and the max block rotation (1Mb).
that's why i have write this post (github) to push the dev. to install a automated way (of peace) to manage this problem.
October 21, 2015, 04:32:39 PM
That system is using spinning-disk media.
A HDD? Do people still use them?
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!
Haha, yeah. It's pretty OK for Bitcoind as mostly you're just storing 60GB of history and they are great for long-term storage of bulky data that is not speed sensitive. I do have a 125G SSD that I just upgraded from from my workstation so I may throw that in as the boot disk but I doubt I'd put the blockchain on it.
Now, if someone want to tell me it would really benefit to have p2pool use one, I'm willing to listen.
October 21, 2015, 03:59:38 PM
That system is using spinning-disk media.
A HDD? Do people still use them?
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!
not really .... mine runs on hdd (wd reds) on RAID 10 is as fast or faster than a regular ssd & much more cost efficient, lots of space & if any of the hdd fails it still works.
RAID 10 & WD Reds are for server/nas, and although it's a good quality configuration & will run fine, if you compare a read/write test result between those discs & the same setup but with quality SSD's instead of HDD's, the SSD's will win hands down, every time. Always. I use Reds on my server, performance is great, but after testing the speeds, I went with a SSD setup on a dedicated mining rig. Also, SSD's use a fraction of the electricity, which is handy for a rig that's on 24/7.
October 21, 2015, 03:44:52 PM
That system is using spinning-disk media.
A HDD? Do people still use them?
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!
not really .... mine runs on hdd (wd reds) on RAID 10 is as fast or faster than a regular ssd & much more cost efficient, lots of space & if any of the hdd fails it still works.
October 21, 2015, 03:04:57 PM
That system is using spinning-disk media.
A HDD? Do people still use them?
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!
October 21, 2015, 02:51:23 PM
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.
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
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.
October 21, 2015, 02:46:48 PM
Yeah, that looks nothing like my monthly chart at all. 
Did you redownload the p2pool sharechain yet?
Edit: Here's mine (click for larger)
Edit1: It might even be a dodgy SSD?
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.
October 21, 2015, 01:20:39 PM
Yes - that sounds like the problem to me too - well spotted Meuh6879
October 21, 2015, 01:12:03 PM
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.
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.
October 21, 2015, 12:59:50 PM
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.
October 21, 2015, 12:57:42 PM
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.
October 21, 2015, 12:57:25 PM
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.
The blank spot is where his node was down. I see some differences...
October 21, 2015, 12:56:12 PM
Yeah, that looks nothing like my monthly chart at all. Did you redownload the p2pool sharechain yet?
Edit: Here's mine (click for larger)
Edit1: It might even be a dodgy SSD?
Did you redownload the p2pool sharechain yet?Edit: Here's mine (click for larger)
Edit1: It might even be a dodgy SSD?
Jump to: