Wallet sync is very slow
-
@looki said in Wallet sync is very slow:
In addition, there is a weird issue, everytime I close the wallet a save dialog is prompted asking to backup the wallet. Is it a configuration option? Or something messed up with my wallet?
thanksYou get that message box, if you close the wallet using the ‘file->quit’ menu entry.
If you close the wallet by clicking the ‘close window’ symbol - mostly an ‘x’ in the very upper right corner- you can leave without saving the wallet.
-
@wrapper said in Wallet sync is very slow:
Can you try feathercoin-qt -maxorphanblocks=2000 ?
This is the one we want.
Hi wrapper,
Still, can’t see any difference. The weirdest thing is at the moment of starting the wallet, the sync process goes smooth for some seconds(about 30) and then it stalls without any progress.
Typically the “Network Traffic” tab shows progress until about 1-2MB.![Network Traffic Tab Screenshot] (http://imghost.io/image/HivjX)
-
From our experiments overnight, adding -maxorphanblocks=4000 stopped it stalling at > 750 orphans chains (i.e. need a reset). It is running slower than we think it should, so I’m continuing to investigate.
I’ve been looking at the debug log with /tails -f debug.log , which shows whats being written, in a linux terminal. Nothing shows particularly so far.
-
@Wellenreiter said in Wallet sync is very slow:
The initial synchronization may take a day, which is a one time event.
I’m having a similar issue. Been running synch for two days (!) now and still got less than 50% (around block 830,000). I’m running v0.9.6.1 on macMini over fast internet connection. Debug window shows 8 outgoing connections. Synch often gets stuck and needs to be restarted, like every 30 min to a couple of hours. Very frustrating experience. :(
Any suggestions?
-
if you can see a lot of ‘orphan block xxx’ where xxx is an increasing number, that stops at 751 try wrappers hint above.
If that doesn’t help stop your client, remove peers.dat an start the client again. This forces the client to find new peers.
In general stopping and starting the client when the sync stalls seems to help.
The problem should be solved in one of the next versions.
-
The problem was a temporary memory setting in Bitcoin was too low. When it was first set, it was not known that orphan chains could be longer than 750. The updated version fixes that problem so there is not a stall during sync.
Unfortunately, during the sync the client must check every block “chain”
If you do get the stalling problem, until 0.9.6.2 is released, stopping and restarting reloads the blocks the wallet is checking into the memory, so it can find the next block.
Sorry for the frustration, one solution, if you urgently need access to the wallet, would be to compile our 0.9.6.2 head, you can go back to the binary after sync.
-
@wrapper said in Wallet sync is very slow:
The problem was a temporary memory setting in Bitcoin was too low. When it was first set, it was not known that orphan chains could be longer than 750. The updated version fixes that problem so there is not a stall during sync.
Unfortunately, during the sync the client must check every block “chain”
If you do get the stalling problem, until 0.9.6.2 is released, stopping and restarting reloads the blocks the wallet is checking into the memory, so it can find the next block.
Sorry for the frustration, one solution, if you urgently need access to the wallet, would be to compile our 0.9.6.2 head, you can go back to the binary after sync.
Is there a release date for 0.9.6.2? i’m currently stuck with this issue and suggestions above are not fixing the problem :(
Nothing i do will allow it to go past 751…
-
git clone
Build instructions :
@gooders heres my build script :
cp -f ~/Feathercoin/src/feathercoind ~/Feathercoin/src/build/feathercoind cp -f ~/Feathercoin/src/feathercoin-cli ~/Feathercoin/src/build/feathercoin-cli cp -f ~/Feathercoin/src/qt/feathercoin-qt ~/Feathercoin/src/build/feathercoin-qt echo back-up bin files, copied .... rm build.txt time make clean echo autogen ........ time ./autogen.sh ./configure --with-gui=qt5 --enable-tests=no --enable-upnp-default --with-qrcode=yes --enable-wallet=yes --disable-hardening LDFLAGS="-L${BDB_PREFIX}/lib/" CPPFLAGS="-I${BDB_PREFIX}/include/" CXXFLAGS="$CXXFLAGS -fPIC -m64 -std=c++11" time make echo finished ...... date cp -f ~/Feathercoin/src/feathercoind ~/Feathercoin/src/build/feathercoind cp -f ~/Feathercoin/src/feathercoin-cli ~/Feathercoin/src/build/feathercoin-cli -
I’m also having problems with slow wallet sync. And now my wallet.exe won’t even start.
-
I can’t post in support for some reason, so does anyone know why my wallet keeps crashing every time I try to start it? It gets to “Verifying blocks…” and then I get the message “feathercoin-qt.exe has stopped working” every time.
-
@japhet said in Wallet sync is very slow:
I can’t post in support for some reason…
I’ve checked and you should be able to post into the support section.
Can you try again?
Regarding your wallet problems, can you open a thread in the support section and past the last 20-30 lined of the file debug.log, which is located in the %appdata%\feathercoin somewhere?
-
Hello. :)
My wallet has been synicing for nearly two weeks now. The bar is at 3/4. I am on a mac.
Is this normal?
Thanks.
Mouth. :)
-
@mouth_101 said in Wallet sync is very slow:
Hello. :)
My wallet has been synicing for nearly two weeks now. The bar is at 3/4. I am on a mac.
Is this normal?
Thanks.
Mouth. :)
No, while the current version of the wallet is rather slow, nobody reported a sync time that long
Did you .notice, that the sync also hang at a given block?
If yes, it has proven to help to shut down the wallet and restart it again.
This causes the wallet to connect to different nodes in the network and the sync continues. -
@wellenreiter Hi thanks for responding. :)
Apologies for my ignorance but where can I find which block the sync is at?
I have closed the wallet and restarted numerous times but it has little effect.
M.
-
@mouth_101 To add… when I hold my cursor over the bottom right graphs of the wallet it reads that I have
“8 active connections to feathercoin network”.
and also…
“Catching up…”
Processed 1419369 blocks of transation history. Last received block was generated 1 year and 3 weeks ago. Transactions after this will not yet be visible."M
-
Great, sounds like you’re past the worst bit. You’ve been unlucky, keep us informed, we can sort out a bootstrap.dat .
-
@mouth_101 said in Wallet sync is very slow:
…
…
and also…“Catching up…”
Processed 1419369 blocks of transation history. Last received block was generated 1 year and 3 weeks ago. Transactions after this will not yet be visible."That’s exactly where you can check, if the sync ist stalled. The block number shown should increase over time.
-
Thanks for the responses guys. I will keep you updated.
Have a good weekend!
M. :)
-
Sorry if I may be reopening an old issue but I was having the same problem and was able to advance the sync by adding the argument -maxorphanblocks=4000 . However it has been running for almost a day now and it has only downloaded roughly 200 MB on a 100 Mbps connection… at this rate it will never finish :(. I have closed and re-opened it as mentioned here but it is still pretty slow. Just wondering if there are any other tweaks to try?
-
@qbg84 said in Wallet sync is very slow:
Sorry if I may be reopening an old issue but I was having the same problem and was able to advance the sync by adding the argument -maxorphanblocks=4000 . However it has been running for almost a day now and it has only downloaded roughly 200 MB on a 100 Mbps connection… at this rate it will never finish :(. I have closed and re-opened it as mentioned here but it is still pretty slow. Just wondering if there are any other tweaks to try?
Unfortunately you just need to leave it on till it’s done. We are working to get a new version out which will reduce the sync time greatly.
