Bitcoin Forum
May 04, 2024, 10:32:40 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Armory stuck 0% Scanning - 1 second (solved)  (Read 1039 times)
atxum (OP)
Newbie
*
Offline Offline

Activity: 3
Merit: 0


View Profile
February 09, 2017, 08:48:54 PM
Last edit: February 10, 2017, 09:02:28 PM by atxum
 #1

Dear Armory Devs,

First of all, many thanks for your efforts in maintaining and improving Armory. I've been using it for about a year and am quite happy with it. Nevertheless I am now stuck with a PB I haven't been able to solve (I'm a basic user without in.depth knowledge; i reviewed the last 2 months of the forum but couldn't find a solution).

Armory worked fine during months but after maybe 1 month or so without using it, I downloaded the bitcoin-core blocks missing (bitcoin core version 0.13.2) and started Armory. But it stayed stuck offline with "Preparing databases", 0% transaction history (1 second). I tried to restart it with rescan and rebuild options but it didn't change anything.

When starting Armory from console with --debug i get this at the end:
[...]
(DEBUG) SDM.py:752 - Creating proxy
(INFO) SDM.py:756 - Creating proxy in SDM: host=127.0.0.1, port=8332
(DEBUG) SDM.py:240 - bitcoind rpc is not actually availalbe
(INFO) ArmoryQt.py:2307 - Setting netmode: 1
-ERROR - 1486672480: (SocketObject.cpp:438) POLLERR error in readAndWrite
-ERROR - 1486672480: (SwigClient.cpp:61) POLLERR error in readAndWrite
(INFO) ArmoryQt.py:2307 - Setting netmode: 0
(INFO) ArmoryQt.py:2289 - loadBlockchainIfNecessary
(INFO) ArmoryQt.py:5645 - Dashboard switched to "Scanning" mode
(INFO) ArmoryQt.py:5645 - Dashboard switched to "Scanning" mode

2 last DB logs:
http://pastebin.com/P10wG6Ah

Last logs:
http://pastebin.com/TL1JeXfh



Thanks!
LmL

Whoever mines the block which ends up containing your transaction will get its fee.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1714818760
Hero Member
*
Offline Offline

Posts: 1714818760

View Profile Personal Message (Offline)

Ignore
1714818760
Reply with quote  #2

1714818760
Report to moderator
1714818760
Hero Member
*
Offline Offline

Posts: 1714818760

View Profile Personal Message (Offline)

Ignore
1714818760
Reply with quote  #2

1714818760
Report to moderator
1714818760
Hero Member
*
Offline Offline

Posts: 1714818760

View Profile Personal Message (Offline)

Ignore
1714818760
Reply with quote  #2

1714818760
Report to moderator
goatpig
Moderator
Legendary
*
Offline Offline

Activity: 3668
Merit: 1345

Armory Developer


View Profile
February 09, 2017, 09:49:35 PM
 #2

Turn off auto bitcoind in File -> Settings, start BitcoinQt manually, then try start Armory. Report here.

atxum (OP)
Newbie
*
Offline Offline

Activity: 3
Merit: 0


View Profile
February 09, 2017, 10:39:31 PM
 #3

That's how it was working so far... and the current setup; the error is with this confirguration
goatpig
Moderator
Legendary
*
Offline Offline

Activity: 3668
Merit: 1345

Armory Developer


View Profile
February 09, 2017, 10:43:35 PM
 #4

Start ArmoryDB from the terminal and let it initialize. If it crashes post the terminal output here. If not, start ArmoryQt.py on top of it

Ratatosk
Sr. Member
****
Offline Offline

Activity: 263
Merit: 250


View Profile
February 10, 2017, 02:36:02 PM
 #5

Solution that works for me :

Wait a very long time if needed (1-4 hours) until the second black windows ArmoryDB.exe appears and let it run for a while, until no more new lines appears (30 minutes ?)

Exit Armory, if the black windows remains, close it

Restart Armory

Should be very quite fast (some minutes) displaying the second windows ArmoryDB.exe and after few minutes maximum, Armony is online

Exceptionnally I have to restart a third time.
atxum (OP)
Newbie
*
Offline Offline

Activity: 3
Merit: 0


View Profile
February 10, 2017, 09:01:40 PM
 #6


Reviewing the comand-line options to start armodydb I discovered that port 9001 is used. I had another aplication using that port, which I changed and after that Armory worked fine.

Thanks for the help!

LmL
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!