That would explain a lot, the thought did occur to me earlier: Is that plonker doing another "stress test" again?  If this is the case, it happening at around the same time as a forking would have to be intentional I reckon........is it from the same origin as the last time? |
|
|
|
Hmmm.......has anyone made contact with forrestv? It would be good to get his take of what's happening........
Hey, I've been watching. You are trying the recent P2Pool commit that blocks pre-v14 peers, right? If that's confirmed to help, I'll make a P2Pool release with it. Some P2P network thrashing is normal after a fork since you have the unupgraded nodes madly trying to find peers and download the (invalid to them) sharechain. Normally, there are less unupgraded nodes, but this fork was rushed, so I think that that contributed to it. However, some are reporting high bitcoind CPU usage - P2Pool P2P network activity shouldn't be affecting bitcoind, so I'm not sure about that. Is that happening for Bitcoin users without P2Pool? It might be some similar post-BIP66 effect. Hi forrestv, Thanks for chiming in buddy. Yes, using the latest p2pool repo. I'm seeing high cpu usage on both p2pool & bitcoind, but the cpu usage on p2pool is much more prolonged & constantly higher than bitcoind, which seems to have sudden peaks & bursts of high usage - resulting in very high latency issues. It's a tricky one eh?  I even tried re-downloading the p2pool sharechain...... |
|
|
|
|
Hmmm.......has anyone made contact with forrestv? It would be good to get his take of what's happening........
|
|
|
|
@ kano - is your relaynetworkclient working OK? Just want to make sure it's not just me  Do tell .... experienced any issue that might be of interest to the wider community? Had to turn mine off too..... |
|
|
|
Yeah, frustrating isn't it? I'm seeing some huge cpu usage by both bitcoind & p2pool - over 80% sometimes, my latency has also gone through the roof, even after restarting. Is that plonker doing another "stress test" again? Edit: OK, this is getting silly. 99% cpu, & often. :  Never seen it jumping up to these levels before - I'm beginning to think that the problem is not with p2pool or bitcoind, but with the network itself. I'm seeing some crazy amounts of traffic with super high latency, it seems to be working my node to death despite limiting connections, disabling the relaynetworkclient, prioritizing python & bitcoind, QOS & every other trick I can think of....... I can see by the total p2pool hash rate & the opinions of others in other threads that something is wrong somewhere, but I'm buggered if I know what it is. I'm open to any & all suggestions people.......just hoping it's not the "usual suspects" again, messing with their pools code & screwing up the network somehow........  |
|
|
|
|
Please, don't double post & ask in the relevant thread, which is the nicehash one.
|
|
|
|
@ kano - is your relaynetworkclient working OK? Just want to make sure it's not just me |
|
|
|
I've not had any issues with the NMC client (using latest namecore), only the bitcoind problem. The pool hash rate has dropped massively - there's obviously a stability problem somewhere - but I haven't seen another disconnect since disabling the relayclient.......yet  This forum constantly dropping isn't helping much either |
|
|
|
Has anyone else started getting bitcoind disconnects since upgrading to the latest version?
Yes, and I went from 10.1 to 10.2 to ensure it was not a Bitcoind version issue. I will not be able to update my node until later today though to see if this solves this issue as well. I hope it does. Right. I also just noticed the eu relaynetwork was down - so I've disabled it (the latest version didn't work on 14.04 anyway) just in case that had something to do with it. |
|
|
|
|
Has anyone else started getting bitcoind disconnects since upgrading to the latest version?
|
|
|
|
|
Any news on this GB? I notice their site is down today......
|
|
|
|
Hi Matt, I didn't use the fix JB kindly suggested, as I thought I'd wait for confirmation from yourself first. If you'd like to tell me what you want me to do, in layman's terms due to my lack of Linux skills, I'll help if I can. I'm also using 14.04 64bit Edit: EU node down? |
|
|
|
Please try the latest commit. It doesn't allow connections to v13 nodes.
Looks like that fixes it. Right out of boot it banned the version 1300 nodes it connected to first, then connected to the version 1400 nodes, and is now no longer getting stuck. Thanks! Yup - that's seems to have done it for me too. Looking at my graphs & logs, it looks like my node has been trying to download & process invalid shares all night:  ..causing this:  Recommend everyone update again asap so as to avoid this happening to them.Thanks forrestv for the quick response & fix!  |
|
|
|
Ah! So it wasn't me going mad then...... Thanks for the info JB - is it running OK still? No errors? |
|
|
|
I just checked my node, as it was showing down. It looks like it's hyper trying to retrieve shares from multiple places: 2015-07-05 19:06:16.252636 Requesting parent share 66033bd7 from 74.82.233.205:9333
2015-07-05 19:06:17.357663 Requesting parent share 66033bd7 from 149.210.228.165:9333
2015-07-05 19:06:18.809206 Requesting parent share 66033bd7 from 80.60.85.169:9333
2015-07-05 19:06:19.088368 Requesting parent share 37dddcee from 74.82.233.205:9333
Notice it requested the same parent share from four nodes within 4 seconds. That's not very efficient, and I assume that's why it's having a hard time keeping up with the shares. It's doing this regularly. M I've been seeing this the last few days too, but put it down to the forking & old nodes still not being updated - but maybe it's something else.....? |
|
|
|
I am running the current 13.4-83-gb07b1e3 P2P version and 0.10.1 core.
Current is v14 & 0.10.2 |
|
|
|
|
Hi JB,
Did you also try running the pre-compiled binary by any chance?
|
|
|
|
I'm having problems too. 2 out of 3 of my SP20's no longer boot - dead controllers. Tried every kind of SD card, recovery, boot & in every possible combination - dead. The worst thing is, SPTech are charging way too much for the replacement controller boards to make it economically viable to buy them - especially when there's a very good chance that the same thing could happen again at any time. It's a shame, cos when they work, they work great - but when they don't, you're screwed. I'm a bit miffed about it all tbh...... UPDATE: Lost my internet for 5 minutes this morning & my 3rd & last remaining SP20 never came back online. I now have the pleasure of reflashing SD cards & rebooting them all over the rest of the weekend in the hope that they "might" recognize an SD card & run again...... I hate baby sitting these things  3 out of 3 down. |
|
|
|
And we believe the way we are doing bitcoin mining is safe yet profitable to our miners.
Unfortunately, recent events have proven that this is not the case. |
|
|
|
Mining on block header is nothing wrong. It is not greed. It is strategy.
Then it is an incompetent, greedy & damaging strategy. For you, miners & the network in general. As has been pointed out repeatedly. |
|
|
|
|
Show Posts
