Bitcoin Forum
May 27, 2024, 04:22:27 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: ArmoryDB exits silently upon synchronization  (Read 773 times)
gencha (OP)
Newbie
*
Offline Offline

Activity: 7
Merit: 0


View Profile
September 21, 2017, 12:30:08 PM
 #1

A couple of days ago Armory stopped working for me. Whenever the transaction history was about to be fully synchronized, ArmoryDB would exit.

The issue started happening when I was still letting Armory run bitcoind. I had Bitcoin Core 0.14.2 with Armory 0.96.2 installed.

Since then, to troubleshoot, I have changed the setup so that I'm running bitcoin-qt myself. I also upgraded to 0.15.0.1 and then down again to 0.15, after reading that the former causes other issues. None of that seemed to have any impact on the issue.

I have also started ArmoryDB standalone in a console to see if it prints anything when it exists. It doesn't.

The dbLog shows no identifyable errors and ends with `-INFO  - 14:24:02.391: (..\BlockchainScanner.cpp:852) scanned from block #484062 to #484718`
The armoryLog shows no identifyable errors and ends with `2017-09-21 14:24:02 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode`

armorycpplog shows 2 errors, presumably around the time ArmoryDB exits:
Code:
-ERROR - 14:24:12.063: (..\SocketObject.cpp:447) POLLERR error in readAndWrite
-ERROR - 14:24:12.078: (..\StringSockets.cpp:359) POLLERR error in readAndWrite
goatpig
Moderator
Legendary
*
Offline Offline

Activity: 3668
Merit: 1347

Armory Developer


View Profile
September 21, 2017, 02:54:23 PM
 #2

Post your logs.

gencha (OP)
Newbie
*
Offline Offline

Activity: 7
Merit: 0


View Profile
September 21, 2017, 03:13:41 PM
 #3

Posted them here: https://kopy.io/1Kscg
goatpig
Moderator
Legendary
*
Offline Offline

Activity: 3668
Merit: 1347

Armory Developer


View Profile
September 21, 2017, 04:00:24 PM
 #4

1) Don't use Core 0.15.0.1 until the fix is out.

2) Delete your logs, start Armory, post the fresh logs.

gencha (OP)
Newbie
*
Offline Offline

Activity: 7
Merit: 0


View Profile
September 21, 2017, 04:49:10 PM
 #5

I'm not using 0.15.0.1. I'm currently using 0.15.

I had just deleted the logs and restarted Armory before I posted them. I'll repeat.
gencha (OP)
Newbie
*
Offline Offline

Activity: 7
Merit: 0


View Profile
September 21, 2017, 05:28:53 PM
 #6

Here are the fresh logs: https://kopy.io/WPSfx

I see a reference to mempool.bin in there, which does not exist. However, I do have a mempool.dat in my Bitcoin directory. Not sure if this is relevant.
gencha (OP)
Newbie
*
Offline Offline

Activity: 7
Merit: 0


View Profile
September 23, 2017, 06:06:23 PM
 #7

I updated to 0.96.3, but the situation is unchanged.

Suggestions on how to recover from this would be greatly appreciated.
goatpig
Moderator
Legendary
*
Offline Offline

Activity: 3668
Merit: 1347

Armory Developer


View Profile
September 23, 2017, 10:14:30 PM
 #8

Use pastebin, my browser blocks that domain.

gencha (OP)
Newbie
*
Offline Offline

Activity: 7
Merit: 0


View Profile
September 24, 2017, 04:20:40 PM
 #9

Here we go: https://pastebin.com/raw/svP22U60
goatpig
Moderator
Legendary
*
Offline Offline

Activity: 3668
Merit: 1347

Armory Developer


View Profile
September 24, 2017, 06:05:26 PM
 #10

It's scanning two address sets independently for whatever reason. Do a rebuild & rescan.

gencha (OP)
Newbie
*
Offline Offline

Activity: 7
Merit: 0


View Profile
September 24, 2017, 10:18:46 PM
 #11

That worked beautifully. Thanks a lot.
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!