Yes
Cпacибo!!
Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 133. (Read 2591920 times)
October 24, 2015, 05:54:59 AM
October 24, 2015, 05:48:19 AM
Yes
October 24, 2015, 05:38:24 AM
The latest firmware from Bitman (adjustable fan) cgminer 4.9.0 and queue 0 https://yadi.sk/d/9DZhkgcjjNKtZ
Previous firmware on the Bitman (without adjusting the fan) cgminer 4.9.0 and queue 0 https://yadi.sk/d/biL8s7URh59Zp
Previous firmware on the Bitman (without adjusting the fan) cgminer 4.9.0 and queue 0 https://yadi.sk/d/biL8s7URh59Zp
Right, so as I understand it, the correct one to use for p2pool on your blog is the first one (No. 1). This uses a queue 0, lowmem & submit stale - am I correct?
Thanks again igorwhite - I will test & send you a tip to the BTC address on your blog
October 24, 2015, 05:33:48 AM
The latest firmware from Bitman (adjustable fan) cgminer 4.9.0 and queue 0 https://yadi.sk/d/9DZhkgcjjNKtZ
Previous firmware on the Bitman (without adjusting the fan) cgminer 4.9.0 and queue 0 https://yadi.sk/d/biL8s7URh59Zp
Previous firmware on the Bitman (without adjusting the fan) cgminer 4.9.0 and queue 0 https://yadi.sk/d/biL8s7URh59Zp
October 24, 2015, 05:24:29 AM
For p2pool only better CGM 4.9.0 queue 0
submit stale it is to reduce the orphan (do not know exactly how to say in English) but this is not good because at p2pool also pay for orphan
submit stale it is to reduce the orphan (do not know exactly how to say in English) but this is not good because at p2pool also pay for orphan
OK - so that is download number 1)?
First on the list?
Or number 3)?
Sorry, it's difficult to tell
October 24, 2015, 05:21:33 AM
For p2pool only better CGM 4.9.0 queue 0
submit stale it is to reduce the orphan (do not know exactly how to say in English) but this is not good because at p2pool also pay for orphan
submit stale it is to reduce the orphan (do not know exactly how to say in English) but this is not good because at p2pool also pay for orphan
October 24, 2015, 04:37:57 AM
Hello!
Here's my post with all the firmware for antminer s5 ---- https://forum.bits.media/index.php?/blog/194/entry-337-proshivka-antminer-s5-cgminer-490-ot-kolivas/
Post in Russian language.
Install like normal firmware from BITMAN.
After rebooting cgminer no falls
Here's my post with all the firmware for antminer s5 ---- https://forum.bits.media/index.php?/blog/194/entry-337-proshivka-antminer-s5-cgminer-490-ot-kolivas/
Post in Russian language.
Install like normal firmware from BITMAN.
After rebooting cgminer no falls
Ah yes - I wondered where I got this firmware from, I noticed the "White" sig in the firmware release - many thanks for this work igorwhite.
I have used a webtranslator for your blog, but much of the details are lost in translation - can you tell me what firmware has queue 0 & submit stale?
Thanks
Edit: Also, is there a queue 1 & submit stale?
October 24, 2015, 04:22:17 AM
Hello!
Here's my post with all the firmware for antminer s5 ---- https://forum.bits.media/index.php?/blog/194/entry-337-proshivka-antminer-s5-cgminer-490-ot-kolivas/
Post in Russian language.
Install like normal firmware from BITMAN.
After rebooting cgminer no falls
Here's my post with all the firmware for antminer s5 ---- https://forum.bits.media/index.php?/blog/194/entry-337-proshivka-antminer-s5-cgminer-490-ot-kolivas/
Post in Russian language.
Install like normal firmware from BITMAN.
After rebooting cgminer no falls
October 23, 2015, 06:57:48 PM
you mean this one http://lnlb.sourceforge.net/ for example?
Maybe. I don't know enough about it. I would imagine that p2pool talking to bitcoind is simple enough that simple load balancing would be enough but I don't know enough to say for sure.
I have found crossroads as a load balancer possible able to do this work. I am going soon to test running two bitcoind with two independent internet connections and let my p2pool node to be connected to them over crossroads.
Let us know how it goes!
October 23, 2015, 02:08:17 PM
just posted on IRC asking whereisblock & a thx for the boost in p2pool.
Here it is :
BITCOIN BLOCK FOUND by 1NJJgrGhU7rTFCgD9ZbfktKoyj4vFHe4yB! @ 124482.10 GH/s
https://blockchain.info/block/000000000000000008a08fd6ec6625113a7013673847e5950ce57467aa09761b
i've also redirected some of my miners to the pool for a boost.
more to come soon
rav3n_pl any new updates on your p2p fork ? appreciate a link.
i;ve just updated to latest qt 11.1 so far so good.
Here it is :
BITCOIN BLOCK FOUND by 1NJJgrGhU7rTFCgD9ZbfktKoyj4vFHe4yB! @ 124482.10 GH/s
https://blockchain.info/block/000000000000000008a08fd6ec6625113a7013673847e5950ce57467aa09761b
i've also redirected some of my miners to the pool for a boost.
more to come soon
rav3n_pl any new updates on your p2p fork ? appreciate a link.
i;ve just updated to latest qt 11.1 so far so good.
October 23, 2015, 01:17:12 PM
Port 9333 need to be open if you want (and you want) incoming connections from other nodes.
If you want allow others to mine on your node you also need forward port 9332.
If you want allow others to mine on your node you also need forward port 9332.
October 23, 2015, 09:48:15 AM
Though also in the log with the same error are the private IP of my p2pool node and the private IP of my router.
unlock (manually with rule on a fixed IP) the NAT : p2pool 9333 TCP
Not sure what you mean by unlock but I do already have 9333 port forwarded.
Been running gangbusters since starting with a fresh install of p2pool FWIW.
October 23, 2015, 08:28:31 AM
Though also in the log with the same error are the private IP of my p2pool node and the private IP of my router.
unlock (manually with rule on a fixed IP) the NAT : p2pool 9333 TCP
October 23, 2015, 08:26:30 AM
I have 14 Bitmain s-5 and i have approx 5 that lockup almost daily, and require a power cycle to get them back on line. And a couple of then run at half there hash rate.
change supply.
October 23, 2015, 07:21:23 AM
Two of mine locked up with the nicehash firmware too - so I dumped it. Are you running them overclocked?
Try this firmware:
https://www.dropbox.com/s/gk6gva5e12g4qsr/SD-S5-20150107_cgm_4_9_0-queue_0_no-submit.tar.gz?dl=0
It's been solid for me & has the correct settings, ie submit stale, queue & lowmem. If you must OC, Start off at default clock speed & work up gradually keeping an eye on HW errors. If it locks up it usually means you're over cooking it. Bear in mind that p2pool is quite miner intensive & hash rates will always be slightly lower. Bitmain firmware can't cope, cos its poo......
Edit: It should also stick after reboots.
Try this firmware:
https://www.dropbox.com/s/gk6gva5e12g4qsr/SD-S5-20150107_cgm_4_9_0-queue_0_no-submit.tar.gz?dl=0
It's been solid for me & has the correct settings, ie submit stale, queue & lowmem. If you must OC, Start off at default clock speed & work up gradually keeping an eye on HW errors. If it locks up it usually means you're over cooking it. Bear in mind that p2pool is quite miner intensive & hash rates will always be slightly lower. Bitmain firmware can't cope, cos its poo......
Edit: It should also stick after reboots.
October 22, 2015, 10:43:04 PM
I have 14 Bitmain s-5 and i have approx 5 that lockup almost daily, and require a power cycle to get them back on line. And a couple of then run at half there hash rate.
Does any one have any ideas, it makes not different what version of firmware to include the nicehase version there still doing the same thing. I have 8 to 10 that run rock solid like my s-3 do.
I am out of ideas and am wondering if anyone else has this issue.
Thanks
John
Does any one have any ideas, it makes not different what version of firmware to include the nicehase version there still doing the same thing. I have 8 to 10 that run rock solid like my s-3 do.
I am out of ideas and am wondering if anyone else has this issue.
Thanks
John
October 22, 2015, 09:46:35 PM
Richy_T: noes!, you quoted my typo.
@typo
Polyatomic's typo is awesome.
@typo
October 22, 2015, 08:44:43 PM
See this post:
https://bitcointalksearch.org/topic/m.829445
I get them now & again too, I don't think it's a problem.
I think it's a corruption issue that's causing your problems. Have you checked your memory & HDD's for errors?
Not recently but I do other stuff on that system that runs with no issue. I'll schedule a disk scan and some time with memtest but I personally don't think that's going to be it.
I am trying with a clean install of p2pool to see where that gets me though.
October 22, 2015, 08:40:43 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?
See this post:
https://bitcointalksearch.org/topic/m.829445
I get them now & again too, I don't think it's a problem.
I think it's a corruption issue that's causing your problems. Have you checked your memory & HDD's for errors?
October 22, 2015, 08:34:05 PM
err is that an internal ip, there reserved.
I'm thinking it should be ok to not hide them.
I'm thinking it should be ok to not hide them.
Sorry, no, I should have specified. That is my external public IP
Though also in the log with the same error are the private IP of my p2pool node and the private IP of my router. Looks like p2pool got itself into a state somehow. These are also in the addrs file so that would be why it persists I guess.
Jump to: