I tried the extranonce one time when I came back from westhash after the "great spike" on my SP20's and they "seemed" to be getting less shares. As we all know this could have just been bad timing. I run them without the extranonce, doing so puts the unit back to cgminer 4.7.0. I have the same F/W as well. I run these two at around 1100 GHs with a start voltage of .62 and a max of .625. My fans are set to auto and run at "6", this might be different for you depending on you ambient room temp. The S5 I have running at the default 350 setting but with the Kano cgminer 4.9 version, the original version is crap. I average between .07 - .05 for a payout with ~3.33 TH for reference. I have got up to .1 before when people bailed on the pool in February. I point these to one address. If you are getting higher payouts please let me know.

I update my P2P to version 14.0-9 and bitcoin to v0.11 and my GBT is now <1s as it was before the change from v13 to v14. I have not blocked any peers as the application seems to be doing it's job since now after the initial P2P v14 was not able to block v13 peers (thanks forrestv). My GBT had been at >3s before this last update. Can't say this is a coincident or not just providing my status.

Simple, you run a Bitcoind just for your P2P Node, you never have any coins there so it is not at risk (8333). My comment about no peers covers 9333. 9332 if you want others to use your node for mining. My answer was only directed at the 0 peers as indicated. Now in the present condition, yes 0 peers could have been indicative of an increase in traffic saturating your connection which could cause an interrupt and thus you just lost all of your peers.

As I said, JB was probably on the right track for his answer. The port information is common knowledge in the P2P community but I put it out there in case he was not aware.

Did you open up ports 8333 (Bitcoin peer to peer), 9333 (p2p peer to peer) and optional 9332 (for connections and web interface). I only ask because you do not have an incoming connections. This would not answer your original question which JB may have hit on the right direction already.

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.

It appears that if you are updated to version 14 you will not show up here http://p2pool.jir.dk/bitcoin/ anymore. Not sure if you guys have taken a look here before but if this is the case we have more that will be left behind.

Thanks guys I was looking at the protocol of 1400 and thought the pull had updated my version, dumb on my part. I now have 14.0-5-gb07b1e3 running. I did keep my data and web-static files after performing a clone. All looks good with the version now just a wait and let it run to see if the latency and traffic rate get back to normal.

So do I really need to move up to 10.2 or can I just continue at this point with 10.1?

EDIT: Updated to 10.2 as well.

That was the last pull from GitHub. Heck I thought I was up to speed great.

So I can't just perform a pull but need to delete this version and start with the new one I see.

Does anybody know what is going on with P2P today with the high latency? It is causing my bitcoind to drop connectivity and my SP's to drop as well (the S5 seems to drop as well looking at my node). It has been up/down for the last six hours. I looked at other pools and some seem to have the same problem as well. I am running the current 13.4-83-gb07b1e3 P2P version and 0.10.1 core.

I too have the same results. I fixed my last issue of a missing GLIBC...21 but now I am in the same boat as P3....
I have been running the RelayNode since it came out last year and never had any issues until the last two versions. I see that many are not having issues and it is running fine or I am sure this would have been a hot item as the Relay Network is a game changer for the community. I am sure this is an oversight on my part so any assistance or insight would be appreciated.

I bought one like this http://www.amazon.com/BESTOPE®-Charger-Doctor-Current-Voltage/dp/B00GC9I61I/ref=pd_sim_60_6?ie=UTF8&refRID=06NT3Z3HJDSP20M7JWE7 a few years back for USB Ants and Gridseeds that still works. Looking Amazon and it seems they have a bigger selection now. http://www.amazon.com/s/ref=nb_sb_noss_2?url=search-alias%3Daps&field-keywords=USB+power+meter

Very good work by the way, thanks for keeping us informed.

I run mine right where you are at but I run the fan in Auto. This has the fan speed at 6 after the initial run up of about 5 min. My ambient temp is ~75-80F in the space these are located and they run below 60C recorded from the exhaust temp. I can't remember the chip temps right now but can provide later if you would like to know.

I am sure I was not the only one to update Bitcoin Core yesterday as part of the procrastinators group. Ironic how the luck went up, guess time will tell if there is any correlation.

Here you go, you need to add 2 as the ExtraFlag and #xnsub after :3334 as shown here and you should be good to go.
https://bitcointalk.org/index.php?topic=521520.msg10478127#msg10478127

I moved mine this past weekend for the same reasons. Stuck with it as long as I could. I will continue to check in to see about any progress for the future.

The deliver what they sell. I bought some Gridseeds from them before multiple times and never had an issue.

Look here this should help https://bitcointalk.org/index.php?topic=872014.msg10314356#msg10314356

With everybody leaving I have just about made up for the slow week as my share value has more than doubled. Good thing I was on the road last week and just decided not to bother with the miners until I came home.

So normal CGminer has submit stale on by default correct?
I know CK provided a fix for the S3, what do we do about the S5? (Assuming we need corrective action)
Is it safe to say that Spondoolies did this the correct way, that is submit stale is on by default?

Sure has been a little tough after the difficulty change. Oh well variance and luck.