Armory - Discussion Thread

[picobit]

Anything to be done about armoryd's crazy memory usage? I'm seeing 41GB virt and about 6GB residual. It's causing other processes to start swapping. It is done scanning blocks, this is persistent memory usage. In comparison, bitcoind only uses about 55MB residual.

Restarting the process causes the memory to go down, but then armoryd starts eating up CPU and filling up again. It continually is using the lion's share of resources on the system.

When a program (such as Armory) reads a file, the file is copied into memory.  As soon as Armory is done using the file, the memory is marked as available for other programs, but until another program claims the memory, you still see it as assigned to Armory because the kernel assumes that there is a chance that Armory will open that file again, and Armory's data is still there.

All modern operating systems do this, so it always look like there is very little RAM free.  I do not know about Windows, but on Linux the kernel still keeps track of that memory after Armory quits, in case some other program happens to want the same file.  As soon as the memory is needed for something else, it is wiped and assigned to that something else.

[bluudz]

I just downloaded newest armory version and was waiting for blockchain to download, but now it got stuck on Build Database and even when I leave it run for ages it did not pass the point.

[Ente]

Is bitcoin-core up-to-date with the blockchain?
Define "ages". :-)

Ente

[Muhammed Zakir]

I just downloaded newest armory version and was waiting for blockchain to download, but now it got stuck on Build Database and even when I leave it run for ages it did not pass the point.

You are using Bitcoin Core 0.10, right? If no, upgrade it and try rebuilding database.

[bluudz]

Just noticed I'm still using old bitcoins-qt. Will update it and try again. Thanks!

[Carlton Banks]

Just noticed I'm still using old bitcoins-qt. Will update it and try again. Thanks!

Depends how old. I think version 0.9 upwards should be no problem with Armory version 0.93.x (possibly earlier versions too, all I know is that 0.9 will have been well tested). Seems like a lot of Windows users had a similar problem to yours with version 0.93, are you using Windows?

[bluudz]

Just noticed I'm still using old bitcoins-qt. Will update it and try again. Thanks!

Depends how old. I think version 0.9 upwards should be no problem with Armory version 0.93.x (possibly earlier versions too, all I know is that 0.9 will have been well tested). Seems like a lot of Windows users had a similar problem to yours with version 0.93, are you using Windows?

I'm using windows and yes I had 0.93 version.

[Muhammed Zakir]

Just noticed I'm still using old bitcoins-qt. Will update it and try again. Thanks!

Depends how old. I think version 0.9 upwards should be no problem with Armory version 0.93.x (possibly earlier versions too, all I know is that 0.9 will have been well tested). Seems like a lot of Windows users had a similar problem to yours with version 0.93, are you using Windows?

Isn't latest Armory version* meant to work with new DB? Does it still work with old DB(Core <0.10)?

P.S. * Version 0.93.x

[Carlton Banks]

Isn't latest Armory version* meant to work with new DB? Does it still work with old DB(Core <0.10)?

P.S. * Version 0.93.x

Yes, but not exclusively with 0.10.x, version 0.9.x is still properly supported

[bluudz]

Where exactly should I point armory to look for blockchain? I used to have it to main folder, but that did not work now I'm pointing here \BitData\blocks\index and it at least does something. But right now its on initializing bitcoin engine for about 30 minutes already.

[Muhammed Zakir]

Where exactly should I point armory to look for blockchain? I used to have it to main folder, but that did not work now I'm pointing here \BitData\blocks\index and it at least does something. But right now its on initializing bitcoin engine for about 30 minutes already.

Pointing the main folder of %AppData%\Bitcoin and pointing to the Bitcoin core installation(usually C:\Program Files\Bitcoin) will work.

[bluudz]

Where exactly should I point armory to look for blockchain? I used to have it to main folder, but that did not work now I'm pointing here \BitData\blocks\index and it at least does something. But right now its on initializing bitcoin engine for about 30 minutes already.

Pointing the main folder of %AppData%\Bitcoin and pointing to the Bitcoin core installation(usually C:\Program Files\Bitcoin) will work.

Well I don't have the data folder in app data as my SSD system drive is quite small so I have it on E:\ProgramFiles\BitData

Armory now moved to Buiding Database. So far 0%, but I give it some time.

[Carlton Banks]

Well I don't have the data folder in app data as my SSD system drive is quite small so I have it on E:\ProgramFiles\BitData

Armory now moved to Buiding Database. So far 0%, but I give it some time.

It's slow on mechanical disks.

Another recommendation is to change Armory settings so that "Manage Bitcoin" is turned off, not on. Quit Armory. Next, start up Bitcoin Qt, and then start up Armory only when Bitcoin Qt is synchronized (with the new Armory settings, bitcoin qt and Armory run simultaneously).

[bluudz]

Well I don't have the data folder in app data as my SSD system drive is quite small so I have it on E:\ProgramFiles\BitData

Armory now moved to Buiding Database. So far 0%, but I give it some time.

It's slow on mechanical disks.

Another recommendation is to change Armory settings so that "Manage Bitcoin" is turned off, not on. Quit Armory. Next, start up Bitcoin Qt, and then start up Armory only when Bitcoin Qt is synchronized (with the new Armory settings, bitcoin qt and Armory run simultaneously).

How slow do you reckon? I don't mind letting it run as long as it will happen eventually. I'd rather used armory as solo client instead of silmunateously with bitcoin-qt.

[Carlton Banks]

How slow do you reckon?

Haven't tried, so I can't help there. Longer than a half hour, which is what it takes on a typical SSD

I'd rather used armory as solo client instead of silmunateously with bitcoin-qt.

It's recommended against doing that for now. It genuinely does work better, or at least it solves some of the initialization issues some people had. Most likely be fixed once the Db work is totally done, or possibly alongside, it depends on the priorities of the Armory team I guess.

[Ente]

I'd rather used armory as solo client instead of silmunateously with bitcoin-qt.

You can, technically, use both the bitcoin-qt wallet and the Armory wallet on the same machine.
You can not use/install Armory only by itself without having bitcoin-qt (aka bitcoin-core aka bitcoin-cli) installed, running and synced on the same machine.

Ente

[bluudz]

Well at first I'd like to at least get armory working. Whole yday it was building database and didn't move of 0%. Something is not right.

[bluudz]

Well I don't have the data folder in app data as my SSD system drive is quite small so I have it on E:\ProgramFiles\BitData

Armory now moved to Buiding Database. So far 0%, but I give it some time.

It's slow on mechanical disks.

Another recommendation is to change Armory settings so that "Manage Bitcoin" is turned off, not on. Quit Armory. Next, start up Bitcoin Qt, and then start up Armory only when Bitcoin Qt is synchronized (with the new Armory settings, bitcoin qt and Armory run simultaneously).

When I try this my armory will crash as soon as it gets to organizing blockchain..I wonder if my blockchain structure is not damaged or something..my bitcoin-qt is running ok...I just seem to have troubles with armory.

[Carlton Banks]

Well I don't have the data folder in app data as my SSD system drive is quite small so I have it on E:\ProgramFiles\BitData

Armory now moved to Buiding Database. So far 0%, but I give it some time.

It's slow on mechanical disks.

Another recommendation is to change Armory settings so that "Manage Bitcoin" is turned off, not on. Quit Armory. Next, start up Bitcoin Qt, and then start up Armory only when Bitcoin Qt is synchronized (with the new Armory settings, bitcoin qt and Armory run simultaneously).

When I try this my armory will crash as soon as it gets to organizing blockchain..I wonder if my blockchain structure is not damaged or something..my bitcoin-qt is running ok...I just seem to have troubles with armory.

Delete armorylog.txt and armorycpplog.txt, then load Armory with Bitcoin-qt running to repeat the crash. You'll get a new copy of the 2 log files, send them to Armory support or post them up here.

[bluudz]

armorylog.txt

2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1074 - C++ block utilities loaded successfully
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1184 -
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1185 -
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1186 -
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1187 - ************************************************************
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1188 - Invoked: E:\ProgramFiles\Armory\ArmoryQt.exe
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1189 - ************************************************************
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1190 - Loading Armory Engine:
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1191 -    Armory Version        : 0.93.1
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1192 -    Armory Build:         : a9e0f25d51
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1193 -    PyBtcWallet  Version  : 1.35
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1194 - Detected Operating system: Windows
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1195 -    OS Variant            : 7-6.1.7601-SP1-Multiprocessor Free
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1196 -    User home-directory   : C:\Users\Bluudz\AppData\Roaming
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1197 -    Satoshi BTC directory : C:\Users\Bluudz\AppData\Roaming\Bitcoin\
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1198 -    Armory home dir       : C:\Users\Bluudz\AppData\Roaming\Armory\
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1199 - Detected System Specs    :
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1200 -    Total Available RAM   : 7.87 GB
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1201 -    CPU ID string         : Intel64 Family 6 Model 60 Stepping 3, GenuineIntel
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1202 -    Number of CPU cores   : 4 cores
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1203 -    System is 64-bit      : True
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1204 -    Preferred Encoding    : cp1252
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1205 -    Machine Arch          : amd64
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1206 -    Available HDD (ARM)   : 16 GB
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1207 -    Available HDD (BTC)   : 16 GB
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1208 -
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1209 - Network Name: Main Network
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1210 - Satoshi Port: 8333
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1211 - Do wlt check: True
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1212 - Named options/arguments to armoryengine.py:
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1214 -     nettimeout      : 2
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1214 -     rescan          : False
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1214 -     ignoreAllZC     : False
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1214 -     enableSupernode : False
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1214 -     disableModules  : False
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1214 -     port            : None
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1214 -     interport       : 8223
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1214 -     skipStatsReport : False
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1214 -     forceWalletCheck: False
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1214 -     rebuild         : False
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1214 -     datadir         : DEFAULT
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1214 -     clearMempool    : False
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1214 -     offline         : False
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1214 -     coverageOutputDir: None
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1214 -     armoryDBDir     : DEFAULT
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1214 -     satoshiPort     : DEFAULT
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1214 -     useTorSettings  : False
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1214 -     netlog          : False
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1214 -     keypool         : 100
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1214 -     coverageInclude : None
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1214 -     forceOnline     : False
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1214 -     skipAnnounceCheck: False
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1214 -     redownload      : False
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1214 -     multisigFile    : DEFAULT
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1214 -     disableTorrent  : False
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1214 -     testAnnounceCode: False
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1214 -     mtdebug         : False
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1214 -     logDisable      : False
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1214 -     settingsPath    : C:\Users\Bluudz\AppData\Roaming\Armory\ArmorySettings.txt
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1214 -     verbosity       : None
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1214 -     doDebug         : False
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1214 -     enableDetSign   : False
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1214 -     testnet         : False
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1214 -     rpcport         : DEFAULT
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1214 -     satoshiHome     : DEFAULT
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1214 -     satoshiRpcport  : DEFAULT
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1214 -     logFile         : C:\Users\Bluudz\AppData\Roaming\Armory\ArmoryQt.exe.log.txt
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1214 -     disableConfPermis: False
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1215 - Other arguments:
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1218 - ************************************************************
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:1613 - C++ block utilities loaded successfully
2015-04-09 18:48 (INFO) -- BDM.pyc:418 - Using the asynchronous/multi-threaded BlockDataManager.
2015-04-09 18:48 (INFO) -- BDM.pyc:419 - Blockchain operations will happen in the background. 
2015-04-09 18:48 (INFO) -- BDM.pyc:420 - Devs: check TheBDM.getState() before asking for data.
2015-04-09 18:48 (INFO) -- BDM.pyc:421 - Registering addresses during rescans will queue them for
2015-04-09 18:48 (INFO) -- BDM.pyc:422 - inclusion after the current scan is completed.
2015-04-09 18:48 (INFO) -- ArmoryUtils.pyc:3517 - Using settings file: C:\Users\Bluudz\AppData\Roaming\Armory\ArmorySettings.txt
2015-04-09 18:48 (INFO) -- announcefetch.pyc:95 - Reading files in fetcher directory:
2015-04-09 18:48 (INFO) -- announcefetch.pyc:104 -    announce         : ba74fe88b6d2c295f434f6e83c58960f6bd54686ba6dce824054686930a67981
2015-04-09 18:48 (INFO) -- announcefetch.pyc:104 -    bootstrap        : b62c08932668ce162d51226135940724e90f4c71704ac936f74cc153b34cc251
2015-04-09 18:48 (INFO) -- announcefetch.pyc:104 -    changelog        : e24b19df7aa56608725ec2352a8ad14b358d0392fca946033ed7581fb6eb1f54
2015-04-09 18:48 (INFO) -- announcefetch.pyc:104 -    downloads        : 74234e392e918958f48bf56644239a2cf932e7a3d76ee7b3410e78843a33965f
2015-04-09 18:48 (INFO) -- announcefetch.pyc:104 -    notify           : 7d5ded1526ea4fd3ec0f5d83f4d33c069a9d4688f4dd2ebd5d14dd1add720ae6
2015-04-09 18:48 (INFO) -- announcefetch.pyc:271 - Fetching: https://bitcoinarmory.com/announce.txt?osvar=7&os=win&ver=0.93.1&id=8622e602
2015-04-09 18:48 (INFO) -- ArmoryQt.py:2735 - loadWalletsAndSettings
2015-04-09 18:48 (INFO) -- ArmoryQt.py:2789 - Loading wallets...
2015-04-09 18:48 (INFO) -- ArmoryQt.py:2848 - Number of wallets read in: 1
2015-04-09 18:48 (INFO) -- ArmoryQt.py:2853 -    Wallet (tmh8bdy1):    "Restored - tmh8bdy1             "   (Encrypted)
2015-04-09 18:48 (INFO) -- ArmoryQt.py:2297 - Setting up networking...
2015-04-09 18:48 (INFO) -- ArmoryQt.py:2326 - Internet status: 0
2015-04-09 18:48 (INFO) -- ArmoryQt.py:2524 - loadBlockchainIfNecessary
2015-04-09 18:48 (ERROR) -- ArmoryQt.py:1323 - 8 attempts to load blockchain failed.  Remove mempool.bin.
2015-04-09 18:48 (ERROR) -- ArmoryQt.py:1328 - File mempool.bin does not exist. Nothing deleted.
2015-04-09 18:48 (INFO) -- ArmoryQt.py:2545 - Setting netmode: 1
2015-04-09 18:48 (INFO) -- ArmoryQt.py:1514 - setupUriRegistration
2015-04-09 18:48 (INFO) -- ArmoryQt.py:1582 - Armory already registered for current user.  Done!
2015-04-09 18:48 (INFO) -- ArmoryQt.py:664 - Usermode: Advanced
2015-04-09 18:48 (INFO) -- ArmoryQt.py:1809 - Changing usermode:
2015-04-09 18:48 (INFO) -- ArmoryQt.py:1810 -    From: Advanced
2015-04-09 18:48 (INFO) -- ArmoryQt.py:1818 -      To: Advanced
2015-04-09 18:48 (INFO) -- ArmoryQt.py:6021 - Dashboard switched to "Scanning" mode
2015-04-09 18:48 (INFO) -- Networking.pyc:65 - Connection initiated.  Start handshake
2015-04-09 18:48 (INFO) -- ArmoryQt.py:6021 - Dashboard switched to "Scanning" mode
2015-04-09 18:48 (INFO) -- Networking.pyc:156 - Received version message from peer:
2015-04-09 18:48 (INFO) -- Networking.pyc:157 -    Version:     70002
2015-04-09 18:48 (INFO) -- Networking.pyc:158 -    SubVersion:  /Satoshi:0.10.0/
2015-04-09 18:48 (INFO) -- Networking.pyc:159 -    TimeStamp:   1428601701
2015-04-09 18:48 (INFO) -- Networking.pyc:160 -    StartHeight: 351417
2015-04-09 18:48 (INFO) -- Networking.pyc:357 - Handshake finished, connection open!




armorycpplog.txt



Log file opened at 1428601696: C:\Users\Bluudz\AppData\Roaming\Armory\armorycpplog.txt
-INFO  - 1428601698: (..\BlockUtils.cpp:894) blkfile dir: C:\Users\Bluudz\AppData\Roaming\Bitcoin\blocks
-INFO  - 1428601698: (..\BlockUtils.cpp:895) lmdb dir: C:\Users\Bluudz\AppData\Roaming\Armory\databases
-INFO  - 1428601698: (..\lmdb_wrapper.cpp:478) Opening databases...
-INFO  - 1428601698: (..\BlockUtils.cpp:1226) Executing: doInitialSyncOnLoad
-INFO  - 1428601698: (..\BlockUtils.cpp:1297) Total number of blk*.dat files: 1
-INFO  - 1428601698: (..\BlockUtils.cpp:1298) Total blockchain bytes: 16,777,216
-INFO  - 1428601698: (..\BlockUtils.cpp:1671) Reading headers from db
-INFO  - 1428601700: (..\BlockUtils.cpp:1697) Found 351408 headers in db
-DEBUG - 1428601700: (..\Blockchain.cpp:211) Organizing chain w/ rebuild
-WARN  - 1428601701: (..\BlockUtils.cpp:1327) --- Fetching SSH summaries for 1000 registered addresses
-WARN  - 1428601702: (..\BlockUtils.cpp:246) Couldn't find top block hash in last seen blk file. Searching for it further down the chain
-ERROR - 1428601702: (..\BlockUtils.cpp:285) Failed to find last known top block hash in blk files. Rescanning all headers
-INFO  - 1428601702: (..\BlockUtils.cpp:1340) Left off at file 0, offset 0
-INFO  - 1428601702: (..\BlockUtils.cpp:1343) Reading headers and building chain...
-INFO  - 1428601702: (..\BlockUtils.cpp:1344) Starting at block file 0 offset 0
-INFO  - 1428601702: (..\BlockUtils.cpp:1346) Block height 351371
-DEBUG - 1428601703: (..\Blockchain.cpp:211) Organizing chain w/ rebuild
-INFO  - 1428601704: (..\BlockUtils.cpp:1381) Looking for first unrecognized block
-INFO  - 1428601704: (..\BlockUtils.cpp:1532) Loading block data... file 0 offset 0