• 0
marecek666

can not sync after last turn-off

Question

Hi,

I turned off my PC 22 hours ago. I wanted to run my wallet today but it is not able to sync with network. There are enough connections but it is sitting on the block 2018383.

I found something interesting in debug log file.

Here is a piece:

2015-07-06 13:42:12 ProcessBlock: ACCEPTED
2015-07-06 13:42:12 received block c4975a38377186d6dedf98037b04b54936a1a5b07141250df6a860f84f5298bc
2015-07-06 13:42:13 InvalidChainFound: invalid block=c4975a38377186d6dedf98037b04b54936a1a5b07141250df6a860f84f5298bc  height=2020432  log2_work=57.982908  date=2015-07-06 13:38:22
2015-07-06 13:42:13 InvalidChainFound:  current best=73e15aa88996b60e5a32bc3ce721e554cf19a955e092fbce7a254b6deb0e1f27  height=2018383  log2_work=57.979623  date=2015-07-05 15:14:14
2015-07-06 13:42:13 InvalidChainFound: Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade.
2015-07-06 13:42:13 InvalidChainFound: invalid block=5561a6734b3a390b79f93aa5ff610c9f354c5e45c959284e468eef3980be4690  height=2020433  log2_work=57.982909  date=2015-07-06 13:39:01
2015-07-06 13:42:13 InvalidChainFound:  current best=73e15aa88996b60e5a32bc3ce721e554cf19a955e092fbce7a254b6deb0e1f27  height=2018383  log2_work=57.979623  date=2015-07-05 15:14:14
2015-07-06 13:42:13 InvalidChainFound: Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade.
2015-07-06 13:42:13 ProcessBlock: ACCEPTED
2015-07-06 13:42:13 received block 4ab0e66c61ffa3dc1f2c5f1cb5c3c9ef1515095f09defd55bc0b0a88feca9a30
2015-07-06 13:42:13 InvalidChainFound: invalid block=4ab0e66c61ffa3dc1f2c5f1cb5c3c9ef1515095f09defd55bc0b0a88feca9a30  height=2020433  log2_work=57.982909  date=2015-07-06 13:39:03
2015-07-06 13:42:13 InvalidChainFound:  current best=73e15aa88996b60e5a32bc3ce721e554cf19a955e092fbce7a254b6deb0e1f27  height=2018383  log2_work=57.979623  date=2015-07-05 15:14:14
2015-07-06 13:42:13 InvalidChainFound: Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade.
2015-07-06 13:42:13 InvalidChainFound: invalid block=b8a47f7b8cea069cd7cdd49477708132f251c5d0afe860d48be3256ed0a140ce  height=2020434  log2_work=57.982911  date=2015-07-06 13:39:17
2015-07-06 13:42:13 InvalidChainFound:  current best=73e15aa88996b60e5a32bc3ce721e554cf19a955e092fbce7a254b6deb0e1f27  height=2018383  log2_work=57.979623  date=2015-07-05 15:14:14
2015-07-06 13:42:13 InvalidChainFound: Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade.
2015-07-06 13:42:13 InvalidChainFound: invalid block=2ac22c8090716d5454f198d406b90e2b60ae4494ed6e9c7a49e2f1fe1e989486  height=2020435  log2_work=57.982913  date=2015-07-06 13:40:30
2015-07-06 13:42:13 InvalidChainFound:  current best=73e15aa88996b60e5a32bc3ce721e554cf19a955e092fbce7a254b6deb0e1f27  height=2018383  log2_work=57.979623  date=2015-07-05 15:14:14
2015-07-06 13:42:13 InvalidChainFound: Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade.
2015-07-06 13:42:13 ProcessBlock: ACCEPTED
2015-07-06 13:42:19 received block f12cd781ac22a9ce4a6f426aef43d4267246d718483fdac6cb6759518694111c
2015-07-06 13:42:19 InvalidChainFound: invalid block=f12cd781ac22a9ce4a6f426aef43d4267246d718483fdac6cb6759518694111c  height=2020436  log2_work=57.982914  date=2015-07-06 13:41:30
2015-07-06 13:42:19 InvalidChainFound:  current best=73e15aa88996b60e5a32bc3ce721e554cf19a955e092fbce7a254b6deb0e1f27  height=2018383  log2_work=57.979623  date=2015-07-05 15:14:14
2015-07-06 13:42:19 InvalidChainFound: Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade.
2015-07-06 13:42:19 ProcessBlock: ACCEPTED
2015-07-06 13:42:37 received block 0d527282322ccb6c7bc66f3921aec30601a1f082b9981b8adef98b3e7784bf7a
2015-07-06 13:42:37 InvalidChainFound: invalid block=0d527282322ccb6c7bc66f3921aec30601a1f082b9981b8adef98b3e7784bf7a  height=2020437  log2_work=57.982916  date=2015-07-06 13:42:20
2015-07-06 13:42:37 InvalidChainFound:  current best=73e15aa88996b60e5a32bc3ce721e554cf19a955e092fbce7a254b6deb0e1f27  height=2018383  log2_work=57.979623  date=2015-07-05 15:14:14
2015-07-06 13:42:37 InvalidChainFound: Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade.
2015-07-06 13:42:37 ProcessBlock: ACCEPTED

what does it mean INVALID CHAIN FOUND ???

 

and my wallet is reporting that it is syncing but it is waiting on that block 2018383, as you can see:

post-37-0-98309900-1436190584_thumb.jpg

 

I am running the latest wallet:

1.1.0 Chunky Monkey

Share this post


Link to post
Share on other sites

57 answers to this question

  • 0

HI ! , lets try this first :

Backup your wallet  and put that into a safe place (VERY IMPORTANT)

Run the installer and select 'expert' option; choose where you want to install the chain. Copy your wallet.dat backup to the directory you specified.

Share this post


Link to post
Share on other sites
  • 0

thanks for reaction,

the only successful way was to delete whole chain and wallet software from local PC and let the installer to copy new files and download chain again. The ability of syncing was the same without my original wallet.dat file before this reinstallation - It was not working too.

 

And 1 thing: my wallet was running several days without interruption (I was visible on the WDC active nodes webpage as Slovakia - 1 node).  That was the reason letting it run - to support WDC network as a node. But I had to turn my PC off for almost whole day (WDC client closed via menu FILE - EXIT so there was no chance to damage blockchain db). Maybe it is a source of the problem mentioned here. Is it secure to keep windows version of wallet running? I was doing it before with old client (0.8.6.2)  and there was no problem. It was suitable to run whole weeks without interruption.

Share this post


Link to post
Share on other sites
  • 0

There is no problem keeping wallet turned on,  very strange, chain db corrupted.

Anyway we are a few weeks before new wallet arrives and as is uses only the daemon for core functions, it should be a lot more stable.

Meanwhile let's keep an eye on it and see if it happens again so ew can reproduce the bug

 

Thank you very much for reporting

Share this post


Link to post
Share on other sites
  • 0

and again the same problem. I started worldcoin-qt after several hours and it is unable to synchronize from the block when wallet was running the last.

here is a piece of log file:

2015-07-12 04:23:29 received block c81a7b9454a5f21ff06c129a4b17cf05f3aaa17f34c98943ecccf33f149e089c
2015-07-12 04:23:29 InvalidChainFound: invalid block=c81a7b9454a5f21ff06c129a4b17cf05f3aaa17f34c98943ecccf33f149e089c  height=2032111  log2_work=57.998335  date=2015-07-11 12:43:50
2015-07-12 04:23:29 InvalidChainFound:  current best=90cff65196829b25f181b32d77244dd5dcec0c33c010832a16e91b972eac82f7  height=2031613  log2_work=57.997572  date=2015-07-11 09:05:54
2015-07-12 04:23:29 InvalidChainFound: Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade.
2015-07-12 04:23:29 ProcessBlock: ACCEPTED
2015-07-12 04:23:29 received block 7b9263c42631d497625d6381f12bd5495b33411f4bd0e3b55f38a348ed831b0d
2015-07-12 04:23:29 InvalidChainFound: invalid block=7b9263c42631d497625d6381f12bd5495b33411f4bd0e3b55f38a348ed831b0d  height=2032112  log2_work=57.998337  date=2015-07-11 12:44:19
2015-07-12 04:23:29 InvalidChainFound:  current best=90cff65196829b25f181b32d77244dd5dcec0c33c010832a16e91b972eac82f7  height=2031613  log2_work=57.997572  date=2015-07-11 09:05:54
2015-07-12 04:23:29 InvalidChainFound: Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade.
2015-07-12 04:23:29 ProcessBlock: ACCEPTED
2015-07-12 04:23:29 received block bb7d92c00d5e2af390ef013e289554dc4ab99d1f59d23d73f2d3f9a2d3ed6546
2015-07-12 04:23:29 InvalidChainFound: invalid block=bb7d92c00d5e2af390ef013e289554dc4ab99d1f59d23d73f2d3f9a2d3ed6546  height=2032113  log2_work=57.998338  date=2015-07-11 12:44:36
2015-07-12 04:23:29 InvalidChainFound:  current best=90cff65196829b25f181b32d77244dd5dcec0c33c010832a16e91b972eac82f7  height=2031613  log2_work=57.997572  date=2015-07-11 09:05:54
2015-07-12 04:23:29 InvalidChainFound: Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade.
2015-07-12 04:23:29 ProcessBlock: ACCEPTED
2015-07-12 04:24:17 accepted connection 192.241.197.116:59069
2015-07-12 04:24:17 send version message: version 75000, blocks=2031613, us=188.120.5.142:11081, them=192.241.197.116:59069, peer=192.241.197.116:59069
2015-07-12 04:24:17 receive version message: /Node:0.8.7.2/: version 70002, blocks=814261, us=188.120.5.142:11081, them=192.241.197.116:9331, peer=192.241.197.116:59069
2015-07-12 04:24:17 socket closed
2015-07-12 04:24:17 disconnecting node 192.241.197.116:59069
2015-07-12 04:24:53 accepted connection 107.170.24.54:43242
2015-07-12 04:24:53 send version message: version 75000, blocks=2031613, us=188.120.5.142:11081, them=107.170.24.54:43242, peer=107.170.24.54:43242
2015-07-12 04:24:53 receive version message: /Node:0.8.7.2/: version 70002, blocks=814261, us=[::ffff]:48248, them=107.170.24.54:9331, peer=107.170.24.54:43242
2015-07-12 04:24:53 socket closed
2015-07-12 04:24:53 disconnecting node 107.170.24.54:43242
2015-07-12 04:24:55 accepted connection 80.69.77.111:52103
2015-07-12 04:24:56 send version message: version 75000, blocks=2031613, us=188.120.5.142:11081, them=80.69.77.111:52103, peer=80.69.77.111:52103
2015-07-12 04:24:56 receive version message: /Node:0.8.7.2/: version 70002, blocks=814261, us=[::ffff]:48248, them=80.69.77.111:9331, peer=80.69.77.111:52103
2015-07-12 04:24:56 socket closed
2015-07-12 04:24:56 disconnecting node 80.69.77.111:52103
2015-07-12 04:25:00 received block 97d1c49b192ec8db9cb57a9835104ec9e436d9705b789c48ff8be2fe6622892d
2015-07-12 04:25:00 ProcessBlock: ORPHAN BLOCK, prev=9f532fb23b122b86894ac47922078d246803833e64c897295f54ff43548334f2
2015-07-12 04:25:25 received block 916811a0ff94937f2b8f6b6ca69a38ff60630cc258d4950853f45429701cc5bc
2015-07-12 04:25:25 ProcessBlock: ORPHAN BLOCK, prev=97d1c49b192ec8db9cb57a9835104ec9e436d9705b789c48ff8be2fe6622892d
2015-07-12 04:26:11 stored orphan tx 0a2c99785f33f5e6ea19bc72315941f6dbcf413ed2c0f2744fe1478ff694c2bc (mapsz 1)
2015-07-12 04:26:12 stored orphan tx 824b6c92b074a04c5c126a854895c64200fe99a0a22eb4a77f3844792cc36c5c (mapsz 2)
2015-07-12 04:26:21 received block 10acaa608cc9c1d3137346b1c5f6f9c544bf71c1444bc916281c3008712ad325
2015-07-12 04:26:21 ProcessBlock: ORPHAN BLOCK, prev=916811a0ff94937f2b8f6b6ca69a38ff60630cc258d4950853f45429701cc5bc

look at the part:

2015-07-12 04:23:29 received block bb7d92c00d5e2af390ef013e289554dc4ab99d1f59d23d73f2d3f9a2d3ed6546
2015-07-12 04:23:29 InvalidChainFound: invalid block=bb7d92c00d5e2af390ef013e289554dc4ab99d1f59d23d73f2d3f9a2d3ed6546  height=2032113  log2_work=57.998338  date=2015-07-11 12:44:36
2015-07-12 04:23:29 InvalidChainFound:  current best=90cff65196829b25f181b32d77244dd5dcec0c33c010832a16e91b972eac82f7  height=2031613  log2_work=57.997572  date=2015-07-11 09:05:54
2015-07-12 04:23:29 InvalidChainFound: Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade.
2015-07-12 04:23:29 ProcessBlock: ACCEPTED

my last stored block was 2031613, after that I turned wallet and PC off. Now after several hours it is unable to sync, worldcoin-qt is thinking that every block from the last stored is orphan. I am running version 1.1.0.

Tell me what are you going to do with it? If there is somebody who is able to tell what the hell it is, I will send whole debug file.

 

and here is a part of debug file from the time when I turned worldcoin off:

2015-07-11 09:05:57 getblocks 1 to 7c54e9a09606e7be50772d6fb3b04e6994349b12b466ff1b5581b329e9cdb587 limit 500
2015-07-11 09:05:57   getblocks stopping at limit 500 2902e7b4f1871554221343335546fb00f8270b8479870aaaa6d2c2a6498113a7
2015-07-11 09:06:21 Added 1 addresses from 69.30.233.210: 118 tried, 11789 new
2015-07-11 09:06:32 Added 1 addresses from 108.61.10.90: 118 tried, 11790 new
2015-07-11 09:06:34 received block 90cff65196829b25f181b32d77244dd5dcec0c33c010832a16e91b972eac82f7
2015-07-11 09:06:34 Committing 2 changed transactions to coin database...
2015-07-11 09:06:34 SetBestChain: new best=90cff65196829b25f181b32d77244dd5dcec0c33c010832a16e91b972eac82f7  height=2031613  log2_work=57.997572  tx=3764909  date=2015-07-11 09:05:54 progress=0.999998
2015-07-11 09:06:34 ProcessBlock: ACCEPTED
2015-07-11 09:06:35 received getdata for: block 90cff65196829b25f181b32d77244dd5dcec0c33c010832a16e91b972eac82f7
2015-07-11 09:06:36 getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2015-07-11 09:06:37 getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2015-07-11 09:06:39 getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2015-07-11 09:06:39 getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2015-07-11 09:06:43 accepted connection 85.214.38.59:51390
2015-07-11 09:06:43 send version message: version 75000, blocks=2031613, us=188.120.5.142:11081, them=85.214.38.59:51390, peer=85.214.38.59:51390
2015-07-11 09:06:43 Added time data, samples 36, offset +5 (+0 minutes)
2015-07-11 09:06:43 Moving 85.214.38.59:11015 to tried
2015-07-11 09:06:43 receive version message: /Satoshi:1.1.0.1/: version 70002, blocks=378885, us=188.120.5.142:11081, them=85.214.38.59:11015, peer=85.214.38.59:51390
2015-07-11 09:06:43 ERROR: CAlert::CheckSignature() : verify signature failed
2015-07-11 09:06:43 Misbehaving: 85.214.38.59:51390 (0 -> 10)
2015-07-11 09:06:50 msghand thread interrupt
2015-07-11 09:06:50 dumpaddr thread stop
2015-07-11 09:06:50 opencon thread interrupt
2015-07-11 09:06:50 addcon thread interrupt
2015-07-11 09:06:50 net thread interrupt
2015-07-11 09:06:50 Shutdown : In progress...
2015-07-11 09:06:50 Flush(false)
2015-07-11 09:06:50 DBFlush(false) ended               0ms
2015-07-11 09:06:50 StopNode()
2015-07-11 09:06:50 UPNP_DeletePortMapping() returned : 0
2015-07-11 09:06:50 upnp thread interrupt
2015-07-11 09:06:51 Flushed 11908 addresses to peers.dat  117ms
2015-07-11 09:06:51 Committing 0 changed transactions to coin database...
2015-07-11 09:06:51 Flush(true)
2015-07-11 09:06:51 wallet.dat refcount=0
2015-07-11 09:06:51 wallet.dat checkpoint
2015-07-11 09:06:51 wallet.dat detach
2015-07-11 09:06:51 wallet.dat closed
2015-07-11 09:06:51 DBFlush(true) ended             213ms
2015-07-11 09:06:51 Shutdown : done
2015-07-12 04:19:41

Share this post


Link to post
Share on other sites
  • 0

We don't have compiled daemon for windows so don't bother. I will test this on my machine, so after running a few days you turn off pc and turn on again and this problem occurs right ? how many days ? do you close wallet first (shouldn't be a  problem but i want to test exactly the same ) ? anything else specific to replicate exactly the events that trigger the problem ?

Share this post


Link to post
Share on other sites
  • 0

Yes, after several days I properly closed the worldcoin application (via menu FILE - EXIT) and after that I turned off my PC. Then several hours later after turning my PC on I started worldcoin and this problem occured. Does not matter how many days was it running, it was more than a week when this problem occured for the first time and only less than 2 days for the last time. Worldcoin-qt had more than 20 connections to the network in both cases. I am using Avast IS and excluded whole Worldcoin folder in it. So antivirus is not doing tests on wdc structure on my HDD. And as I wrote before, this problem did not occure while I was using old client 0.8.6.2 in the same enviroment.

When I use this new client only for doing TXs (start WDC, wait for sync, send/receive payment, close WDC) this problem does not occur.

Share this post


Link to post
Share on other sites
  • 0

I am trying to reinstall worldcoin but your install program is having a problem. I completely uninstall qt and deleted chain folder. After downloading new installation - it is not able to download anything!

look at it:

wdc_fail.jpg

 

you maybe want to make WDC a good crypto, but such basic problems will make it another fail. I use several wallets of other cryptos but none of them has such problems as yours!

w

could you upload all chain so I can download it for old wallet 0.8.6.2 ? Letting it sync itself from the net would be a long run... and would like to use this older until you will find where the problems are.

Share this post


Link to post
Share on other sites
  • 0

I am trying to reinstall worldcoin but your install program is having a problem. I completely uninstall qt and deleted chain folder. After downloading new installation - it is not able to download anything!

look at it:

wdc_fail.jpg

 

you maybe want to make WDC a good crypto, but such basic problems will make it another fail. I use several wallets of other cryptos but none of them has such problems as yours!

w

could you upload all chain so I can download it for old wallet 0.8.6.2 ? Letting it sync itself from the net would be a long run... and would like to use this older until you will find where the problems are.

I can't replicate previous problem, can anybody try ?

 

Other problem happens when server is being hammered, next version should solve most of these issues. Try again.

Share this post


Link to post
Share on other sites
  • 0

of course, 100mbps fibre

 

and finally got it after several tries

When some one tries to connect to the server without using the installer and tries many times (not you of course), probably to reverse engineer the protocol or something else nasty, the server stays on hold until further inspection.

As nobody was able to do anything I will relax this conditions on next version.

 

What i am unable to replicate is your issue with windows 64 version, can you build https://github.com/WorldcoinGlobal/WorldcoinDaemonand test it a few days ?

Next version will use standard daemon (the one that exchanges use) and around the daemon we are wrapping another application which adds an UI layer and things that users want (detailed on forum), in other words, it should be extremely stable, because even if UI has bugs it won't affect core functions

Still, i would like somebody else help us testing this issue in another Windows 64 machine

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

  • Recently Browsing   0 members

    No registered users viewing this page.