Wallet slow to sync
-
@engetsu I thought the thing that took time is not the download, but the processing.
-
My tests showed the sync with 0.9.6.2 took consistently ~25 hours, using the blockdata.dat - a fast PC with > 16 GB RAM.
Can I ask what PC you are using? memory / clock speed?
-
im doing it from my laptop , i3 with 8gig of ram , ssd .
So woke up today and i think it finished syncing , fire up feathercoin app and now i get an error message saying "connect a new block to chainactive , failed to read block " .and then shutsdown
Tha hell is wrong with this wallet why is it only problems , what are the devs going to do if it ever becomes mainstream and everyone wants to buy themselves some FTC .
i uninstalled and re installed but i still get the message . Do i have to delete everything again and download restart the whole process again ?
-
@engetsu - I deleted the swearing as this is a highjack of someone else welcome thread.
You can try : Start the client with the -reindex command-line option.
Otherwise yes, the bitcoin programmers have included error checking in the code that you sometimes have to do something about , sorry.
Contribute to FTC development and bug fixing : 6p8u3wtct7uxRGmvWr2xvPxqRzbpbcd82A
-
@engetsu - I appreciate your frustration. We are working to sort out all of these sync issues in our next release.
if you’re on windows…
- make a shortcut to feathercoin-qt on your desktop
- right click and click properties
- add the following to the end of the Target path
"C:\Program Files\Feathercoin\feathercoin-qt.exe" -maxorphantx=5000 -maxblockorphans=12000 -dbcache=4096 -rescan
let us know how you get on.
-
For your information guys this command line doesnt work
“C:\Program Files\Feathercoin\feathercoin-qt.exe” -maxorphantx=5000 -maxblockorphans=12000 -dbcache=4096 -rescan
-
Could you please go into more detail?
“Doesn’t work” makes it hard for us to provide support.
-
I have been downloading the Feathercoin blockchain for 2 weeks, I have 1 year and 27 weeks left. I have a very good connection. It’s sloooow.
-
Nothing has changed . It stuck like this … It has been 1 week now :) It is working 24/7 also i can share the debuglog file if you want
2017-12-19 22:17:13 ProcessBlock() ProcessBlock: ORPHAN BLOCK 7501, prev=b3e153f5f315adcd446bab4c05ccf014da93f3cbe056bb28033350973ff79d15
2017-12-19 22:17:13 ProcessBlock() ProcessBlock: ORPHAN BLOCK 7501, prev=3dd4e05b659112e11ad433df3e0aa6abdb7911b4a5491849e2906e0e6bb6f0e7
2017-12-19 22:17:13 ProcessBlock() ProcessBlock: ORPHAN BLOCK 7501, prev=7eefb7831194684ccb2bedd3fe420e15f1ce59048a48c819fcad2efe37eff866
2017-12-19 22:17:14 ProcessBlock() ProcessBlock: ORPHAN BLOCK 7501, prev=838fed5258c63030274996d286ec54ec9e1b52c2aa1aba669dd05dec99e18308
2017-12-19 22:17:14 ProcessBlock() ProcessBlock: ORPHAN BLOCK 7501, prev=dd500d98216417d37f8f4d2b2b5bfe7b351b5bfc345c5802cc60335813078b8c -
@anema said in Wallet slow to sync:
Nothing has changed . It stuck like this … It has been 1 week now :) It is working 24/7 also i can share the debuglog file if you want
2017-12-19 22:17:13 ProcessBlock() ProcessBlock: ORPHAN BLOCK 7501, prev=b3e153f5f315adcd446bab4c05ccf014da93f3cbe056bb28033350973ff79d15
2017-12-19 22:17:13 ProcessBlock() ProcessBlock: ORPHAN BLOCK 7501, prev=3dd4e05b659112e11ad433df3e0aa6abdb7911b4a5491849e2906e0e6bb6f0e7
2017-12-19 22:17:13 ProcessBlock() ProcessBlock: ORPHAN BLOCK 7501, prev=7eefb7831194684ccb2bedd3fe420e15f1ce59048a48c819fcad2efe37eff866
2017-12-19 22:17:14 ProcessBlock() ProcessBlock: ORPHAN BLOCK 7501, prev=838fed5258c63030274996d286ec54ec9e1b52c2aa1aba669dd05dec99e18308
2017-12-19 22:17:14 ProcessBlock() ProcessBlock: ORPHAN BLOCK 7501, prev=dd500d98216417d37f8f4d2b2b5bfe7b351b5bfc345c5802cc60335813078b8cand to be honest I check those hash numbers by one by not all of them I dont know why it says Orphan
-
Hi @Anema
this is the expected behaviour. You just need to leave your machine on and set it to not go onto standby or sleep mode.
Leaving it on for 1 week 24/7 - and you can guarantee it’s been online that whole time… then something else might be wrong with your setup.
The orphan blocks are blocks that have to be processed - in the past Feathercoin had attacks on it’s blockchain and this caused orphan chains to happen.
-
I think from now on the best thing to do just leave the computer open . About my setting I have no idea I just downloaded the setup and then Install it . I dont think I have a problem with my firewall or anything else. Ty for the info btw
-
I did a try from fresh, for the sake of benchmarking and potential useful info.
So far, 36 weeks behind @2days 19hours, will report in upon completion. -
@moonman said in Wallet slow to sync:
I did a try from fresh, for the sake of benchmarking and potential useful info.
So far, 36 weeks behind @2days 19hours, will report in upon completion.Whats the spec / memory CPU speed of the PC?
-
@wrapper
will do a complete spec and times post when its complete, but its an hp tm2 touch laptop with core2duo cpu ~1.5sth ghz, 8gb ram (ddr3 800 if i remember well) -
I really dont think this is about Computer speed
-
DOES ANYONE HAVE A BOOTSTRAP LINK WHICH IS FREE TO DOWNLOAD?
-
@anema said in Wallet slow to sync:
I really dont think this is about Computer speed
Hi, can you lay out all you research and evidence for your conclusion?
-
@mrcrpto said in Wallet slow to sync:
DOES ANYONE HAVE A BOOTSTRAP LINK WHICH IS FREE TO DOWNLOAD?
Could do with a recent one being created.
https://archive.org/download/bootstrap_20170527/bootstrap.dat
-
Ok, reporting in.
Tested fresh download, install and sync.
The sync ended last night (i was sleeping at the time), time now is +4d10h, so the sync stopped at about ~ +4d5hThe sync was done on an HP TM2-2190,
gpu is Intel Graphics Media Accelerator (GMA) 4500MHD (it has a switchable ATI Mobility Radeon HD 4550 gpu but i wanted it to run cooler if it was about to stay on for a long time).
Energy cpu profile was min5% max 100%.
Resource monitoring showed an average cpu usage of
core1: ~20% and core2: ~70%Internet connection is an ADSL2+ synced at 19mbps down/1mpbs up
Internet interruption occured once a day - based on my router scheduling
Internet outages - only Isp and God knows, forgot not to auto flush router log, sorryCpuid shot:
https://imgur.com/0ZTeeqR