Bitcoin Forum>Bitcoin>Bitcoin Technical Support
Author

Topic: Bitcoin Core 11.2.0 same Starting and Sync Height on new install (Read 1380 times)

achow101
staff
Activity: 3458
Merit: 6793
Just writing some code
Bitcoin Core 11.2.0 same Starting and Sync Height on new install
November 24, 2015, 09:21:15 AM
#12
Quote from: overcoin on November 23, 2015, 05:25:21 PM
Quote from: shorena on November 23, 2015, 04:28:49 PM
Its related to the malleability attack[1]. Newer version no longer relay modified transactions to lower the impact of the attack. Once all nodes are updated it will be impossible.
That was helpful too. Thanks, shorena.

I'm observing such a behavior for the first time. For instance as we speak, for 20 minutes there wasn't a single block synced. After that peer list was reset entirely and slowly populated again. Took another 5 minutes during which time 4 peers were disconnected. Took another 10 minutes to have just 5 more blocks synced from the new peers before they stopped responding. Now awaiting the peer list reset again... At such speed blockchain syncing can take more than a week. Definitely there is something wrong.
Can you provide us the debug.log from the time frame of that behavior?
n3rvi0zz0
sr. member
Activity: 289
Merit: 250
Re: Bitcoin Core 11.2.0 same Starting and Sync Height on new install
November 24, 2015, 02:40:53 AM
#11
i told u in my last post Roll Eyes Roll Eyes
overcoin
newbie
Activity: 53
Merit: 0
Re: Bitcoin Core 11.2.0 same Starting and Sync Height on new install
November 23, 2015, 05:25:21 PM
#10
Quote from: shorena on November 23, 2015, 04:28:49 PM
Its related to the malleability attack[1]. Newer version no longer relay modified transactions to lower the impact of the attack. Once all nodes are updated it will be impossible.
That was helpful too. Thanks, shorena.

I'm observing such a behavior for the first time. For instance as we speak, for 20 minutes there wasn't a single block synced. After that peer list was reset entirely and slowly populated again. Took another 5 minutes during which time 4 peers were disconnected. Took another 10 minutes to have just 5 more blocks synced from the new peers before they stopped responding. Now awaiting the peer list reset again... At such speed blockchain syncing can take more than a week. Definitely there is something wrong.
n3rvi0zz0
sr. member
Activity: 289
Merit: 250
Re: Bitcoin Core 11.2.0 same Starting and Sync Height on new install
November 23, 2015, 05:04:57 PM
#9
he has the same issue than me Im running 11.2 in Ubuntu 32bits (VM) and took almost a week to sync

just 8 peers and long periods without load new blocks.

No is normal i use to sync in 48h with another version 0.9 0.10

and just 2 lines of connectivity from the GUI normally are in green
shorena
copper member
Activity: 1498
Merit: 1528
No I dont escrow anymore.
Re: Bitcoin Core 11.2.0 same Starting and Sync Height on new install
November 23, 2015, 04:28:49 PM
#8
Quote from: overcoin on November 23, 2015, 04:24:11 PM

Quote from: achow101 on November 23, 2015, 03:42:43 PM
The root certificates are for BIP70 payment requests which can be signed with an X.509 certificate. Those certificates are SSL certificates, and they are signed by the root certificates. Specifically, I think the root certificates are just the ones that come with your OS.
Yet another security concern. Didn't know that. Thanks.

If you dont use BIP70 payments, e.g. dont click the link on a bitpay payment, bust just copy the data yourself it does not affect you AFAIK.

Quote from: overcoin on November 23, 2015, 04:24:11 PM
Any idea what is this 'Non-canonical signature' about and why 'S value is unnecessarily high'?

Its related to the malleability attack[1]. Newer version no longer relay modified transactions to lower the impact of the attack. Once all nodes are updated it will be impossible.

[1] https://en.bitcoin.it/wiki/Transaction_Malleability
overcoin
newbie
Activity: 53
Merit: 0
Re: Bitcoin Core 11.2.0 same Starting and Sync Height on new install
November 23, 2015, 04:24:11 PM
#7

Quote from: achow101 on November 23, 2015, 03:42:43 PM
The root certificates are for BIP70 payment requests which can be signed with an X.509 certificate. Those certificates are SSL certificates, and they are signed by the root certificates. Specifically, I think the root certificates are just the ones that come with your OS.
Yet another security concern. Didn't know that. Thanks.

Any idea what is this 'Non-canonical signature' about and why 'S value is unnecessarily high'?
achow101
staff
Activity: 3458
Merit: 6793
Just writing some code
Re: Bitcoin Core 11.2.0 same Starting and Sync Height on new install
November 23, 2015, 03:42:43 PM
#6
Quote from: overcoin on November 23, 2015, 03:34:23 PM
Quote from: achow101 on November 23, 2015, 03:28:40 PM
How many peers are you connected to? That will affect your syncing speed.


8 peers
Then that is fine. You should still be syncing. Open the debug window and in the Information tab will show you how many blocks you have already synced. Compare that to the number on a block explorer and you will know how many blocks are left. The number should continue to increase as you sync, but it may not be at a steady rate.

Quote from: overcoin on November 23, 2015, 03:34:23 PM
I'm interested in these lines:

Quote
2015-11-23 19:10:41 ERROR: CScriptCheck(): 8f0d3821b750cb044832f54ea3c48841531ee0b4a06c5f9d0b91be82c3d68908:0 VerifySignature failed: Non-canonical signature: S value is unnecessarily high
2015-11-23 19:10:41 ERROR: AcceptToMemoryPool: ConnectInputs failed 8f0d3821b750cb044832f54ea3c48841531ee0b4a06c5f9d0b91be82c3d68908
2015-11-23 19:10:41 AddToWallet 6191dd33dc2ede6b094222a9c2ee07e5948dd87e477d9698463b5f5da46d30a8 
2015-11-23 19:10:42 GUI: PaymentServer::LoadRootCAs: Loaded  170  root certificates
2015-11-23 19:10:44 connect() to 68.190.172.229:8333 failed after select(): Connection refused (111)

What root certificates I'm loading?
The root certificates are for BIP70 payment requests which can be signed with an X.509 certificate. Those certificates are SSL certificates, and they are signed by the root certificates. Specifically, I think the root certificates are just the ones that come with your OS.
overcoin
newbie
Activity: 53
Merit: 0
Re: Bitcoin Core 11.2.0 same Starting and Sync Height on new install
November 23, 2015, 03:34:23 PM
#5
Quote from: achow101 on November 23, 2015, 03:28:40 PM
How many peers are you connected to? That will affect your syncing speed.


8 peers

I'm interested in these lines:

Quote
2015-11-23 19:10:41 ERROR: CScriptCheck(): 8f0d3821b750cb044832f54ea3c48841531ee0b4a06c5f9d0b91be82c3d68908:0 VerifySignature failed: Non-canonical signature: S value is unnecessarily high
2015-11-23 19:10:41 ERROR: AcceptToMemoryPool: ConnectInputs failed 8f0d3821b750cb044832f54ea3c48841531ee0b4a06c5f9d0b91be82c3d68908
2015-11-23 19:10:41 AddToWallet 6191dd33dc2ede6b094222a9c2ee07e5948dd87e477d9698463b5f5da46d30a8 
2015-11-23 19:10:42 GUI: PaymentServer::LoadRootCAs: Loaded  170  root certificates
2015-11-23 19:10:44 connect() to 68.190.172.229:8333 failed after select(): Connection refused (111)

What root certificates I'm loading?
achow101
staff
Activity: 3458
Merit: 6793
Just writing some code
Re: Bitcoin Core 11.2.0 same Starting and Sync Height on new install
November 23, 2015, 03:28:40 PM
#4
Nothing is wrong, it looks like. Your debug.log shows that it is still syncing.

Where are you seeing the starting height and sync height? If its in the peers tab, then ignore it. Those numbers are for the peers you have connected to and their data, not yours.

How many peers are you connected to? That will affect your syncing speed.
overcoin
newbie
Activity: 53
Merit: 0
Re: Bitcoin Core 11.2.0 same Starting and Sync Height on new install
November 23, 2015, 03:16:58 PM
#3
Quote from: achow101 on November 23, 2015, 03:01:28 PM
Can you post the debug.log?
Deleted part of it as is too long

