Stuck on block 854887 #254

moisespr123 · 2017-03-28T21:40:34Z

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 · 2017-03-28T21:48:21Z

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

moisespr123 · 2017-03-28T21:50:21Z

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

iFoggz · 2017-03-28T21:52:30Z

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 · 2017-03-28T21:56:18Z

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 · 2017-03-28T21:58:52Z

@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 · 2017-03-28T21:59:53Z

I clean installed it since I did a clean Windows install

grctest · 2017-03-28T22:00:23Z

I clean installed it since I did a clean Windows install

Windows updates fully installed?

moisespr123 · 2017-03-28T22:00:38Z

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

moisespr123 · 2017-03-28T22:00:53Z

Synching from 0 to see if it works...

moisespr123 · 2017-03-28T22:01:00Z

Snapshot didn't help

moisespr123 · 2017-03-28T22:01:08Z

Windows 10 build 15063

MarvelWild · 2017-03-28T22:52:56Z

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 · 2017-03-28T23:17:19Z

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 · 2017-03-29T00:10:05Z

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 · 2017-03-29T00:19:00Z

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 · 2017-03-29T00:24:51Z

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 · 2017-03-29T00:27:49Z

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 · 2017-03-29T01:18:06Z

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 · 2017-03-29T01:22:59Z

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 · 2017-03-29T06:30:16Z

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 · 2017-03-29T06:49:53Z

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 · 2017-03-29T07:14:56Z

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

Quezacoatl1 · 2017-03-29T07:16:36Z

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 · 2017-03-29T07:27:15Z

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 · 2017-03-29T09:09:41Z

we just did a test:

a node X was sync yesterday on the A chain
this morning X got stuck
just allowing on X 1 peer (synced linux node L with fresh snapshot) made it stuck again at block 854420
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 · 2017-03-29T09:10:53Z

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 · 2017-03-29T09:13:55Z

@tomasbrod

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

tomasbrod · 2017-03-29T09:22:05Z

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 · 2017-03-29T09:36:58Z

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 · 2017-03-29T09:48:28Z

@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 · 2017-03-31T12:42:01Z

Delete or move everything but wallet and conf. Ensure you have unhidden, hidden files (browser>view>top toolbar to the far right>tick the box for 'show hidden files (may as well do 'show file extension names' as well). Do this with Boinc and GRC clients closed. Check in bottom tool bar or go for the all time classic!. Ctrl+Alt+Delete>Task Manager>eyeball any Boinc or GRC in CPU list>right click select it and left click 'end ?(services)'.Sorry, I'm doing this from memory and I forget it! This makes sure all files and folders are not being addressed and coming back straight after you delete or move them. Double check you are on 2.5.8.7 too :-)

dasta400 · 2017-03-31T12:51:30Z

@Netizen78 It work perfect. Now I'm synced and staking. Thanks a lot!

philipswift · 2017-03-31T13:00:36Z

Can everyone consider security please? I just read this http://www.computing.co.uk/ctg/news/3007592/dimnie-trojan-malware-targeting-open-source-developers-publishing-code-on-github?utm_medium=email&utm_campaign=CTG.Daily_RL.EU.A.U&utm_source=CTG.DCM.Editors_Updates&im_edp=protonmail.com&im_company=

tomasbrod · 2017-03-31T20:39:19Z

"Open source developer" and "Microsoft PowerShell" somehow does not go together :) @philipswift, but I feel that this diverges from the topic too much.

To all having problems with syncing: Make sure (help->about) that you are running the latest version 3.5.8.7. If it does not sync, backup your wallet, delete everything (except wallet and backups), extract the bootstrap file and restart.

Also everyone stuck on some block, please post the block number and hash (from getblockhash command).

Deviant0ne · 2017-03-31T21:11:02Z

I too am fixed up due to the snapshot. Thanks!

As an aside, prior to finding out about the 'emergency' fork, I had staked on the forked chain. That's partially how I found out about the fork, coming home and seeing I was staking like crazy (because network weight was toast). Anyway, after finally syncing on the proper chain with the snapshot I had lost about 4000 GRC. All that staked on the forked chain was gone. Including the staking coins. E.g. if staked 1350 grc for 50 POR, all of that was gone.

I almost said 'meh, live and learn' but then tried a backup of my wallet from a few weeks ago. I now have all my GRC back and on the right chain, and sync'd.

Thought I'd post this in case others staked while forked and are missing GRC as a result. Find a wallet backup and hopefully you'll have the same outcome.

HelterBelter · 2017-04-01T00:23:12Z

Just to add to the good results:
I'm on Linux (Xubuntu 16.10 x64)
had the same problem, Gridcoin (v3.5.8.7-g-research) stuck on block 855569 after starting and constantly using 100% of one CPU thread without progress.

Closed Boinc & Gridcoin
Renamed the ~/.GridcoinResearch folder to ~/.GridcoinResearch_2017-03-31
Created new ~/.GridcoinResearch folder and copied wallet.dat and gridcoinresearch.conf from the old folder
Downloaded the latest database from the Google Drive link above (was a very recent file dated same day 2017-03-31) and extracted the contents of the rar-file to my ~/.GridcoinResearch folder
Started Gridcoin

Within minutes I was sync'ed again and already received some payments I was due.

dariusz-kozlowski · 2017-04-01T06:07:45Z

I've been trying for a week now with all the methods that are mentioned everywhere (didn't try the holly water yet). Syncing gets stuck for various times at different nodes, but the fork, as compared to gridresearchcorp.com, always seems to be at 854402.

frank0051 · 2017-04-01T08:42:58Z

To echo @tomasbrod , I was stuck at this block too a couple days back. I restored from bootstrap and that solved my problem. I have traditional platter harddrive, so I had to leave my computer on overnight but overall it was a easy fix.

@dariusz-kozlowski , are you sure you are trying the bootstrap rather than the snapshot?

philipswift · 2017-04-01T12:37:20Z

@tomasbrod Re: Power shell and open source. LOL OK. But we must try to be cross platform without being systemist. Once we get fully released and the code matures we can start fighting again! :-P

fab-io · 2017-04-01T12:57:02Z

Yesterday, I've restarted from the bootstrap, and blocks advancing very slowly, so I think I'm on a fork, also because my best block (details below) hash doesn't match this one http://www.gridresearchcorp.com/gridcoin/?2d05a54aa8d68b62b1e15d12d0dcc3a18b91b0b92992c32c1737d2401fa6717a

now I don't know the status of the various forks around here, but which are the chances that my node find its way without further manual help?
I really want to see how much the network is resilient.

getblockbynumber 854777
{
    "hash" : "9415a6e56c11395611c4af5a6407c64216b33524a1b65faaaf27291e6088e2e3",
    "confirmations" : 1,
    "size" : 1153,
    "height" : 854777,
    "version" : 7,
    "merkleroot" : "ba53dac57b66f2e3a808c99618527f9259ecd868928cd1d59dfc9024c7797743",
    "mint" : 1.78990124,
    "time" : 1491050320,
    "nonce" : 3742,
    "bits" : "1e0f028b",
    "difficulty" : 0.00026024,
    "blocktrust" : "110e2c",
    "chaintrust" : "73e0f0cf86557b2bb40f58d5b9d39693c2c893c4fe568da6971719020919aad",
    "previousblockhash" : "10bc1973ad2cd95a2fe25391171fe6b8510c6b5f7a912b01d2223d1d4d20ae4f",
    "flags" : "proof-of-stake proof-of-research",
    "proofhash" : "36fa0fd380aba8bb5ede0f9926da43405c411bcae4f194ab8bb18f776440dac7",
    "entropybit" : 1,
    "modifier" : "da8932ab7997d8e7",
    "modifierchecksum" : "afdfa2fd",
    "tx" : [
        "13d4fe19adff47fa8404b652b3d16f02620d62cd49c1ec4e05ed606a6a1d6ab5",
        "b94f42290226d4e08f2e5716dd91603f3172c0074e8290fd270332199abff43a"
    ],
    "signature" : "304402205a5bf13bc97394f62de98183a84d0b980a3f22ea4cdca12c546ef23b29aa1c1e022038043d578f76e48a8193a00314eb80e1827ca4edd309a7259c3501ebfb7d5233",
    "CPID" : "5786fd54a1e774eff07735d52bd8e82e",
    "Magnitude" : 40.00000000,
    "LastPaymentTime" : "04-01-2017 09:46:24",
    "ResearchSubsidy" : 1.11000000,
    "ResearchAge" : 0.11870400,
    "ResearchMagnitudeUnit" : 0.25000000,
    "ResearchAverageMagnitude" : 37.50000000,
    "LastPORBlockHash" : "1876748498d6a1260015ef2579f09704d25b4e3a61b4b9610c86d1b63173f312",
    "Interest" : 0.68000000,
    "GRCAddress" : "S5vFKh3zo1ZFXNU9jfdpyAexZ8HKQX5Kj1",
    "BoincPublicKey" : "0453ba3864aff3c683357d2038446f4e26b9ec805d00974502906207cebd7f2fdf8d064eafb76fc2797dde2a0c8c8d62140c5eb30bb7adeda35eece2772e143d30",
    "BoincSignature" : "MEUCIQDQ/F8zHNKaEoLHrr78umht4d7dvjy85QM4jxtTSIew/AIgCWWaKHEsTZv1V7FvIac6HQ+bmsZS+cFZ/3jSFJ30/Lc=",
    "SignatureValid" : true,
    "ClientVersion" : "v3.5.8.7-g-research",
    "CPIDv2" : "5786fd54a1e774eff07735d52bd8e82e",
    "CPIDValid" : true,
    "NeuralHash" : "",
    "IsSuperBlock" : 0,
    "IsContract" : 0
}

iFoggz · 2017-04-01T14:40:46Z

@fab-io you try the unofficial snapshot like other users have in this thread? if u did apply the unofficial snap shot did u delete the database folder after you extracted?

dariusz-kozlowski · 2017-04-01T14:40:55Z

thank you @frank0051, I'm pretty sure.
I've followed the steps here: https://steemit.com/gridcoin/@erkan/stuck-in-gridcoin-3-5-8-7-inofficial-snapshot-file-available, the better option - bootstrap
got the bootstrap.dat in my folder, cleaned all neccessary files/folders (it's a drill already, believe me) and started the client
after 6 hours (i7-3770K 4.1Ghz) I'm stuck at 854783, so its not even close to what the post promises: 856625.
the debug log may reveal some things for somebody who knows the code well:
after start, I have a nice list of lines reporting new blocks:
04/01/17 06:28:27 {SBC} new best=000000023d3f20931746052068cc9c311dfc7e7dc031f2f71472b72b5614dd37 height=104 ; {PB}: ACC;

this goes smoothly with the increasing block number until 854400, then a dash is added in front of {SBC}, so something is changed:
04/01/17 09:09:33 {SBC} new best=9a1eb378984c8e6c7f271cfd15feafc04640beb7100445dbca4549468f5b341e height=854400 ; {PB}: ACC; 04/01/17 09:09:33 -{SBC} new best=cfd01316377ded290de87c5dce2652cbfb22b65dbb54f76b860205b8701d907b height=854401 ; {PB}: ACC;

Then a well known block number comes 854420 and the fun begins:
04/01/17 09:09:34 -{SBC} new best=f564622e49a6fb20bb7b10bbdd4bcb34b2b17d06d6462b94c3ce01a4f26adc22 height=854420 ; {PB}: ACC; 04/01/17 09:09:34 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= 04/01/17 09:09:34 ERROR: ProcessBlock() : CheckBlock FAILED

Also, I tried with different config files, this one is only with a single node:
addnode=node.gridcoin.us

The one thing that I have not tried yet (no, not the water), is to re-install the gridcoin from scratch. The only file which changed after the client update through grcrestarter (based on the file date) is the gridcoinresearch.exe. Can anybody confirm if this is correct?

A comment which @denravonska made earlier worries me a little: this could be a result of a test conducted on the live chain? It sounds like it would make sense though. Most of us have problems with cpid-s.

iFoggz · 2017-04-01T14:46:07Z

@dariusz-kozlowski only thing ive seen users have issues with its the database folder not being deleted after causing this.

philipswift · 2017-04-01T14:59:36Z

'Inofficial' is not an English word. It should be 'unofficial'.

tomasbrod · 2017-04-01T16:00:50Z

ON TESTNET
I can't get past 224278 on my testnet node due to this infamous "Bad CPID" error. Hashes for few last blocks are below, could anybody check where I diverged?
Self-built from e7108ab, a7ecba6, 5e28c03, and c7b1b22 merged.

224278 6852ce82de558ec7458a227ef4eb52149cade76d6d92ccd500ec8ecd8b27a4ce
224277 395f684ff6f8d5a83f9e1ca79e2010e5aa6a3cf9bed5206e06dfef842d42489f
224276 f2da6a45c01e575099ba31c07b29f6456f2f622e673ab39cb75d124fa4f1554d
224275 d219befdb7cf58e32729271aad866b66c97d1d3427a9f531656056e47316978f
224274 6ca0af95fb58d1624b94a930b1031288cca1af601f19914c523a8c4a0e5066ee
224250 92104e85d7d3c4970159e5e56604df35740961b7b89aaa0fa814ed30d71f2291
224200 7ca89e4bf1c3c05bfbde7200a1108db3b41ef37d8ecb104d24fd5caa08fccc62
224180 10ec25195f74b977584e34700186766278eafd360d75da1eb53956166d4da6da

(hashes optained with getblockhash command, please do the same when reporting) And one of the errors:

Received block 44f2eb19c9a83bc8ffff446fda2ea71034ce6f7de3dc0e263093c1b264fe9f5a; ERROR: Bad CPID : height 224278,000000, CPID 9ce6f19e20f69790601c9bf9c0b03928, cpidv2 9ce6f19e20f69790601c9bf9c0b03928c73b6c996b6c35336c9b96c89791c79c623e3c38959b66996d3d9962696691336837766c3236417471626e6370682f64706e, LBH 31a8d1c8c12805f5890ca03fd600695009a3034f459298cd7fbe8fdd380cbd51, Bad Hashboinc 9ce6f19e20f69790601c9bf9c0b03928<|><|><|>0<|>0.00000<|>0<|><|><|>0<|>0<|>v3.5.8.6-g-research<|>0.79<|>1489911456<|>0<|>9ce6f19e20f69790601c9bf9c0b03928c73b6c996b6c35336c9b96c89791c79c623e3c38959b66996d3d9962696691336837766c3236417471626e6370682f64706e<|>155<|>n3C1AM2myBdfhKjWegutHCEJBSXxyTBsa2<|>31a8d1c8c12805f5890ca03fd600695009a3034f459298cd7fbe8fdd380cbd51<|>0.03<|><|><|>038aa911ad11016605379796ef8103bb<|><|>0.79<|>0.040556<|>0.125000<|>155.00<|>edd211ad5f37175885db20fbbc93e36c8575af4547184d5bc714c7c8ceb2f266<|>038aa911ad11016605379796ef8103bb<|>044574967c97c9b2f4a9899c775ab78dd5451485a62a2b420b2f97c6e8f74def1a542b5d97e17fc4359d56a6ec677aca98e8b15690ea719ba1b38d93f64e9a2e3f<|>MEQCIHVjR7i67GgYQYWyqJBQyBxsh2/sfXr0EjLrjEIo0uA5AiA9btSIIScHncShnnTNNQB/nw4NwF/6S7qZtoyziy35HA== ERROR: ProcessBlock() : CheckBlock FAILED

fab-io · 2017-04-01T19:40:21Z

Yes @Foggyx420 I've deleted the files and folders as said in the guide, then I've restarted from the bootstrap file. My understanding is that using the bootstrap file has the same effect of the snapshot, only safer.
Now I'm at block 854964, hash
b1bbb8d3fc316fd4cee198fee9de3b495faa113086bed23cee555d71087aa446

edit: I'm doing it again, this time moving also wallet.dat in another location because I've staked on the fork.

iFoggz · 2017-04-01T19:51:52Z

@fab-io how long you been stuck there and for the hash you mentioned it doesnt match with me as the hash for that block should be 854964 --> fed7258c4d44e6beebd799b42527ccc84bf34cd0dc8b177181f9476fac07af67 --

im not to fimular with the boot strap procedure only the snap shot. perhaps someone has something to add to this.

fab-io · 2017-04-01T20:02:59Z

Actually I was not stuck but slowly advancing on the fork.
Just started again with the bootstrap after moving the wallet in a safe location, let's see what happens tomorrow morning

tomasbrod · 2017-04-01T21:18:25Z

@fab-io Please, to help debug the problem, save the datadir where you are on the fork and if you can post some of the hashes and try to find where the hashes start diverge. You can use https://gridcoinstats.eu/block.php?id=854964 to check (replace the with your block number).

matthew11 · 2017-04-02T00:56:43Z

Mine diverges at block 854402
For 854401 I have 'cfd01316377ded290de87c5dce2652cbfb22b65dbb54f76b860205b8701d907b' which is the same of the blockhash displayed by the gridcoinstats.

However, on block 854402 I have the following blockhash: 'd98328744e3fd4ddf8699c302922c97589a4066e28e0ca7483c2492444c5b3c1' which is different from 'e2a95c4040104a316b9e4e3dbb3dedb4487c5f1c9e59d6689aa6fdd2a8d5cd1b'

So I'm definitely on a fork. I have resynced the whole database just before the .7 released. Maybe it is time for a full resync again? (I refuse to use snapshot, because the network itself should be the only authentic source of the blockchain) I can provide my database if you are interested in.

jimbo-slice · 2017-04-02T01:28:21Z

I used the unofficial snapshot to get into sync two days ago.

I am now stuck on 859238. The hash for this block matches the hash on http://www.gridresearchcorp.com/. I also currently have 11 connections to the network, my addnodes are up to date, and I've rebooted the client a few times already. If someone wants to look at the debug files, or other files, let me know.

I know many people are stuck. I'm just posting this because I didn't come across any as recent as 859238.

denravonska · 2017-04-02T05:51:28Z

@matthew11 885402 seems to be created with one of those out of reach beacons.

        Block  Time       Now
--------------------------------------
Stuck  854402 1490568144 1491111620
Beacon 670652 1474230055 
Diff   183750   16338089   16881565

Max time for a beacon is age is 150000 blocks in .6 and 15552000 seconds in .7. This block falls out of both those limits.

@jimbo-slice Are you still stuck on 859238 (trying to get 859239?)?

jimbo-slice · 2017-04-02T06:16:57Z

@denravonska

I was still stuck about an hour ago when I closed out of the wallet. I'm restarting it right now to check. I'm tempted to just use another (newer) snapshot, but I'd like to figure out why this is happening.

edit: yes, still seems to be stuck. magnitude has dropped to 0 as well.
edit 2: and yes, that is correct. i currently have 859238, trying to get to 859239.
edit 3: same block that 'lennstar' is stuck on: https://cryptocointalk.com/topic/1331-new-coin-launch-announcement-grc-gridcoin/?p=236384

iFoggz · 2017-04-02T06:29:32Z

my wallet stil in sync and running well but did notice a debug.log message i thought was a little out of the oridinary.
Last staked block found at height 597796.000000, but cannot verify magnitude older than 6 months!

my client staking fine and normal blocks so i dont know what that is about or if that helps the devs. its not affecting my client getting good blocks but just seemed odd

philipswift · 2017-04-02T06:29:42Z

@matthew11 5 up, 'the network itself should be the only authentic source of the blockchain'
I concur.
@denravonska 3 up, '885402' should read '854402'

fab-io · 2017-04-02T08:14:54Z

I'm quite puzzled right know, after restarting from scratch with the bootstrap file, I'm again on a fork, searching for the blocks that diverges, I've found that according to Gridcoinstats.eu the block 854421 diverges:
https://gridcoinstats.eu/block.php?id=854421
https://gist.github.com/fab-io/917acb735180f59e308df240559e83b6

Is there anything special in this block?

BTW this other explorer is on another fork http://www.gridresearchcorp.com/gridcoin/?a5674851401fceef07bbf47c881d87a6c6b24d024f6cf85a99f09df65ed21e90

while Gridcoin Asia is aligned with Gridcoinstats
http://explorer.gridcoin.asia/block/2fc37c1746786a156253bcd869fe0372f244b16b6ceb5a5dab60a534373adfe8

which is the explorer that you trust more?
and more important which is the longest chain at the moment?
I don't yet know a way to discover the different chains that my node is seeing, any suggestion?

denravonska mentioned this issue Mar 31, 2017

Fix nodes getting stuck syncing #256

Merged

denravonska mentioned this issue Apr 1, 2017

Nodes sending bad blocks should be punished #258

Closed

gridcoin closed this as completed in #256 Apr 2, 2017

skcin mentioned this issue Sep 22, 2017

[CLOSED] 25k GRC bounty -> finding additional root causes & delivering solutions (e.g. users being out-of-sync) gridcoin-community/Gridcoin-Tasks#101

Closed

Stuck on block 854887 #254

Stuck on block 854887 #254

Comments

moisespr123 commented Mar 28, 2017

grctest commented Mar 28, 2017

moisespr123 commented Mar 28, 2017

iFoggz commented Mar 28, 2017

grctest commented Mar 28, 2017

iFoggz commented Mar 28, 2017

moisespr123 commented Mar 28, 2017

grctest commented Mar 28, 2017

moisespr123 commented Mar 28, 2017

moisespr123 commented Mar 28, 2017

moisespr123 commented Mar 28, 2017

moisespr123 commented Mar 28, 2017

MarvelWild commented Mar 28, 2017 • edited

GridcoinNoob commented Mar 28, 2017

Deviant0ne commented Mar 29, 2017

grctest commented Mar 29, 2017

Deviant0ne commented Mar 29, 2017

Deviant0ne commented Mar 29, 2017

philipswift commented Mar 29, 2017 • edited

GridcoinNoob commented Mar 29, 2017

GridcoinNoob commented Mar 29, 2017 • edited

Netizen78 commented Mar 29, 2017 • edited

nateonthenet commented Mar 29, 2017 • edited

Quezacoatl1 commented Mar 29, 2017

Netizen78 commented Mar 29, 2017

Erkan-Yilmaz commented Mar 29, 2017 • edited

tomasbrod commented Mar 29, 2017

Erkan-Yilmaz commented Mar 29, 2017

tomasbrod commented Mar 29, 2017

Erkan-Yilmaz commented Mar 29, 2017

skcin commented Mar 29, 2017

philipswift commented Mar 31, 2017 • edited

dasta400 commented Mar 31, 2017

philipswift commented Mar 31, 2017

tomasbrod commented Mar 31, 2017

Deviant0ne commented Mar 31, 2017

HelterBelter commented Apr 1, 2017

dariusz-kozlowski commented Apr 1, 2017

frank0051 commented Apr 1, 2017 • edited

philipswift commented Apr 1, 2017

fab-io commented Apr 1, 2017

iFoggz commented Apr 1, 2017

dariusz-kozlowski commented Apr 1, 2017

iFoggz commented Apr 1, 2017

philipswift commented Apr 1, 2017

tomasbrod commented Apr 1, 2017

fab-io commented Apr 1, 2017 • edited

iFoggz commented Apr 1, 2017

fab-io commented Apr 1, 2017

tomasbrod commented Apr 1, 2017

matthew11 commented Apr 2, 2017

jimbo-slice commented Apr 2, 2017 • edited

denravonska commented Apr 2, 2017 • edited

jimbo-slice commented Apr 2, 2017 • edited

iFoggz commented Apr 2, 2017

philipswift commented Apr 2, 2017 • edited

fab-io commented Apr 2, 2017

MarvelWild commented Mar 28, 2017 •

edited

philipswift commented Mar 29, 2017 •

edited

GridcoinNoob commented Mar 29, 2017 •

edited

Netizen78 commented Mar 29, 2017 •

edited

nateonthenet commented Mar 29, 2017 •

edited

Erkan-Yilmaz commented Mar 29, 2017 •

edited

philipswift commented Mar 31, 2017 •

edited

frank0051 commented Apr 1, 2017 •

edited

fab-io commented Apr 1, 2017 •

edited

jimbo-slice commented Apr 2, 2017 •

edited

denravonska commented Apr 2, 2017 •

edited

jimbo-slice commented Apr 2, 2017 •

edited

philipswift commented Apr 2, 2017 •

edited