Bitcoin Forum
November 09, 2024, 11:44:28 PM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: No Error messages in Log but forever Scanning blocks 506902 to 507248. Advice?  (Read 151 times)
Gat420 (OP)
Newbie
*
Offline Offline

Activity: 5
Merit: 0


View Profile
February 02, 2018, 10:36:46 AM
 #1

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
goatpig
Moderator
Legendary
*
Offline Offline

Activity: 3752
Merit: 1364

Armory Developer


View Profile
February 02, 2018, 02:52:51 PM
 #2

Make sure the node is off while the DB is catching up. Once the DB is ready, start the node.

Gat420 (OP)
Newbie
*
Offline Offline

Activity: 5
Merit: 0


View Profile
February 03, 2018, 01:10:18 AM
 #3

How do I start and stop the node exactly? Is the node bitcoin core?

UPDATE: problem has persisted
goatpig
Moderator
Legendary
*
Offline Offline

Activity: 3752
Merit: 1364

Armory Developer


View Profile
February 03, 2018, 01:51:42 AM
 #4

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.

jojo69
Legendary
*
Offline Offline

Activity: 3346
Merit: 4621


diamond-handed zealot


View Profile
February 03, 2018, 04:40:14 AM
 #5

Make sure the node is off while the DB is catching up. Once the DB is ready, start the node.

wait...what?

This is not some pseudoeconomic post-modern Libertarian cult, it's an un-led, crowd-sourced mega startup organized around mutual self-interest where problems, whether of the theoretical or purely practical variety, are treated as temporary and, ultimately, solvable.
Censorship of e-gold was easy. Censorship of Bitcoin will be… entertaining.
goatpig
Moderator
Legendary
*
Offline Offline

Activity: 3752
Merit: 1364

Armory Developer


View Profile
February 03, 2018, 07:02:46 PM
 #6

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.

jojo69
Legendary
*
Offline Offline

Activity: 3346
Merit: 4621


diamond-handed zealot


View Profile
February 03, 2018, 07:22:45 PM
 #7

ok, sorry, specifically for low RAM situation, got it

This is not some pseudoeconomic post-modern Libertarian cult, it's an un-led, crowd-sourced mega startup organized around mutual self-interest where problems, whether of the theoretical or purely practical variety, are treated as temporary and, ultimately, solvable.
Censorship of e-gold was easy. Censorship of Bitcoin will be… entertaining.
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!