Not syncing. I'm a noob and don't know how to do fast sync

[Thequick-brownfox]

PLease help. Can someone explain on a very simple level how i can fix the sincing problem. It always get stuc around 2%. I deleted the chaindata a few times but it keeps getting stuck at 2 or 3%. I know there is a way to fast sinc but i don't know how to do it.

Do i just need to type " Geth--fast" in the command prompt or something?

Sorry for being a nood.

Thanks!

[luclu]

@Yorick111, please try to follow this guide and by any chance do yourself a favour in using a SSD instead a HDD.

[Thequick-brownfox]

What guide do you mean?

[luclu]

Oh sorry ;-)
This one.

[Thequick-brownfox]

I followed the step in the guide, but it is still stuck at 2%. Should i wait because it is (super slowly) syncing or is it just stuck?
Why does it take this long for syncing? Online wallets let you acces your account immediatly..

Thanks for the quick respons btw!

[frozeman]

It might be your firewall which slows down syncing if you are on windows

[Thequick-brownfox]

I turned of my firewall but it is still not working. It is always syncing but it always stops at 2%...

[luclu]

@Yorick111 could you please provide the following:

• Type of storage device (SSD or HDD)
• Log files
  • go to menu -> accounts -> backup -> application data
  • zip and upload node.log and all other node.log.X files
• Check the console (type CTRL/CMD + ALT + i)
  • take a screenshot
  • post the output of the following commands:
    • web3.admin.peers.length

[Thequick-brownfox]

I have HDD :(

Node files in this link:
https://www.dropbox.com/s/v734pmr0e50g1cf/Node%20log%20x.zip?dl=0

[luclu]

Your computer seems to be running out of memory while processing the state, so geth is crashing.
How much memory do you have installed?

[...]
I0113 16:21:47.410794 eth/downloader/downloader.go:966] imported 384 state entries in 878.586ms: processed 235712, pending at least 74499
I0113 16:21:47.523869 eth/downloader/downloader.go:966] imported 384 state entries in 516.343ms: processed 236096, pending at least 74596
I0113 16:21:48.012196 core/blockchain.go:792] imported 2048 receipts in    1.763s. #212294 [eeccff64… / 84a8f3c0…]
I0113 16:21:48.016198 eth/downloader/downloader.go:966] imported 281 state entries in 211.141ms: processed 236377, pending at least 74309
I0113 16:21:48.724671 eth/downloader/downloader.go:966] imported 384 state entries in 654.437ms: processed 236761, pending at least 74708
I0113 16:21:49.228007 eth/downloader/downloader.go:966] imported 384 state entries in 738.493ms: processed 237145, pending at least 74666
I0113 16:21:50.044552 eth/downloader/downloader.go:966] imported 384 state entries in 973.649ms: processed 237529, pending at least 74510
I0113 16:21:50.582911 eth/downloader/downloader.go:966] imported 384 state entries in    1.528s: processed 237913, pending at least 74245
I0113 16:21:50.616933 core/headerchain.go:331] imported 1984 headers in    6.146s. #226436 [1db1fe78… / 2e075e3f…]
I0113 16:21:51.214331 eth/downloader/downloader.go:966] imported 384 state entries in    1.164s: processed 238297, pending at least 74204
I0113 16:21:51.239349 core/blockchain.go:792] imported 2048 receipts in    3.217s. #214342 [df24738c… / 55cdb9af…]
runtime: out of memory: cannot allocate 268435456-byte block (856358912 in use)
fatal error: out of memory

runtime stack:
runtime.throw(0xcf0c6d, 0xd)
	C:/go/src/runtime/panic.go:566 +0x7f
runtime.largeAlloc(0x10000000, 0x1364501, 0x4636d0)
	C:/go/src/runtime/malloc.go:776 +0xb7
runtime.mallocgc.func1()
	C:/go/src/runtime/malloc.go:669 +0x31
runtime.systemstack(0x12f20000)
	C:/go/src/runtime/asm_386.s:323 +0x5e
runtime.mstart()
	C:/go/src/runtime/proc.go:1079

[...]

[Thequick-brownfox]

Only 8 Gb of ram, but i'm running indesign and other programs. So if i close them it should work?

[luclu]

Hmm, 8Gb is plenty. I think even 2Gb should be enough (at least on simple linux boxes).
Please give it a try.

[Thequick-brownfox]

Still stuck at 2%...

[luclu]

Please try to reboot to have a "cleaner" execution environment and monitor the available memory until the crash. (Before the crash is important as after it the memory should be freed again)

[Thequick-brownfox]

Doesn't work. Still stops with syncing at 2%. memory was never over 40%

[evertonfraga]

What do the logs show now, that memory doesn't seem to be the problem?

…

On Sat, 14 Jan 2017 at 16:19 Yorick111 ***@***.***> wrote: Doesn't work. Still stops with syncing at 2%. memory was never over 40% — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#1584 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAC4BPtTKgMVJKmv30JicnwuBXjvXAJsks5rSRGUgaJpZM4Liy9Y> .

[Thequick-brownfox]

https://www.dropbox.com/sh/qn4e33evwtob5vw/AACI2UtbxBk-T0kq0JNY6qi7a?dl=0

Here are the log files

[Thequick-brownfox]

[Thequick-brownfox]

@luclu It's still not working. Any idea on how to fix it?

[Thequick-brownfox]

[luclu]

@Yorick111 just a quick check, does updating to version 0.8.9 help?

[Thequick-brownfox]

no it didn't work. I just installed it on an other computer and copied my key to that wallet. It worked and now i have send it to an other wallet.

[senarvi]

I'm experiencing a pretty identical problem. I also have 8 GB of RAM and 64-bit Windows 10. I just updated to 0.8.10.

runtime: out of memory: cannot allocate 268435456-byte block (806813696 in use)
fatal error: out of memory

[evertonfraga]

Hi, we have just launched Mist v0.9.1, with Light Client integration (beta).

What does that mean?

• Sync times reduced by an order of magnitude while staying safe.
• Much smaller storage required.

How to activate?

I'm closing this issue. Should you have any trouble, please refer to these channels:

• Canonical issue regarding sync: Issues related with Syncing #3097
• Gitter channel, where the community is, and can certainly help as well: https://gitter.im/ethereum/mist

[lock]

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.