Search content
Sort by
Showing 20 of 97 results by corrow
Re: [3500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool
I see you're using an Rc version: v99900 - Maybe that's what's causing your errors. I only use the stable release versions for mining.......
OMG, Why I didn't saw that myself?
I'm gonna deploy a stable release of Bitcoin Core to factor this out! Thanks!
I've been monitoring my P2Pool Node very closely since the update to the last Bitcoin Core version. I found out with Block #339.597 (which took about 50mins and had more than 2000tx did not grow beyond the the maxblocksize of 1.000.000! This is great news now the P2Pool did not gave any "playload too long" error at console. The update to a later Bitcoin Core did the trick. I would advise everyone to update their Bitcoin Core concerning this issue!
Thanks for the good help and your efforts everyone!!!
Re: [3500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool
Well when recoding p2pool, It would be Nice to solve the "payload too long" issue as well.
Does somebody know how to deal with this?
Please check this post: https://bitcointalk.org/index.php?topic=18313.msg10164796#msg10164796
Does somebody know how to deal with this?
Please check this post: https://bitcointalk.org/index.php?topic=18313.msg10164796#msg10164796
So doing some digging, the "payload too long" error comes about when a packet's length is greater than max_payload_length. This can be seen in p2pool/util/p2protocol.py.
This is called from p2pool/bitcoin/p2p.py and p2pool/p2p.py where it sets max_payload_length to 1,000,000.
I am going to change the code to print out the packet size, as well as, change the max_payload_length to twice the size. I will let the code run for awhile and see what happens and report back.
If I'm correct the 'maxblocksize' is hardcoded to 1MB into the Bitcoin protocol. So I guess changing the payload length does do the trick within P2Pool code (until the blocksize will be increased). Well it is still unclear to me what part of the code you have changed. Logically it had to do with Bitcoin Core which is responsible for "packaging" the block and verify the hash of it. It would be awesome if you still could update us with news. I've also updated my Bitcoin Core and I'm waiting for a long blocktime with lots of transactions to debug my new setup. So, I'll keep you guys posted! Thanks!
Re: [3500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool
I see you're using an Rc version: v99900 - Maybe that's what's causing your errors. I only use the stable release versions for mining.......
OMG, Why I didn't saw that myself?
I'm gonna deploy a stable release of Bitcoin Core to factor this out! Thanks!
Re: [3500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool
Well when recoding p2pool, It would be Nice to solve the "payload too long" issue as well.
Does somebody know how to deal with this?
Please check this post: https://bitcointalk.org/index.php?topic=18313.msg10164796#msg10164796
Does somebody know how to deal with this?
Please check this post: https://bitcointalk.org/index.php?topic=18313.msg10164796#msg10164796
What is Your Bitcoind GetBlockTemplate Latency? Has You p2pool node external IP to see stats?
Thanks for the reply!
Well my stats looks like this:
Code:
P2Pool Status
Local rate 155.77 GH/s (DOA 3.67 GH/s / 2.35%) Shares Total: 2 (Orphan: 0, Dead: 1, Unknown: 1)
Global pool rate 1.93 PH/s (DOA 321.61 TH/s / 16.67%) Share difficulty 6,707,631.61
Current block value Expected time to share 2d 3h 22m 33 s
Total node payout if block found NOW Expected time to block 1d 3h 11m 10 s
Node peers [in] 2 / 30 [out] Node uptime 2d 6h 35m 22 s
Node p2pool version 13.5-73-g12ca9d8-dirty Protocol version 1300
Node efficiency 60.00% Node getwork latency 305 ms
Node fee 0% Node donation 0%
Bitcoin Status
Network rate 303.41 PH/s Blocks 339,372
Current block 998,775 bytes / 1,600 txs Block difficulty 43,971,662,056.08958
Hashes to win 9.22 EH Block probability per GH 5.295015761671106e-12%
Total Bitcoins Expected time to block 0h 0m 30 s
Exchange rate Block interval 0h 10m 30 s
Connections [in] 12 / 523 [out] Node uptime 2d 6h 37m 53 s
Node bitcoind version 99900 Protocol version 70002
Relay fee Peer latency 675 ms
Local rate 155.77 GH/s (DOA 3.67 GH/s / 2.35%) Shares Total: 2 (Orphan: 0, Dead: 1, Unknown: 1)
Global pool rate 1.93 PH/s (DOA 321.61 TH/s / 16.67%) Share difficulty 6,707,631.61
Current block value Expected time to share 2d 3h 22m 33 s
Total node payout if block found NOW Expected time to block 1d 3h 11m 10 s
Node peers [in] 2 / 30 [out] Node uptime 2d 6h 35m 22 s
Node p2pool version 13.5-73-g12ca9d8-dirty Protocol version 1300
Node efficiency 60.00% Node getwork latency 305 ms
Node fee 0% Node donation 0%
Bitcoin Status
Network rate 303.41 PH/s Blocks 339,372
Current block 998,775 bytes / 1,600 txs Block difficulty 43,971,662,056.08958
Hashes to win 9.22 EH Block probability per GH 5.295015761671106e-12%
Total Bitcoins Expected time to block 0h 0m 30 s
Exchange rate Block interval 0h 10m 30 s
Connections [in] 12 / 523 [out] Node uptime 2d 6h 37m 53 s
Node bitcoind version 99900 Protocol version 70002
Relay fee Peer latency 675 ms
I assume my Bitcoind GetBlockTemplate Latency is 675ms, right? From what I've read, the latencies are OK and they are stable when the "payload too long" error is not occurring. Only when the error comes up in the console of p2pool then those latencies are indeed skyrocketing. As I understand from the logs and statistics this payload error does not look like a cause from latencies, but latencies are the symptoms of the payload error. So where all the sudden arises this payload error from? Is it the "maxblocksize" of Bitcoind Core which is 1MB? Because the payload error is always in combination when the blocktime between blocks were +10mins (and +2000 transactions). Get the idea the problem comes from that direction.
Any thoughts?
Re: [3500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool
Well when recoding p2pool, It would be Nice to solve the "payload too long" issue as well.
Does somebody know how to deal with this?
Please check this post: https://bitcointalk.org/index.php?topic=18313.msg10164796#msg10164796
Does somebody know how to deal with this?
Please check this post: https://bitcointalk.org/index.php?topic=18313.msg10164796#msg10164796
Re: [3500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool
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?
I received the same error as well at around the same time. I will post it on github if anyone hasn't already.
I posted the issue here https://github.com/forrestv/p2pool/issues/238 so others can update as well.
Did this happen to anyone else?
Well I experience more or less the same issues. P2Pool or Bitcoind does not crash, except the static site of P2Pool (http://localhost:9332/static/) is frozen during this error and mining becomes impossible. Sometimes it takes up to 60 seconds and sometimes several minutes; the error keeps showing up until that block has been solved. The "freeze" on the static website and the interruption of mining is temporarily and only happens during the error "payload is too long". Please check the log below:
Code:
2015-01-15 14:50:04.013590 > Error submitting primary block: (will retry)
2015-01-15 14:50:04.013683 > Traceback (most recent call last):
2015-01-15 14:50:04.013742 > File "/home/bitcoind/p2pool/p2pool/work.py", line 381, in got_response
2015-01-15 14:50:04.013785 > helper.submit_block(dict(header=header, txs=[new_gentx] + other_transactions), False, self.node.factory, self.node.bitcoind, self.node.bitcoind_work, self.node.net)
2015-01-15 14:50:04.013817 > File "/home/bitcoind/p2pool/p2pool/bitcoin/helper.py", line 86, in submit_block
2015-01-15 14:50:04.013858 > submit_block_p2p(block, factory, net)
2015-01-15 14:50:04.013900 > File "/usr/local/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1181, in unwindGenerator
2015-01-15 14:50:04.013932 > return _inlineCallbacks(None, gen, Deferred())
2015-01-15 14:50:04.013977 > File "/usr/local/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1039, in _inlineCallbacks
2015-01-15 14:50:04.014007 > result = g.send(result)
2015-01-15 14:50:04.014037 > --- ---
2015-01-15 14:50:04.014067 > File "/home/bitcoind/p2pool/p2pool/util/deferral.py", line 41, in f
2015-01-15 14:50:04.014097 > result = yield func(*args, **kwargs)
2015-01-15 14:50:04.014127 > File "/home/bitcoind/p2pool/p2pool/bitcoin/helper.py", line 67, in submit_block_p2p
2015-01-15 14:50:04.014157 > factory.conn.value.send_block(block=block)
2015-01-15 14:50:04.014191 > File "/home/bitcoind/p2pool/p2pool/util/p2protocol.py", line 102, in
2015-01-15 14:50:04.014222 > return lambda **payload2: self.sendPacket(command, payload2)
2015-01-15 14:50:04.014257 > File "/home/bitcoind/p2pool/p2pool/util/p2protocol.py", line 93, in sendPacket
2015-01-15 14:50:04.014289 > raise TooLong('payload too long')
2015-01-15 14:50:04.014318 > p2pool.util.p2protocol.TooLong: payload too long
2015-01-15 14:50:04.013683 > Traceback (most recent call last):
2015-01-15 14:50:04.013742 > File "/home/bitcoind/p2pool/p2pool/work.py", line 381, in got_response
2015-01-15 14:50:04.013785 > helper.submit_block(dict(header=header, txs=[new_gentx] + other_transactions), False, self.node.factory, self.node.bitcoind, self.node.bitcoind_work, self.node.net)
2015-01-15 14:50:04.013817 > File "/home/bitcoind/p2pool/p2pool/bitcoin/helper.py", line 86, in submit_block
2015-01-15 14:50:04.013858 > submit_block_p2p(block, factory, net)
2015-01-15 14:50:04.013900 > File "/usr/local/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1181, in unwindGenerator
2015-01-15 14:50:04.013932 > return _inlineCallbacks(None, gen, Deferred())
2015-01-15 14:50:04.013977 > File "/usr/local/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1039, in _inlineCallbacks
2015-01-15 14:50:04.014007 > result = g.send(result)
2015-01-15 14:50:04.014037 > --- ---
2015-01-15 14:50:04.014067 > File "/home/bitcoind/p2pool/p2pool/util/deferral.py", line 41, in f
2015-01-15 14:50:04.014097 > result = yield func(*args, **kwargs)
2015-01-15 14:50:04.014127 > File "/home/bitcoind/p2pool/p2pool/bitcoin/helper.py", line 67, in submit_block_p2p
2015-01-15 14:50:04.014157 > factory.conn.value.send_block(block=block)
2015-01-15 14:50:04.014191 > File "/home/bitcoind/p2pool/p2pool/util/p2protocol.py", line 102, in
2015-01-15 14:50:04.014222 > return lambda **payload2: self.sendPacket(command, payload2)
2015-01-15 14:50:04.014257 > File "/home/bitcoind/p2pool/p2pool/util/p2protocol.py", line 93, in sendPacket
2015-01-15 14:50:04.014289 > raise TooLong('payload too long')
2015-01-15 14:50:04.014318 > p2pool.util.p2protocol.TooLong: payload too long
This error in the log file showed up during block #339060 ( https://blockchain.info/block-height/339060 ) which took ~22 minutes to solve and contained +2200 transactions.
Note: Timezone is GMT+1
What is wrong here? Why the error "payload too long" occurs? I'm having this issue for 1-2 weeks now and noticed that the error occurs when blocks have a larger time interval than average (+10 mins and +2000 transactions).
Does anyone has any idea how to fix this issue?
Nice new picostocks page design Leszek 
I think is worse than previous...I do not care much about the new interface. I would like to know about new plans and prospects of the project in the near future instead!
Are there any further plans with this project? Further expansion of the hashingpower? Any news or prospectives?
There has not been any expansion in over a year - and there wont be any more expansion.
Can Leszek or buzzdave confirm this?!
Hello everybody,
I'm willing to sell multiple BlackArrow Prospero X3 Units. When you are interested in buying all of them PM me or leave a message in the thread!
Also offers for one BlackArrow Prospero X3 Unit are welcome!
- All Units perform a minimum of 1100+Ghps alone.
- Unit will include a PSU.
- Unit is in hand and will ship immediately.
- Shipping worldwide (DHL Express Delivery in 1-4 business days), but is NOT included within the price.
- Located in the EU.
- Escrow possible costs are yours.
Thanks!
I'm willing to sell multiple BlackArrow Prospero X3 Units. When you are interested in buying all of them PM me or leave a message in the thread!
Also offers for one BlackArrow Prospero X3 Unit are welcome!
- All Units perform a minimum of 1100+Ghps alone.
- Unit will include a PSU.
- Unit is in hand and will ship immediately.
- Shipping worldwide (DHL Express Delivery in 1-4 business days), but is NOT included within the price.
- Located in the EU.
- Escrow possible costs are yours.
Thanks!
price, pictures?
Not looking for a particular price, just about what it is worth mining or considered as the current value of the market.
Hello everybody,
I'm willing to sell multiple October Jupiter Units for the best price. When you are interested in buying all of them PM me for a nice offer!
- All Units perform a minimum of 550+Ghps alone.
- Unit is in hand and will ship immediately.
- Shipping worldwide (DHL Express Delivery in 1-4 business days), but is NOT included within the price.
- Located in the EU.
- Escrow possible costs are yours.
Thanks!
I'm willing to sell multiple October Jupiter Units for the best price. When you are interested in buying all of them PM me for a nice offer!
- All Units perform a minimum of 550+Ghps alone.
- Unit is in hand and will ship immediately.
- Shipping worldwide (DHL Express Delivery in 1-4 business days), but is NOT included within the price.
- Located in the EU.
- Escrow possible costs are yours.
Thanks!
Keep it clean and ask for offers in the thread. Photos would be nice with nick and date.
Thanks, for the information! I'll update the post tomorrow with photo's.
Anyways feel free to post your price and amount in this thread!
Cheers!
Hello everybody,
I'm willing to sell multiple October Jupiter Units for the best price. When you are interested in buying all of them PM me for a nice offer!
- All Units perform a minimum of 550+Ghps alone.
- Unit is in hand and will ship immediately.
- Shipping worldwide (DHL Express Delivery in 1-4 business days), but is NOT included within the price.
- Located in the EU.
- Escrow possible costs are yours.
Thanks!
I'm willing to sell multiple October Jupiter Units for the best price. When you are interested in buying all of them PM me for a nice offer!
- All Units perform a minimum of 550+Ghps alone.
- Unit is in hand and will ship immediately.
- Shipping worldwide (DHL Express Delivery in 1-4 business days), but is NOT included within the price.
- Located in the EU.
- Escrow possible costs are yours.
Thanks!
This proves again, they have wrong ethics!!!!!
They need to pay back their customers first!!!
Cheap self serving fear mongering, nothing more, nothing less.
KNC said in their recent announcement that they will stand by and support their loyal customers, and I believe them.
KNC said in their recent announcement that they will stand by and support their loyal customers, and I believe them.
At the moment the mistakes are piling up, due to bad management. Logical KnC is doing everything to make it right and save their soul. Sure I believe they will try, but still people are suffering hard due to their lack of profession. Which is not fair at all! Not keeping promises, keeping information behind etc. does not fit within the picture of a trusted and proper corporate governance. Is it rational to be loyal to them? Well maybe it is, when people are blind for it.