Stuck on block 854887

[moisespr123]

Hi everyone,

Yesterday, I believe the network decided to ban me as I believe I was a fork, according to some hashes Erkan compared with mine. Today, I was able to load the wallet and get connections again but I'm not getting any more blocks and stuck in block 854887. In IRC, there are several other members having issues syncing as well.

Attached the log file: debug.log.txt

[grctest]

What OS are you on? What are your computer specs? What client are you using? (windows, linux self-compile/ppa (daily/stable)) ?

[moisespr123]

Windows 10, Intel i7-3610QM, 16GB RAM, latest Windows build, 3.5.8.7

[iFoggz]

wouldnt a updated snapshot that is beyond 855001 on .7 client save these problems? just an idea to put out there as others have had this issue as well.

[grctest]

wouldnt a updated snapshot that is beyond 855001 on .7 client save these problems? just an idea to put out there as others have had this issue as well.

Technically, there shouldn't be any problem getting past the previously bad blocks since the upgrade to .7

@moisesmcardona How did you upgrade? Using the MSI over the existing installation? I used the upgrader within the client + download blocks to sync fully. Perhaps you could uninstall the gridcoin client, delete any leftover files from /Program Files/GridcoinResearch/ and reinstall? (Not appdata folder, programfiles).

[iFoggz]

@grctest ah got cha didnt think .7 kicked in its additions till past 855001. i know my .7 client was fighting checkblock fails during the whole process up to 855001. thx for the info.

[moisespr123]

I clean installed it since I did a clean Windows install

[grctest]

I clean installed it since I did a clean Windows install

Windows updates fully installed?

[moisespr123]

But I second Foggyx420. A snapshot would help here, and yes, Windows is up to date....

[moisespr123]

Synching from 0 to see if it works...

[moisespr123]

Snapshot didn't help

[moisespr123]

Windows 10 build 15063

[MarvelWild]

My wallet is stuck too.

Log messages: Mar 29 2017 01:50, Error while Speaking Good Morning marvel.me, Your Magnitude is 0Conversion from string ",in Production." to type 'Double' is not valid.

[GridcoinNoob]

Having the same problem. Deleted the log, however, this is the error message I was getting in my debug.log:

ERROR: Bad CPID : height 854887.000000, CPID cbbe01ae2c53cad990a6867a51255657, cpidv2 cbbe01ae2c53cad990a6867a512556573a3a3992c93e3ecb696a673e6d3a3c989d3a6c979ccc993939c63d3fc8666b9b6e62736c76746d627577626d62416d76766c6c762f64706e, LBH 49b1969c0be6c46c23c8feb302104c1713686b6c4fe22b03c3c0d40e72589270, Bad Hashboinc cbbe01ae2c53cad990a6867a51255657<|><|><|>0<|>0.00000<|>0<|><|><|>0<|>0<|>v3.5.8.7-g-research<|>704.93<|>0<|>0<|>cbbe01ae2c53cad990a6867a512556573a3a3992c93e3ecb696a673e6d3a3c989d3a6c979ccc993939c63d3fc8666b9b6e62736c76746d627577626d62416d76766c6c762f64706e<|>95<|>Rx8CrVuJg1kmP1tAcZeCuVu2t3384ddtVx<|>49b1969c0be6c46c23c8feb302104c1713686b6c4fe22b03c3c0d40e72589270<|>101.33<|><|><|><|><|>704.93<|>31.025556<|>0.250000<|>90.88<|>c69cdbfb82ed8a1fb259dc8610429bbba1d0eab3d71136627a0dcc1ad2c7d066<|>d41d8cd98f00b204e9800998ecf8427e<|>04b4bdd31f5ee9101f29206cc74d943e4cc4af72688611792f3a8bb0410f84f9bda14a9c88d016bc7116315758fd88cbf5274679a69834e77d2aee2eefb59b993d<|>MEUCIQCTYveRRG3obbkGKjkvNOz42QejN7jzBwzCNpaQ6avXaQIgAt44Eg4KRPUpx/2XkTtbHckiPr4E0SzrGl9x9hS2WyE= 03/28/17 22:47:58 ERROR: ProcessBlock() : CheckBlock FAILED

Note that the block hash is actually the correct hash for block 854887, so I have no idea why this error is occurring.

Additionally, before I had this error, I was getting a nearly identical error on block 855631, and again, when I verified the hash for that block, it was the correct hash. That was what prompted me to attempt to sync from the snapshot, only to run into the same error on this earlier block.

[Deviant0ne]

Just piling on my "me 2". Stuck on block 854887. Tried downloading blocks and again stuck on same block. same story in my logs as well.

[grctest]

Anyone interested in testing out a theory?

Make a backup of your gridcoinresearch.conf, then create a new config file without your BOINC details and no email line - attempting to make your wallet INVESTOR mode. I'm fully synced but I'm running windows/linux both in INVESTOR mode.

@Deviant0ne @GridcoinNoob Have you tried safely restarting the wallet 30mins in between attempts to sync?

[Deviant0ne]

Ive restarted a few times, but can say they were longer than 30 mins apart. It generally takes that long to build some connections and pray it moves past that block before coming to terms that it wont. :) I just restarted again and will move onto a fresh config test if this time is not the charm.

[Deviant0ne]

Same story... This repeating in the debug file:

Received block d6806457047a4d9c9a92fe2d1f1da9d0590995a97f7c79ebafa4db13670e726e; ERROR: Bad CPID : height 854887.000000, CPID ca657fbf7b4d3fd03538951fb431716c, cpidv2 ca657fbf7b4d3fd03538951fb431716c3f9a646a959e99c43939cb6d3a999c956cc79633936f9d3539996ccc3a3c656f6469666f78792f7674756441686e626a6d2f64706e, LBH d4232d9a1b4ea80dc486be04597cbfb230a145f1a749b5dd5853b8243c984312, Bad Hashboinc ca657fbf7b4d3fd03538951fb431716c<|><|><|>0<|>0.00000<|>0<|><|><|>0<|>0<|>v3.5.8.7-g-research<|>4.39<|>1490692752<|>0<|>ca657fbf7b4d3fd03538951fb431716c3f9a646a959e99c43939cb6d3a999c956cc79633936f9d3539996ccc3a3c656f6469666f78792f7674756441686e626a6d2f64706e<|>185<|>SHcMjioKN5E8RxrsDfKZKc7eAH7DM3UWVY<|>d4232d9a1b4ea80dc486be04597cbfb230a145f1a749b5dd5853b8243c984312<|>0.89<|><|><|><|><|>4.39<|>0.105556<|>0.225000<|>185.00<|>943b299348bb025ffeaed15acfc83737a17cff2f0691a4366b5d3adaf55c792e<|>d41d8cd98f00b204e9800998ecf8427e<|>04ec1180e11f5b53f31b565562636c9bd9fdd6275b2546bdddac7f4d0352f44f0ca5e2f1cded9ae8d5a65cdf0500cf068af5217cc5d679005156a8b0f79b2f2c1f<|>MEUCIQD6TqDrTS/nSR1shwzxPvF013A2G1vuOtexEzgM6f0EkAIgGdUQ8uzQ7W5cjZI/tQGLlsF1ne1IuHwNPZLQwCXQeTs= 03/29/17 00:22:32 ERROR: ProcessBlock() : CheckBlock FAILED

[philipswift]

There's a caveat to the mandatory latest release. You need to run GRCRestarter.exe with a switch calling for 'downloadblocks'. This not the same as having you wallet running and clicking 'downloadblocks'. You can either run the command from console or make a batch file in the same folder as GRCRestarter.exe. Using the batch is easiest. Make a new notepad .txt file in the same folder as the GRCRestarter.exe. Open it and type GRCRestarter.exe downloadblocks. [GRCRestarter.exe downloadblocks]. Then go file>save as>change the file type from .txt to all file types in the lower drop-down. Then save it as name.bat where name can be anything. [downloadblocks.bat] Then make sure the client/wallet is shutdown. Double click your bat file and it will run starting GRCRestarter but with the download blocks command. After 20 minutes or so you should have got the blocks and the wallet will start up. Let it sync fully if it needs to. That should do it. Good luck.

[GridcoinNoob]

That won't work... I did that after I upgraded the wallet, and again today when I got stuck at 855631, still ended up stuck on 854887

[GridcoinNoob]

As an additional note... I tried to rebuild the block chain from scratch, without using "download blocks" through any method, wiped out my entire gridcoin appdata directory, except for my config file and wallet.dat, and re-ran it...

And I'm now stuck at 854420, with the same issue happening as before. Bad CPID error.

03/29/17 05:33:27 Received block 2fc37c1746786a156253bcd869fe0372f244b16b6ceb5a5dab60a534373adfe8; ERROR: Bad CPID : height 854420.000000, CPID a7a537ff8ad4d8fff4b3dad444e681ef, cpidv2 a7a537ff8ad4d8fff4b3dad444e681ef999642666b3a3a97379d9a9c3337686f6b673a333bc63a3e994134c7669d683a7a6f7a6b6d4172722f64706e, LBH f564622e49a6fb20bb7b10bbdd4bcb34b2b17d06d6462b94c3ce01a4f26adc22, Bad Hashboinc a7a537ff8ad4d8fff4b3dad444e681ef<|><|><|>0<|>0.00000<|>0<|><|><|>0<|>0<|>v3.5.8.7-g-research<|>9.18<|>0<|>0<|>a7a537ff8ad4d8fff4b3dad444e681ef999642666b3a3a97379d9a9c3337686f6b673a333bc63a3e994134c7669d683a7a6f7a6b6d4172722f64706e<|>8<|>SAyxEueRaSMEdXjQFhAj96qkPYDZnxrmpj<|>f564622e49a6fb20bb7b10bbdd4bcb34b2b17d06d6462b94c3ce01a4f26adc22<|>0.23<|><|><|><|><|>9.18<|>4.591481<|>0.250000<|>8.00<|>b5f38c6e782bb11dee3106173128953dff56ba6429892b03797d78ee90b0a395<|>d41d8cd98f00b204e9800998ecf8427e<|>04924981df28b7ed280adbe9375d8e36857c81766784225c9c5b608be0d4341da98770a4047ccbcbd3ac846417bb12e39c1a8900a86f7263cf9c173f2bef756278<|>MEUCIQDpiC05WgAQp6iC6Uu2yRgNci59K86LtzkbmwLjvSUuggIgY8zV+0/oZJSYauSawkW2Rc+Ie3WtUX2tNgKWClw+kqU= 03/29/17 05:33:27 ERROR: ProcessBlock() : CheckBlock FAILED

I'm actually getting several different bad versions of this block from different peers, but that one should actually be the right one, and it's still stuck.

[Netizen78]

Same here. Did a fresh install of the Gridcoin client and used a recent snapshot, but it's stuck at 854420. EDIT: Tried an almost empty conf file, no connection to Boinc, empty wallet - same result.

[nateonthenet]

Also stuck at 854420, both using downloadblocks and sync from zero. I'm running in INVESTOR mode at the moment, no BOINC involved.

[Quezacoatl1]

Currently running 2 Win nodes (still syncing from 0 as they have been stuck on 855631 with the snapshot) and 3 ARM nodes (2 still syncing).

One Ubuntu ARM node stuck on 854887, synced from 0, 10+ connections, debug, debug2, debug3 and fDebug10 active, debug log here: https://pastebin.com/jJgg5VbW

[Netizen78]

I'm not too familiar with the internal stuff of the Gridcoin network, so this is just an observation. If I compare some hashes from the block explorer with the latest ones my client got, I can see they're in sync only up to 854401: http://www.gridresearchcorp.com/gridcoin/?cfd01316377ded290de87c5dce2652cbfb22b65dbb54f76b860205b8701d907b

According to the block explorer the next hash should be d98328744e3fd4ddf8699c302922c97589a4066e28e0ca7483c2492444c5b3c1, but in my log file it shows e2a95c4040104a316b9e4e3dbb3dedb4487c5f1c9e59d6689aa6fdd2a8d5cd1b for 854402. And then a few blocks later at 854420 it fails completely.

[Erkan-Yilmaz]

we just did a test:

1. a node X was sync yesterday on the A chain
2. this morning X got stuck
3. just allowing on X 1 peer (synced linux node L with fresh snapshot) made it stuck again at block 854420
4. same step 3 with synced win node W: also stuck

logs may be available from @barton2526 later on

X, L, W are all on version 3.5.8.7

[tomasbrod]

Site gridresearchcorp.com seems to be on the fork. I advise you @Netizen78 to use gridcoinstats.eu. See your block here: https://gridcoinstats.eu/block.php?id=854402

[Erkan-Yilmaz]

@tomasbrod

I just checked: gridresearchcorp is on the A chain: getblockhash 856335 hash = 0e99fa281e95d6e93e424b2b649ef1e4b8bb8d2842ef6da001bbeb1bdf260d10

[tomasbrod]

Yes, you are right @Erkan-Yilmaz. But the past blocks are mixed and the prev and next pointers are wrong. See: http://www.gridresearchcorp.com/gridcoin/?854405 it diverges at 854401 854402.

[Erkan-Yilmaz]

Yes, you are right @Erkan-Yilmaz. But the past blocks are mixed and the prev and next pointers are wrong. See: http://www.gridresearchcorp.com/gridcoin/?854405 it diverges at 854401 854402.

ok, then @GridResearchCorp should have a look

[skcin]

@moisesmcardona I had a similar issues. I added nodes to my configfile that were already upgraded. Solved it for me. @grctest nodes for example. If you only have old nodes in your .conf file you can't sync.

[philipswift]

Nice..... 🥇 and thankyou. Can someone with write access to make some changes to webpage contents maybe? Is this the wrong place to mention it? Is it better to stick with just one addnode (gridcoin.us) even though it makes syncing a long process (if you don't downloadbocks)? All this information below is confusing for newbs (and me on occasion!) who may not know the way of things and may not even look at the date these were issued. Someone once said that finding pertinent and accurate data on the internet was like trying to fill a drinking glass from a waterfall.

Sites with spurious or out of date inforamtion. http://wiki.gridcoin.us/FAQ http://wiki.gridcoin.us/List_of_Addnodes http://wiki.gridcoin.us/Gridcoinresearch_config_file https://github.com/gridcoin/Gridcoin-master/blob/master/Gridcoin%20Addnodes.txt https://www.reddit.com/r/gridcoin/comments/2tretb/0_connections_to_the_gridcoin_network/ https://cryptocointalk.com/topic/20307-gridcoin-proof-of-research-mining-researching-support-thread/page-2 https://cryptocointalk.com/topic/20303-gridcoin-proof-of-research-connection-sync-problem-thread/ https://steemit.com/gridcoin/@erkan/howto-if-you-do-not-get-any-new-blocks-in-gridcoin https://bitcointalk.org/index.php?topic=324118.3765;imode http://coinwiki.info/en/Mining_setup

That is just 'page one' from a Google search!

[philipswift]

@Netizen78 Hi, you said you 'Tried an almost empty conf file, no connection to Boinc, empty wallet - same result.' Do you know if there was only one addnode and that was addnode=node.gridcoin.us? Thanks

[Dantali0n]

I tried syncing from latest snapshot with only one node in config being addnode=node.gridcoin.us and now it is stuck again at 854420 with many Error bad cpid messages in log.

[Netizen78]

@philipswift In my first test with a new config there was no addnode at all. Now I tried the same again with the given node - same thing, exactly as @Dantali0n describes. Right now I can't get past 854420, whatever I do.

[moisespr123]

Also, my getpeerinfo shows I'm connected to .7 clients. However, there are some that have no details at all (the last ones). I'm just using the addnodes from the wiki and listen=0 so I am just connecting to the addnodes. I currently have 8 connections which are the following:

getpeerinfo [ { "addr" : "188.79.112.66:32749", "services" : "00000001", "lastsend" : 1490785400, "lastrecv" : 1490785643, "conntime" : 1490781089, "pingtime" : 323.02270000, "pingwait" : 264.60056000, "version" : 180322, "subver" : "/Nakamoto:3.5.8.7(317.1999)/", "inbound" : false, "startingheight" : 856364, "sNeuralNetworkVersion" : "", "nTrust" : 7652, "banscore" : 0, "Neural Network" : true, "Neural Hash" : "" }, { "addr" : "35.160.210.181:32749", "services" : "00000001", "lastsend" : 1490785579, "lastrecv" : 1490785653, "conntime" : 1490781558, "pingtime" : 383.38242000, "pingwait" : 85.96596800, "version" : 180322, "subver" : "/Nakamoto:3.5.8.7(0)/", "inbound" : false, "startingheight" : 856366, "sNeuralNetworkVersion" : "", "nTrust" : 5102, "banscore" : 0, "Neural Network" : false, "Neural Hash" : "" }, { "addr" : "139.162.171.24:32749", "services" : "00000001", "lastsend" : 1490785665, "lastrecv" : 1490785541, "conntime" : 1490781854, "pingtime" : 403.34337200, "version" : 180322, "subver" : "/Nakamoto:3.5.8.7(0)/", "inbound" : false, "startingheight" : 856369, "sNeuralNetworkVersion" : "", "nTrust" : 4937, "banscore" : 0, "Neural Network" : false, "Neural Hash" : "" }, { "addr" : "40.71.210.7:32749", "services" : "00000001", "lastsend" : 1490785339, "lastrecv" : 1490785642, "conntime" : 1490782085, "pingtime" : 249.77207200, "pingwait" : 326.48081400, "version" : 180322, "subver" : "/Nakamoto:3.5.8.7(0)/", "inbound" : false, "startingheight" : 856370, "sNeuralNetworkVersion" : "", "nTrust" : 2484, "banscore" : 0, "Neural Network" : false, "Neural Hash" : "" }, { "addr" : "52.168.87.83:32749", "services" : "00000001", "lastsend" : 1490785340, "lastrecv" : 1490785644, "conntime" : 1490782103, "pingtime" : 407.25902500, "pingwait" : 325.33102300, "version" : 180322, "subver" : "/Nakamoto:3.5.8.7(0)/", "inbound" : false, "startingheight" : 856371, "sNeuralNetworkVersion" : "", "nTrust" : 842, "banscore" : 0, "Neural Network" : false, "Neural Hash" : "" }, { "addr" : "24.200.134.144:32749", "services" : "00000000", "lastsend" : 1490785015, "lastrecv" : 1490785643, "conntime" : 1490785015, "pingtime" : 0.00000000, "version" : 0, "subver" : "", "inbound" : false, "startingheight" : -1, "sNeuralNetworkVersion" : "", "nTrust" : 0, "banscore" : 0, "Neural Network" : false, "Neural Hash" : "" }, { "addr" : "96.41.240.105:32749", "services" : "00000000", "lastsend" : 1490785375, "lastrecv" : 1490785642, "conntime" : 1490785375, "pingtime" : 0.00000000, "version" : 0, "subver" : "", "inbound" : false, "startingheight" : -1, "sNeuralNetworkVersion" : "", "nTrust" : 0, "banscore" : 0, "Neural Network" : false, "Neural Hash" : "" }, { "addr" : "70.181.21.186:32749", "services" : "00000000", "lastsend" : 1490785389, "lastrecv" : 1490785449, "conntime" : 1490785389, "pingtime" : 0.00000000, "version" : 0, "subver" : "", "inbound" : false, "startingheight" : -1, "sNeuralNetworkVersion" : "", "nTrust" : 0, "banscore" : 0, "Neural Network" : false, "Neural Hash" : "" } ]

[philipswift]

Im on 854425 http://pasteboard.co/PenIdNOpe.png. Just one addnode (gridcoin.us). running getpeerinfo gives me https://pastebin.com/LixUmQKD. Maybe new nodes coming online that have not gone to 2.3.8.7 mandatory are affecting the 51%. Checking the heights on the output from getpeerinfo we have two 856387's against the wallets stated estimate of 855967 Debug is here https://pastebin.com/TLV2yh4d,

[moisespr123]

So, the error log shows BAD CPID after the Received block and the next line shows ProcessBlock FAILED... Tried running an "execute syncdpor2". Still on block 854420 even when running in INVESTOR mode.

[denravonska]

Could all this be because of when we were testing out lifting the ban of old beacons? If some of those nodes accepted the old beacon and the new block then nodes which are now running 3.5.8.7 will no longer have that beacon so they can't validate the block, right? Or is that not how it works?

[philipswift]

I don't think there is anything that end-users can do. Maybe we sit tight and carefully explore options and mull it over. Tomorrow may be the light bulb moment. Can we code so that if client is not 3.5.8.7-Mandatory [latest mandatory version]it is banned under 'banscore' or some such mechanism? This is ethical and reasonable seeing how much one node can affect another. This would force users to search/research for press releases on new mandatory holla's. If they don't put the work in, they don't get the joy out. User uptake and compliance is notoriously low in IT. Sometimes you have to force the issue and then appease with explanations, freebies and compliments! Also, maybe we should keep the media and press type releases down to minimum as in 'big fix-read all about it' then a let-down. This is all normal stuff for us but for Joe Public it can be perceived differently.

[philipswift]

Could someone consider giving Rob the heads up on a gridcoin.us DNS warning? http://dnscheck.pingdom.com/?domain=gridcoin.us&timestamp=1404366735&view=1 jomax.net is 'GoDaddy'. This may be intended of course.

[moisespr123]

@philipswift the Gridcoin website is hosted on GoDaddy. I believe that's normal.

[grctest]

I've created a snapshot of my amsterdam node, you could give that a try - I'd keep a backup of your appdata folder though to not lose any syncing progress. <Ommitted until I've got my own nodes running, sorry - 15mins tops>

If you're using linux, remember to check "ls -l" for username ownership of files, if different from the user you run the gridcoin client as do: "chown -R yourusername:yourusername *" within the appdata folder.

[roycolbert]

I have tried "grcrestarter.exe downloadblocks", "execute advertisebeacon", restarted the client several times with clean conf file and the debug log still shows this same errors below. What should I do? I am stuck on block 854420.

03/29/17 15:27:16 {SBC} new best=0406706cb9687d356149b7d99e8d5fcce7bc0e5e89f6a1c551953c601691ebf7 height=854417 ; -Researcher PPD 11510.901099 > Reference PPD 28.606965 for CPID f6a5fdbf4e0742e13e3937b68ed76739 with Lifetime Avg Mag of 114.427861, Days 0.006852

03/29/17 15:27:16 {SBC} new best=2c211aad0bb437fc7f726e8648bd12335c46938175d6c607b96b75696b7beeea height=854418 ; -Researcher PPD 9352.607143 > Reference PPD 28.654485 for CPID f6a5fdbf4e0742e13e3937b68ed76739 with Lifetime Avg Mag of 114.617940, Days 0.010741

03/29/17 15:27:17 {SBC} new best=13cc431c7e881d7dd926a493c14a9febc51fd95065545283221df281a8ed0b0d height=854419 ; -{SBC} new best=f564622e49a6fb20bb7b10bbdd4bcb34b2b17d06d6462b94c3ce01a4f26adc22 height=854420 ; -ERROR: Bad CPID : height 854420.000000, CPID a7a537ff8ad4d8fff4b3dad444e681ef, cpidv2 a7a537ff8ad4d8fff4b3dad444e681ef999642666b3a3a97379d9a9c3337686f6b673a333bc63a3e994134c7669d683a7a6f7a6b6d4172722f64706e, LBH f564622e49a6fb20bb7b10bbdd4bcb34b2b17d06d6462b94c3ce01a4f26adc22, Bad Hashboinc a7a537ff8ad4d8fff4b3dad444e681ef<|><|><|>0<|>0.00000<|>0<|><|><|>0<|>0<|>v3.5.8.7-g-research<|>9.18<|>0<|>0<|>a7a537ff8ad4d8fff4b3dad444e681ef999642666b3a3a97379d9a9c3337686f6b673a333bc63a3e994134c7669d683a7a6f7a6b6d4172722f64706e<|>8<|>SAyxEueRaSMEdXjQFhAj96qkPYDZnxrmpj<|>f564622e49a6fb20bb7b10bbdd4bcb34b2b17d06d6462b94c3ce01a4f26adc22<|>0.23<|><|><|><|><|>9.18<|>4.591481<|>0.250000<|>8.00<|>b5f38c6e782bb11dee3106173128953dff56ba6429892b03797d78ee90b0a395<|>d41d8cd98f00b204e9800998ecf8427e<|>04924981df28b7ed280adbe9375d8e36857c81766784225c9c5b608be0d4341da98770a4047ccbcbd3ac846417bb12e39c1a8900a86f7263cf9c173f2bef756278<|>MEUCIQDpiC05WgAQp6iC6Uu2yRgNci59K86LtzkbmwLjvSUuggIgY8zV+0/oZJSYauSawkW2Rc+Ie3WtUX2tNgKWClw+kqU= 03/29/17 15:27:18 ConnectBlock::Failed -

03/29/17 15:27:18 InvalidChainFound: invalid block=2fc37c1746786a156253 height=854421 trust=3275838333972824660711873320762369734724920483558585417587751775004721799679 blocktrust=1048577 date=03/27/17 04:08:16 03/29/17 15:27:18 InvalidChainFound: current best=f564622e49a6fb20bb7b height=854420 trust=3275838333972824660711873320762369734724920483558585417587751775004720751102 blocktrust=1048577 date=03/27/17 04:07:12 03/29/17 15:27:18 ERROR: SetBestChain() : SetBestChainInner failed 03/29/17 15:27:18 ERROR: AcceptBlock() : AddToBlockIndex failed 03/29/17 15:27:18 {PB}: ACC;

03/29/17 15:27:18 Received block e956f41d1809022be1fa532ae4590a5030d645bacae2412b9c95c556cd98e35b; ERROR: ProcessBlock() : already have block 854077 e956f41d1809022be1fa532ae4590a5030d645bacae2412b9c95c556cd98e35b 03/29/17 15:27:18 Received block 3b8fadeac7ed18b328321b433cf80d5fba49d1034efbfb1e0e70bd56cf5fed46; ERROR: ProcessBlock() : already have block 854078 3b8fadeac7ed18b328321b433cf80d5fba49d1034efbfb1e0e70bd56cf5fed46 03/29/17 15:27:18 Received block c8a936233d5a382a16171e6a4577e5a16d5e94f16e8e2301bb8573c0cdca66d3; ERROR: ProcessBlock() : already have block 854079 c8a936233d5a382a16171e6a4577e5a16d5e94f16e8e2301bb8573c0cdca66d3 03/29/17 15:27:18 Received block 4c4964fe7b91fb169fe4cc86a76d940af72d9131d499db2f8cd6a0d602d5aaa0; ERROR: ProcessBlock() : already have block 854080 4c4964fe7b91fb169fe4cc86a76d940af72d9131d499db2f8cd6a0d602d5aaa0 03/29/17 15:27:18 Received block e843642798e49bf861b0f0e65f36574eef7753ead7b04d2f552048a55b08a10a; ERROR: ProcessBlock() : already have block 854081 e843642798e49bf861b0f0e65f36574eef7753ead7b04d2f552048a55b08a10a 03/29/17 15:27:18 Received block d8095232b3aba53255f75d9fdded9bff208b5b89e10072b5365b5d35fa011b5a; ERROR: k() : already have block 854082 d8095232b3aba53255f75d9fdded9bff208b5b89e10072b5365b5d35fa011b5a

[moisespr123]

Ok so I downloaded the snapshot file from @grctest and it worked. Just don't copy the database folder as it may give an error when loading the wallet and it will load correctly :D

So, I'll leave this issue open as there seems to be some issues while syncing from zero or older snapshots, but using a newer snapshot does work.

[GridcoinNoob]

Left my wallet working overnight to see if it would get past 854420, and it did... But now I'm off the chain, at 854437, with a wrong hash :(

[nateonthenet]

@grctest seems to have removed the link to his updated snapshot, unfortunately.

I have the same issue as @GridcoinNoob - left the client open, and it got past 854420, but looks like it just forked itself onto a solo chain instead of correctly reorganizing. I've given up for the moment and will try again later when somebody posts a good snapshot or there's a client update that fixes this.

[moisespr123]

@nateonthenet the link works, but it seems to crash sometimes. I made a mirror of it with his permission. Here's the link: https://drive.google.com/drive/u/0/folders/0B16UEVFqxiRyV1pVSERyd2hxWlk

[nateonthenet]

@moisesmcardona @grctest No luck with this -- the client fails to validate the database (https://gyazo.com/64cfb81be53237609bdd3789a6b1f152)

[moisespr123]

@nateonthenet , Forgot to mention, delete the database folder and load the wallet. Basically copy everything except the database folder.

[nateonthenet]

@moisesmcardona Thanks -- took me a second to realize that you meant "delete your local database folder and do NOT copy the database folder from the zip file." I'm theoretically in sync - hopefully it stays that way!