Quote
2015-11-23 19:09:31 Bitcoin version v0.11.2.0-g7e27892 (Tue, 10 Nov 2015 14:46:18 +0100)
2015-11-23 19:09:31 Using OpenSSL version OpenSSL 1.0.1f 6 Jan 2014
2015-11-23 19:09:31 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2015-11-23 19:09:31 Default data directory /home/my-home-dir/.bitcoin
2015-11-23 19:09:31 Using data directory /home/my-home-dir/.bitcoin
2015-11-23 19:09:31 Using config file /home/my-home-dir/.bitcoin/bitcoin.conf
2015-11-23 19:09:31 Using at most 125 connections (1024 file descriptors available)
2015-11-23 19:09:31 Using 4 threads for script verification
2015-11-23 19:09:31 Using wallet wallet.dat
2015-11-23 19:09:31 scheduler thread start
2015-11-23 19:09:31 init message: Verifying wallet...
2015-11-23 19:09:31 CDBEnv::Open: LogDir=/home/my-home-dir/.bitcoin/database ErrorFile=/home/my-home-dir/.bitcoin/db.log
2015-11-23 19:09:31 Bound to [::]:8333
2015-11-23 19:09:31 Bound to 0.0.0.0:8333
2015-11-23 19:09:31 Cache configuration:
2015-11-23 19:09:31 * Using 2.0MiB for block index database
2015-11-23 19:09:31 * Using 32.5MiB for chain state database
2015-11-23 19:09:31 * Using 65.5MiB for in-memory UTXO set
2015-11-23 19:09:31 init message: Loading block index...
2015-11-23 19:09:31 Opening LevelDB in /home/my-home-dir/.bitcoin/blocks/index
2015-11-23 19:09:31 Opened LevelDB successfully
2015-11-23 19:09:31 Opening LevelDB in /home/my-home-dir/.bitcoin/chainstate
2015-11-23 19:09:33 Opened LevelDB successfully
2015-11-23 19:09:45 LoadBlockIndexDB: last block file = 239
2015-11-23 19:09:45 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=95, size=40365754, heights=346215...346382, time=2015-03-05...2015-03-06)
2015-11-23 19:09:45 Checking all blk files are present...
2015-11-23 19:09:45 LoadBlockIndexDB: transaction index disabled
2015-11-23 19:09:45 LoadBlockIndexDB: hashBestChain=00000000000000000bdfb94076bf7f739cf3daa271b08094639beb7647bf9bc8 height=346321 date=2015-03-05 21:35:36 progress=0.671812
2015-11-23 19:09:45 init message: Verifying blocks...
2015-11-23 19:09:45 Verifying last 288 blocks at level 3
2015-11-23 19:09:56 No coin database inconsistencies in last 5 blocks (2641 transactions)
2015-11-23 19:09:56  block index           24582ms
2015-11-23 19:09:56 init message: Loading wallet...
2015-11-23 19:09:56 nFileVersion = 110200
2015-11-23 19:09:56 Keys: 0 plaintext, 247 encrypted, 11 w/ metadata, 247 total
2015-11-23 19:09:56  wallet                  116ms
2015-11-23 19:09:56 init message: Rescanning...
2015-11-23 19:09:56 Rescanning last 161 blocks (from block 346160)...
2015-11-23 19:09:59 AddToWallet 78ab3540157c578c304e411f5a8530a3343bdfe39cf7c20025c78811a7942cdf  
2015-11-23 19:10:00  rescan                 4536ms
2015-11-23 19:10:00 init message: Activating best chain...
...

