Author

Topic: No Error messages in Log but forever Scanning blocks 506902 to 507248. Advice? (Read 135 times)

legendary
Activity: 3164
Merit: 4345
diamond-handed zealot
ok, sorry, specifically for low RAM situation, got it
legendary
Activity: 3640
Merit: 1345
Armory Developer
Make sure the node is off while the DB is catching up. Once the DB is ready, start the node.

wait...what?

The DB builds off of on disk data. If you have a low RAM system, letting the DB build the initial dataset before turning on the node (which eats ~3GB RAM) is a good work around. You can then start the node to catch up the last 100 blocks or so.
legendary
Activity: 3164
Merit: 4345
diamond-handed zealot
Make sure the node is off while the DB is catching up. Once the DB is ready, start the node.

wait...what?
legendary
Activity: 3640
Merit: 1345
Armory Developer
1) Delete your DB folder

2) Create a file named armoryqt.conf in your Armory datadir. Put that in it:

Code:
db-type=DB_BARE

3) Make sure auto bitcoind is turned off in File -> Settings (first checkbox)

4) Start Armory without your node running. It will build the DB.

5) Once the DB is ready, shut down Armory, start your node, then start Armory again.

If you're having trouble, post your logs again.
newbie
Activity: 5
Merit: 0
How do I start and stop the node exactly? Is the node bitcoin core?

UPDATE: problem has persisted
legendary
Activity: 3640
Merit: 1345
Armory Developer
Make sure the node is off while the DB is catching up. Once the DB is ready, start the node.
newbie
Activity: 5
Merit: 0
https://pastebin.com/AUsNMcv6

I'll leave it running all afternoon and update on the progress when I get back.

I'm under the impression this has come about because I turned my computer off for a week or so.  Roll Eyes

I have the latest version installed. Also uninstalled and installed again when I first started getting trouble starting armory and bitcoin core after turning my computer back on again.

I have bitcoin core synched and running.  Smiley

Let me know what advices you may have for me to get it up and running again! Thanks  Cheesy
Jump to: