|
> Error submitting primary block: (will retry)
2014-12-01 08:58:52.269638 > Traceback (most recent call last):
2014-12-01 08:58:52.269676 > File "/usr/lib64/python2.7/site-packages/twisted/internet/defer.py", line 490, in _startRunCallbacks
2014-12-01 08:58:52.269704 > self._runCallbacks()
2014-12-01 08:58:52.269738 > File "/usr/lib64/python2.7/site-packages/twisted/internet/defer.py", line 577, in _runCallbacks
2014-12-01 08:58:52.269780 > current.result = callback(current.result, *args, **kw)
2014-12-01 08:58:52.269832 > File "/usr/lib64/python2.7/site-packages/twisted/internet/defer.py", line 1155, in gotResult
2014-12-01 08:58:52.269856 > _inlineCallbacks(r, g, deferred)
2014-12-01 08:58:52.269880 > File "/usr/lib64/python2.7/site-packages/twisted/internet/defer.py", line 1099, in _inlineCallbacks
2014-12-01 08:58:52.269913 > result = g.send(result)
2014-12-01 08:58:52.269954 > --- <exception caught here> ---
2014-12-01 08:58:52.269987 > File "/mnt/60gb/p2pool/p2pool/util/deferral.py", line 41, in f
2014-12-01 08:58:52.270028 > result = yield func(*args, **kwargs)
2014-12-01 08:58:52.270059 > File "/mnt/60gb/p2pool/p2pool/bitcoin/helper.py", line 67, in submit_block_p2p
2014-12-01 08:58:52.270112 > factory.conn.value.send_block(block=block)
2014-12-01 08:58:52.270136 > File "/mnt/60gb/p2pool/p2pool/util/p2protocol.py", line 102, in <lambda>
2014-12-01 08:58:52.270169 > return lambda **payload2: self.sendPacket(command, payload2)
2014-12-01 08:58:52.270201 > File "/mnt/60gb/p2pool/p2pool/util/p2protocol.py", line 93, in sendPacket
2014-12-01 08:58:52.270224 > raise TooLong('payload too long')
2014-12-01 08:58:52.270247 > p2pool.util.p2protocol.TooLong: payload too long
Whatsup?
It became orphan because payload too long? Too many users on pool or too many transactions in a block or what?
|
|
|
|
The number 1 issue is fixed with latest firmware, which runs cgminer 4.6.1. When the work restart request comes in, I usually see the flush work within 1 second, then the new block task usually arrives in another second. Often there are new accepted shares submitted within 2 seconds of the work restart request. The new cgminer 4.6.1 has brought new life to the S2. I used to point the S2's to a different pool, while all my other miners used P2Pool. It's so nice to see them doing the full 1000 GH/s with P2Pool. I have 2x S2's and 2x C1's, and all 4 of them run neck-and-neck.
Bear in mind if you are pointing an S1/2/3/4 to p2pool with bitmain's default firmware binaries, they throw out stale shares which is potentially disastrous on p2pool because that can throw out a valid block solve. Kano and I have pointed this out to them numerous times but that behaviour is still in their fork. Is it enough to get rid of this prob if cgminer is replaced with http://ck.kolivas.org/apps/cgminer/antminer/s3/4.6.1-141020/ ? Or some option in /etc/config/cgminer params line --submit-stales or similiar?? Any info where to get working or updated cgminers to other ants, heres few s1:s still making noise Yes it's only fixed with my binaries which I've only made for s3 and 4 and kano's binary for s2. There is no option that will fix it in the bitmain fork. This is what they answered from bitmain of new s4 ive ordered to umisoo hosting when i asked about this prob. "Hi, no worries, we've updated the firmware.Our antpool is open public and you may try with solo.antpool.com to try. it's more stable than p2pool. Engineers are still working on the popool issue to get it more stable:)" |
|
|
|
The number 1 issue is fixed with latest firmware, which runs cgminer 4.6.1. When the work restart request comes in, I usually see the flush work within 1 second, then the new block task usually arrives in another second. Often there are new accepted shares submitted within 2 seconds of the work restart request. The new cgminer 4.6.1 has brought new life to the S2. I used to point the S2's to a different pool, while all my other miners used P2Pool. It's so nice to see them doing the full 1000 GH/s with P2Pool. I have 2x S2's and 2x C1's, and all 4 of them run neck-and-neck.
Bear in mind if you are pointing an S1/2/3/4 to p2pool with bitmain's default firmware binaries, they throw out stale shares which is potentially disastrous on p2pool because that can throw out a valid block solve. Kano and I have pointed this out to them numerous times but that behaviour is still in their fork. Is it enough to get rid of this prob if cgminer is replaced with http://ck.kolivas.org/apps/cgminer/antminer/s3/4.6.1-141020/ ? Or some option in /etc/config/cgminer params line --submit-stales or similiar?? Any info where to get working or updated cgminers to other ants, heres few s1:s still making noise |
|
|
|
Kanos pool seems to be very effective! Is there a bonus for block finder? Like p2p has 0,5%
It could be very interesting to mine in a pool with 10% blockfinder bonus, or at least 5%... Or kind of a solo pool that pays 50% to founder and the rest to all to cover electricity...
You do know what solo mining is don't you? On this solo pool you get the entire block minus the small fee. 99.5% I think is enough of a "blockfinder bonus". Don't you? Having a bad day or what? Serious Sam? What do you mean? I don't understand why your asking for a block finder bonus on a solo pool? What do you understand then? I guess nothing. Sorry if I hurt your feelings, dont start to cry baby. Asked if theres a bonus in Kanos ckpool - and it did hurt you badly. Try to get some sleep. |
|
|
|
Kanos pool seems to be very effective! Is there a bonus for block finder? Like p2p has 0,5%
It could be very interesting to mine in a pool with 10% blockfinder bonus, or at least 5%... Or kind of a solo pool that pays 50% to founder and the rest to all to cover electricity...
You do know what solo mining is don't you? On this solo pool you get the entire block minus the small fee. 99.5% I think is enough of a "blockfinder bonus". Don't you? Having a bad day or what? Serious Sam? |
|
|
|
|
Kanos pool seems to be very effective! Is there a bonus for block finder? Like p2p has 0,5%
It could be very interesting to mine in a pool with 10% blockfinder bonus, or at least 5%... Or kind of a solo pool that pays 50% to founder and the rest to all to cover electricity...
|
|
|
|
|
How ou how should the voltage be written in new firmware field - chinese cant put an example to ease things.
so is it 0.63 or .63 or 0.63v perhaps .63v or even 0.63V .. .63V Please tell.
So ive got s3:s , I think i found it from s4 manual 0630 ? Doesnt seem to affect anyhow - is this field a Bitmain joke?
|
|
|
|
|
So im not sure how the voltage should be applied 0.55 or .55 or .55v - is there a way to check that is does something? .55v 218mhz and iget 0.01% hw. Those have burned alot electricity for nothing and keeped some noice too...
|
|
|
|
Pseudo share doesnt affect in founding block anyotherway than it restarts works everytime that changes, so selecting constant could help abit keeping miner busy. Large miners should use bigger sharedifficulty - that would help poolwide. Like btcaddress+501/100000000, then there should be less 5 s restart times, and big miners earn that way more too. Ckolivas proxy helps keeping miners busy also, I have got very good results with it in p2pool and solo pool, it squeezes juice out of miners, with s3s mindiff and startdiff have to be chosen so that you can see best share.. Last weeks bests with 2th= 2,347,645,293, one ~1,500000000, 537,352,921 .. newer got those kind of results without proxy. S3:s doesnt show best share with all share diff + 512, 1024, 4096 doesnt show, 500, 4000 ... it shows nohup ./ckpool -p -A -k> /dev/null 2>&1 & Wondering how ants would perform if those are turned to diskless nodes and booted with tftp, that way cgminer could be running on some more powerfull machine, i think s2 s3 s4 are suffering constan restarts - the mainoboard doesnt have enough power. And that way I doesnt have to wait new firmware and cgminer... http://wiki.gentoo.org/wiki/Diskless_nodes |
|
|
|
Please sir, can I have some more?.........  Let there be some seconds between please, that last was ~0.6s after discus fish found one.. |
|
|
|
2014-10-17 16:51:43.421556 Skipping from block 16312a716d4e7e963a3c7ae3a41f5153965ddf6438ca4ec6 to block 1a2d435b1e4a18aac8afadd6b9617283d36ac0b47de944a5! 2014-10-17 16:51:43.437800 New work for worker! Difficulty: 612.751420 Share difficulty: 13134569.950544 Total block value: 25.000000 BTC including 0 transactions 2014-10-17 16:51:43.446743 New work for worker! Difficulty: 4000.000000 Share difficulty: 30000678.069252 Total block value: 25.000000 BTC including 0 transactions 2014-10-17 16:51:43.454766 New work for worker! Difficulty: 2000.000000 Share difficulty: 30000678.069252 Total block value: 25.000000 BTC including 0 transactions 2014-10-17 16:51:43.643125 Peer sent entire transaction 58d1e1762040c1887bfa7697dda3cdaf6ab0189832077058ab3e3ab77f4515a1 that was already received 2014-10-17 16:51:43.749030 Peer sent entire transaction 08dabbc9998b366eaf56a3572bacb187c06215e3f955af20ba745f4ba92a4b66 that was already received 2014-10-17 16:51:43.859451 Peer sent entire transaction 58d1e1762040c1887bfa7697dda3cdaf6ab0189832077058ab3e3ab77f4515a1 that was already received 2014-10-17 16:51:44.006821 2014-10-17 16:51:44.006911 GOT BLOCK FROM PEER! Passing to bitcoind! f4545609 bitcoin: https://blockchain.info/block/0000000000000000050ef6f0b71e83a8ee299f646a2c53f21b3e1ba3f45456092014-10-17 16:51:44.006971 |
|
|
|
This is amazing to see the share numbers on ckpool, just like my old miners have found another gear or something  |
|
|
|
I wonder how would ant s2 and s4 perform if those are turned to diskless nodes and booted from network, much more power maybe? Im thinking booting those s1:s to gentoo, could that be possibleto get those mining that way?
You mean would their hashrate be higher? Absolutely not, at least not on this or any other ckpool. Ckpool is getting everything out from the miners, only time fans sometimes gets quiet for a few sec is just after a block is found, but on some other pools its different with less than 30sec blocktime, the ants openwrt board is just not enough to handle that. If there just would be an usb port to bypass openwrt.. |
|
|
|
|
I wonder how would ant s2 and s4 perform if those are turned to diskless nodes and booted from network, much more power maybe? Im thinking booting those s1:s to gentoo, could that be possibleto get those mining that way?
|
|
|
|
The workload keeps dropping down at regular intervals when you're on p2pool. On ckpool your s3 will be working its arse off all the time, meaning if you are running it at some kind of overclock, you may need to cut back a bit. Might be the load, or s3s dont like when stratum connection is interrupted - switching from ckpool to p2pool and back. That happens here, Ill install local ckpool and set that as first backup. S3:s got some bug maybe with stats because those wont display best share with all miner settings on p2pool. With share diff 1024 best share doesnt show, diff 500 it does.. It doesnt matter here that stats are reseted if it still goes on and finds a block  |
|
|
|
my s3's are fine, no problems hashing away. maybe you wanna try the 3334 port ? mine are running stock FW from BM. so far so good here. Same reboot happened when tried to solomine terracoin, cant remember if it was stock FW then on s3s. S1 ones rebooted also when tried to solo terracoin, they seem to be stable on ckpool. Theyre all hashing at +6C temperature so overheating is not possible I think. 6c seems really low most hash 250m at like 48-50c are your sensors bad Room temperature is +6C |
|
|
|
my s3's are fine, no problems hashing away. maybe you wanna try the 3334 port ? mine are running stock FW from BM. so far so good here. Same reboot happened when tried to solomine terracoin, cant remember if it was stock FW then on s3s. S1 ones rebooted also when tried to solo terracoin, they seem to be stable on ckpool. Theyre all hashing at +6C temperature so overheating is not possible I think. |
|
|
|
|
If I install this Ckpool software to my own node are my odds better or worse with lets say 1Th vs mining at solo.ckpool.org? (with i7 300mb/s networking...)
After difficult rise ive noticed that theres few days bad luck in p2pool with my miners, or is this just something noncense?
Does it help to have more miners on one bitcoind, more hashpower?
|
|
|
|
Managed to run proxy with -p but With -P it fails and have no clue what this means.. This is from a gentoo box so there should be those build essentials without any change - might be wrong though..
boxi src # ./ckpool -A -P
[2014-10-02 13:10:04] ckproxy generator starting
[2014-10-02 13:10:04] ckproxy generator ready
[2014-10-02 13:10:04] ckproxy stratifier starting
[2014-10-02 13:10:04] ckproxy connector starting
[2014-10-02 13:10:04] Failed to get a json result in passthrough_stratum, got: {"error": {"message": "Method not found", "code": -32601, "data": null}, "jsonrpc": "2.0", "id": null, "result": null}
[2014-10-02 13:10:04] ckproxy connector ready
[2014-10-02 13:10:04] ckproxy stratifier ready
If you read the docs, -P MUST have a full ckpool instance upstream or it will not work, so you can only use -p with another pool, like p2pool. Ok thanks, works great with -p |
|
|
|
|
Show Posts
