Jump to content
headzoo

Possible for Wallet to Have Indexed Recent Blocks, But Not Older Blocks?

Recommended Posts

So any time I start the desktop wallet in Windows, this starts happening about 30 minutes later:

 

tJhH5JS.png

 

The number of blocks went down by about 10 over the course of 4 hours. The strange thing is, I'm positive the most recent blocks have been indexed. I can see them being index through the log file. But this gets better! Now this is what I'm seeing:

 

xKtMeie.png

 

I could be wrong, but I think the block chain has fewer than 300k blocks.

 

I'm using MinCoin v0.6.5.0-g498f5d1-beta on Windows 8.1.

Share this post


Link to post
Share on other sites

This is some of the log file while this is happening.

 

send version message: version 60002, blocks=288606, us=96.250.250.181:9334, them=203.100.1.50:9334, peer=203.100.1.50:9334
trying connection 178.78.63.209:9334 lastseen=2.4hrs
Added time data, samples 5, offset -2 (+0 minutes)
nTimeOffset = -2  (+0 minutes)
receive version message: version 60002, blocks=288606, us=96.250.250.181:1688, them=203.100.1.50:9335, peer=203.100.1.50:9334
received block be4bbb46402efc63331f
SetBestChain: new best=be4bbb46402efc63331f  height=288607  work=1330488401807024  date=01/03/14 03:11:56
ProcessBlock: ACCEPTED
socket no message in first 60 seconds, 0 1
disconnecting node 54.218.140.11:9334
connection timeout
Added 1 addresses from 173.160.57.9: 554 tried, 13262 new
Flushing wallet.dat
Flushed wallet.dat 8ms
trying connection 213.29.218.142:9334 lastseen=0.9hrs
Added 398 addresses from 68.34.99.87: 554 tried, 13205 new
Added 461 addresses from 68.34.99.87: 554 tried, 13181 new
Added 235 addresses from 68.34.99.87: 554 tried, 13172 new
ERROR: FetchInputs() : 12dfaa0e0b mempool Tx prev not found 94643c5b5c
stored orphan tx 12dfaa0e0b (mapsz 1)
ERROR: FetchInputs() : 411e9954b0 mempool Tx prev not found 2c4881bfe8
stored orphan tx 411e9954b0 (mapsz 2)
connection timeout
ERROR: FetchInputs() : 1d39a70b2d mempool Tx prev not found 65afa050fd
stored orphan tx 1d39a70b2d (mapsz 3)
Added 482 addresses from 203.100.1.50: 554 tried, 13179 new
trying connection 46.98.15.129:9334 lastseen=7.9hrs
Added 471 addresses from 203.100.1.50: 554 tried, 13163 new
Added 256 addresses from 203.100.1.50: 554 tried, 13176 new
ERROR: FetchInputs() : e7aaf13b38 mempool Tx prev not found 6d910126b9
stored orphan tx e7aaf13b38 (mapsz 4)
connection timeout
ERROR: FetchInputs() : 16f3bc6faf mempool Tx prev not found 10eea3562a
stored orphan tx 16f3bc6faf (mapsz 5)
ERROR: FetchInputs() : 77216b3b50 mempool Tx prev not found 7aaa94a285
stored orphan tx 77216b3b50 (mapsz 6)
ERROR: FetchInputs() : 6beb184c92 mempool Tx prev not found 619678527b
stored orphan tx 6beb184c92 (mapsz 7)
ERROR: FetchInputs() : 996966fd90 mempool Tx prev not found 399a9a400e
stored orphan tx 996966fd90 (mapsz 8)
ERROR: FetchInputs() : 3038e410aa mempool Tx prev not found 5d59b718bf
stored orphan tx 3038e410aa (mapsz 9)
ERROR: FetchInputs() : d5a698fdaa mempool Tx prev not found 0a77bdb66d
stored orphan tx d5a698fdaa (mapsz 10)
ERROR: FetchInputs() : 5cc474f0ac mempool Tx prev not found 2e11bd71c8
stored orphan tx 5cc474f0ac (mapsz 11)
ERROR: FetchInputs() : 81fd70aaa6 mempool Tx prev not found c81dcb758b
stored orphan tx 81fd70aaa6 (mapsz 12)
trying connection 119.162.67.131:9334 lastseen=5.9hrs
ERROR: FetchInputs() : d8aedd4c09 mempool Tx prev not found 7c37818d64
stored orphan tx d8aedd4c09 (mapsz 13)
connection timeout
trying connection 76.183.45.240:9333 lastseen=4.9hrs
received block ce710c99880afd58cedb
SetBestChain: new best=ce710c99880afd58cedb  height=288608  work=1330502166201102  date=01/03/14 03:12:10
ProcessBlock: ACCEPTED
Flushing wallet.dat
Flushed wallet.dat 8ms
connection timeout
trying connection 198.27.80.205:9334 lastseen=3.9hrs
connection timeout
trying connection 66.169.156.148:9334 lastseen=4.8hrs
connection timeout
trying connection 86.163.160.12:9334 lastseen=0.9hrs
Flushed 13729 addresses to peers.dat  91ms

 

Share this post


Link to post
Share on other sites

Previous wallets were occasionally showing the LTC blockchain, but I thought the new wallet version fixed that issue.  It's not really much of a problem overall, as it will get back on the proper chain with a restart, or on its own after a while, from my experience.

 

You might try to try restarting it occasionally to see if it gets synced up quicker (this is a common workaround for most wallets for the various currencies, not just MNC).  Also, do the addnode additions to your mincoin.conf file to see if that helps:

 

http://mincoinforum.com/index.php/topic/27-creating-your-mincoinconf-file-adding-nodes-for-better-connection/

 

I suppose you could try to delete your peers.dat file and restart, but I'm not sure that's really going to be of any benefit. If you choose that route, do this:  Shut down the MNC wallet; delete peers.dat; edit your mincoin.conf file as per the above link; start up the MNC wallet and see how it goes.

Share this post


Link to post
Share on other sites

Previous wallets were occasionally showing the LTC blockchain, but I thought the new wallet version fixed that issue.  It's not really much of a problem overall, as it will get back on the proper chain with a restart, or on its own after a while, from my experience.

 

You might try to try restarting it occasionally to see if it gets synced up quicker (this is a common workaround for most wallets for the various currencies, not just MNC).  Also, do the addnode additions to your mincoin.conf file to see if that helps:

 

http://mincoinforum.com/index.php/topic/27-creating-your-mincoinconf-file-adding-nodes-for-better-connection/

 

I suppose you could try to delete your peers.dat file and restart, but I'm not sure that's really going to be of any benefit. If you choose that route, do this:  Shut down the MNC wallet; delete peers.dat; edit your mincoin.conf file as per the above link; start up the MNC wallet and see how it goes.

 

Thanks for the tips. I think the wallet actually is in sync. The strange behavoir starts about 30 minutes after the wallet has been running. "Showing the LTC block chain" may explain the other error I've been having.

Share this post


Link to post
Share on other sites

It's not really much of a problem overall, as it will get back on the proper chain with a restart, or on its own after a while,

 

Yup i can confim that i can even mine blocks while its doing this..im pretty sure it has to do with irc but not sure 

Share this post


Link to post
Share on other sites

I've always been able to just ignore messages and resync behavior and keep on mining solo and it's worked fine.  I know that's not the best response to this, but for now, it's been fine for me for over 6 months or something, so I can attest that it's not a critical issue.

 

We do need to resolve this thoug, of course.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×

Important Information

By using this site, you agree to our Terms of Use.