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

Ethereum Wallet gets stuck on sync #2595

Closed
califa opened this issue Jun 22, 2017 · 90 comments
Closed

Ethereum Wallet gets stuck on sync #2595

califa opened this issue Jun 22, 2017 · 90 comments
Labels
v0.8.10

Comments

@califa
Copy link

califa commented Jun 22, 2017

System information

Version: Ethereum Wallet 0.8.10
OS & Version: OS X 10.12.5 (Sierra)
Node type: Geth 1.6.5 (default)

I've tried to delete the chaindata folder and start over 3 times now, but every time the sync process gets started on a seemingly random block. I'm not sure what's up or how to resolve this.

image

Not sure if this is related, but Cmd-Q or closing it down doesn't seem to work (it just adds a message "Checking network..." and stays open) and I've had to kill the process to shut it down.

Here's the console:

image

And the log files:

logfiles.zip

Any ideas? Thanks!
@spoikonen
Copy link

My sync has been extremely slow (and inconsistent) since yesterday. --fast and --cache=1024 haven't seemed to help. I've been stuck on the same block for an hour now. It just says Downloading Block 3,xxx,xxx out of 3,913,622.

@IvanM1993
Copy link

I have the same situation, the new blocks are downloaded quickly, and then for a very long time looking for peers for a few hours. What can be the reason?

@Sylk
Copy link

Sylk commented Jun 22, 2017

Same issue here... What's going on someone help us out.

@j-chimienti
Copy link

Same issue here. Been stuck around 1.5 - 1.7 m blocks last 2 days

@nicoleta31
Copy link

same issue. is anyone helping? is not possible to wait 2-3 or more days just to have the wallet up to date.

@eldadwasserman
Copy link

very simple, some hackers of the big companies what to block the individuals and to force them to use "online" wallets.

But they are stupids, in this way millions of people will go to bitcoin and other virtual currencies.

Just bunch of Idiots.

@solarin
Copy link

solarin commented Jun 23, 2017 •
edited
Loading

I had the same problem on 3 different PCs.
My issue was that geth suddenly crashes when started in background by the Ethereum Wallet application. You can verify this from the Task Manager: when you start Ethereum Wallet, you will notice that also geth is started and after a few minutes, it will disappear (probably crashing).

My solution was to close Ethereum Wallet and start geth from its directory which you can reach from the etherem wallet menu Account->Backup->Applicative Data and then, once the file explorer shows up, "binaries\Geth\unpacked\geth.exe".
now let it be until you see that it adds a line every 30 seconds.
Press CTRL C and re-open Ethereum Wallet.

However, geth will continue to disappear, but once the blockchain is synchronized, you can just close and reopen the Ethereum Wallet.

hope it helps

@solarin solarin mentioned this issue Jun 23, 2017
Closed
@califa
Copy link
Author

califa commented Jun 24, 2017

@solarin do you have similar advice for OS X? I'm running geth in the background and it's giving me issues:

image

INFO [06-23|22:36:33] Allocated cache and file handles         database=/Users/joel/Library/Ethereum/geth/chaindata cache=128 handles=1024
INFO [06-23|22:36:33] Initialised chain configuration          config="{ChainID: 1 Homestead: 1150000 DAO: 1920000 DAOSupport: true EIP150: 2463000 EIP155: 2675000 EIP158: 2675000 Metropolis: 9223372036854775807 Engine: ethash}"
INFO [06-23|22:36:33] Disk storage enabled for ethash caches   dir=/Users/joel/Library/Ethereum/geth/ethash count=3
INFO [06-23|22:36:33] Disk storage enabled for ethash DAGs     dir=/Users/joel/.ethash                      count=2
INFO [06-23|22:36:33] Initialising Ethereum protocol           versions="[63 62]" network=1
INFO [06-23|22:36:33] Loaded most recent local header          number=766837 hash=ac48ae…e821e8 td=4846919864801191634
INFO [06-23|22:36:33] Loaded most recent local full block      number=0      hash=d4e567…cb8fa3 td=17179869184
INFO [06-23|22:36:33] Loaded most recent local fast block      number=761344 hash=98c446…44ecc0 td=4799615785073116761
INFO [06-23|22:36:33] Starting P2P networking 
INFO [06-23|22:36:35] Mapped network port                      proto=udp extport=30303 intport=30303 interface="UPNP IGDv2-IP1"
INFO [06-23|22:36:35] UDP listener up                          self=enode://12749cacc6227c63e7c2a167c0a0d862dfe1ffab2cb3bdbceae49ad6485217a34bf8f74afcf3a6eb4d80fa87a4182a3219d414c456ff94b702ccf1106756c4d9@24.90.4.73:30303
INFO [06-23|22:36:35] RLPx listener up                         self=enode://12749cacc6227c63e7c2a167c0a0d862dfe1ffab2cb3bdbceae49ad6485217a34bf8f74afcf3a6eb4d80fa87a4182a3219d414c456ff94b702ccf1106756c4d9@24.90.4.73:30303
INFO [06-23|22:36:35] IPC endpoint opened: /Users/joel/Library/Ethereum/geth.ipc 
INFO [06-23|22:36:35] Mapped network port                      proto=tcp extport=30303 intport=30303 interface="UPNP IGDv2-IP1"
INFO [06-23|22:36:45] Block synchronisation started 
WARN [06-23|22:36:55] Synchronisation failed, retrying         err="block download canceled (requested)"
INFO [06-23|22:36:58] Imported new state entries               count=1 flushed=0 elapsed=997.892µs processed=1 pending=17 retry=0 duplicate=0 unexpected=0
INFO [06-23|22:36:58] Imported new state entries               count=2 flushed=0 elapsed=1.030ms   processed=3 pending=49 retry=2 duplicate=0 unexpected=0
INFO [06-23|22:36:58] Imported new state entries               count=5 flushed=0 elapsed=4.732ms   processed=8 pending=129 retry=0 duplicate=0 unexpected=0
INFO [06-23|22:36:59] Imported new state entries               count=33 flushed=0 elapsed=13.850ms  processed=41 pending=657 retry=3 duplicate=0 unexpected=0
INFO [06-23|22:36:59] Imported new state entries               count=215 flushed=0 elapsed=75.819ms  processed=256 pending=4088 retry=2 duplicate=0 unexpected=0
INFO [06-23|22:36:59] Imported new state entries               count=78  flushed=0 elapsed=22.824ms  processed=334 pending=5336 retry=0 duplicate=0 unexpected=0
INFO [06-23|22:36:59] Imported new block headers               count=0   elapsed=4.224ms   number=761536 hash=802579…262ac1 ignored=192
INFO [06-23|22:36:59] Imported new state entries               count=384 flushed=0 elapsed=281.100ms processed=718 pending=10624 retry=2 duplicate=0 unexpected=0
INFO [06-23|22:37:00] Imported new state entries               count=1   flushed=0 elapsed=92.737µs  processed=719 pending=10627 retry=1 duplicate=0 unexpected=0
INFO [06-23|22:37:00] Imported new state entries               count=5   flushed=0 elapsed=4.320ms   processed=724 pending=10626 retry=1 duplicate=0 unexpected=0
WARN [06-23|22:37:00] Node data write error                    err="leveldb/table: corruption on data-block (pos=770870): checksum mismatch, want=0x53d75c8e got=0x1a62c72c [file=003843.ldb]"
WARN [06-23|22:37:00] Synchronisation failed, retrying         err="leveldb/table: corruption on data-block (pos=770870): checksum mismatch, want=0x53d75c8e got=0x1a62c72c [file=003843.ldb]"
INFO [06-23|22:37:03] Imported new state entries               count=0   flushed=0 elapsed=788.485µs processed=724 pending=1     retry=1 duplicate=0 unexpected=252
INFO [06-23|22:37:03] Imported new state entries               count=1   flushed=0 elapsed=288.474µs processed=725 pending=17    retry=0 duplicate=0 unexpected=252
INFO [06-23|22:37:03] Imported new state entries               count=16  flushed=0 elapsed=4.207ms   processed=741 pending=273   retry=0 duplicate=0 unexpected=252
INFO [06-23|22:37:04] Imported new state entries               count=256 flushed=0 elapsed=69.156ms  processed=997 pending=4369  retry=0 duplicate=0 unexpected=252
INFO [06-23|22:37:04] Imported new state entries               count=384 flushed=0 elapsed=125.867ms processed=1381 pending=10488 retry=0 duplicate=0 unexpected=252
INFO [06-23|22:37:05] Imported new state entries               count=384 flushed=0 elapsed=434.040ms processed=1765 pending=15158 retry=0 duplicate=0 unexpected=252
INFO [06-23|22:37:05] Imported new state entries               count=1   flushed=0 elapsed=2.199ms   processed=1766 pending=15173 retry=3 duplicate=0 unexpected=252
INFO [06-23|22:37:05] Imported new state entries               count=384 flushed=0 elapsed=48.109ms  processed=2150 pending=16151 retry=0 duplicate=0 unexpected=252
WARN [06-23|22:37:05] Node data write error                    err="leveldb/table: corruption on data-block (pos=770870): checksum mismatch, want=0x53d75c8e got=0x1a62c72c [file=003843.ldb]"
INFO [06-23|22:37:05] Imported new block headers               count=0   elapsed=26.812ms  number=761920 hash=4bf4a0…45a0cc ignored=576
WARN [06-23|22:37:05] Synchronisation failed, retrying         err="leveldb/table: corruption on data-block (pos=770870): checksum mismatch, want=0x53d75c8e got=0x1a62c72c [file=003843.ldb]"
WARN [06-23|22:37:05] Synchronisation failed, dropping peer    peer=0a6dc852bc2469a0 err="action from bad peer ignored"
WARN [06-23|22:37:06] Synchronisation failed, dropping peer    peer=499b5debd0a7c5db err="action from bad peer ignored"
INFO [06-23|22:37:20] Imported new block headers               count=0   elapsed=53.057ms  number=762304 hash=d1d9de…9ff234 ignored=960
INFO [06-23|22:37:21] Imported new block headers               count=0   elapsed=24.873ms  number=762880 hash=01b42d…e983ef ignored=576
CRIT [06-23|22:37:24] Failed to store block body               err="leveldb/table: corruption on data-block (pos=770870): checksum mismatch, want=0x53d75c8e got=0x1a62c72c [file=003843.ldb]"```

@califa
Copy link
Author

califa commented Jun 24, 2017

Deleted chaindata and ran it again. This time it failed on another block. Really not sure what's happening.

logout
Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.

@Arthur111
Copy link

Arthur111 commented Jun 24, 2017 •
edited
Loading

I started on Monday and it was extremely slow like explained above. I delete all eth* on all my disks. Restart ... let it run ... (with --fast --cache 1024 saw in "ps -ax") and today ... 5 days later ... (until 20 mn per block sometimes) it is written "1 553 897 block left". Its slow but blocks are processed.
So i think it will finish at the middle of next week. (I share my 30303 port). The only thing interesting i found is this : https://ethereum.stackexchange.com/questions/9883/why-is-my-node-synchronization-stuck-extremely-slow-at-block-2-306-843 and not "some hackers of the big companies".

@Salmen2
Copy link

Salmen2 commented Jun 24, 2017

It is very slow and at a some point it won't sync anymore though there are active peers connection.

@solarin
Copy link

solarin commented Jun 24, 2017

jcalifa, unfortunately I didn't try on OS X, one question: how many free GBs do you have?

@zboneh
Copy link

zboneh commented Jun 24, 2017

tried for week same problem, can I get my ether sent back to coin base?
TxHash: 0xeb8194034103199574ad8c10bb5c4be31e13530a2f8194d3e2107fb623b9c47a

Block Height: 3764170 (158308 block confirmations)

TimeStamp: 30 days 2 hrs ago (May-25-2017 07:58:56 AM +UTC)

From: 0xfb50195f39be7f7b71f712ed5baa0374f3abe809

To: 0x0ea415b4574f5204ebea642dd9430967a35b70a6

Value: 4.17 Ether ($1,360.59)

Gas Limit: 90000

Gas Price: 0.00000002 Ether (20 Gwei)

Gas Used By Txn: 21000

Actual Tx Cost/Fee: 0.00042 Ether ($0.14)

Cumulative Gas Used: 1318761

Nonce: 0
And I also tried to buy direct from wallet............................

TxHash: 0x867188bf8b6f0ad6843a88c3222739acfa5a301ae7389a1f18e32e45ab1fd74a

Block Height: 3766241 (156264 block confirmations)

TimeStamp: 29 days 17 hrs ago (May-25-2017 05:02:23 PM +UTC)

From: 0x6d20885d201297bcb0ad503071540262fa686679

To: 0ea415b4574f5204ebea642dd9430967a35b70a6

Value: 0.25777091 Ether ($84.06)

Gas Limit: 90000

Gas Price: 0.00000002 Ether (20 Gwei)

Gas Used By Txn: 21000

Actual Tx Cost/Fee: 0.00042 Ether ($0.14)

Cumulative Gas Used: 2511929

Nonce: 0

@Arthur111
Copy link

It is very slow and at a some point it won't sync anymore though there are active peers connection.

And Eth/Usd will go south, until they clean up the mess.

@Arthur111
Copy link

Another thing to add is it imply a very very high disk activity. For this reason i stop it and run disk utility and other tools to repair the directory and defragment the disk every 6 hours. (I got a message saying "Disk is too hot"). Maybe this explain why some people have crash or are unable to run it. Check your hard drive ! (Repair it and defragment it !).

@Arthur111
Copy link

Arthur111 commented Jun 24, 2017 •
edited
Loading

There is a problem with --fast because its disabled if the blockchain is not empty when the app is launched see : ethereum/go-ethereum#2639 and the problem is closed with this reason : " That's intended. Fast sync runs only once for security reasons. ".

and i added this comment :

"fast sync must be disabled when the first time its sync.
Until its not sync the first time --fast must stay enabled.
Like this you can restart as you want, or after a crash (bug) until its sync for the first time."

@califa
Copy link
Author

califa commented Jun 24, 2017

Hey so, any idea what can be done to resolve this and complete sync?

@califa
Copy link
Author

califa commented Jun 25, 2017

@solarin I have 470GB free

@BoBBer446
Copy link

BoBBer446 commented Jun 25, 2017 •
edited
Loading

What does it mean? Eth is death?

Since 7 days i try to sync all chain but he stars random new

5 hours ago i have 2peer at 13%

1 hour ago i have 1 peer and 2%.....

more then 2 peers i never had.

@stevedekorte
Copy link

Same problem. Hasn't synced after a week on a gigabit connection running on a new desktop with plenty of disk space.

@Arthur111
Copy link

Its a disaster .... i have 100 blocks until its sync and its since yesterday ... there is no end ... so ... i am moving to openledger ... bitshares etc ...

@eldadwasserman
Copy link

eldadwasserman commented Jun 28, 2017 via email

@califa
Copy link
Author

califa commented Jul 4, 2017

Is there anyone attached to the project that can chime in?

@stevedekorte
Copy link

I was able to finally sync by deleting the chain data and using the geth CLI with --fast. Not a friendly user experience.

@ShikiGami
Copy link

ShikiGami commented Jul 18, 2017 •
edited
Loading

Same problem here, I have to keep closing and reopening it for it to continue. If it gets stuck, it wont continue downloading until the next time it is reopened.
And some times it just starts to give errors and cannot sync unless you delete the data files, which makes it almost imposible to sync the wallet.

@JeremyTCD
Copy link

Same problem here, stuck at "268 blocks left, 99%" for 4 hours

@Szerzetes
Copy link

Szerzetes commented Jul 31, 2017 •
edited
Loading

Try use the automated Start/Stop small tool for Ethereum Wallet, if stuck in sync.
www.teremi.hu/ethereum

@Aziaev
Copy link

Aziaev commented Sep 6, 2017

i have 133 blocks to end and it stucks for 2 days, i have no idea what i should to do

@Apekool
Copy link

Apekool commented Dec 12, 2017

Try running the default geth

Not via the wallet application and/or mist browser, but loading geth.exe in cmd without fast and a cache of only 128 (default), like double clicking it.

It's running again here now and processing the state entries without errors and unexpected nonsense, but as soon as I load the wallet application everything goes haywire again.

@ethancrist
Copy link

ethancrist commented Dec 13, 2017 •
edited
Loading

Deleted all the chain data and ran as geth, no luck. Get up to the last ~100 blocks and no progress. Restart, 400 or so blocks behind, it catches back up a little, but freezes right within the last ~100.

This is technically a fatal error since it makes the application, and tons of people's wallets, completely unusable. This could massively prevent adoption if not fixed soon.

@Guttler
Copy link

Guttler commented Dec 13, 2017

Yes it is still unable to get to a full sync and gets stock when around 150 blocks left. Also tried to delete old blockchain data several times, but the same happens every time. I also upgraded the wallet to see if that should do the trick, but no....:(

@trbsi
Copy link

trbsi commented Dec 14, 2017 •
edited
Loading

Having the same problem. Mist and Ethereum network are pretty bad, unfortunately we can't move on to any other platform for now. I hope we can lose Ethereum and use some other blockchain in the future

@Arthur111
Copy link

PR... maybe. Putin seems to love it, that's why

Putin has his own coin : https://www.rt.com/business/413303-putin-coin-surge-cryptocurrency

@Guttler
Copy link

Guttler commented Dec 15, 2017

Yesterday I deleted the chaindata folder again and made a full re-sync overnight. And this morning it went through?! I updated Ethereum wallet before that, so maybe that also had an effect?!

@rico345100
Copy link

SAME HERE. IT NEVER ENDS.

@trbsi
Copy link

trbsi commented Dec 17, 2017

Don't use Mist people, Use Ethereum Remix and MyEtherWallet to deploy and interact with your contract. You can use it for main or ropsten network.

I'll write tutorial about it on Medium tomorrow

@mpasserini
Copy link

mpasserini commented Dec 17, 2017 •
edited
Loading

I managed to launch by running: geth removedb.. and then ethereumwallet -node-light. Now it's waiting for peers, it looks like there is none..

@ethancrist
Copy link

I got mine to work. I had to use the wallet on an entirely different machine which had an SSD.

@rudynunez
Copy link

Hey all,

I think this might be a memory / allocation issue. I could not download ethereum on my old comp. But now that I have a new machine, its working fine...except that it is getting stuck occasionally but it seems to only get stuck when i have other apps competing for mem during download. What if it's as simple as having enuf ram? Or maybe has something to do with allocation settings or cache?

@Ottimusen
Copy link

I have the same problem, deleted chaindata, when I resync I'm stuck at 89%

@loopyd
Copy link

loopyd commented Dec 22, 2017

Of note about SSD's - Irrelevant but still important

Don't use an SSD - this is bad for any P2P software anyhow. Its irrelevant to this issue, but it was brought up. May as well deem it relevant to any P2P software in general (this includes BitTorrent, and really anything using a swarm based connection method that hikes the disk access).

The new wallet app DOES work
The new wallet app with improved sync has rectified this issue. I'm half the blockchain download in in just under 30 minutes, and not even the best internet in the world. (37mbit/s) My Discord buds have better. Don't blame your internet, blame your router's misconfiguration (or your ISP for blocking P2P access ports) - in this case. I have to run behind VPN, a bonder, and an out-of-country ISP to even have the option to P2P.

Thorough explanation about deep packet inspection and consumer profiling used to block P2P swarming

  • If you can answer "yes" to "Comcast is my Internet Provider" you should not be Etherium mining. They're the worst about deep-packet inspection, and they will terminate any peer accesses or swarms relatively quickly.
  • If you tend to receive a lot of warnings about peer stalls, but it works for a time and potentially stops, the finger goes pointed in the ISP's direction - not the Etherium developers. Speed doesn't matter. It is what/and if such traffic is being potentially sniffed and discarded out of your pipe. These monitorings are often done on ports remindful of P2P software: 8000-9000 range for localhosts, 6666 and 6667 for private IRC client connections (typical of unlawful behavior), onion router ports, and higher ranges typical of default BitTorrent protocols.
  • This behavior is normal of an internet service provider lax in the protection of the information of its customers. Its a process known as "Consumer Connection Profiling". Most often written off as an infrastructural integrity measure, but more-so intended to line the ISP's pockets. I had to purchase a static IP and a dedicated line under the jurisdiction of a different country to be able to avoid this.

Summary
About Peer Stalls
Do not blame the Etherium developers if you are observing Peer Stalls in your logs and repeat attempts fail due to errors. You should instead, be terminating services with whichever ISP you call your own, and switch to a provider that isn't periodically terminating P2P connections.

Node Write Error and Apple products
Do not blame the Etherium developers if you are observing Node Write Error messages in your logs. For MacOS users, unless jailbroken and homebrewed, or hackintoshed, MacOS is essentially proprietary Apple software, as-is all the hardware inside of the computer. P2P blocking happens at Apple's level unless explicitly disabled by alternative means.

Node Write Error Storage and Software Tips
Additionally, Node Write Error is caused by: an overheating SSD, or a mechanical in a fragmented state. Defragment (if formatted to an NTFS filesystem on a mechanical drive, ext3/4 users, you're probably smart enough to have already installed your passive heatsinks, but you could still have bad sectors). The sdelete Windows Systeminternals tool works well to cap free space on NTFS after an operation on a mechanical drive. Keep Cortana at bay sword-and-shield with local group policy snap-in if you intend to use P2P software on a Windows 10 machine (and please, I say this to Windows users, please - if you are doing something as complex as using these types of software, get an Enterprise or Server version of windows that has the feature-set to DISABLE telemetry and these types of packet analysis, and has the featureset to properly deal with your LAN controllers, switches, and networking components. P2P disabling happens in the OS at kernel-level from Microsoft on Home editions of Windows (intended for families to protect their children from the internet, not for heavy server software).

Microsoft offers an option for us. That is often overlooked due to the price tag, but they do give us an option. Apple does not.

You must maintain your hardware for things to continue running smoothly.

and as always:

The software is only ever as smart as its end-user

@Ottimusen
Copy link

Ottimusen commented Dec 22, 2017 via email

@trbsi
Copy link

trbsi commented Dec 23, 2017

I found a solution and explained it in details step by step here
http://hellomimic.com/blog/2017/12/23/how-to-code-smart-contract-without-mist/
Also on my Medium
https://medium.com/@mimicapp.official/how-to-code-smart-contract-without-mist-64199a78fe7c

@calvinstiff
Copy link

calvinstiff commented Dec 24, 2017 via email

@mustafatorun
Copy link

I have the same problem, what will we do?
Will we ever make it?

@Ottimusen
Copy link

Ottimusen commented Dec 26, 2017 via email

@QuarksRules
Copy link

Ottimunsen, easy enough to move and I was planing to use nano ledger s. I sent 0.2 ETH to my etherium wallet main account to test it and because of sync problem it still shows 0.0 ETH there. I used the off site account checker and there I can see the eth in my ether wallet i just can not take it out until it syncs... How to take out the eth if it won't sync?

@Ottimusen
Copy link

Ottimusen commented Dec 26, 2017 via email

@php-wizard
Copy link

php-wizard commented Dec 27, 2017 •
edited
Loading

@Ottimusen there is an easier way: just turn Mist in Lite mode from the main menu. So that it doesn't need to sync anymore since it gets updated via a server ( like Electrum does for Bitcoin).
See #2595 (comment)
Then you can directly send your coins from Mist.

@mrrickwilson
Copy link

mrrickwilson commented Dec 31, 2017 •
edited
Loading

@Ottimusen 's suggestion worked!

Backstory: I wanted to start migrating my cryptocurrency to the Ethereum Wallet desktop application. So I sent 0.25 Ether from Coinbase to my Ethereum Wallet address as a test. When I opened the Ethereum Wallet on my desktop, and found that loading the blocks wasn't happening (same problem as the entire discussion above), I decided that I needed to find a way to reverse the transaction - because I couldn't even see my Ether in Ethereum Wallet. Also, it was eating up space on my hard-drive...

Resolution: I followed @Ottimusen 's instructions. I found my keystore on Windows 10 by using File Explorer:
C:\Users\xxx xxx xxx\AppData\Roaming\Ethereum\keystore

Math: But in order to send the 0.25 Ether back to Coinbase (for now) I had to do a little math to estimate how much ether I needed to leave off for MyEtherWallet to convert to Gas and to complete the transaction. Here is a good website to help with the math:
https://ethgasstation.info/index.php
In my case, it was 0.0000000005 Ether = 0.5 Gwei
In other words, I sent back 0.24 Ether to Coinbase, hoping that would leave enough Gas to complete the transaction.

Hit me up if you need more explanation.

@GlenHughes
Copy link

@Ottimusen thanks for your info, that's helped me recover my coins and put them back into Coinbase. My problem was that the wallet was just crashing every couple of mins and I would need to reload it each time. I ended up giving up as it just wasn't worth the hassle!!

@stevedekorte
Copy link

stevedekorte commented Jan 16, 2018 via email

@sudoman999
Copy link

Here are four points that could solve your issue:

  1. Update to the latest version. At the time of writing this post, the latest version was 0.9.3
  2. Make sure that you have at least 20GB of free space on your hard drive.
  3. Use a high-speed internet of about 100MBPs
  4. Use an SSD Hard Drive.

Mostly point 1 and 2 will solve the issue. Point 3 and 4 are optional.

Bonus Tips

  1. To clear your memory space, you can use 'Disc Inventory X'. Link: http://www.derlien.com/
  2. If you don't have any of the above requirements i.e. Memory Space, High Speed and SSD then you can use a VPS on Digital Ocean. Here is a link to get free $10 credits: https://m.do.co/c/679338b50344

Explanation of why I think this will work:
I was stuck at 99% with 210 Blocks left. Nothing moved for about 8 hours. I had 6GB of free space and was on 1 MBPS internet connection. I simultaneously did two points. i.e. Removed the extra memory and moved to a high-speed internet. One of the two points seems to have worked.

My MacBook Air already had an SSD so not sure if it is a must but I read in multiple places that it is suggested to have an SSD. Let me know if my solution helps.

If it helps, you might want to show some love 😁. Here is my address for Etherium wallet: 0x22C1C345830fC82b1D1E26aBc26a32B7ad7D4D7A

@NathanaelGandhi
Copy link

NathanaelGandhi commented Feb 18, 2018 •
edited
Loading

Ethereum won't sync - Memory Error

Windows 10 Home 1709 64-bit 8gb RAM.
Ethereum Wallet 0.9.3

  1. Open Command Prompt (Win+R cmd)

  2. [optional] Move Ethereum from an SSD to an HDD
    Backup "keystore"
    Move "Ethereum" (from appdata) to HDD (if you copy, make sure to delete the source after)
    mklink [old path] [new path]
    example: mklink "%APPDATA%\Ethereum D:\Ethereum
    (@loopyd I haven't had a write error, would not using an SSD still be wise?)

  3. "%APPDATA%\Ethereum Wallet\binaries\Geth\unpacked\geth.exe" --fast
    (@robme thanks for sharing this, why do you delete the db?)

  4. [optional] Open Ethereum Wallet & Launch Application
    (I don't think this is necessary, but who doesn't love a progress bar)

The sync lasted for 1.5hrs until

ERROR[02-16|01:25:58] Failed to generate mapped ethash cache epoch=141 err="MapViewOfFile: Not enough storage is available to process this command."
runtime: out of memory: cannot allocate 35258368-byte block (1525252096 in use)
fatal error: out of memory

  1. Run step 3 again (there is no need to close anything)

Notes: Geth seems to use more and more RAM as it runs the sync. For my computer, I would run out of RAM which would cause the runtime error. Geth would end on this error. Repeating step 3 would continue from the previous partial sync.
I have not tried deleting the blockchain file.

I know this is a very brute-force approach, suggestions about a more elegant way would be much appreciated.

Q: Why would this sync process continuously use more and more memory? @rudynunez maybe like you suggested, allocation settings or cache?

@tyramisoux tyramisoux mentioned this issue Mar 13, 2018
Closed
@tyramisoux
Copy link

tyramisoux commented Mar 15, 2018 •
edited
Loading

Was able to boost the number of connected peers after installing "Meinberg NTP Service" (Windoze). Looks like the win10 NTP-Client makes no good job.
Allways had 1 or 2 peers connected before (even after manual time synchronisation). After installing the NTP-Service I've seen 10 peers connected and my chaindata will be done in a few hours.
coincidence? I don't think so.

Btw I had "high I/O and Disk load" only after a power-failure when geth reorganised the stuff. But it did not take too much time.

I had all that trouble only when running geth through MIST (even with proper --node-parameters). When running geth from console it looks way better for me.

the "getBlock("latest") should not return anything at all but an Error when not synced. Id does when requesting a block > eth.syncing.currentBlock
I had legitimate expectation MIST output was valid and relied on the data. If known one might check .number != 0

@tyramisoux
Copy link

tyramisoux commented Mar 15, 2018 •
edited
Loading

last status I've seen about an hour ago was:

eth.syncing
{
currentBlock: 5256025,
highestBlock: 5258273,
knownStates: 17472478,
pulledStates: 17460225,
startingBlock: 5255425
}

still connected to a few peer but now I get:

eth.syncing
false

So there is no way to check if currentBlock reached highestBlock? How to ensure it is synced? It obviously is NOT and this might explain why the status MIST shows also is confusing.
(eth.blockNumber returns 0 as well the getBlock("latest") does)

what the fu* does eth.getWork() return in this state? (it is the same for days but I guess nothing I should spend energy for)

I see - chain seem not finished at all. It is Busy "Importing new state entries" now.
But how ensure through RPC the status? How can I tell if stuff is synced?
"admin.chainSyncStatus"? unfortunately admin module is off by default in recent geth

edit:
I've read an article claiming "--fast" was made default? This might explain what is going on here since it switched "fast" off (as it should) and downloading more.

edit:

eth.syncing
{
currentBlock: 5259089,
highestBlock: 5259169,
knownStates: 25705755,
pulledStates: 25702370,
startingBlock: 5256286
}

am I right? it auto-switched back from fast-mode to full? (as supposed to).
Just need to know how tell the exact status (to make the mining rigs not work on garbage for example)

edit:
enabled admin-module by adding --rpcapi "admin,eth,miner,net,rpc,web3" (or --node-rpcapi when starting through MIST).
It is no longer enabled by default in 1.8.2.

bzw. sync became very slow now and I wonder if "currentBlock" ever will reach "highestBlock"

I/O and Disc access very low
Network: about about 200Kb/s
Peers about 7

errors like; err="state node c381d0…b12eb8 failed with all peers (3 tries, 3 peers)"
shitloads of them....

@tyramisoux
Copy link

WTF?

eth.syncing
{
currentBlock: 2,
highestBlock: 5263087,
knownStates: 31506154,
pulledStates: 31502113,
startingBlock: 5263087
}

Importing new state-entries now

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
v0.8.10
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests