search

mastercoin-MSC / mastercore

mastercore info
mastercoin.org
MIT License
24 stars 11 forks source link

`ERROR: AcceptToMemoryPool : nonstandard transaction: non-final` after block chain get synchronized #272

Closed flaneur2020 closed 9 years ago

flaneur2020 commented 9 years ago

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?

2015-01-23 05:47:43 UpdateTip: new best=000000000000000024204a43cc69be52450b92e651530f07b8ef83e9fae8b509  height=322081  log2_work=80.793796  tx=47281965  date=2014-09-22 21:55:54 progress=0.710876
2015-01-23 05:47:46 UpdateTip: new best=00000000000000001e6da8c11a8669fa7353cb5f56d5679591b10072f49e5cd2  height=322082  log2_work=80.793884  tx=47283418  date=2014-09-22 22:26:14 progress=0.710928
2015-01-23 05:47:46 ERROR: CScriptCheck() : 971b4d9d20553ed5183e807a5aebba036599189b20a6b9a831c7f2c402654552 VerifySignature failed
2015-01-23 05:47:46 Misbehaving: 24.247.64.135:8333 (0 -> 100) BAN THRESHOLD EXCEEDED
2015-01-23 05:47:46 InvalidChainFound: invalid block=00000000000000001b02953d79004a6e9da88fd4fe8e76ca7c58d69eb85f8ad9  height=322083  log2_work=80.793972  date=2014-09-22 22:45:12
2015-01-23 05:47:46 InvalidChainFound:  current best=00000000000000001e6da8c11a8669fa7353cb5f56d5679591b10072f49e5cd2  height=322082  log2_work=80.793884  date=2014-09-22 22:26:14
2015-01-23 05:47:46 ERROR: ConnectTip() : ConnectBlock 00000000000000001b02953d79004a6e9da88fd4fe8e76ca7c58d69eb85f8ad9 failed
2015-01-23 05:47:46 InvalidChainFound: invalid block=00000000000000001b02953d79004a6e9da88fd4fe8e76ca7c58d69eb85f8ad9  height=322083  log2_work=80.793972  date=2014-09-22 22:45:12
2015-01-23 05:47:46 InvalidChainFound:  current best=00000000000000001e6da8c11a8669fa7353cb5f56d5679591b10072f49e5cd2  height=322082  log2_work=80.793884  date=2014-09-22 22:26:14
2015-01-23 05:47:46 Pre-allocating up to position 0x6000000 in blk00177.dat
2015-01-23 05:47:47 Pre-allocating up to position 0x7000000 in blk00177.dat
2015-01-23 05:47:47 Pre-allocating up to position 0x8000000 in blk00177.dat
2015-01-23 05:47:47 ProcessBlock: ACCEPTED
2015-01-23 05:47:47 ProcessBlock: ACCEPTED
2015-01-23 05:47:47 connect() to 178.213.117.52:8333 failed after select(): Connection refused (111)
2015-01-23 05:47:47 ERROR: AcceptToMemoryPool : nonstandard transaction: non-final
2015-01-23 05:47:47 ERROR: AcceptToMemoryPool : nonstandard transaction: non-final
2015-01-23 05:47:48 ProcessBlock: ACCEPTED
2015-01-23 05:47:48 ProcessBlock: ACCEPTED
2015-01-23 05:47:48 ProcessBlock: ACCEPTED
2015-01-23 05:47:48 ProcessBlock: ACCEPTED
2015-01-23 05:47:48 ProcessBlock: ACCEPTED
2015-01-23 05:47:48 ProcessBlock: ACCEPTED
2015-01-23 05:47:48 ProcessBlock: ACCEPTED
2015-01-23 05:47:48 ProcessBlock: ACCEPTED
2015-01-23 05:47:48 ERROR: AcceptToMemoryPool : nonstandard transaction: non-final
2015-01-23 05:47:48 ProcessBlock: ACCEPTED
2015-01-23 05:47:48 ProcessBlock: ACCEPTED
2015-01-23 05:47:48 ProcessBlock: ACCEPTED
2015-01-23 05:47:48 ProcessBlock: ACCEPTED
2015-01-23 05:47:48 ProcessBlock: ACCEPTED
2015-01-23 05:47:48 ProcessBlock: ACCEPTED
2015-01-23 05:47:48 ProcessBlock: ACCEPTED
2015-01-23 05:47:48 ProcessBlock: ACCEPTED
2015-01-23 05:47:48 ProcessBlock: ACCEPTED
2015-01-23 05:47:48 ProcessBlock: ACCEPTED
2015-01-23 05:47:48 ProcessBlock: ACCEPTED
2015-01-23 05:47:48 ProcessBlock: ACCEPTED
2015-01-23 05:47:48 ProcessBlock: ACCEPTED
2015-01-23 05:47:48 ProcessBlock: ACCEPTED
2015-01-23 05:47:48 ProcessBlock: ACCEPTED
2015-01-23 05:47:48 ProcessBlock: ACCEPTED
2015-01-23 05:47:48 ProcessBlock: ACCEPTED
2015-01-23 05:47:48 ProcessBlock: ACCEPTED
2015-01-23 05:47:48 ProcessBlock: ACCEPTED
2015-01-23 05:47:48 ProcessBlock: ACCEPTED
2015-01-23 05:47:48 ProcessBlock: ACCEPTED
2015-01-23 05:47:48 ProcessBlock: ACCEPTED
2015-01-23 05:47:48 ProcessBlock: ACCEPTED
2015-01-23 05:47:48 ProcessBlock: ACCEPTED
2015-01-23 05:47:48 ProcessBlock: ACCEPTED
2015-01-23 05:47:48 ProcessBlock: ACCEPTED
2015-01-23 05:47:48 ProcessBlock: ACCEPTED
2015-01-23 05:47:54 nTargetTimespan = 1209600    nActualTimespan = 1040986
2015-01-23 05:47:54 Before: 1824dbe9  000000000000000024dbe9000000000000000000000000000000000000000000
2015-01-23 05:47:54 After:  181fb893  00000000000000001fb893cd9ba8a9798687576465354243132020f0fdfecedb
2015-01-23 05:47:54 ProcessBlock: ACCEPTED
2015-01-23 05:47:54 ProcessBlock: ACCEPTED
2015-01-23 05:47:54 ProcessBlock: ACCEPTED
2015-01-23 05:47:54 ProcessBlock: ACCEPTED
2015-01-23 05:47:54 Pre-allocating up to position 0x6000000 in blk00178.dat
2015-01-23 05:47:54 ProcessBlock: ACCEPTED
2015-01-23 05:47:54 ProcessBlock: ACCEPTED
2015-01-23 05:47:54 ProcessBlock: ACCEPTED
2015-01-23 05:47:54 ProcessBlock: ACCEPTED
2015-01-23 05:47:54 ProcessBlock: ACCEPTED
2015-01-23 05:47:54 ProcessBlock: ACCEPTED
2015-01-23 05:47:54 ProcessBlock: ACCEPTED
2015-01-23 05:47:56 ResendWalletTransactions()
2015-01-23 05:50:00 ERROR: AcceptToMemoryPool : nonstandard transaction: non-final
2015-01-23 05:50:25 ERROR: AcceptToMemoryPool : nonstandard transaction: non-final
2015-01-23 05:52:01 ERROR: AcceptToMemoryPool : nonstandard transaction: non-final
2015-01-23 05:52:25 ERROR: AcceptToMemoryPool : nonstandard transaction: non-final
2015-01-23 05:54:21 ProcessBlock: ORPHAN BLOCK 106, prev=00000000000000001008057f0a87ef5ee69312c5361ad374856b6b186eed0337
2015-01-23 05:54:25 ERROR: AcceptToMemoryPool : nonstandard transaction: non-final
2015-01-23 06:00:03 ERROR: AcceptToMemoryPool : nonstandard transaction: non-final
2015-01-23 06:02:02 ERROR: AcceptToMemoryPool : nonstandard transaction: non-final
2015-01-23 06:03:43 ERROR: CheckTransaction() : vin empty
2015-01-23 06:03:43 ERROR: AcceptToMemoryPool: : CheckTransaction failed
2015-01-23 06:03:43 Misbehaving: 144.76.64.109:8333 (10 -> 20)
2015-01-23 06:04:02 ERROR: AcceptToMemoryPool : nonstandard transaction: non-final
2015-01-23 06:06:02 ERROR: AcceptToMemoryPool : nonstandard transaction: non-final
2015-01-23 06:08:02 ERROR: AcceptToMemoryPool : nonstandard transaction: non-final
2015-01-23 06:10:02 ERROR: AcceptToMemoryPool : nonstandard transaction: non-final
2015-01-23 06:12:02 ERROR: AcceptToMemoryPool : nonstandard transaction: non-final
2015-01-23 06:13:23 ProcessBlock: ORPHAN BLOCK 107, prev=00000000000000000c52bb331e4800f7903eb67b655a648024648bdf31032dfa
2015-01-23 06:26:53 ERROR: AcceptToMemoryPool : nonstandard transaction: non-final
2015-01-23 06:28:52 ERROR: AcceptToMemoryPool : nonstandard transaction: non-final
2015-01-23 06:30:52 ERROR: AcceptToMemoryPool : nonstandard transaction: non-final
2015-01-23 06:32:52 ERROR: AcceptToMemoryPool : nonstandard transaction: non-final
2015-01-23 06:34:03 ProcessBlock: ORPHAN BLOCK 108, prev=0000000000000000125a73410b378ff91ffcd2023c50e2d63c2b4b39871d1d6e
2015-01-23 06:34:52 ERROR: AcceptToMemoryPool : nonstandard transaction: non-final
2015-01-23 06:36:52 ERROR: AcceptToMemoryPool : nonstandard transaction: non-final
dacoinminster commented 9 years ago

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.

zathras-crypto commented 9 years ago

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:

ERROR: AcceptToMemoryPool : nonstandard transaction: dust
ERROR: AcceptToMemoryPool : inputs already spent
ERROR: AcceptToMemoryPool : free transaction rejected by rate limiter
ERROR: AcceptToMemoryPool : ConnectInputs failed 
ERROR: AcceptToMemoryPool : nonstandard transaction: non-final

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 [] response from the RPC server then the client isn't frozen - could we start off with something simple? Once you've started up can you please run the following calls:

getbalance_MP the_address_you_mentioned_you_had_deposited_MSC_too 1 getbalance_MP 1EXoDusjGwvnjZUyKkxZ4UHEf77z6A5S4P 1

And paste the results here?

Thanks :) Z

flaneur2020 commented 9 years ago

@dacoinminster @zathras-crypto

thank you!

here is my result of getbalance_MP the_address_you_mentioned_you_had_deposited_MSC_too 1, and getbalance_MP 1EXoDusjGwvnjZUyKkxZ4UHEf77z6A5S4P 1

mastercoin@mmastercoind:~$ ./mastercored getbalance_MP 1CY7n4N2RSST3F5DW894jV6tFjnni1qBzW 1
{
    "balance" : "0.00000000",
    "reserved" : "0.00000000"
}
mastercoin@mmastercoind:~$ ./mastercored getbalance_MP 1EXoDusjGwvnjZUyKkxZ4UHEf77z6A5S4P 1
{
    "balance" : "13413.55784478",
    "reserved" : "0.00000000"
}

the infomation about my origin sending transaction:

    {
        "txid" : "130fa87534a8d6b8453f425275d54ebf6922522363889b0ba72a2eca74f6c0e7",
        "sendingaddress" : "1MDZkSC5ErMVBYtH6eDvhY81QEg5CtUviD",
        "referenceaddress" : "1CY7n4N2RSST3F5DW894jV6tFjnni1qBzW",
        "ismine" : true,
        "confirmations" : 263,
        "fee" : 0.00010000,
        "blocktime" : 1421904903,
        "type" : "Simple Send",
        "propertyid" : 1,
        "divisible" : true,
        "amount" : "10.00000000",
        "valid" : true
    },

result of getblockcount, while the current network block height is 340273+

mastercoin@mmastercoind:~$ ./mastercored getblockcount
322082

regards

zathras-crypto commented 9 years ago

Hi, Thanks. It does sound like your client has gotten hung up somewhere during parsing. I'd like to get to the bottom of how that has occurred.

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? tail -100 ~/.bitcoin/mastercore.log Then do the same with the end of your bitcoin log? tail -100 ~/.bitcoin/debug.log

You mentioned you'd tried both 0.0.8 and 0.0.9 branches with the same behaviour?

Thanks Z

flaneur2020 commented 9 years ago

@zathras-crypto that's reasonable, i believe the mastercored would get the balance as soon as the block chain get synced after 340009.

You mentioned you'd tried both 0.0.8 and 0.0.9 branches with the same behaviour?

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 tail -100 debug.log: https://gist.github.com/Fleurer/8e61153fad5a5e0147d2

regards

dexX7 commented 9 years ago

Hey @Fleurer, @zathras-crypto:

I believe this issue is related to a recent OpenSSL incompatibility of Bitcoin Core and Master Core:

I pushed https://github.com/mastercoin-MSC/mastercore/pull/274 to update to Bitcoin Core 0.9.4 which was released to handle this.

flaneur2020 commented 9 years ago

@dexX7 wow, really appreciated!

flaneur2020 commented 9 years ago

@dexX7 @zathras-crypto unfortunately my node still get some ERROR: AcceptToMemoryPool errors after patched #274 manually, mastercored still hangs at synchronising :(

mastercoin2@mmastercoind:~$ tail -f .bitcoin/debug.log
2015-01-25 14:28:27 ProcessBlock: ORPHAN BLOCK 300, prev=000000000000002470804a75f46e294a0d109b8f63ed5d8aa083a3596691540f
2015-01-25 14:28:28 ProcessBlock: ORPHAN BLOCK 301, prev=00000000000000000ff2c16136c7ead3a3d82ca1ff7ad654cde1ede1b8bc75d7
2015-01-25 14:30:25 ERROR: AcceptToMemoryPool : nonstandard transaction: non-final
2015-01-25 14:32:24 ERROR: AcceptToMemoryPool : nonstandard transaction: non-final
2015-01-25 14:32:41 ProcessBlock: ORPHAN BLOCK 302, prev=000000000000000013e84d8530e034433a4e2fef37a99849a0b9c322c99fe01b
2015-01-25 14:34:24 ERROR: AcceptToMemoryPool : nonstandard transaction: non-final
2015-01-25 14:36:24 ERROR: AcceptToMemoryPool : nonstandard transaction: non-final
2015-01-25 14:38:18 ERROR: AcceptToMemoryPool : nonstandard transaction: non-final
2015-01-25 14:38:24 ERROR: AcceptToMemoryPool : nonstandard transaction: non-final
2015-01-25 14:40:17 ERROR: AcceptToMemoryPool : nonstandard transaction: non-final
2015-01-25 14:40:24 ERROR: AcceptToMemoryPool : nonstandard transaction: non-final
mastercoin2@mmastercoind:~$ ./mastercored --help | head
Bitcoin Core Daemon version v0.9.4.0-a099a24-dirty-beta

Usage:
  bitcoind [options]                     Start Bitcoin Core Daemon
Usage (deprecated, use bitcoin-cli):
  bitcoind [options] <command> [params]  Send command to Bitcoin Core
  bitcoind [options] help                List commands
  bitcoind [options] help <command>      Get help for a command

as the release notes described, maybe i'd better build the mastercored with a earlier version of openssl ?


OpenSSL Warning
================
OpenSSL 1.0.0p / 1.0.1k was recently released and is being pushed out by
various operating system maintainers. Review by Gregory Maxwell determined that
this update is incompatible with the Bitcoin system and could lead to consensus
forks.

Bitcoin Core released binaries from https://bitcoin.org are unaffected,
as are any built with the gitian deterministic build system.

However, if you are running either
- The Ubuntu PPA from https://launchpad.net/~bitcoin/+archive/ubuntu/bitcoin
- A third-party or self-compiled Bitcoin Core

upgrade to Bitcoin Core 0.9.4, which includes a workaround, **before** updating
OpenSSL.

The incompatibility is due to the OpenSSL update changing the
behavior of ECDSA validation to reject any signature which is
not encoded in a very rigid manner. This was a result of
OpenSSL's change for CVE-2014-8275 "Certificate fingerprints
can be modified".

best regards

dexX7 commented 9 years ago

Hmm.. @Fleurer: do the tests (./src/test/test_bitcoin) run without problem now? Can you please post the output of openssl version?

It's a bit strange, I have OpenSSL 1.0.1f on my system, which was not listed as affected, but appears to be affected, which I can confirm. The patch solved the issue with the tests, so I think it should be fine.

It was mentioned to start Bitcoin/Master Core with -reindex after patching. Did you test this?

flaneur2020 commented 9 years ago

@dexX7 the test_bitcoin has passed , 

mastercoin@mmastercore2:~$ mastercore/src/test/test_bitcoin
mastercore_init(), line 2434, file: mastercore.cpp
CMPTradeList(): OK, line 376, file: mastercore.h
CMPSTOList(): OK, line 333, file: mastercore.h
CMPTxList(): OK, line 433, file: mastercore.h
[Snapshot] Exodus balance: 0.00000000
[Initialized] Exodus balance: 0.00000000
Running 132 test cases...

*** No errors detected

the version of openssl is:

mastercoin@mmastercore2:~$ apt-cache madison openssl
   openssl | 1.0.1f-1ubuntu2.8 | http://gce.clouds.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
   openssl | 1.0.1f-1ubuntu2.8 | http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages
   openssl | 1.0.1f-1ubuntu2 | http://gce.clouds.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
   openssl | 1.0.1f-1ubuntu2 | http://gce.clouds.archive.ubuntu.com/ubuntu/ trusty/main Sources
   openssl | 1.0.1f-1ubuntu2.8 | http://gce.clouds.archive.ubuntu.com/ubuntu/ trusty-updates/main Sources
   openssl | 1.0.1f-1ubuntu2.8 | http://security.ubuntu.com/ubuntu/ trusty-security/main Sources

i believe it must because i didn't -reindex after rebuild, let me try it!

regards

dexX7 commented 9 years ago

I hope it works this time. Please report back. :)

flaneur2020 commented 9 years ago

hi @dexX7 ,

I provisioned a new patched mastercored node in 14.04, unfortunately syncing still hangs ToT... the debug.log shows:

2015-01-26 04:19:52 Bitcoin version v0.9.4.0-a099a24-dirty-beta (2015-01-08 15:55:24 -0500)
2015-01-26 04:19:52 Using OpenSSL version OpenSSL 1.0.1f 6 Jan 2014
2015-01-26 04:19:52 Using BerkeleyDB version Berkeley DB 5.3.28: (September  9, 2013)
2015-01-26 04:19:52 Default data directory /home/mastercoin/.bitcoin
2015-01-26 04:19:52 Using data directory /home/mastercoin/.bitcoin
2015-01-26 04:19:52 Using at most 125 connections (1024 file descriptors available)
2015-01-26 04:19:52 Using wallet wallet.dat
2015-01-26 04:19:52 init message: Verifying wallet...
...
...
2015-01-26 04:28:19 ERROR: AcceptToMemoryPool : nonstandard transaction: non-final
2015-01-26 04:28:22 ProcessBlock: ORPHAN BLOCK 700, prev=00000000000000260d41405dec11a7b354fd78c8e72aa6f43a6944bae4c83415
2015-01-26 04:28:23 ProcessBlock: ORPHAN BLOCK 701, prev=0000000000000037a7526a1846d2dd7e6b66e92973b23610dc9995f5675ea87d
2015-01-26 04:28:24 ProcessBlock: ORPHAN BLOCK 702, prev=00000000000000961728f7ee9ca7cdd9747568f4c52e42de41bba6d2163ead1d
2015-01-26 04:28:25 ProcessBlock: ORPHAN BLOCK 703, prev=0000000000000042ba31ebe82ccf2cea284ad99fc6d1187b91b1d62abbe42266
2015-01-26 04:28:27 ProcessBlock: ORPHAN BLOCK 704, prev=000000000000006459a07d09366eb38935ae302310d5e7eda8f59590a8667b89
2015-01-26 04:28:28 ProcessBlock: ORPHAN BLOCK 705, prev=00000000000000055429dc3eb16f218f7e42cbe512c2e1530421d43073bb2b79
2015-01-26 04:28:28 ProcessBlock: ORPHAN BLOCK 706, prev=000000000000004993f2e7f6b5eb82329edd0cad2c876d68f5317573acba5d8c
2015-01-26 04:28:29 ProcessBlock: ORPHAN BLOCK 707, prev=000000000000007e3993eb6fb656487cefa84f24d38b693304607c2cff0a3cb8
2015-01-26 04:28:30 ProcessBlock: ORPHAN BLOCK 708, prev=0000000000000080d16a64589136617bd956ddd95e26679ec42baa00a102fd89
2015-01-26 04:28:31 ProcessBlock: ORPHAN BLOCK 709, prev=000000000000009fda603b7037a16f920a956317b53f3c3044424b62c7bd5dbf
2015-01-26 04:28:31 ProcessBlock: ORPHAN BLOCK 710, prev=0000000000000031b9f4a3881484adb9c73999925b0f7bf659210511c41a0ebd
2015-01-26 04:28:32 Misbehaving: 90.193.194.78:8333 (0 -> 10)
2015-01-26 04:28:32 Misbehaving: 90.193.194.78:8333 (10 -> 20)
2015-01-26 04:28:32 Misbehaving: 90.193.194.78:8333 (20 -> 30)
2015-01-26 04:28:32 Misbehaving: 90.193.194.78:8333 (30 -> 40)
2015-01-26 04:28:32 Misbehaving: 90.193.194.78:8333 (40 -> 50)
2015-01-26 04:28:32 Misbehaving: 90.193.194.78:8333 (50 -> 60)
2015-01-26 04:28:32 Misbehaving: 90.193.194.78:8333 (60 -> 70)
2015-01-26 04:28:32 Misbehaving: 90.193.194.78:8333 (70 -> 80)
2015-01-26 04:28:32 Misbehaving: 90.193.194.78:8333 (80 -> 90)
2015-01-26 04:28:32 Misbehaving: 90.193.194.78:8333 (90 -> 100) BAN THRESHOLD EXCEEDED
2015-01-26 04:28:32 Misbehaving: 90.193.194.78:8333 (100 -> 110) BAN THRESHOLD EXCEEDED
2015-01-26 04:28:32 Misbehaving: 90.193.194.78:8333 (110 -> 120) BAN THRESHOLD EXCEEDED
2015-01-26 04:28:32 receive version message: /Satoshi:0.8.6/: version 70001, blocks=340512, us=107.167.181.251:38844, them=82.179.225.118:8333, peer=82.179.225.118:8333
2015-01-26 04:28:32 Added time data, samples 10, offset +0 (+0 minutes)
2015-01-26 04:29:18 ERROR: AcceptToMemoryPool : nonstandard transaction: non-final
2015-01-26 04:30:07 ERROR: AcceptToMemoryPool : nonstandard transaction: non-final
2015-01-26 04:30:19 ERROR: AcceptToMemoryPool : nonstandard transaction: non-final
2015-01-26 04:31:18 ERROR: AcceptToMemoryPool : nonstandard transaction: non-final
2015-01-26 04:32:07 ERROR: AcceptToMemoryPool : nonstandard transaction: non-final
2015-01-26 04:32:19 ERROR: AcceptToMemoryPool : nonstandard transaction: non-final
2015-01-26 04:33:18 ERROR: AcceptToMemoryPool : nonstandard transaction: non-final

regards

flaneur2020 commented 9 years ago

oh, ignore me, the block chain continued syncing after seconds

regards

dexX7 commented 9 years ago

If all this doesn't work, I suggest the following:

1) Check, if an untouched Bitcoin Core 0.9.4 version, build with another OpenSSL version works:

Binaries are available here: http://luke.dashjr.org/programs/bitcoin/files/bitcoind/0.9.4/

It should have the following file hashes which can be confirmed here and here:

~/Downloads/bitcoin-0.9.4/bin$ sha256sum bitcoind bitcoin-cli bitcoin-qt
7565d80fef41fd06281d2b01f14de12da145349bb5678827ccf57734e8b172ec  bitcoind
d03e778ead3ce9b37fae0b29ec2bd4fae9fce7e3d033697b79867ba5be45fa2f  bitcoin-cli
0ec41e9c77ae2fe9c005ce304ecac713531e51a60621d51fb312824ae5f85009  bitcoin-qt

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.

2) Assuming it works, let's check if a self build of Bitcoin Core 0.9.4 also works:

To fetch, build, and test the 0.9 branch:

git clone -b 0.9 https://github.com/bitcoin/bitcoin.git bitcoin-0.9
cd bitcoin-0.9/src
./autogen.sh
./configure
make
make check

3) Assuming it does not work, then there probably no way around getting another OpenSSL version.

The 0.9 Bitcoin Core binaries linked above were build with OpenSSL 1.0.1k.

zathras-crypto commented 9 years ago

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 --startclean to your params at startup it'll give you a fresh set of MP* folders.

Thanks Z

flaneur2020 commented 9 years ago

@dexX7 @zathras-crypto

So many useful pieces to me, really appricate for your patience help! I'll follow your advices ^

Best Regards

flaneur2020 commented 9 years ago

@dexX7 @zathras-crypto

My node works now after the block chain fully rebuilt, really thanks for your help! ^ ^

dexX7 commented 9 years ago

Thanks for reporting back @Fleurer. Happy it worked. So you simply build with the current 0.0.9 and that was it?

flaneur2020 commented 9 years ago

yes it is :) On Jan 30, 2015 10:37 PM, "dexX7" notifications@github.com wrote:

Thanks for reporting back @Fleurer https://github.com/Fleurer. Happy it worked. So you simply build with the current 0.0.9 and that was it?

Reply to this email directly or view it on GitHub https://github.com/mastercoin-MSC/mastercore/issues/272#issuecomment-72210147 .

beliomir commented 9 years ago

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 2015-03-20 07:37:22 ERROR: AcceptToMemoryPool : nonstandard transaction: non-final

antother error: socket recv error Une connexion existante a dû être fermée par l’hôte distant. (10054)

last errors at the end: 2015-03-22 03:35:21 ERROR: AcceptToMemoryPool : nonstandard transaction: dust 2015-03-22 03:35:21 ERROR: AcceptToMemoryPool : nonstandard transaction: dust 2015-03-22 03:35:22 ERROR: AcceptToMemoryPool : nonstandard transaction: dust

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 2015-03-20 07:34:53 UpdateTip: new best=0000000000000000180d3d831095b8d5fd8e280acf2e9e272ed19513f76bca5d height=330414 log2_work=81.482972 tx=51637853 date=2014-11-17 12:17:33 progress=0.752498 cache=61391 2015-03-20 07:34:54 UpdateTip: new best=00000000000000000fef9441006aea2927eb3bc485f1d4a576368b48df724b09 height=330415 log2_work=81.483044 tx=51638055 date=2014-11-17 12:17:44 progress=0.752500 cache=61927 2015-03-20 07:34:58 UpdateTip: new best=000000000000000005d1b8afa0849bc620ded33f5e02c01c7da11b8b0ab947d4 height=330416 log2_work=81.483117 tx=51639093 date=2014-11-17 12:34:17 progress=0.752526 cache=63631 2015-03-20 07:34:59 UpdateTip: new best=0000000000000000086e8edbac091f96b99e7a979f8238076245261baebfa8de height=330417 log2_work=81.48319 tx=51639415 date=2014-11-17 12:41:36 progress=0.752536 cache=64156

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 Really?

I want to know wath do you mean exactly this error.

Help me my btc Friends!

Thank's for all!!!

dexX7 commented 9 years ago

Hey @beliomir,

2015-03-20 07:37:20 ERROR: AcceptToMemoryPool : nonstandard transaction: non-final

socket recv error Une connexion existante a dû être fermée par l’hôte distant. (10054)

2015-03-22 03:35:21 ERROR: AcceptToMemoryPool : nonstandard transaction: dust

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.

rebroad commented 9 years ago

https://github.com/bitcoin/bitcoin/issues/6275 is related to this.

dustwolf commented 9 years ago

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.

dexX7 commented 9 years ago

Hey @dustwolf,

thanks for the information! As a side note: the project moved over to OmniLayer/omnicore.