2015-11-23 19:10:41 mapBlockIndex.size() = 385004
2015-11-23 19:10:41 nBestHeight = 346331
2015-11-23 19:10:41 setKeyPool.size() = 100
2015-11-23 19:10:41 mapWallet.size() = 147
2015-11-23 19:10:41 mapAddressBook.size() = 43
2015-11-23 19:10:41 init message: Loading addresses...
2015-11-23 19:10:41 Loaded 494 addresses from peers.dat  8ms
2015-11-23 19:10:41 dnsseed thread start
2015-11-23 19:10:41 net thread start
2015-11-23 19:10:41 addcon thread start
2015-11-23 19:10:41 opencon thread start
2015-11-23 19:10:41 msghand thread start
2015-11-23 19:10:41 init message: Done loading
2015-11-23 19:10:41 AddToWallet 0f471799390897155b188dc86bd6ed4675e98091aed64504f0df30f37db67a60  
2015-11-23 19:10:41 ERROR: CScriptCheck(): 8f0d3821b750cb044832f54ea3c48841531ee0b4a06c5f9d0b91be82c3d68908:0 VerifySignature failed: Non-canonical signature: S value is unnecessarily high
2015-11-23 19:10:41 ERROR: AcceptToMemoryPool: ConnectInputs failed 8f0d3821b750cb044832f54ea3c48841531ee0b4a06c5f9d0b91be82c3d68908
2015-11-23 19:10:41 AddToWallet 6191dd33dc2ede6b094222a9c2ee07e5948dd87e477d9698463b5f5da46d30a8  
2015-11-23 19:10:42 GUI: PaymentServer::LoadRootCAs: Loaded  170  root certificates
2015-11-23 19:10:44 connect() to 68.190.172.229:8333 failed after select(): Connection refused (111)
2015-11-23 19:10:45 receive version message: /Satoshi:0.10.1/: version 70003, blocks=385005, us=77.238.70.145:26278, peer=2
2015-11-23 19:10:45 Added time data, samples 2, offset +0 (+0 minutes)
...
2015-11-23 19:10:46 UpdateTip: new best=00000000000000000994a50273b563c54cf3224acd230d1b5dbb32cd2aa0a594  height=346332
2015-11-23 19:15:10 UpdateTip: new best=000000000000000008ee6cd1e2e15480088c3e2bda47a68a8d0dcf79dcd598af  height=346398  log2_work=82.372484  tx=61567849  date=2015-03-06 09:45:03 progress=0.672523  cache=23.8MiB(7494tx)
2015-11-23 19:15:13 UpdateTip: new best=000000000000000015c7b2196f5f03fe717171e7748dc60ba823df3ec01d5079  height=346399  log2_work=82.37253  tx=61568182  date=2015-03-06 09:49:21 progress=0.672527  cache=28.6MiB(8504tx)
2015-11-23 19:15:15 UpdateTip: new best=000000000000000003880a75ca8a9730335720c7c121d4fa863f2bae4efedacb  height=346400  log2_work=82.372576  tx=61568529  date=2015-03-06 09:56:35 progress=0.672534  cache=31.1MiB(9464tx)
2015-11-23 19:15:17 UpdateTip: new best=0000000000000000128ac6d567b10d3949a7e13cf44a9c29e0f3af7534187a1e  height=346401  log2_work=82.372622  tx=61568813  date=2015-03-06 10:01:03 progress=0.672539  cache=32.4MiB(10329tx)
2015-11-23 19:15:18 Pre-allocating up to position 0x900000 in rev00239.dat
2015-11-23 19:15:18 UpdateTip: new best=000000000000000006e679325e79ee3b0a1d25f97c745d7c410267f9440ee8c2  height=346402  log2_work=82.372669  tx=61568909  date=2015-03-06 10:03:17 progress=0.672540  cache=40.1MiB(10770tx)
2015-11-23 19:15:19 UpdateTip: new best=000000000000000007e131711c20635275f181fb2a9934e9eefd616661f187d3  height=346403  log2_work=82.372715  tx=61569288  date=2015-03-06 10:11:27 progress=0.672548  cache=46.5MiB(11554tx)
2015-11-23 19:15:22 Pre-allocating up to position 0x7000000 in blk00239.dat
2015-11-23 19:15:23 ERROR: AcceptToMemoryPool: nonstandard transaction: dust
2015-11-23 19:15:26 Pre-allocating up to position 0x8000000 in blk00239.dat
2015-11-23 19:15:28 ERROR: AcceptToMemoryPool: nonstandard transaction: dust
2015-11-23 19:15:28 ERROR: AcceptToMemoryPool: nonstandard transaction: dust
2015-11-23 19:15:29 ERROR: AcceptToMemoryPool: nonstandard transaction: dust
2015-11-23 19:15:29 ERROR: AcceptToMemoryPool: nonstandard transaction: dust
2015-11-23 19:15:29 Leaving block file 240: CBlockFileInfo(blocks=0, size=0, heights=0...0, time=1970-01-01...1970-01-01)
2015-11-23 19:15:30 Pre-allocating up to position 0x1000000 in blk00240.dat
2015-11-23 19:15:33 ERROR: AcceptToMemoryPool: nonstandard transaction: dust
2015-11-23 19:15:33 Pre-allocating up to position 0x2000000 in blk00240.dat
2015-11-23 19:15:38 Pre-allocating up to position 0x3000000 in blk00240.dat
2015-11-23 19:15:42 Pre-allocating up to position 0x4000000 in blk00240.dat
2015-11-23 19:15:47 Pre-allocating up to position 0x5000000 in blk00240.dat
2015-11-23 19:15:52 Pre-allocating up to position 0x6000000 in blk00240.dat
2015-11-23 19:15:56 Pre-allocating up to position 0x7000000 in blk00240.dat
2015-11-23 19:16:01 Pre-allocating up to position 0x8000000 in blk00240.dat
2015-11-23 19:16:06 Leaving block file 241: CBlockFileInfo(blocks=0, size=0, heights=0...0, time=1970-01-01...1970-01-01)
2015-11-23 19:16:06 Pre-allocating up to position 0x1000000 in blk00241.dat
2015-11-23 19:16:10 Pre-allocating up to position 0x2000000 in blk00241.dat
2015-11-23 19:16:15 Pre-allocating up to position 0x3000000 in blk00241.dat
2015-11-23 19:16:19 Pre-allocating up to position 0x4000000 in blk00241.dat
2015-11-23 19:16:24 Pre-allocating up to position 0x5000000 in blk00241.dat
2015-11-23 19:16:29 Pre-allocating up to position 0x6000000 in blk00241.dat
2015-11-23 19:16:34 Pre-allocating up to position 0x7000000 in blk00241.dat
2015-11-23 19:16:38 Pre-allocating up to position 0x8000000 in blk00241.dat
2015-11-23 19:16:43 Leaving block file 242: CBlockFileInfo(blocks=0, size=0, heights=0...0, time=1970-01-01...1970-01-01)
2015-11-23 19:16:43 Pre-allocating up to position 0x1000000 in blk00242.dat
2015-11-23 19:16:47 Pre-allocating up to position 0x2000000 in blk00242.dat
2015-11-23 19:16:52 Pre-allocating up to position 0x3000000 in blk00242.dat
2015-11-23 19:16:53 Peer=1 is stalling block download, disconnecting
2015-11-23 19:16:53 receive version message: /Satoshi:0.11.2/: version 70002, blocks=385005, us=77.238.70.145:26427, peer=9
2015-11-23 19:16:53 Added time data, samples 10, offset +0 (+0 minutes)
2015-11-23 19:16:55 Pre-allocating up to position 0x100000 in rev00242.dat
...
2015-11-23 19:21:23 UpdateTip: new best=000000000000000011187dd5d1e764e0e54bd91125fce3198fb154e2d8148789  height=346474  log2_work=82.375991  tx=61624391  date=2015-03-06 22:35:47 progress=0.673353  cache=45.7MiB(13282tx)
2015-11-23 19:21:24 Pre-allocating up to position 0x4000000 in blk00242.dat
2015-11-23 19:21:25 Peer=8 is stalling block download, disconnecting
2015-11-23 19:21:26 receive version message: /Satoshi:0.10.1/ljr:20150220/: version 70002, blocks=385005, us=77.238.70.145:26227, peer=10
2015-11-23 19:21:26 Added time data, samples 11, offset -1 (+0 minutes)
2015-11-23 19:21:26 nTimeOffset = -1  (+0 minutes)
2015-11-23 19:21:28 ERROR: AcceptToMemoryPool: nonstandard transaction: dust
2015-11-23 19:21:28 ERROR: AcceptToMemoryPool: nonstandard transaction: dust
2015-11-23 19:21:28 ERROR: AcceptToMemoryPool: nonstandard transaction: dust
2015-11-23 19:21:28 ERROR: AcceptToMemoryPool: nonstandard transaction: dust
2015-11-23 19:21:29 ERROR: AcceptToMemoryPool: nonstandard transaction: dust
2015-11-23 19:21:29 Peer=3 is stalling block download, disconnecting
2015-11-23 19:21:29 connect() to 94.23.216.205:8333 failed after select(): Connection refused (111)
2015-11-23 19:21:30 Pre-allocating up to position 0x5000000 in blk00242.dat
2015-11-23 19:21:31 receive version message: /Satoshi:0.11.99/: version 70002, blocks=385005, us=77.238.70.145:26312, peer=11
2015-11-23 19:21:31 Added time data, samples 12, offset -58 (+0 minutes)
2015-11-23 19:21:33 UpdateTip: new best=00000000000000000cb2528f3bce18a55c4c409f37b42d22b46a8605c4eb48e7  height=346475  log2_work=82.376038  tx=61624662  date=2015-03-06 22:47:07 progress=0.673361  cache=45.9MiB(14025tx)
2015-11-23 19:21:39 UpdateTip: new best=0000000000000000078fe19a813baaef0af791be59bbf3a9343404ee801f601d  height=346476  log2_work=82.376084  tx=61625687  date=2015-03-06 22:54:05 progress=0.673372  cache=60.4MiB(16062tx)
2015-11-23 19:21:47 UpdateTip: new best=000000000000000000f8b3275ec56a69ce2896df4a81ac1e801b95d143b9bc38  height=346477  log2_work=82.37613  tx=61627105  date=2015-03-06 23:15:44 progress=0.673395  cache=8.4MiB(3779tx)
2015-11-23 19:21:47 ERROR: AcceptToMemoryPool: nonstandard transaction: dust
2015-11-23 19:21:47 Pre-allocating up to position 0x6000000 in blk00242.dat
2015-11-23 19:21:49 ERROR: AcceptToMemoryPool: nonstandard transaction: dust
2015-11-23 19:21:49 ERROR: AcceptToMemoryPool: nonstandard transaction: dust
 log2_work=82.378893  tx=61659797  date=2015-03-07 09:01:15 progress=0.673956  cache=0.3MiB(0tx)
2015-11-23 19:24:42 UpdateTip: new best=0000000000000000004144ae8f49b61fb8b82bb63fdb4b806653c2ca2a7856e4  height=346538  log2_work=82.378939  tx=61660277  date=2015-03-07 09:17:48 progress=0.673969  cache=15.5MiB(1259tx)
2015-11-23 19:24:42 ERROR: AcceptToMemoryPool: nonstandard transaction: dust

2015-11-23 19:44:19 UpdateTip: new best=0000000000000000144ce9a4b60d0b758d535b7d666ecbdb51b55d14d2ffaab3  height=346873  log2_work=82.394356  tx=61870948  date=2015-03-09 15:51:48 progress=0.677291  cache=45.4MiB(11054tx)
2015-11-23 19:44:19 UpdateTip: new best=00000000000000000af14e4081f2d3f9f776a9fbfd0ca75d82717be3ef2dfb57  height=346874  log2_work=82.394402  tx=61870949  date=2015-03-09 15:51:51 progress=0.677291  cache=45.4MiB(11055tx)
2015-11-23 19:44:21 ping timeout: 1200.009567s
2015-11-23 19:44:21 ping timeout: 1200.006451s
2015-11-23 19:44:21 ping timeout: 1200.031617s
2015-11-23 19:44:26 UpdateTip: new best=000000000000000012028c0e1a68fa575e2193f5b023c5b2264752e30810433c  height=346875  log2_work=82.394449  tx=61871672  date=2015-03-09 15:58:26 progress=0.677300  cache=50.9MiB(14837tx)
2015-11-23 19:44:31 UpdateTip: new best=00000000000000000b9c0241771280d857fb71548aa7226bcf9dbe3d80983e07  height=346876  log2_work=82.394495  tx=61872351  date=2015-03-09 16:06:24 progress=0.677309  cache=62.5MiB(17065tx)
2015-11-23 19:44:32 receive version message: /Satoshi:0.11.0/: version 70002, blocks=385007, us=77.238.70.145:26335, peer=12
2015-11-23 19:44:32 Added time data, samples 13, offset -462 (-7 minutes)
2015-11-23 19:44:32 nTimeOffset = -1  (+0 minutes)
2015-11-23 19:44:32 receive version message: /Satoshi:0.10.2/: version 70002, blocks=385007, us=77.238.70.145:26306, peer=13
2015-11-23 19:44:32 Added time data, samples 14, offset -156 (-2 minutes)
2015-11-23 19:44:33 receive version message: /Satoshi:0.11.1/: version 70002, blocks=385007, us=77.238.70.145:26409, peer=15
2015-11-23 19:44:33 Added time data, samples 15, offset +0 (+0 minutes)
2015-11-23 19:44:33 nTimeOffset = -1  (+0 minutes)
2015-11-23 19:44:35 Pre-allocating up to position 0x7000000 in blk00242.dat
2015-11-23 19:44:36 receive version message: /Satoshi:0.11.0/: version 70002, blocks=385007, us=77.238.70.145:26267, peer=17
2015-11-23 19:44:36 Added time data, samples 16, offset -6 (+0 minutes)
2015-11-23 19:44:36 receive version message: /Satoshi:0.9.3/: version 70002, blocks=385007, us=77.238.70.145:26271, peer=18
2015-11-23 19:44:36 Added time data, samples 17, offset +3 (+0 minutes)
2015-11-23 19:44:36 nTimeOffset = -1  (+0 minutes)
2015-11-23 19:44:36 connect() to [2401:a400:3202:2000::1e9e]:8333 failed: Network is unreachable (101)
2015-11-23 19:44:37 receive version message: /Satoshi:0.11.1(bitcorenode)/: version 70002, blocks=385007, us=77.238.70.145:26410, peer=19
2015-11-23 19:44:37 Added time data, samples 18, offset +12 (+0 minutes)
2015-11-23 19:44:37 receive version message: /Satoshi:0.11.2/: version 70002, blocks=385007, us=77.238.70.145:26225, peer=20
2015-11-23 19:44:37 Added time data, samples 19, offset +0 (+0 minutes)
2015-11-23 19:44:37 nTimeOffset = -1  (+0 minutes)
2015-11-23 19:44:37 receive version message: /Satoshi:0.9.2.1/: version 70002, blocks=384997, us=77.238.70.145:26288, peer=16
2015-11-23 19:44:37 Added time data, samples 20, offset +7 (+0 minutes)
2015-11-23 19:44:40 Pre-allocating up to position 0x8000000 in blk00242.dat
2015-11-23 19:44:42 ERROR: AcceptToMemoryPool: nonstandard transaction: dust
2015-11-23 19:44:45 Leaving block file 243: CBlockFileInfo(blocks=0, size=0, heights=0...0, time=1970-01-01...1970-01-01)
2015-11-23 19:44:45 Pre-allocating up to position 0x1000000 in blk00243.dat
2015-11-23 19:44:47 ERROR: AcceptToMemoryPool: nonstandard transaction: dust
2015-11-23 19:44:49 ERROR: AcceptToMemoryPool: nonstandard transaction: dust
2015-11-23 19:44:49 ERROR: AcceptToMemoryPool: nonstandard transaction: dust
2015-11-23 19:44:50 Pre-allocating up to position 0x2000000 in blk00243.dat
2015-11-23 19:44:54 Pre-allocating up to position 0x3000000 in blk00243.dat
2015-11-23 19:45:03 Pre-allocating up to position 0x100000 in rev00243.dat
2015-11-23 19:45:03 UpdateTip: new best=000000000000000006943cfa58604e216201fb38bd07d6331010610921e9d69a  height=346877  log2_work=82.394541  tx=61873228  date=2015-03-09 16:15:25 progress=0.677320  cache=15.8MiB(2958tx)
2015-11-23 19:45:07 UpdateTip: new best=000000000000000006ac47d288ce3daa2cedd1c762b187097bbf49263b214220  height=346878  log2_work=82.394587  tx=61874252  date=2015-03-09 16:37:28 progress=0.677340  cache=17.5MiB(5068tx)
2015-11-23 19:45:10 UpdateTip: new best=0000000000000000029fc16df3bce0bc3b7a3cb2e1b3469efbcdfb656541bc49  height=346879

achow101
staff
Activity: 3458
Merit: 6793
Just writing some code
Re: Bitcoin Core 11.2.0 same Starting and Sync Height on new install
November 23, 2015, 03:01:28 PM
#2
Can you post the debug.log?
overcoin
newbie
Activity: 53
Merit: 0
Re: Bitcoin Core 11.2.0 same Starting and Sync Height on new install
November 23, 2015, 02:49:43 PM
#1
New installation and syncing blockchain for a 3-rd day. There is something wrong. Debug window shows too much and too long periods of Network Traffic inactivity. I've also tried via Tor, same result. My conclusion is that my new node is somehow treated as misbehaving from the rest and after some time they simply stop sending data to me.

On debug window:
Starting Height is showing 385005. Sync Height is showing 'Fetching...' but from time to time is showing an actual figure again... 385005. Shouldn't it show the current number of blocks synced (which in my case is 346536)?

All that leads to often nodes dropped and new peer included. I'm able to progress with syncing only until new peers stop responding in 5-10 minutes. Anyone having same experience not only with 11.2.0 but older versions as well?
Bitcoin Forum>Bitcoin>Bitcoin Technical Support
Jump to: