Evil-Knievel
Legendary
Offline
Activity: 1260
Merit: 1168
|
|
September 02, 2016, 09:46:38 PM Last edit: September 02, 2016, 10:03:44 PM by Evil-Knievel |
|
Wow, unvoid! It looks like you have found just another glitch! I think Lannister would send you 2 more BTC (as I recall you are eligible for the first bug bounty as well) if you can reproduce what happened. This is the error log: at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) 2016-09-02 23:43:20 FINE: TransactionProcessorImpl.processPeerTransactions: Invalid transaction from peer: {"senderPublicKey":"ae0df06215caa34bf680a84b24330554d0af092b925b5bcf8704ac31cd489019","signature":"d9a188015ff1c333095bb417833ee2baef34baa6eb23db4d5b7bd791c4d88b01de4059f9682553ac6ff1d96f86b352939befbdc6df22c3d513045fa3ac88a612","feeNQT":0,"type":3,"version":1,"ecBlockId":"2573426999249322481","attachment":{"input":[227557251,-1921958936,-762815411],"version.PiggybackedProofOfWork":1,"id":"4210165941331695358"},"subtype":2,"amountNQT":1000000000,"recipient":"12808828738982832951","ecBlockHeight":2242,"deadline":1440,"timestamp":21236953} nxt.NxtException$NotValidException: Cannot submit POW for an already cancelled or finished work at nxt.TransactionType$WorkControl$4.validateAttachment(TransactionType.java:641) at nxt.Attachment$AbstractAttachment.validate(Attachment.java:34) at nxt.TransactionImpl.validate(TransactionImpl.java:835) at nxt.TransactionProcessorImpl.processPeerTransactions(TransactionProcessorImpl.java:468) at nxt.TransactionProcessorImpl.access$8(TransactionProcessorImpl.java:440) at nxt.TransactionProcessorImpl$5.run(TransactionProcessorImpl.java:211) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) 2016-09-02 23:43:20 FINE: TransactionProcessorImpl.processPeerTransactions: Invalid transaction from peer: {"senderPublicKey":"ae0df06215caa34bf680a84b24330554d0af092b925b5bcf8704ac31cd489019","signature":"7bad419fa86d3389dcecb9c87f7bf4a1aac1996bd570f1f56721e7d536cc250bf18c7cb7687db1c256048176e5509f0150ff0df0c2a9cb0864db82d79a3ce680","feeNQT":0,"type":3,"version":1,"ecBlockId":"9110437482347234720","attachment":{"input":[1908206150,-339794908,-1895261197],"version.PiggybackedProofOfWork":1,"id":"4210165941331695358"},"subtype":2,"amountNQT":1000000000,"recipient":"12808828738982832951","ecBlockHeight":2243,"deadline":1440,"timestamp":21237068} nxt.NxtException$NotValidException: Cannot submit POW for an already cancelled or finished work at nxt.TransactionType$WorkControl$4.validateAttachment(TransactionType.java:641) at nxt.Attachment$AbstractAttachment.validate(Attachment.java:34) at nxt.TransactionImpl.validate(TransactionImpl.java:835) at nxt.TransactionProcessorImpl.processPeerTransactions(TransactionProcessorImpl.java:468) at nxt.TransactionProcessorImpl.access$8(TransactionProcessorImpl.java:440) at nxt.TransactionProcessorImpl$5.run(TransactionProcessorImpl.java:211) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) 2016-09-02 23:43:20 FINE: TransactionProcessorImpl.processPeerTransactions: Invalid transaction from peer: {"senderPublicKey":"ae0df06215caa34bf680a84b24330554d0af092b925b5bcf8704ac31cd489019","signature":"377a1355b86c0465139542b7994c5c5a999eac25774f1e54076242a6d4232707c8d534fe54ee7fb53cfddd67176cf79f1a8591b4c49e1755301fee0eb21a14ae","feeNQT":0,"type":3,"version":1,"ecBlockId":"12998068690024528804","attachment":{"input":[518577662,1779649994,1251435883],"version.PiggybackedProofOfWork":1,"id":"4210165941331695358"},"subtype":2,"amountNQT":1000000000,"recipient":"12808828738982832951","ecBlockHeight":2244,"deadline":1440,"timestamp":21237090} nxt.NxtException$NotValidException: Cannot submit POW for an already cancelled or finished work at nxt.TransactionType$WorkControl$4.validateAttachment(TransactionType.java:641) at nxt.Attachment$AbstractAttachment.validate(Attachment.java:34) at nxt.TransactionImpl.validate(TransactionImpl.java:835) at nxt.TransactionProcessorImpl.processPeerTransactions(TransactionProcessorImpl.java:468) at nxt.TransactionProcessorImpl.access$8(TransactionProcessorImpl.java:440) at nxt.TransactionProcessorImpl$5.run(TransactionProcessorImpl.java:211) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) java.lang.RuntimeException: Proof of work is invalid: does not meet target at nxt.WorkLogicManager.validatePOW(WorkLogicManager.java:1199) at nxt.TransactionType$WorkControl$4.validateAttachment(TransactionType.java:661) at nxt.Attachment$AbstractAttachment.validate(Attachment.java:34) at nxt.TransactionImpl.validate(TransactionImpl.java:835) at nxt.TransactionProcessorImpl.processPeerTransactions(TransactionProcessorImpl.java:468) at nxt.TransactionProcessorImpl.access$8(TransactionProcessorImpl.java:440) at nxt.TransactionProcessorImpl$5.run(TransactionProcessorImpl.java:211) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) 2016-09-02 23:43:20 FINE: TransactionProcessorImpl.processPeerTransactions: Invalid transaction from peer: {"senderPublicKey":"ae0df06215caa34bf680a84b24330554d0af092b925b5bcf8704ac31cd489019","signature":"0abe685bdb4060c9d1ed9fe4f471b973797256ce07e37ff588c25083d97b640319dff076e884c6b661a4e37eb97361c5b9845fafcd1ef0958c34f83865b44fd7","feeNQT":0,"type":3,"version":1,"ecBlockId":"9110437482347234720","attachment":{"input":[1365308818,-704527682,-70936512],"version.PiggybackedProofOfWork":1,"id":"11341360148518111736"},"subtype":2,"amountNQT":1000000000,"recipient":"12808828738982832951","ecBlockHeight":2243,"deadline":1440,"timestamp":21237055} java.lang.RuntimeException: Proof of work is invalid: causes ElasticPL function to crash at nxt.WorkLogicManager.validatePOW(WorkLogicManager.java:1204) at nxt.TransactionType$WorkControl$4.validateAttachment(TransactionType.java:661) at nxt.Attachment$AbstractAttachment.validate(Attachment.java:34) at nxt.TransactionImpl.validate(TransactionImpl.java:835) at nxt.TransactionProcessorImpl.processPeerTransactions(TransactionProcessorImpl.java:468) at nxt.TransactionProcessorImpl.access$8(TransactionProcessorImpl.java:440) at nxt.TransactionProcessorImpl$5.run(TransactionProcessorImpl.java:211) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) 2016-09-02 23:43:20 FINE: TransactionProcessorImpl.processPeerTransactions: Invalid transaction from peer: {"senderPublicKey":"ae0df06215caa34bf680a84b24330554d0af092b925b5bcf8704ac31cd489019","signature":"74577f9d208e5119e48772a394f7aa255b1895434a876d21b47d0466039c450770031c9f41adee104bc539786d0ea3dba62f03eed82d78f5d5dd7f3e073ca537","feeNQT":0,"type":3,"version":1,"ecBlockId":"2573426999249322481","attachment":{"input":[-658827307,-1689579444,1999346988],"version.PiggybackedProofOfWork":1,"id":"4210165941331695358"},"subtype":2,"amountNQT":1000000000,"recipient":"12808828738982832951","ecBlockHeight":2242,"deadline":1440,"timestamp":21236979} nxt.NxtException$NotValidException: Cannot submit POW for an already cancelled or finished work at nxt.TransactionType$WorkControl$4.validateAttachment(TransactionType.java:641) at nxt.Attachment$AbstractAttachment.validate(Attachment.java:34) at nxt.TransactionImpl.validate(TransactionImpl.java:835) at nxt.TransactionProcessorImpl.processPeerTransactions(TransactionProcessorImpl.java:468) at nxt.TransactionProcessorImpl.access$8(TransactionProcessorImpl.java:440) at nxt.TransactionProcessorImpl$5.run(TransactionProcessorImpl.java:211) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) java.lang.RuntimeException: Proof of work is invalid: does not meet target at nxt.WorkLogicManager.validatePOW(WorkLogicManager.java:1199) at nxt.TransactionType$WorkControl$4.validateAttachment(TransactionType.java:661) at nxt.Attachment$AbstractAttachment.validate(Attachment.java:34) at nxt.TransactionImpl.validate(TransactionImpl.java:835) at nxt.TransactionProcessorImpl.processPeerTransactions(TransactionProcessorImpl.java:468) at nxt.TransactionProcessorImpl.access$8(TransactionProcessorImpl.java:440) at nxt.TransactionProcessorImpl$5.run(TransactionProcessorImpl.java:211) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) 2016-09-02 23:43:20 FINE: TransactionProcessorImpl.processPeerTransactions: Invalid transaction from peer: {"senderPublicKey":"ae0df06215caa34bf680a84b24330554d0af092b925b5bcf8704ac31cd489019","signature":"0fa10e53673f40371caa1afd80464175fd6db42a735f673e80a94e026a5e5d03772eeccdfd72d7292c130d4c5053c08b638406c7a8ee203afbcbf3504e8542cb","feeNQT":0,"type":3,"version":1,"ecBlockId":"12998068690024528804","attachment":{"input":[-558658430,-1424419223,-684303585],"version.PiggybackedProofOfWork":1,"id":"11341360148518111736"},"subtype":2,"amountNQT":1000000000,"recipient":"12808828738982832951","ecBlockHeight":2244,"deadline":1440,"timestamp":21237106} java.lang.RuntimeException: Proof of work is invalid: causes ElasticPL function to crash at nxt.WorkLogicManager.validatePOW(WorkLogicManager.java:1204) at nxt.TransactionType$WorkControl$4.validateAttachment(TransactionType.java:661) at nxt.Attachment$AbstractAttachment.validate(Attachment.java:34) at nxt.TransactionImpl.validate(TransactionImpl.java:835) at nxt.TransactionProcessorImpl.processPeerTransactions(TransactionProcessorImpl.java:468) at nxt.TransactionProcessorImpl.access$8(TransactionProcessorImpl.java:440) at nxt.TransactionProcessorImpl$5.run(TransactionProcessorImpl.java:211) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Validating POW for work = -7105383925191439880 Validating POW for work = -7105383925191439880 java.lang.RuntimeException: Proof of work is invalid: does not meet target
I will have a more detailed look tomorrow morning, I hope nobody is worried, this is expected behaviour! We need to identify all side cases and all glitches that may be possible. Unvoid, thank you so much for helping out! I am sure that you will be rewarded hugely. The problem currently obviously lies in the block generation routine. If you take a look at this function (nxt.BlockchainProcessorImpl.generateBlock(BlockchainProcessorImpl.java:958)), you see it somehow includes invalid work. Not sure why invalid work even got included into the mempool in the first place. Maybe it got accepted first, then not included in any block, and then became invalid due to changed difficulty. Everything that is in the mempool should be accepted in a block in the first place!!! There is a bug somewhere! Clearly. java.lang.RuntimeException: Proof of work is invalid: does not meet target at nxt.WorkLogicManager.validatePOW(WorkLogicManager.java:1199) at nxt.TransactionType$WorkControl$4.validateAttachment(TransactionType.java:661) at nxt.Attachment$AbstractAttachment.validate(Attachment.java:34) at nxt.TransactionImpl.validate(TransactionImpl.java:835) at nxt.BlockchainProcessorImpl.generateBlock(BlockchainProcessorImpl.java:958) at nxt.Generator.forge(Generator.java:296) at nxt.Generator$1.run(Generator.java:79) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) 2016-09-02 23:55:21 FINE: Generator$1.run: Error in block generation thread I would say, if you can fix this mistake before my holiday is over I would give you 5 BTC of my personal savings on top of the bug bounties that Lannister will pay out to you.
|
|
|
|
|
|
|
|
|
"Governments are good at cutting off the heads of a centrally
controlled
networks like Napster, but pure P2P networks like Gnutella and Tor seem
to be holding their own." -- Satoshi
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
trader19
Legendary
Offline
Activity: 1232
Merit: 1001
|
|
September 02, 2016, 10:08:57 PM Last edit: September 02, 2016, 10:49:27 PM by trader19 |
|
Wow, unvoid! It looks like you have found just another glitch! I think Lannister would send you 2 more BTC (as I recall you are eligible for the first bug bounty as well) .... I would say, if you can fix this mistake before my holiday is over I would give you 5 BTC of my personal savings on top of the bug bounties that Lannister will pay out to you.
yes i have the same on my logs, when i was setting up second server it throwed alot of errors and banned all the peers.. can this be the reason that network stoped moving?? Edit: i must admit i played a bit with ports on second node i setuped, may be that triggered me banning other nodes. change i made were on nxt-default.properties!! it could be a problem with how peers interact. here my log maybe it helps: 2016-09-03 00:03:58 FINE: TransactionProcessorImpl.processPeerTransactions: Invalid transaction from peer: {"senderPublicKey":"ae0df06215caa34bf680a84b24330554d0af092b925b5bcf8704ac31cd489019","signature":"184ab92b3d18eb8b6dc426415c8fd47c471db184e7ec743ba6b54f3e7358d901d8245682f92285baae65db3df9b6c795b72ccaf58a9c152acba825147c20f9da","feeNQT":0,"type":3,"version":1,"ecBlockId":"2871771636556869817","attachment":{"input":[179229214,1466908374,1493491762],"version.PiggybackedProofOfWork":1,"id":"11341360148518111736"},"subtype":2,"amountNQT":1000000000,"recipient":"12808828738982832951","ecBlockHeight":2258,"deadline":1440,"timestamp":21238027} java.lang.RuntimeException: Proof of work is invalid: causes ElasticPL function to crash at nxt.WorkLogicManager.validatePOW(WorkLogicManager.java:1204) at nxt.TransactionType$WorkControl$4.validateAttachment(TransactionType.java:661) at nxt.Attachment$AbstractAttachment.validate(Attachment.java:34) at nxt.TransactionImpl.validate(TransactionImpl.java:835) at nxt.TransactionProcessorImpl.processPeerTransactions(TransactionProcessorImpl.java:468) at nxt.TransactionProcessorImpl.access$500(TransactionProcessorImpl.java:36) at nxt.TransactionProcessorImpl$5.run(TransactionProcessorImpl.java:211) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Validating POW for work = -7105383925191439880 java.lang.RuntimeException: Proof of work is invalid: does not meet target at nxt.WorkLogicManager.validatePOW(WorkLogicManager.java:1199) at nxt.TransactionType$WorkControl$4.validateAttachment(TransactionType.java:661) at nxt.Attachment$AbstractAttachment.validate(Attachment.java:34) at nxt.TransactionImpl.validate(TransactionImpl.java:835) at nxt.TransactionProcessorImpl.processPeerTransactions(TransactionProcessorImpl.java:468) at nxt.TransactionProcessorImpl.access$500(TransactionProcessorImpl.java:36) at nxt.TransactionProcessorImpl$5.run(TransactionProcessorImpl.java:211) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) 2016-09-03 00:03:58 FINE: TransactionProcessorImpl.processPeerTransactions: Invalid transaction from peer: {"senderPublicKey":"ae0df06215caa34bf680a84b24330554d0af092b925b5bcf8704ac31cd489019","signature":"ab35345f8fd915a8271e3e42e453eae978fb381f42e08add99f960d920ae90077709ee289768548661d2e8fbad93e5e49fa73810e94c51e8a2a3be02e571bc55","feeNQT":0,"type":3,"version":1,"ecBlockId":"8374719821771097422","attachment":{"input":[-927207464,-1246912258,1665854923],"version.PiggybackedProofOfWork":1,"id":"11341360148518111736"},"subtype":2,"amountNQT":1000000000,"recipient":"12808828738982832951","ecBlockHeight":2260,"deadline":1440,"timestamp":21238093} java.lang.RuntimeException: Proof of work is invalid: causes ElasticPL function to crash at nxt.WorkLogicManager.validatePOW(WorkLogicManager.java:1204) at nxt.TransactionType$WorkControl$4.validateAttachment(TransactionType.java:661) at nxt.Attachment$AbstractAttachment.validate(Attachment.java:34) at nxt.TransactionImpl.validate(TransactionImpl.java:835) at nxt.TransactionProcessorImpl.processPeerTransactions(TransactionProcessorImpl.java:468) at nxt.TransactionProcessorImpl.access$500(TransactionProcessorImpl.java:36) at nxt.TransactionProcessorImpl$5.run(TransactionProcessorImpl.java:211) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Validating POW for work = -7105383925191439880 java.lang.RuntimeException: Proof of work is invalid: does not meet target at nxt.WorkLogicManager.validatePOW(WorkLogicManager.java:1199) at nxt.TransactionType$WorkControl$4.validateAttachment(TransactionType.java:661) at nxt.Attachment$AbstractAttachment.validate(Attachment.java:34) at nxt.TransactionImpl.validate(TransactionImpl.java:835) at nxt.TransactionProcessorImpl.processPeerTransactions(TransactionProcessorImpl.java:468) at nxt.TransactionProcessorImpl.access$500(TransactionProcessorImpl.java:36) at nxt.TransactionProcessorImpl$5.run(TransactionProcessorImpl.java:211) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) 2016-09-03 00:03:58 FINE: TransactionProcessorImpl.processPeerTransactions: Invalid transaction from peer: {"senderPublicKey":"ae0df06215caa34bf680a84b24330554d0af092b925b5bcf8704ac31cd489019","signature":"750e00d1d840a09a7917a519653f1f58fe7af2f5f8e6fc2fe1010ba285420801e748c8dd1f0cfacac89b80b9f3ed2d7eee4483b8cb7bec7438f9bb807bd3980b","feeNQT":0,"type":3,"version":1,"ecBlockId":"8374719821771097422","attachment":{"input":[-243064765,-1325190373,-329177223],"version.PiggybackedProofOfWork":1,"id":"11341360148518111736"},"subtype":2,"amountNQT":1000000000,"recipient":"12808828738982832951","ecBlockHeight":2260,"deadline":1440,"timestamp":21238095} java.lang.RuntimeException: Proof of work is invalid: causes ElasticPL function to crash at nxt.WorkLogicManager.validatePOW(WorkLogicManager.java:1204) at nxt.TransactionType$WorkControl$4.validateAttachment(TransactionType.java:661) at nxt.Attachment$AbstractAttachment.validate(Attachment.java:34) at nxt.TransactionImpl.validate(TransactionImpl.java:835) at nxt.TransactionProcessorImpl.processPeerTransactions(TransactionProcessorImpl.java:468) at nxt.TransactionProcessorImpl.access$500(TransactionProcessorImpl.java:36) at nxt.TransactionProcessorImpl$5.run(TransactionProcessorImpl.java:211) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Validating POW for work = -7105383925191439880 java.lang.RuntimeException: Proof of work is invalid: does not meet target at nxt.WorkLogicManager.validatePOW(WorkLogicManager.java:1199) at nxt.TransactionType$WorkControl$4.validateAttachment(TransactionType.java:661) at nxt.Attachment$AbstractAttachment.validate(Attachment.java:34) at nxt.TransactionImpl.validate(TransactionImpl.java:835) at nxt.TransactionProcessorImpl.processPeerTransactions(TransactionProcessorImpl.java:468) at nxt.TransactionProcessorImpl.access$500(TransactionProcessorImpl.java:36) at nxt.TransactionProcessorImpl$5.run(TransactionProcessorImpl.java:211) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) 2016-09-03 00:03:58 FINE: TransactionProcessorImpl.processPeerTransactions: Invalid transaction from peer: {"senderPublicKey":"ae0df06215caa34bf680a84b24330554d0af092b925b5bcf8704ac31cd489019","signature":"23efd6d0f5d475a7bacbff1712cf47e59a17ca838854ccf9806bea12e3482f0c607f32f146a67530c957fa83da96d810d81760f62f8330464e00063bba97255b","feeNQT":0,"type":3,"version":1,"ecBlockId":"9625735294777976311","attachment":{"input":[-296756662,298707674,763600244],"version.PiggybackedProofOfWork":1,"id":"11341360148518111736"},"subtype":2,"amountNQT":1000000000,"recipient":"12808828738982832951","ecBlockHeight":2261,"deadline":1440,"timestamp":21238123} java.lang.RuntimeException: Proof of work is invalid: causes ElasticPL function to crash at nxt.WorkLogicManager.validatePOW(WorkLogicManager.java:1204) at nxt.TransactionType$WorkControl$4.validateAttachment(TransactionType.java:661) at nxt.Attachment$AbstractAttachment.validate(Attachment.java:34) at nxt.TransactionImpl.validate(TransactionImpl.java:835) at nxt.TransactionProcessorImpl.processPeerTransactions(TransactionProcessorImpl.java:468) at nxt.TransactionProcessorImpl.access$500(TransactionProcessorImpl.java:36) at nxt.TransactionProcessorImpl$5.run(TransactionProcessorImpl.java:211) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Validating POW for work = -7105383925191439880 java.lang.RuntimeException: Proof of work is invalid: does not meet target at nxt.WorkLogicManager.validatePOW(WorkLogicManager.java:1199) at nxt.TransactionType$WorkControl$4.validateAttachment(TransactionType.java:661) at nxt.Attachment$AbstractAttachment.validate(Attachment.java:34) at nxt.TransactionImpl.validate(TransactionImpl.java:835) at nxt.TransactionProcessorImpl.processPeerTransactions(TransactionProcessorImpl.java:468) at nxt.TransactionProcessorImpl.access$500(TransactionProcessorImpl.java:36) at nxt.TransactionProcessorImpl$5.run(TransactionProcessorImpl.java:211) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) 2016-09-03 00:03:58 FINE: TransactionProcessorImpl.processPeerTransactions: Invalid transaction from peer: {"senderPublicKey":"ae0df06215caa34bf680a84b24330554d0af092b925b5bcf8704ac31cd489019","signature":"531eb1490e04eefe9e9ac0992fa44cc4d2d412fba9d6780b3638597aad8e5307eb30c676d2a9f6363a2adba7cde6d5154fd3e416c5e837fb93c019bb840301bf","feeNQT":0,"type":3,"version":1,"ecBlockId":"7943361064250860785","attachment":{"input":[-990667952,654208454,-2008405028],"version.PiggybackedProofOfWork":1,"id":"11341360148518111736"},"subtype":2,"amountNQT":1000000000,"recipient":"12808828738982832951","ecBlockHeight":2282,"deadline":1440,"timestamp":21239436} java.lang.RuntimeException: Proof of work is invalid: causes ElasticPL function to crash at nxt.WorkLogicManager.validatePOW(WorkLogicManager.java:1204) at nxt.TransactionType$WorkControl$4.validateAttachment(TransactionType.java:661) at nxt.Attachment$AbstractAttachment.validate(Attachment.java:34) at nxt.TransactionImpl.validate(TransactionImpl.java:835) at nxt.TransactionProcessorImpl.processPeerTransactions(TransactionProcessorImpl.java:468) at nxt.TransactionProcessorImpl.access$500(TransactionProcessorImpl.java:36) at nxt.TransactionProcessorImpl$5.run(TransactionProcessorImpl.java:211) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) 2016-09-03 00:03:58 FINE: PeerImpl.blacklist: Blacklisting 52.28.123.208 because of: nxt.NxtException$NotValidException: Peer sends invalid transactions nxt.NxtException$NotValidException: Peer sends invalid transactions at nxt.TransactionProcessorImpl.processPeerTransactions(TransactionProcessorImpl.java:495) at nxt.TransactionProcessorImpl.access$500(TransactionProcessorImpl.java:36) at nxt.TransactionProcessorImpl$5.run(TransactionProcessorImpl.java:211) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)
also getting bunch of this since network frozen: Clearing inactive listener: 383971131 Clearing inactive listener: 383971131 Clearing inactive listener: 383971131 Clearing inactive listener: 383971131 Clearing inactive listener: 383971131 Clearing inactive listener: 383971131 Clearing inactive listener: 383971131 Clearing inactive listener: 383971131 Clearing inactive listener: 383971131 Clearing inactive listener: 383971131 Clearing inactive listener: 383971131 Clearing inactive listener: 383971131 Clearing inactive listener: 383971131
|
|
|
|
Evil-Knievel
Legendary
Offline
Activity: 1260
Merit: 1168
|
|
September 03, 2016, 06:26:04 AM Last edit: September 03, 2016, 06:45:16 AM by Evil-Knievel |
|
Never mind, I think I have fixed the mistake!The problem was, that the work cancellation transaction threw a "RuntimeException" when they were invalid. Usually invalid ones get dropped from the memory pool immediately (we should think about why that didn't happen here? Maybe you mined with two different computers?). In this case they all were in the mempool. This should be no problem, because the blockGeneration should ignore them. But it didn't do it, because it only ignored TX with an Exception type of "NotValidException". try { unconfirmedTransaction.getTransaction().validate(); } catch (NxtException.NotCurrentlyValidException e) { continue; } catch (NxtException.ValidationException e) { transactionProcessor.removeUnconfirmedTransaction(unconfirmedTransaction.getTransaction()); continue; } So its important we make sure that all transactions that invalidate give back a NotValidTransaction! (TODO to myself)Block 2317 was just mined!
One Problem that still might occur is that the old corrupt TX are in the mempool and are trying to be broadcasted which may get you blacklisted by the two public peers. We have to think about a solution for that!
I think, git pull, deleting nxt_test_db/, doing a compile.sh and a run.sh should be enough to clear the mempool and redownload the blockchain from the "fixed" nodes. The chain was not reset.
I still have no idea why invalid transactions are broadcast?! I am mobile at the moment and do not always have internet access! If someone finds out, and provides a fix I would give 2 BTC of my own savings as a bonus for the help.
|
|
|
|
Evil-Knievel
Legendary
Offline
Activity: 1260
Merit: 1168
|
|
September 03, 2016, 06:26:36 AM |
|
We need more crashes! Thank you all for stress-testing! Every crash in this phase is a good crash!
|
|
|
|
unvoid
|
|
September 03, 2016, 04:34:16 PM |
|
@EK awesome. Another step to XEL maturity. Blockchain explorer on it's way.
|
BTC: 1CMgHWx4wkAaAy2FfeCyPdedUExmhGhfi5 XEL: XEL-HCM8-KB6E-YFLK-8BWMF
|
|
|
StratisKing
|
|
September 03, 2016, 05:09:40 PM |
|
We need more crashes! Thank you all for stress-testing! Every crash in this phase is a good crash! Yrp, crashing in test-net is 100% good things, to avoid bug in main-net running, crashing befote main-net live is an improvement of this project.
|
|
|
|
unvoid
|
|
September 03, 2016, 05:20:03 PM |
|
@ImI is there any problem with your node? I'm mining all blocks since 30min.
|
BTC: 1CMgHWx4wkAaAy2FfeCyPdedUExmhGhfi5 XEL: XEL-HCM8-KB6E-YFLK-8BWMF
|
|
|
ImI
Legendary
Offline
Activity: 1946
Merit: 1019
|
|
September 03, 2016, 05:25:33 PM |
|
@ImI is there any problem with your node? I'm mining all blocks since 30min.
i'll check edit: http://ec2-52-28-123-208.eu-central-1.compute.amazonaws.com:6876/index.html seems down. so far i havent upgraded my own vps-node to 0.2.0 and therefore you are running the network now. good that we are now past those 1440 blocks so you are able to forge. i will update my node as soon as i have a little free time and then start forging again. or maybe aws will come back online soon anyway.
|
|
|
|
|
BigBoom3599
|
|
September 03, 2016, 06:19:09 PM |
|
Maybe for the next version of the testnet there should be a better to distribute XELs, because only a couple of people are able to forge atm.
|
|
|
|
ImI
Legendary
Offline
Activity: 1946
Merit: 1019
|
|
September 03, 2016, 06:22:33 PM |
|
Maybe for the next version of the testnet there should be a better to distribute XELs, because only a couple of people are able to forge atm.
just post your address and we send you some. np. edit: and as the big stack isnt forging at the moment it should be quite easy to forge now. edit2: if you want to run a 24/7 vps you will obv get a good chunk
|
|
|
|
BigBoom3599
|
|
September 03, 2016, 06:38:40 PM |
|
Maybe for the next version of the testnet there should be a better to distribute XELs, because only a couple of people are able to forge atm.
just post your address and we send you some. np. edit: and as the big stack isnt forging at the moment it should be quite easy to forge now. edit2: if you want to run a 24/7 vps you will obv get a good chunk XEL-XD24-CTKL-DT3K-DGF25 here it is
|
|
|
|
unvoid
|
|
September 03, 2016, 06:49:32 PM |
|
Maybe for the next version of the testnet there should be a better to distribute XELs, because only a couple of people are able to forge atm.
There is no problem with distribution. Main problem here is that no one who is willing to run full 24/7 node is asking for test XEL. If you asking for test XEL and you know that you will run full node (forging), up for 24/7 let us know. @ImI will send you x10 (than normal) more coins then.
|
BTC: 1CMgHWx4wkAaAy2FfeCyPdedUExmhGhfi5 XEL: XEL-HCM8-KB6E-YFLK-8BWMF
|
|
|
|
Evil-Knievel
Legendary
Offline
Activity: 1260
Merit: 1168
|
|
September 03, 2016, 08:49:48 PM |
|
By the way, there is an old node broadcasting bad transactions and getting blacklisted frequently. An update (git pull & compile) should help @ 108.61.177.169
|
|
|
|
cryptodv
|
|
September 03, 2016, 09:15:09 PM |
|
Need help with XEL distribution, trying to contact Lannister but his PM is blocked.
|
|
|
|
Evil-Knievel
Legendary
Offline
Activity: 1260
Merit: 1168
|
|
September 03, 2016, 09:18:57 PM |
|
Need help with XEL distribution, trying to contact Lannister but his PM is blocked. https://bitmsg.meBM-2cXXoFkRtXKvV4oiJcJjBXyYBiqo8Eibmc
|
|
|
|
trader19
Legendary
Offline
Activity: 1232
Merit: 1001
|
|
September 03, 2016, 09:36:41 PM |
|
By the way, there is an old node broadcasting bad transactions and getting blacklisted frequently. An update (git pull & compile) should help @ 108.61.177.169
thx for heads up, i will update asap
|
|
|
|
cryptodv
|
|
September 03, 2016, 10:19:28 PM |
|
Need help with XEL distribution, trying to contact Lannister but his PM is blocked. https://bitmsg.meBM-2cXXoFkRtXKvV4oiJcJjBXyYBiqo8Eibmc Thank you sir!!
|
|
|
|
jupiter00000
Member
Offline
Activity: 111
Merit: 10
http://jupitertheproducer.bandcamp.com
|
|
September 03, 2016, 10:28:58 PM |
|
Any idea how to redeem XEL?
|
Twitter: @Jupiter00000
|
|
|
|