-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ERROR: AcceptToMemoryPool : nonstandard transaction: non-final
after block chain get synchronized
#272
Comments
ERROR: AcceptToMemoryPool : nonstandard transaction: non-final
after synchronized the block chainERROR: AcceptToMemoryPool : nonstandard transaction: non-final
after block chain get synchronised
ERROR: AcceptToMemoryPool : nonstandard transaction: non-final
after block chain get synchronisedERROR: AcceptToMemoryPool : nonstandard transaction: non-final
after block chain get synchronized
Hopefully one of the devs will have a suggestion. In the meantime, let me be the first to welcome you to our repo! People are very busy, so you may have to message one of the devs directly if nobody notices this posting. |
Hi Fleurer, That error is perfectly normal - it's just regular operation of the underlying bitcoin code doing its job - in this case rejecting transactions that have been relayed to it by a peer that are not valid according to your client. Your local client has a pool of transactions (the 'mempool') waiting to be mined in the next block (unconfirmed transactions) and your client can reject unconfirmed transactions from peers if it does not believe that they are valid. This can be for a number of reasons. For example if I grab a debug.log from one of my public nodes and grep I have lots of rejections from peers sending me bad transactions:
I can actually see from your log above that your client has actually banned peers for exceeding the threshold on sending you bad transactions - so it's understandable you have a number of these types of errors in your debug.log. If you are getting a
And paste the results here? Thanks :) |
@dacoinminster @zathras-crypto thank you! here is my result of
the infomation about my origin sending transaction:
result of getblockcount, while the current network block height is 340273+
regards |
Hi, The good news is that your transaction definitely went through (http://omnichest.info/lookupadd.aspx?address=1CY7n4N2RSST3F5DW894jV6tFjnni1qBzW) - since the transaction was in block 340009 and it seems your client has only parsed up to 322082 that's going to be the reason you don't currently see a balance in the 1CY7n address. Could you post the end of your mastercore log into a pastie and link it here? You mentioned you'd tried both 0.0.8 and 0.0.9 branches with the same behaviour? Thanks |
@zathras-crypto that's reasonable, i believe the mastercored would get the balance as soon as the block chain get synced after 340009.
yes, this behaviour could be reproduced both in 0.0.8 and 0.0.9 tail -100 mastercore.log: https://gist.github.com/Fleurer/ce6196f3b1217c7f43df regards |
Hey @fleurer, @zathras-crypto: I believe this issue is related to a recent OpenSSL incompatibility of Bitcoin Core and Master Core:
I pushed #274 to update to Bitcoin Core 0.9.4 which was released to handle this. |
@dexX7 wow, really appreciated! |
@dexX7 @zathras-crypto unfortunately my node still get some
as the release notes described, maybe i'd better build the mastercored with a earlier version of openssl ?
best regards |
Hmm.. @fleurer: do the tests ( It's a bit strange, I have It was mentioned to start Bitcoin/Master Core with |
@dexX7 the test_bitcoin has passed ,
the version of openssl is:
i believe it must because i didn't regards |
I hope it works this time. Please report back. :) |
hi @dexX7 , I provisioned a new patched mastercored node in 14.04, unfortunately syncing still hangs ToT... the debug.log shows:
regards |
oh, ignore me, the block chain continued syncing after seconds regards |
If all this doesn't work, I suggest the following:
Binaries are available here: It should have the following file hashes which can be confirmed here and here:
Bitcoin Core 0.9 and Master Core 0.0.9 are interchangeable to some degree, in the sense that you don't need to download the whole blockchain or reindex, but when switching back to Master Core, it's likely required to delete the MP_* folders.
To fetch, build, and test the 0.9 branch:
The 0.9 Bitcoin Core binaries linked above were build with OpenSSL 1.0.1k. |
Thanks DexX, as always great stuff here :) @fleurer just shout on Skype if I can help at all... Also quick tip, if you find yourself deleting MP_* folders too often while troubleshooting I added a (currently undocumented) startup param in 0.0.9 that will do this for you; just add Thanks |
So many useful pieces to me, really appricate for your patience help! I'll follow your advices ^ Best Regards |
My node works now after the block chain fully rebuilt, really thanks for your help! ^ ^ |
Thanks for reporting back @fleurer. Happy it worked. So you simply build with the current 0.0.9 and that was it? |
yes it is :)
|
Thank's for your answers. But I continue to see the debug log. And when i see him. there are 3 errors occured frequently in my file. can you give me the best server for socks connect? I want to give you my debug log. I'll comme back later to do this, by a direct link to download. I've three erros in my debug.log: There is a litlle copy of my debug.log: First error: 2015-03-20 07:37:20 ERROR: AcceptToMemoryPool : nonstandard transaction: non-final antother error: last errors at the end: Can you explain me this transaction error. i think that is my soscks server doesn't work? But i want to receive my bitcoin. I'm not liying because i've in my debug log: 2015-03-20 07:34:49 UpdateTip: new best=000000000000000004d34898c7be407bd7c2be4f6d685565ac5998f9ef2f3948 height=330413 log2_work=81.482899 tx=51637023 date=2014-11-17 11:58:27 progress=0.752471 cache=59967 i'm sure that i've maybe bad socks configuration...but after i configure the sosks5 server simply and work normaly, but the other errors in antother forumers told me that can be a malware who keep and invalidate transaction to your own I want to know wath do you mean exactly this error. Help me my btc Friends! Thank's for all!!! |
Hey @beliomir,
No worries here, this is perfectly fine and there is actually no error with your wallet or client, but for debug purposes the logfile contains those entries, and reports occurrences, where transactions that other peers sent do not comply with the local or global network and transaction validation policies or rules. |
bitcoin#6275 is related to this. |
A similar problem occurred on my bitcoin server and turned out to be the result of the system time being incorrect (being in the future). Resolved by installing and configuring NTP. |
Hey @dustwolf, thanks for the information! As a side note: the project moved over to OmniLayer/omnicore. |
hi mastercoin team,
i'm working on deploying a mastercored in an Ubuntu 14.04 node, but it failed with several
ERROR: AcceptToMemoryPool : nonstandard transaction: non-final
(shown in debug.log) after the block chain has been synchoronized, then block chain hangs.and
./mastercored getblockcount
always returns the same block height, while./mastercored listtransactions
and./mastercored listtransactions_MP
returns[]
, however I've already deposited some MSC into its wallet and get confirmations.it could be reproduced by the 0.0.8 and 0.0.9 branches, I tried rm -rf ~/.bitcoin/MP_* and restart again, this issue could still be reproduced :(
any suggestion?
The text was updated successfully, but these errors were encountered: