Skip to content
This repository has been archived by the owner on Sep 5, 2020. It is now read-only.

MIST 0.7.4 "Waiting for blocks" for a long period of time #654

Closed
FaguiCurtain opened this issue May 18, 2016 · 3 comments
Closed

MIST 0.7.4 "Waiting for blocks" for a long period of time #654

FaguiCurtain opened this issue May 18, 2016 · 3 comments

Comments

@FaguiCurtain
Copy link

FaguiCurtain commented May 18, 2016

I am running MIST 0.7.4 (updated this morning) on MacOS X 10.11.4 (El Capitan)

same problem, cannot sync. I bought some DAO tokens like many people.

on the Github HP, it says,

If you still have the "Invalid Date" error or is stuck at "Waiting for blocks" for a long period of time, then you might have a corrupted database and might need to sync it again. Go to your Ethereum folder (access it via accounts > backup > accounts), delete (or simply rename) the folder chain data and start the app again.

my questions:

  1. how do i delete the watch token ???

  2. where exactly is the folder chain data ? should i use the terminal to do that ?

  3. i have already some version of geth on my Mac. How do i update it with brew ?

the instructions on github only explain to do an install from zero.
should i erase everything and reinstall or is there some other way? how about the keystore files in that process ? and about the passwords ?

thank you

log from MIST 0.7.4

...rie error: Missing trie node 19a4a47639ea2c5fcd0b0c4a6bf02c70dd366f86b53bb4498b4fa1869f5d0158
E0518 17:06:33.990014 trie/secure_trie.go:74] Unhandled trie error: Missing trie node 19a4a47639ea2c5fcd0b0c4a6bf02c70dd366f86b53bb4498b4fa1869f5d0158
E0518 17:06:33.991759 trie/secure_trie.go:74] Unhandled trie error: Missing trie node 4d0c25cd380358ee29de7c193941080b62d7bcb870cc2bfb124eb9a853ce0336
E0518 17:06:33.992005 trie/secure_trie.go:74] Unhandled trie error: Missing trie node 4d0c25cd380358ee29de7c193941080b62d7bcb870cc2bfb124eb9a853ce0336
E0518 17:06:33.993254 trie/secure_trie.go:74] Unhandled trie error: Missing trie node c08fc342e983f8bde27ca6df83dfeae657dc99d0bd44040b0bfea41aacee9b2c
E0518 17:06:33.993470 trie/secure_trie.go:74] Unhandled trie error: Missing trie node c08fc342e983f8bde27ca6df83dfeae657dc99d0bd44040b0bfea41aacee9b2c
E0518 17:06:33.994016 trie/secure_trie.go:74] Unhandled trie error: Missing trie node 0d891815bf449152cf7144137fc2f9498029f13e736416eacd8d42590bb55069
@luclu
Copy link
Contributor

luclu commented May 18, 2016

The chaindata-folder is located under ~/Library/Ethereum/please delete this one as you seem to have a corrupted chain-replica geth is not able to recover. (as answered to you on this thread #636)

As for 1. and 2. I answer you on this thread #616.

I will close this for now.

@luclu luclu closed this as completed May 18, 2016
@luclu
Copy link
Contributor

luclu commented May 19, 2016

I am running MIST 0.7.4 (updated this morning) on MacOS.
same problem, cannot sync. I bought some DAO tokens like many people.

on the Github HP, it says,

If you still have the "Invalid Date" error or is stuck at "Waiting for blocks" for a long period of time, then you might have a corrupted database and might need to sync it again. Go to your Ethereum folder (access it via accounts > backup > accounts), delete (or simply rename) the folder chain data and start the app again.

my questions:

  1. how do i delete the watch token ???
  2. where exactly is the folder chain data ? should i use the terminal to do that ?

thank you

You might want to unwatch (delete) "The DAO"-Contract for now.

how do we unwatch it please ? whats the command on geth ?

@FaguiCurtain hover over the token and click on the trash-bin-symbol.

luclu, i've updated to 0.7.4 and reinstalled GETH on my MacOS
I deleted the chaindata, and restarted it.
now my wallet is stuck at block 1,464,740 and i saw a popup from my AV software (AVAST) telling me something is corrupted with geth, and looks like some files have been quarantined.

here is the log when i restarted and launched geth
arted
I0519 15:08:01.673995 core/blockchain.go:959] imported 2 block(s) (0 queued 0 ignored) including 27 txs in 1.129941113s. #1467644 [0f8ed070 / 331482ad]
I0519 15:08:05.871338 core/blockchain.go:959] imported 10 block(s) (0 queued 0 ignored) including 27 txs in 251.332304ms. #1467654 [5e70d4eb / eb3a7b21]
I0519 15:08:11.545979 core/blockchain.go:959] imported 215 block(s) (0 queued 0 ignored) including 1086 txs in 5.43845346s. #1467869 [82176fb0 / 5d2dc8da]
I0519 15:08:13.013530 core/blockchain.go:959] imported 64 block(s) (0 queued 0 ignored) including 195 txs in 1.467108197s. #1467933 [0aff469e / 39b4efd3]
E0519 15:08:13.136338 trie/secure_trie.go:74] Unhandled trie error: Missing trie node 37f87e784b793d1897e146196fc9d3b122cab868110ea978c03dc30a4d73e1e0
E0519 15:08:13.136524 trie/secure_trie.go:74] Unhandled trie error: Missing trie node 37f87e784b793d1897e146196fc9d3b122cab868110ea978c03dc30a4d73e1e0
E0519 15:08:13.136702 trie/secure_trie.go:74] Unhandled trie error: Missing trie node 37f87e784b793d1897e146196fc9d3b122cab868110ea978c03dc30a4d73e1e0
E0519 15:08:13.137623 trie/secure_trie.go:74] Unhandled trie error: Missing trie node f59fd29ce660c250c35a0aabef683e531a2cad985f1b0f01b4bc77741000af6c
E0519 15:08:13.137752 trie/secure_trie.go:74] Unhandled trie error: Missing trie node f59fd29ce660c250c35a0aabef683e531a2cad985f1b0f01b4bc77741000af6c
E0519 15:08:13.137876 trie/secure_trie.go:74] Unhandled trie error: Missing trie node f59fd29ce660c250c35a0aabef683e531a2cad985f1b0f01b4bc77741000af6c
E0519 15:08:13.143272 trie/secure_trie.go:74] Unhandled trie error: Missing trie node d1616f5329662ef5e82f6c212fb3c1392c13432cd8f28b617958a220a82d7519
E0519 15:08:13.143428 trie/secure_trie.go:74] Unhandled trie error: Missing trie node

@FaguiCurtain please look here: #573
I will start to delete your posts hijacking other threads tonight. Please come join the gitter-channel, that's a better way to communicate and solve your problems.

@lock
Copy link

lock bot commented Apr 1, 2018

This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread.

@lock lock bot locked and limited conversation to collaborators Apr 1, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants