0.96.1 testing build #4 - page 7. | Bitcointalksearch.org

Mr.Vice

member

Activity: 96

Merit: 10

Quote

Thx mr Vice, but unfortunately it didnt work out for me. I'm logged in as administrator and it was already owner of the folder and has full permissions.
I did change it to server=1. Still crashing at some %.

@creamers: I'm sorry to hear that :-/
Actually I've been undergoing quite similar issues like you are with Core (0.14+) and Armory (0.96+). These issues where mostly caused by AntiVirus software (McAfee), to be specific it was due to the real-time scanner. I'm not sure if I remember it right that Windows Server R2 2008 has a buildt in Windows Defender? Because from what I know WinDef hasn't really changed over the years (Win10 has practically no difference with the ones in Vista, 7 etc.).

What I've done was first uninstalling all McAfee AV files and so on and tried running Core and Armory only with WinDef. But that hasn't worked verry well either. To prevent it from interfering you have two options: deactivate real-time scanner or set up exceptions for specific directories. For me that worked, so I really hope you can solve it the same way.

1) Exceptions for the following paths:
C:\Users\..\AppData\Roaming\Bitcoin (or your specific Core folder)
C:\Users\..\AppData\Roaming\Armory (like above)

2) Exceptions for the following processes:
C:\ProgramFiles\Armory\ArmoryQt.exe (please look up your installation path, it may differ from mine)
C:\ProgramFiles\Bitcoin\bitcoin-qt.exe (like above)
C:\ProgramFiles\Bitcoin\bitcoind.exe (like above)

But I would first recommend to just deactivate real-time scanner of WinDef to test if this is the cause (I do not want to hurt your security with my recommendations, so if you're not sure about that you should skip this and try the exceptions first). After that delete your database folder of the Armory directory to force a rebuild & rescan. Another thing I've noticed is that WinDef might interfer in the shut-down process of Armory, where some processes in background are still running even if you closed it properly. So to ensure that isn't the case I would also prefer to restart your server before you try to run Armory again (if restarting is possible for you - or if it has to be online 24/7).

creamers

newbie

Activity: 53

Merit: 0

Thank you.

It ran all night, but after importing a paper backup, armorydb.exe was very busy and finally it crashed with the following in the logfiles:

armorylog

Quote

2017-06-04 08:34:08 (INFO) -- qtdialogs.pyc:10895 - Wallet Restore Complete!

armorycpplog

Quote

Log file opened at 18:42:54.000: D:\Armory Database\armorycpplog.txt
-ERROR - 17:27:46.070: (..\SocketObject.cpp:440) POLLERR error in readAndWrite
Log file opened at 17:38:34.000: D:\Armory Database\armorycpplog.txt
-ERROR - 22:04:07.928: (..\SocketObject.cpp:440) POLLERR error in readAndWrite
Log file opened at 22:09:55.000: D:\Armory Database\armorycpplog.txt
-ERROR - 14:58:31.580: (..\SocketObject.cpp:440) POLLERR error in readAndWrite
Log file opened at 11:18:23.000: D:\Armory Database\armorycpplog.txt
Log file opened at 12:33:37.000: D:\Armory Database\armorycpplog.txt
Log file opened at 16:26:35.000: D:\Armory Database\armorycpplog.txt
-ERROR - 16:26:42.942: (c:\users\goat\code\armory3\cppforswig\DataObject.h:286) exhausted entries in Arguments object
-ERROR - 16:26:42.942: (..\SwigClient.cpp:61) exhausted entries in Arguments object
Log file opened at 16:30:31.000: D:\Armory Database\armorycpplog.txt
Log file opened at 19:22:08.000: D:\Armory Database\armorycpplog.txt
-ERROR - 21:47:03.277: (..\SocketObject.cpp:440) POLLERR error in readAndWrite
Log file opened at 21:47:58.000: D:\Armory Database\armorycpplog.txt
Log file opened at 22:02:54.000: D:\Armory Database\armorycpplog.txt
Log file opened at 23:46:04.000: D:\Armory Database\armorycpplog.txt

dblog

Quote

-INFO - 09:00:01.737: (..\BlockchainScanner.cpp:650) scanned from height #430571 to #431600
-INFO - 09:00:15.183: (..\BlockchainScanner.cpp:650) scanned from height #431601 to #432267
-INFO - 09:00:30.488: (..\BlockchainScanner.cpp:650) scanned from height #432268 to #432970
-INFO - 09:00:43.452: (..\BlockchainScanner.cpp:650) scanned from height #432971 to #433637
-INFO - 09:00:44.981: (..\BlockchainScanner.cpp:650) scanned from height #433638 to #433787
-INFO - 09:00:44.293: (..\BlockchainScanner.cpp:225) scanned transaction history in 1596.52s
-INFO - 09:00:45.698: (..\BlockchainScanner.cpp:1560) resolving txhashes
-INFO - 09:02:22.824: (..\BlockchainScanner.cpp:1616) 11 blocks hit by tx filters
-ERROR - 09:02:24.696: (..\BlockchainScanner.cpp:1405) Block deser error while processing tx filters:
-ERROR - 09:02:24.712: (..\BlockchainScanner.cpp:1406) raw data does not match expected block hash
-ERROR - 09:02:24.712: (..\BlockchainScanner.cpp:1407) Skipping this block
-ERROR - 09:02:24.712: (..\BlockchainScanner.cpp:1405) Block deser error while processing tx filters:
-ERROR - 09:02:24.728: (..\BlockchainScanner.cpp:1406) raw data does not match expected block hash
-ERROR - 09:02:24.728: (..\BlockchainScanner.cpp:1407) Skipping this block
-ERROR - 09:02:26.005: (..\BlockchainScanner.cpp:1405) Block deser error while processing tx filters:
-ERROR - 09:02:26.005: (..\BlockchainScanner.cpp:1406) raw data does not match expected block hash
-ERROR - 09:02:26.021: (..\BlockchainScanner.cpp:1407) Skipping this block
-ERROR - 09:02:26.021: (..\BlockchainScanner.cpp:1405) Block deser error while processing tx filters:
-ERROR - 09:02:26.036: (..\BlockchainScanner.cpp:1406) raw data does not match expected block hash
-ERROR - 09:02:26.036: (..\BlockchainScanner.cpp:1407) Skipping this block
-ERROR - 09:02:26.348: (..\BlockchainScanner.cpp:1405) Block deser error while processing tx filters:
-ERROR - 09:02:26.364: (..\BlockchainScanner.cpp:1406) raw data does not match expected block hash
-ERROR - 09:02:26.364: (..\BlockchainScanner.cpp:1407) Skipping this block
-ERROR - 09:02:26.364: (..\BlockchainScanner.cpp:1405) Block deser error while processing tx filters:
-ERROR - 09:02:26.395: (..\BlockchainScanner.cpp:1406) raw data does not match expected block hash
-ERROR - 09:02:26.395: (..\BlockchainScanner.cpp:1407) Skipping this block

Here it crashed!

469666 blocks are shown in BitcoinCore and it's uptodate, but Armory only shows 433xxx blocks and is online ?!
That's probably also the reason that I don't have a correct end balance and missing transactions.

I'll try 0.96.2 , let me know what you want me to do/test.

goatpig

legendary

Activity: 3640

Merit: 1345

Armory Developer

Ima push another build tomorrow, try with that then.

creamers

newbie

Activity: 53

Merit: 0

Thx mr Vice, but unfortunately it didnt work out for me. I'm logged in as administrator and it was already owner of the folder and has full permissions.
I did change it to server=1. Still crashing at some %.

I also copied everything from the bitcoincore database folder to a new folder to make sure windows hasnt a problem with the file.
Bitcoin core also hasnt a problem with it's own database.

armorylog since the beginning with all the errors in it:
https://pastebin.com/QUSgMCd5

dblog since:
https://pastebin.com/DaDhxH63

Bitcoincore is now catching up and I'm running armory with an unchecked 'let armory run bitcoind in background' to see what happens.

Hope someone can make sence out of the logfiles to solve this for me and others who want to update from older versions.

*EDIT:

For it's further than before with unchecked 'let armory run bitcoind in background' and server=1 and having bitcoin core running next to it: https://ibb.co/ecE1oF
100% and now it's Organizing chain: https://ibb.co/iA8fFv
Now finished: https://ibb.co/d9KCvv
BUT, after closing both bitcoin core and armory, I see the armorydb.exe still running under processes taking up 100% on one core?
Starting armory with the armorydb.exe left behind and still running, nothing happens.
Killed the armorydb.exe and restarted armory.
Seems like it's going again but waiting for it to get 'online'
ONLINE and Working
somehow it worked to disable the bitcoind background option, but closing Armory isnt going well cause armorydb.exe stays behind...
Balance ended into zero ! I forced rebalance after restart, but it began building databases again )-:

Mr.Vice

member

Activity: 96

Merit: 10

Quote from: creamers on May 31, 2017, 04:14:47 PM

Unfortunately it crashed again at a higher % but the application eventlog says it has to do with the same file (blk00646.dat).
http://imgur.com/a/XitHD

After closing the crash notification window if found some more info in the logfiles. Maybe this clears things up?

The strange thing about this is that I've been using the old version and the old bitcoin core already for a long time on this server, there should be something that causes this. If we find it, it will be beneficial for others and new users.

Quote

-INFO - 19:28:30.643: (..\DatabaseBuilder.cpp:268) parsed block file #647
-INFO - 19:29:02.015: (..\DatabaseBuilder.cpp:268) parsed block file #649
-INFO - 19:33:55.406: (..\DatabaseBuilder.cpp:268) parsed block file #651
-INFO - 19:34:11.584: (..\DatabaseBuilder.cpp:268) parsed block file #653
-ERROR - 22:04:06.118: (..\SocketObject.cpp:126) poll() error in writeToSocket: 10022
-ERROR - 22:04:06.211: (..\BitcoinP2P.cpp:1027) caught SocketError exception in processDataStackThread: poll() error in writeToSocket: 10022
-INFO - 22:04:06.320: (..\BitcoinP2P.cpp:969) Disconnected from Bitcoin node

@creamers:
I think I know what's causing your problem. I've gotten a similar issue when I was upgrading to Core (0.14+) and Armory (0.96+). The Bitcoin Core versions since 0.14 can cause a right management bug on Windows machines, which does not affect BitcoinQt, but every software that runs on top of it.

Could you please check the properties of your Bitcoin folder by right clicking on the folder, selecting properties, tab security and go to extended or additional (I'm not sure how that button is called in English, it's the last one at the bottom). Now you'll see another pop-up window where it says "owner:". When it says "SYSTEM" you have to change that into your local user's account, otherwise you'll ran into the same issue over and over.

Afterwards start BitcoinQt only and let it completely sync the blockchain. Then exit BitcoinQt, go to your Bitcoin folder and modify your bitcoin.conf file. Remove the lines with rpcuser and rpcpassword, add the following line "server=1" and save it. Now let Armory do a rebuild & rescan and everything should work fine.

Mr.Vice

member

Activity: 96

Merit: 10

@goatpig:
server=1 and cookie auth works fine... actually everything essential works well! :-D
There are only some minor bugs left regarding the property window (address explorer like I call it). E.g. in the offline version the right click options don't work and the pop-up window when clicking on specific addresses does not show up. And when you are in the sending dialoge and open the address book you can not select addresses. You have to right click and copy/paste the address in order to select it.

creamers

newbie

Activity: 53

Merit: 0

Quote

Restarted the 2008R2 server and running armory for the third time to see what happens.

Same problem again at the same percentage.

any suggestions ?

Betatester

member

Activity: 118

Merit: 10

Quote from: goatpig on May 14, 2017, 05:32:57 PM

--------------

Linux users:

If the build fails to run on your setup (unknown instructions), it means your CPU is missing SSE4/AES/PCLMUL instructions. There will be a fail safe gcc4.7 build without any of those instructions for the actual release, but for the testing phase, you'll want to build the code directly on your machine. The build process has been fixed so you should have an easy time with it.

--------------

So what setup (Distro, CPU, RAM) did you use for those builds? I will buy such a machine to get my coins sent.

creamers

newbie

Activity: 53

Merit: 0

Unfortunately it crashed again at a higher % but the application eventlog says it has to do with the same file (blk00646.dat).
http://imgur.com/a/XitHD

After closing the crash notification window if found some more info in the logfiles. Maybe this clears things up?

The strange thing about this is that I've been using the old version and the old bitcoin core already for a long time on this server, there should be something that causes this. If we find it, it will be beneficial for others and new users.

Quote

-INFO - 19:28:30.643: (..\DatabaseBuilder.cpp:268) parsed block file #647
-INFO - 19:29:02.015: (..\DatabaseBuilder.cpp:268) parsed block file #649
-INFO - 19:33:55.406: (..\DatabaseBuilder.cpp:268) parsed block file #651
-INFO - 19:34:11.584: (..\DatabaseBuilder.cpp:268) parsed block file #653
-ERROR - 22:04:06.118: (..\SocketObject.cpp:126) poll() error in writeToSocket: 10022
-ERROR - 22:04:06.211: (..\BitcoinP2P.cpp:1027) caught SocketError exception in processDataStackThread: poll() error in writeToSocket: 10022
-INFO - 22:04:06.320: (..\BitcoinP2P.cpp:969) Disconnected from Bitcoin node

Quote

2017-05-31 19:34:11 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-31 22:04:29 (INFO) -- ArmoryQt.py:5389 - BDM state is scanning -- force shutdown BDM
2017-05-31 22:04:29 (INFO) -- SDM.pyc:456 - Called stopBitcoind
2017-05-31 22:04:31 (ERROR) -- ArmoryQt.py:5402 - Strange error during shutdown
Traceback (most recent call last):
  File "ArmoryQt.py", line 5393, in closeForReal
  File "SDM.pyc", line 482, in stopBitcoind
  File "armoryengine\ArmoryUtils.pyc", line 828, in LOGERROR
TypeError: cannot concatenate 'str' and 'exceptions.RuntimeError' objects
2017-05-31 22:04:31 (INFO) -- ArmoryQt.py:5404 - Attempting to close the main window!

Restarted the 2008R2 server and running armory for the third time to see what happens.

creamers

newbie

Activity: 53

Merit: 0

Quote from: goatpig on May 30, 2017, 04:55:17 PM

Is D: a USB drive?

No, a second (raid 1) volume/disk. (same disk where bitcoin core stores it's database)

I'll try to start bitcoin core again and see if it syncs up. Then I'll try armory again.

*EDIT: so far so good the second time around: http://imgur.com/a/0b9fS

goatpig

legendary

Activity: 3640

Merit: 1345

Armory Developer

Is D: a USB drive?

creamers

newbie

Activity: 53

Merit: 0

I first updated bitcoin core to the latest version. This went without problem.
"C:\Program Files\Bitcoin\bitcoin-qt.exe" -datadir="D:\Bitcoin Core Database"

After this I removed the old armory database and installed armory. (not deinstalled the armory client)

I started armory:
"C:\Program Files (x86)\Armory\ArmoryQt.exe" --datadir="D:\Armory Database" --satoshi-datadir="D:\Bitcoin Core Database"

After a while I got this error:
http://i65.tinypic.com/10r7g1t.png

Code:

(ERROR) ArmoryUtils.pyc:3744 - Unsupported language specified. Defaulting to English (en)
(WARNING) SDM.pyc:395 - Spawning DB with command:./ArmoryDB.exe --db-type="DB_FULL" --cookie --satoshi-datadir="D:\Bitcoin Core Database\blocks" --datadir="D:\Armory Database" --dbdir="D:\Armory Database\databases"

armorylog.txt https://pastebin.com/Q7CaghHj
dblog.txt https://pastebin.com/XVCK9Qyv

Then I saw this in eventlog on server 2008R2:

Quote

Windows cannot access the file D:\Bitcoin Core Database\blocks\blk00646.dat for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program ArmoryDB.exe because of this error.

Strange reason. There is no virusscanner installed and the file is accessible.

What should be the next step.? Should I try again or are there things you need to know before I do, so you can solve this for future updates?

goatpig

legendary

Activity: 3640

Merit: 1345

Armory Developer

Quote from: creamers on May 29, 2017, 04:58:46 PM

Q: should I download en just install everything on the 'online' server without deinstalling stuff first ? What do you advice ?

If you are updating from 0.94, you will need to delete your Armory database as it is not compatible with 0.95+. The installer just replace the binaries. Uninstalling does not wipe the user data (db/wallets/settings), so you will have to wipe the db data manually.

Quote

Q: is my cold wallet still usable with the new versions ? When isnt it usable anymore?

No difference with 0.95. 0.96 default settings are backwards compatible with up to 0.92. If you use the new scripts types (deviate from the defaults), you will need a 0.96+ signer.

Quote

Q: I assume my paper wallet is still usable on the new armory version?

This stuff will always be supported.

Spieler636

brand new

Activity: 0

Merit: 0

So I checked and I actually had clamav installed. I am pretty sure thought, that it didn't do anything, since I didn't let it delete anything.
I also have ufw installed, which also shouldn't do anything. Can I make Bitcoin Core check the blockchain maybe? I didn't find any option for that anywhere.

creamers

newbie

Activity: 53

Merit: 0

Hi !

I've been using a cold armory wallet on my ubuntu pi version 94.x and a online version on server 2008R2 94.x.
Core is version 13.x (if I'm not mistaken)

Q: should I download en just install everything on the 'online' server without deinstalling stuff first ? What do you advice ?
Q: is my cold wallet still usable with the new versions ? When isnt it usable anymore?
Q: I assume my paper wallet is still usable on the new armory version?

Thanks in advance ... Hopefully it's gonna be a nice migration Grin

goatpig

legendary

Activity: 3640

Merit: 1345

Armory Developer

Quote from: Mr.Vice on May 26, 2017, 06:05:01 AM

@goatpig: I just wanted to thank you for everything man, finally everything works with Armory 0.96.1-testing. There where multiple issues that have caused my unique problem.

1): McAfee AV was configured to (not only) real-time scanning, but also with the option of direct blocking "threats" before written on HDD.
2): Encrypted HDD with AES-CBC 256bit.
3): Custom bitcoin.conf with server=1 and the old rpcuser & rpcpasswords set that are deprecated now (cookie-auth).

cookie auth replaces rpclogin/password

You need server=1 to enable the RPC though.

Spieler636

brand new

Activity: 0

Merit: 0

It doesn't get finished anymore. After 30% of scanning AmoryDB closes. If I start it in a terminal it gives a lot of messages about skipping blockes and no history to be found.

Code:

2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1135 - C++ block utilities loaded successfully
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:664 - Executing popen: free -m
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:664 - Executing popen: ['cat', '/proc/cpuinfo']
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1252 -
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1253 -
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1254 -
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1255 - ************************************************************
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1256 - Invoked: /usr/local/bin/../lib/armory/ArmoryQt.py
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1257 - ************************************************************
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1258 - Loading Armory Engine:
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1259 - Armory Version : 0.96.0.1
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1260 - Armory Build: : 654b380411
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1261 - PyBtcWallet Version : 1.35
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1262 - Detected Operating system: Linux
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1263 - OS Variant : Ubuntu-16.04-xenial
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1264 - User home-directory : /home/username
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1265 - Satoshi BTC directory : /home/username/.bitcoin/
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1266 - Armory home dir : /home/username/.armory/
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1267 - Detected System Specs :
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1268 - Total Available RAM : 15.63 GB
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1269 - CPU ID string : Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1270 - Number of CPU cores : 4 cores
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1271 - System is 64-bit : True
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1272 - Preferred Encoding : UTF-8
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1273 - Machine Arch : x86_64
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1274 - Available HDD (ARM) : 390 GB
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1275 - Available HDD (BTC) : 390 GB
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1276 -
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1277 - Network Name: Main Network
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1278 - Satoshi Port: 8333
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1279 - Do wlt check: True
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1280 - Named options/arguments to armoryengine.py:
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1282 - thread_count : -1
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1282 - rescan : False
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1282 - ignoreAllZC : False
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1282 - rescanBalance : False
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1282 - disableModules : False
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1282 - port : None
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1282 - interport : 8223
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1282 - coverageOutputDir: None
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1282 - forceWalletCheck: False
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1282 - regtest : False
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1282 - rebuild : False
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1282 - nettimeout : 2
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1282 - datadir : DEFAULT
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1282 - clearMempool : False
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1282 - offline : False
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1282 - armoryDBDir : DEFAULT
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1282 - armorydb_port : 9001
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1282 - satoshiPort : DEFAULT
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1282 - useTorSettings : False
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1282 - netlog : False
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1282 - keypool : 100
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1282 - coverageInclude : None
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1282 - forceOnline : False
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1282 - redownload : False
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1282 - rpcBindAddr : 127.0.0.1
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1282 - armorydb_ip : 127.0.0.1
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1282 - multisigFile : DEFAULT
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1282 - ram_usage : -1
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1282 - mtdebug : False
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1282 - logDisable : False
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1282 - settingsPath : /home/username/.armory/ArmorySettings.txt
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1282 - language : en
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1282 - db_type : DB_FULL
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1282 - doDebug : False
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1282 - enableDetSign : True
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1282 - disableConfPermis: False
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1282 - testnet : False
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1282 - rpcport : DEFAULT
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1282 - satoshiHome : DEFAULT
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1282 - satoshiRpcport : DEFAULT
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1282 - logFile : /home/username/.armory/ArmoryQt.py.log.txt
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1282 - verbosity : None
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1283 - Other arguments:
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1286 - ************************************************************
2017-05-25 15:50:44 (INFO) -- ArmoryUtils.py:1689 - C++ block utilities loaded successfully
2017-05-25 15:50:45 (INFO) -- ArmoryUtils.py:3587 - Using settings file: /home/username/.armory/ArmorySettings.txt
2017-05-25 15:50:45 (INFO) -- ArmoryUtils.py:3747 - Using Language: de
2017-05-25 15:50:45 (INFO) -- BDM.py:365 - Using the asynchronous/multi-threaded BlockDataManager.
2017-05-25 15:50:45 (INFO) -- BDM.py:366 - Blockchain operations will happen in the background.
2017-05-25 15:50:45 (INFO) -- BDM.py:367 - Devs: check TheBDM.getState() before asking for data.
2017-05-25 15:50:45 (INFO) -- BDM.py:368 - Registering addresses during rescans will queue them for
2017-05-25 15:50:45 (INFO) -- BDM.py:369 - inclusion after the current scan is completed.
2017-05-25 15:50:45 (INFO) -- ArmoryUtils.py:3587 - Using settings file: /home/username/.armory/ArmorySettings.txt
2017-05-25 15:50:45 (INFO) -- ArmoryQt.py:2047 - loadWalletsAndSettings
2017-05-25 15:50:45 (INFO) -- ArmoryQt.py:2107 - Loading wallets...
2017-05-25 15:50:46 (INFO) -- ArmoryQt.py:2172 - Number of wallets read in: 2
2017-05-25 15:50:46 (INFO) -- ArmoryQt.py:2177 - Wallet (BbxgbkBH): "Primary Wallet " (Encrypted)
2017-05-25 15:50:46 (INFO) -- ArmoryQt.py:2177 - Wallet (bQ6dchyR): "Cold Storage (Watch) " (No Encryption)
2017-05-25 15:50:46 (INFO) -- ArmoryQt.py:2182 - Loading Multisig Lockboxes
2017-05-25 15:50:46 (INFO) -- ArmoryQt.py:1749 - acquiring process mutex...
2017-05-25 15:50:46 (INFO) -- ArmoryQt.py:1388 - setupUriRegistration
2017-05-25 15:50:46 (INFO) -- ArmoryUtils.py:664 - Executing popen: gconftool-2 --get /desktop/gnome/url-handlers/bitcoin/command
2017-05-25 15:50:46 (INFO) -- ArmoryUtils.py:664 - Executing popen: xdg-mime query default x-scheme-handler/bitcoin
2017-05-25 15:50:46 (INFO) -- ArmoryQt.py:562 - Usermode: Expert
2017-05-25 15:50:46 (INFO) -- ArmoryQt.py:1684 - Changing usermode:
2017-05-25 15:50:46 (INFO) -- ArmoryQt.py:1685 - From: Expert
2017-05-25 15:50:46 (INFO) -- ArmoryQt.py:1693 - To: Expert
2017-05-25 15:50:46 (INFO) -- ArmoryQt.py:1822 - startBitcoindIfNecessary
2017-05-25 15:50:46 (INFO) -- ArmoryQt.py:1858 - setSatoshiPaths
2017-05-25 15:50:46 (INFO) -- ArmoryUtils.py:664 - Executing popen: ['whereis', 'bitcoind']
2017-05-25 15:50:46 (INFO) -- SDM.py:289 - "whereis" returned: ['/usr/bin/bitcoind']
2017-05-25 15:50:46 (INFO) -- SDM.py:169 - Found bitcoind in the following places:
2017-05-25 15:50:46 (INFO) -- SDM.py:171 - /usr/bin/bitcoind
2017-05-25 15:50:46 (INFO) -- SDM.py:171 - /usr/bin/bitcoind
2017-05-25 15:50:46 (INFO) -- SDM.py:173 - Using: /usr/bin/bitcoind
2017-05-25 15:50:46 (INFO) -- SDM.py:337 - Called startBitcoind
2017-05-25 15:50:58 (INFO) -- ArmoryUtils.py:664 - Executing popen: ['/usr/bin/bitcoind', '-datadir=/home/username/.bitcoin/']
2017-05-25 15:50:58 (INFO) -- SDM.py:442 - PID of bitcoind: 19615
2017-05-25 15:50:58 (INFO) -- SDM.py:443 - PID of armory: 19581
2017-05-25 15:50:58 (INFO) -- ArmoryUtils.py:664 - Executing popen: ['python', '/usr/local/lib/armory/guardian.py', '19581', '19615']
2017-05-25 15:50:58 (INFO) -- ArmoryQt.py:1858 - setSatoshiPaths
2017-05-25 15:50:58 (WARNING) -- SDM.py:395 - Spawning DB with command:ArmoryDB --db-type="DB_FULL" --cookie --satoshi-datadir="/home/username/.bitcoin/blocks" --datadir="/home/username/.armory/" --dbdir="/home/username/.armory/databases"
2017-05-25 15:50:58 (INFO) -- ArmoryUtils.py:664 - Executing popen: ['ArmoryDB', '--db-type="DB_FULL"', '--cookie', '--satoshi-datadir="/home/username/.bitcoin/blocks"', '--datadir="/home/username/.armory/"', '--dbdir="/home/username/.armory/databases"']
2017-05-25 15:50:58 (INFO) -- ArmoryQt.py:1810 - Connecting on port 62962
2017-05-25 15:50:58 (INFO) -- ArmoryQt.py:1910 - Setting netmode: 1
2017-05-25 15:50:58 (INFO) -- ArmoryQt.py:1892 - loadBlockchainIfNecessary
2017-05-25 15:50:58 (ERROR) -- ArmoryQt.py:1191 - 8 attempts to load blockchain failed. Remove mempool.bin.
2017-05-25 15:50:58 (ERROR) -- ArmoryQt.py:1196 - File mempool.bin does not exist. Nothing deleted.
2017-05-25 15:50:58 (INFO) -- ArmoryQt.py:1910 - Setting netmode: 1
2017-05-25 15:50:58 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 15:50:58 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 15:50:58 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 15:50:59 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 15:50:59 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 15:50:59 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 15:50:59 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 15:50:59 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 15:51:00 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 15:51:00 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 15:51:00 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 15:51:00 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 15:51:02 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 15:51:02 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 15:51:02 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 15:51:02 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 15:51:16 (INFO) -- ArmoryQt.py:4548 - Dashboard switched to auto-InitSync
2017-05-25 15:51:16 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 15:51:39 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 15:51:40 (INFO) -- ArmoryQt.py:5389 - BDM state is scanning -- force shutdown BDM
2017-05-25 15:51:40 (INFO) -- SDM.py:456 - Called stopBitcoind
2017-05-25 15:51:41 (INFO) -- ArmoryQt.py:5404 - Attempting to close the main window!
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1135 - C++ block utilities loaded successfully
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:664 - Executing popen: free -m
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:664 - Executing popen: ['cat', '/proc/cpuinfo']
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1252 -
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1253 -
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1254 -
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1255 - ************************************************************
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1256 - Invoked: /usr/local/bin/../lib/armory/ArmoryQt.py
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1257 - ************************************************************
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1258 - Loading Armory Engine:
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1259 - Armory Version : 0.96.0.1
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1260 - Armory Build: : 654b380411
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1261 - PyBtcWallet Version : 1.35
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1262 - Detected Operating system: Linux
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1263 - OS Variant : Ubuntu-16.04-xenial
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1264 - User home-directory : /home/username
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1265 - Satoshi BTC directory : /home/username/.bitcoin/
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1266 - Armory home dir : /home/username/.armory/
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1267 - Detected System Specs :
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1268 - Total Available RAM : 15.63 GB
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1269 - CPU ID string : Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1270 - Number of CPU cores : 4 cores
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1271 - System is 64-bit : True
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1272 - Preferred Encoding : UTF-8
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1273 - Machine Arch : x86_64
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1274 - Available HDD (ARM) : 390 GB
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1275 - Available HDD (BTC) : 390 GB
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1276 -
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1277 - Network Name: Main Network
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1278 - Satoshi Port: 8333
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1279 - Do wlt check: True
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1280 - Named options/arguments to armoryengine.py:
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1282 - thread_count : -1
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1282 - rescan : False
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1282 - ignoreAllZC : False
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1282 - rescanBalance : False
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1282 - disableModules : False
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1282 - port : None
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1282 - interport : 8223
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1282 - coverageOutputDir: None
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1282 - forceWalletCheck: False
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1282 - regtest : False
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1282 - rebuild : False
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1282 - nettimeout : 2
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1282 - datadir : DEFAULT
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1282 - clearMempool : False
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1282 - offline : False
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1282 - armoryDBDir : DEFAULT
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1282 - armorydb_port : 9001
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1282 - satoshiPort : DEFAULT
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1282 - useTorSettings : False
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1282 - netlog : False
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1282 - keypool : 100
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1282 - coverageInclude : None
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1282 - forceOnline : False
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1282 - redownload : False
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1282 - rpcBindAddr : 127.0.0.1
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1282 - armorydb_ip : 127.0.0.1
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1282 - multisigFile : DEFAULT
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1282 - ram_usage : -1
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1282 - mtdebug : False
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1282 - logDisable : False
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1282 - settingsPath : /home/username/.armory/ArmorySettings.txt
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1282 - language : en
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1282 - db_type : DB_FULL
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1282 - doDebug : False
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1282 - enableDetSign : True
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1282 - disableConfPermis: False
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1282 - testnet : False
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1282 - rpcport : DEFAULT
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1282 - satoshiHome : DEFAULT
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1282 - satoshiRpcport : DEFAULT
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1282 - logFile : /home/username/.armory/ArmoryQt.py.log.txt
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1282 - verbosity : None
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1283 - Other arguments:
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1286 - ************************************************************
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:1689 - C++ block utilities loaded successfully
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:3587 - Using settings file: /home/username/.armory/ArmorySettings.txt
2017-05-25 20:00:25 (INFO) -- ArmoryUtils.py:3747 - Using Language: de
2017-05-25 20:00:25 (INFO) -- BDM.py:365 - Using the asynchronous/multi-threaded BlockDataManager.
2017-05-25 20:00:25 (INFO) -- BDM.py:366 - Blockchain operations will happen in the background.
2017-05-25 20:00:25 (INFO) -- BDM.py:367 - Devs: check TheBDM.getState() before asking for data.
2017-05-25 20:00:25 (INFO) -- BDM.py:368 - Registering addresses during rescans will queue them for
2017-05-25 20:00:25 (INFO) -- BDM.py:369 - inclusion after the current scan is completed.
2017-05-25 20:00:26 (INFO) -- ArmoryUtils.py:3587 - Using settings file: /home/username/.armory/ArmorySettings.txt
2017-05-25 20:00:26 (INFO) -- ArmoryQt.py:2047 - loadWalletsAndSettings
2017-05-25 20:00:26 (INFO) -- ArmoryQt.py:2107 - Loading wallets...
2017-05-25 20:00:26 (INFO) -- ArmoryQt.py:2172 - Number of wallets read in: 2
2017-05-25 20:00:26 (INFO) -- ArmoryQt.py:2177 - Wallet (BbxgbkBH): "Primary Wallet " (Encrypted)
2017-05-25 20:00:26 (INFO) -- ArmoryQt.py:2177 - Wallet (bQ6dchyR): "Cold Storage (Watch) " (No Encryption)
2017-05-25 20:00:26 (INFO) -- ArmoryQt.py:2182 - Loading Multisig Lockboxes
2017-05-25 20:00:26 (INFO) -- ArmoryQt.py:1749 - acquiring process mutex...
2017-05-25 20:00:26 (INFO) -- ArmoryQt.py:1388 - setupUriRegistration
2017-05-25 20:00:26 (INFO) -- ArmoryUtils.py:664 - Executing popen: gconftool-2 --get /desktop/gnome/url-handlers/bitcoin/command
2017-05-25 20:00:26 (INFO) -- ArmoryUtils.py:664 - Executing popen: xdg-mime query default x-scheme-handler/bitcoin
2017-05-25 20:00:26 (INFO) -- ArmoryQt.py:562 - Usermode: Expert
2017-05-25 20:00:26 (INFO) -- ArmoryQt.py:1684 - Changing usermode:
2017-05-25 20:00:26 (INFO) -- ArmoryQt.py:1685 - From: Expert
2017-05-25 20:00:26 (INFO) -- ArmoryQt.py:1693 - To: Expert
2017-05-25 20:00:26 (INFO) -- ArmoryQt.py:1822 - startBitcoindIfNecessary
2017-05-25 20:00:26 (INFO) -- ArmoryQt.py:1858 - setSatoshiPaths
2017-05-25 20:00:26 (INFO) -- ArmoryUtils.py:664 - Executing popen: ['whereis', 'bitcoind']
2017-05-25 20:00:27 (INFO) -- SDM.py:289 - "whereis" returned: ['/usr/bin/bitcoind']
2017-05-25 20:00:27 (INFO) -- SDM.py:169 - Found bitcoind in the following places:
2017-05-25 20:00:27 (INFO) -- SDM.py:171 - /usr/bin/bitcoind
2017-05-25 20:00:27 (INFO) -- SDM.py:171 - /usr/bin/bitcoind
2017-05-25 20:00:27 (INFO) -- SDM.py:173 - Using: /usr/bin/bitcoind
2017-05-25 20:00:27 (INFO) -- SDM.py:337 - Called startBitcoind
2017-05-25 20:01:03 (INFO) -- ArmoryUtils.py:664 - Executing popen: ['/usr/bin/bitcoind', '-datadir=/home/username/.bitcoin/']
2017-05-25 20:01:03 (INFO) -- SDM.py:442 - PID of bitcoind: 3062
2017-05-25 20:01:03 (INFO) -- SDM.py:443 - PID of armory: 2806
2017-05-25 20:01:03 (INFO) -- ArmoryUtils.py:664 - Executing popen: ['python', '/usr/local/lib/armory/guardian.py', '2806', '3062']
2017-05-25 20:01:03 (INFO) -- ArmoryQt.py:1858 - setSatoshiPaths
2017-05-25 20:01:03 (WARNING) -- SDM.py:395 - Spawning DB with command:ArmoryDB --db-type="DB_FULL" --cookie --satoshi-datadir="/home/username/.bitcoin/blocks" --datadir="/home/username/.armory/" --dbdir="/home/username/.armory/databases"
2017-05-25 20:01:03 (INFO) -- ArmoryUtils.py:664 - Executing popen: ['ArmoryDB', '--db-type="DB_FULL"', '--cookie', '--satoshi-datadir="/home/username/.bitcoin/blocks"', '--datadir="/home/username/.armory/"', '--dbdir="/home/username/.armory/databases"']
2017-05-25 20:01:03 (INFO) -- ArmoryQt.py:1810 - Connecting on port 61357
2017-05-25 20:01:03 (INFO) -- ArmoryQt.py:1910 - Setting netmode: 1
2017-05-25 20:01:03 (INFO) -- ArmoryQt.py:1892 - loadBlockchainIfNecessary
2017-05-25 20:01:03 (ERROR) -- ArmoryQt.py:1191 - 9 attempts to load blockchain failed. Remove mempool.bin.
2017-05-25 20:01:03 (ERROR) -- ArmoryQt.py:1196 - File mempool.bin does not exist. Nothing deleted.
2017-05-25 20:01:03 (INFO) -- ArmoryQt.py:1910 - Setting netmode: 1
2017-05-25 20:01:03 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:01:03 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:01:04 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:01:13 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:01:24 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:01:34 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:01:42 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:01:46 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:01:50 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:01:53 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:01:54 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:01:56 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:01:56 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:01:57 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:02:01 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:02:01 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:02:01 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:02:44 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:03:06 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:03:32 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:03:53 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:04:10 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:04:29 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:04:47 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:05:06 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:05:23 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:05:42 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:06:06 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:06:30 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:06:54 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:07:25 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:07:54 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:08:21 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:08:47 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:09:14 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:09:42 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:10:12 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:10:43 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:11:14 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:11:47 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:12:19 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:12:52 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:13:11 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:13:35 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:13:52 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:14:11 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:14:29 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:14:47 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:14:58 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:15:14 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:15:28 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:15:41 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:15:55 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:16:10 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:16:25 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:16:40 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:16:55 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:17:14 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:17:35 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:17:54 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:18:13 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:18:33 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:18:51 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:19:12 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:19:33 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:19:54 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:20:11 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:20:32 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:20:54 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:21:17 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:21:38 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:21:57 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:22:27 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:22:52 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:23:17 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:24:02 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:24:35 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:24:54 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:25:16 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:25:34 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:25:56 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:26:04 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:26:27 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:26:47 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:27:05 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:27:23 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:27:44 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:28:04 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:28:17 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:28:38 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:28:58 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:29:19 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:29:39 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:30:07 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:30:27 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:30:33 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:30:42 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:31:03 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:31:23 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:31:50 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:32:16 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:32:36 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:32:51 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:33:12 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:33:34 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 20:33:54 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-25 21:35:20 (INFO) -- ArmoryQt.py:5389 - BDM state is scanning -- force shutdown BDM
2017-05-25 21:35:20 (INFO) -- SDM.py:456 - Called stopBitcoind
2017-05-25 21:35:20 (ERROR) -- ArmoryQt.py:5402 - Strange error during shutdown
Traceback (most recent call last):
File "/usr/local/bin/../lib/armory/ArmoryQt.py", line 5393, in closeForReal
TheSDM.stopBitcoind()
File "/usr/local/lib/armory/SDM.py", line 482, in stopBitcoind
LOGERROR(e)
File "/usr/local/lib/armory/armoryengine/ArmoryUtils.py", line 828, in LOGERROR
logging.error(callerStr + logstr)
TypeError: cannot concatenate 'str' and 'exceptions.RuntimeError' objects
2017-05-25 21:35:20 (INFO) -- ArmoryQt.py:5404 - Attempting to close the main window!

Code:

Log file opened at 15:50:58: /home/username/.armory/dbLog.txt
-INFO - 15:50:58: (main.cpp:29) Running on 4 threads
-INFO - 15:50:58: (main.cpp:30) Ram usage level: 4
-INFO - 15:50:58: (BlockUtils.cpp:907) blkfile dir: /home/username/.bitcoin/blocks
-INFO - 15:50:58: (BlockUtils.cpp:908) lmdb dir: /home/username/.armory/databases
-INFO - 15:50:58: (lmdb_wrapper.cpp:388) Opening databases...
-INFO - 15:50:58: (BDM_Server.h:248) Listening on port 62962
-INFO - 15:50:58: (BlockUtils.cpp:1091) Executing: doInitialSyncOnLoad
-INFO - 15:50:58: (DatabaseBuilder.cpp:169) Reading headers from db
-INFO - 15:50:58: (BDM_Server.cpp:996) registered bdv: 140e51f482b35029005d
-INFO - 15:51:00: (DatabaseBuilder.cpp:208) Found 468078 headers in db
-INFO - 15:51:02: (DatabaseBuilder.cpp:51) updating HEADERS db
-INFO - 15:51:02: (DatabaseBuilder.cpp:477) Found next block after skipping 498905bytes
-INFO - 15:51:02: (DatabaseBuilder.cpp:268) parsed block file #880
-DEBUG - 15:51:02: (Blockchain.cpp:242) Organizing chain
-INFO - 15:51:02: (DatabaseBuilder.cpp:56) updated HEADERS db in 0.434292s
-INFO - 15:51:02: (BDM_supportClasses.cpp:1841) Enabling zero-conf tracking
-INFO - 15:51:02: (BDM_supportClasses.cpp:366) Starting address registration process
-INFO - 15:51:10: (BitcoinP2P.cpp:947) Connected to Bitcoin node
-INFO - 15:51:11: (nodeRPC.cpp:59) RPC connection established
-INFO - 15:51:16: (BlockchainScanner.cpp:650) scanned from height #0 to #141861
-WARN - 15:51:37: (BDM_supportClasses.cpp:1898) running 10 zc parser threads
-INFO - 15:51:39: (BlockchainScanner.cpp:650) scanned from height #141862 to #163190
-INFO - 15:51:40: (nodeRPC.cpp:368) Bitcoin server stopping
-ERROR - 15:51:40: (SocketObject.cpp:285) POLLERR error in readFromSocketThread
-ERROR - 15:51:40: (BitcoinP2P.cpp:1027) caught SocketError exception in processDataStackThread: POLLERR error in readFromSocketThread
-INFO - 15:51:40: (BitcoinP2P.cpp:969) Disconnected from Bitcoin node

Log file opened at 20:01:03: /home/username/.armory/dbLog.txt
-INFO - 20:01:03: (main.cpp:29) Running on 4 threads
-INFO - 20:01:03: (main.cpp:30) Ram usage level: 4
-INFO - 20:01:03: (BlockUtils.cpp:907) blkfile dir: /home/username/.bitcoin/blocks
-INFO - 20:01:03: (BlockUtils.cpp:908) lmdb dir: /home/username/.armory/databases
-INFO - 20:01:03: (lmdb_wrapper.cpp:388) Opening databases...
-INFO - 20:01:03: (BDM_Server.h:248) Listening on port 61357
-INFO - 20:01:03: (BlockUtils.cpp:1091) Executing: doInitialSyncOnLoad
-INFO - 20:01:03: (BDM_Server.cpp:996) registered bdv: 8503acf1efeb3bf0de21
-INFO - 20:01:03: (DatabaseBuilder.cpp:169) Reading headers from db
-INFO - 20:01:56: (DatabaseBuilder.cpp:208) Found 468078 headers in db
-INFO - 20:01:57: (DatabaseBuilder.cpp:51) updating HEADERS db
-INFO - 20:02:00: (DatabaseBuilder.cpp:477) Found next block after skipping 498905bytes
-INFO - 20:02:01: (DatabaseBuilder.cpp:268) parsed block file #880
-DEBUG - 20:02:01: (Blockchain.cpp:242) Organizing chain
-INFO - 20:02:01: (DatabaseBuilder.cpp:56) updated HEADERS db in 0.639652s
-INFO - 20:02:01: (BDM_supportClasses.cpp:1841) Enabling zero-conf tracking
-INFO - 20:02:01: (BDM_supportClasses.cpp:366) Starting address registration process
-INFO - 20:02:30: (BitcoinP2P.cpp:947) Connected to Bitcoin node
-INFO - 20:02:44: (BlockchainScanner.cpp:650) scanned from height #0 to #141861
-INFO - 20:03:06: (BlockchainScanner.cpp:650) scanned from height #141862 to #163190
-INFO - 20:03:32: (BlockchainScanner.cpp:650) scanned from height #163191 to #180838
-INFO - 20:03:53: (BlockchainScanner.cpp:650) scanned from height #180839 to #186458
-INFO - 20:03:59: (BlockchainScanner.cpp:52) no history to scan
-INFO - 20:04:10: (BlockchainScanner.cpp:650) scanned from height #186459 to #191530
-INFO - 20:04:29: (BlockchainScanner.cpp:650) scanned from height #191531 to #195897
-INFO - 20:04:47: (BlockchainScanner.cpp:650) scanned from height #195898 to #200341
-INFO - 20:05:05: (BlockchainScanner.cpp:650) scanned from height #200342 to #204490
-INFO - 20:05:23: (BlockchainScanner.cpp:650) scanned from height #204491 to #208981
-INFO - 20:05:42: (BlockchainScanner.cpp:650) scanned from height #208982 to #212151
-INFO - 20:06:06: (BlockchainScanner.cpp:650) scanned from height #212152 to #215802
-INFO - 20:06:30: (BlockchainScanner.cpp:650) scanned from height #215803 to #218081
-INFO - 20:06:54: (BlockchainScanner.cpp:650) scanned from height #218082 to #220842
-INFO - 20:07:25: (BlockchainScanner.cpp:650) scanned from height #220843 to #223362
-INFO - 20:07:54: (BlockchainScanner.cpp:650) scanned from height #223363 to #225712
-INFO - 20:08:21: (BlockchainScanner.cpp:650) scanned from height #225713 to #228589
-INFO - 20:08:26: (BlockchainScanner.cpp:52) no history to scan
-INFO - 20:08:47: (BlockchainScanner.cpp:650) scanned from height #228590 to #230815
-INFO - 20:09:14: (BlockchainScanner.cpp:650) scanned from height #230816 to #233156
-INFO - 20:09:33: (BlockchainScanner.cpp:52) no history to scan
-INFO - 20:09:42: (BlockchainScanner.cpp:650) scanned from height #233157 to #235655
-INFO - 20:10:12: (BlockchainScanner.cpp:650) scanned from height #235656 to #238056
-INFO - 20:10:43: (BlockchainScanner.cpp:650) scanned from height #238057 to #240996
-INFO - 20:11:06: (BlockchainScanner.cpp:52) no history to scan
-INFO - 20:11:14: (BlockchainScanner.cpp:650) scanned from height #240997 to #244037
-WARN - 20:11:39: (BDM_supportClasses.cpp:1898) running 10 zc parser threads
-WARN - 20:11:39: (BDM_supportClasses.cpp:1898) running 15 zc parser threads
-WARN - 20:11:39: (BDM_supportClasses.cpp:1898) running 20 zc parser threads
-WARN - 20:11:39: (BDM_supportClasses.cpp:1898) running 25 zc parser threads
-WARN - 20:11:39: (BDM_supportClasses.cpp:1898) running 30 zc parser threads
-WARN - 20:11:39: (BDM_supportClasses.cpp:1898) running 35 zc parser threads
-WARN - 20:11:39: (BDM_supportClasses.cpp:1898) running 40 zc parser threads
-WARN - 20:11:39: (BDM_supportClasses.cpp:1898) running 45 zc parser threads
-WARN - 20:11:39: (BDM_supportClasses.cpp:1898) running 50 zc parser threads
-WARN - 20:11:39: (BDM_supportClasses.cpp:1898) running 55 zc parser threads
-WARN - 20:11:39: (BDM_supportClasses.cpp:1898) running 60 zc parser threads
-WARN - 20:11:39: (BDM_supportClasses.cpp:1898) running 65 zc parser threads
-WARN - 20:11:39: (BDM_supportClasses.cpp:1898) running 70 zc parser threads
-WARN - 20:11:39: (BDM_supportClasses.cpp:1898) running 75 zc parser threads
-INFO - 20:11:45: (BlockchainScanner.cpp:52) no history to scan
-INFO - 20:11:47: (BlockchainScanner.cpp:650) scanned from height #244038 to #248325
-INFO - 20:12:01: (BlockchainScanner.cpp:52) no history to scan
-INFO - 20:12:19: (BlockchainScanner.cpp:650) scanned from height #248326 to #251813
-INFO - 20:12:20: (BlockchainScanner.cpp:52) no history to scan
-INFO - 20:12:34: (BlockchainScanner.cpp:52) no history to scan
-INFO - 20:12:51: (BlockchainScanner.cpp:52) no history to scan
-INFO - 20:12:52: (BlockchainScanner.cpp:650) scanned from height #251814 to #254451
-INFO - 20:13:06: (BlockchainScanner.cpp:52) no history to scan
-INFO - 20:13:11: (BlockchainScanner.cpp:650) scanned from height #254452 to #257599
-INFO - 20:13:12: (BlockchainScanner.cpp:52) no history to scan
-INFO - 20:13:17: (BlockchainScanner.cpp:52) no history to scan
-INFO - 20:13:35: (BlockchainScanner.cpp:650) scanned from height #257600 to #261531
-INFO - 20:13:52: (BlockchainScanner.cpp:650) scanned from height #261532 to #265023
-INFO - 20:14:11: (BlockchainScanner.cpp:650) scanned from height #265024 to #268212
-INFO - 20:14:17: (BlockchainScanner.cpp:52) no history to scan
-INFO - 20:14:29: (BlockchainScanner.cpp:650) scanned from height #268213 to #270339
-INFO - 20:14:47: (BlockchainScanner.cpp:650) scanned from height #270340 to #272033
-WARN - 20:14:57: (BDM_supportClasses.cpp:1898) running 80 zc parser threads
-WARN - 20:14:57: (BDM_supportClasses.cpp:1898) running 85 zc parser threads
-WARN - 20:14:57: (BDM_supportClasses.cpp:1898) running 90 zc parser threads
-WARN - 20:14:57: (BDM_supportClasses.cpp:1898) running 95 zc parser threads
-WARN - 20:14:57: (BDM_supportClasses.cpp:1898) running 100 zc parser threads
-WARN - 20:14:57: (BDM_supportClasses.cpp:1898) running 105 zc parser threads
-WARN - 20:14:57: (BDM_supportClasses.cpp:1898) running 110 zc parser threads
-WARN - 20:14:58: (BDM_supportClasses.cpp:1898) running 115 zc parser threads
-WARN - 20:14:58: (BDM_supportClasses.cpp:1898) running 120 zc parser threads
-WARN - 20:14:58: (BDM_supportClasses.cpp:1898) running 125 zc parser threads
-WARN - 20:14:58: (BDM_supportClasses.cpp:1898) running 130 zc parser threads
-WARN - 20:14:58: (BDM_supportClasses.cpp:1898) running 135 zc parser threads
-WARN - 20:14:58: (BDM_supportClasses.cpp:1898) running 140 zc parser threads
-INFO - 20:14:58: (BlockchainScanner.cpp:650) scanned from height #272034 to #274080
-INFO - 20:15:14: (BlockchainScanner.cpp:650) scanned from height #274081 to #276226
-INFO - 20:15:28: (BlockchainScanner.cpp:650) scanned from height #276227 to #278682
-INFO - 20:15:41: (BlockchainScanner.cpp:650) scanned from height #278683 to #281205
-INFO - 20:15:55: (BlockchainScanner.cpp:650) scanned from height #281206 to #283559
-INFO - 20:16:10: (BlockchainScanner.cpp:650) scanned from height #283560 to #285495
-INFO - 20:16:25: (BlockchainScanner.cpp:650) scanned from height #285496 to #287346
-INFO - 20:16:40: (BlockchainScanner.cpp:650) scanned from height #287347 to #288889
-INFO - 20:16:55: (BlockchainScanner.cpp:650) scanned from height #288890 to #290553
-INFO - 20:17:14: (BlockchainScanner.cpp:650) scanned from height #290554 to #292556
-INFO - 20:17:35: (BlockchainScanner.cpp:650) scanned from height #292557 to #294457
-INFO - 20:17:54: (BlockchainScanner.cpp:650) scanned from height #294458 to #296201
-INFO - 20:18:13: (BlockchainScanner.cpp:650) scanned from height #296202 to #298194
-INFO - 20:18:33: (BlockchainScanner.cpp:650) scanned from height #298195 to #299802
-INFO - 20:18:51: (BlockchainScanner.cpp:650) scanned from height #299803 to #301760
-INFO - 20:19:12: (BlockchainScanner.cpp:650) scanned from height #301761 to #303288
-INFO - 20:19:33: (BlockchainScanner.cpp:650) scanned from height #303289 to #305167
-INFO - 20:19:54: (BlockchainScanner.cpp:650) scanned from height #305168 to #307267
-INFO - 20:20:11: (BlockchainScanner.cpp:650) scanned from height #307268 to #308881
-INFO - 20:20:32: (BlockchainScanner.cpp:650) scanned from height #308882 to #310683
-INFO - 20:20:54: (BlockchainScanner.cpp:650) scanned from height #310684 to #312319
-INFO - 20:21:17: (BlockchainScanner.cpp:650) scanned from height #312320 to #313692
-INFO - 20:21:38: (BlockchainScanner.cpp:650) scanned from height #313693 to #315575
-INFO - 20:21:57: (BlockchainScanner.cpp:650) scanned from height #315576 to #317092
-INFO - 20:22:27: (BlockchainScanner.cpp:650) scanned from height #317093 to #319589
-INFO - 20:22:52: (BlockchainScanner.cpp:650) scanned from height #319590 to #320800
-INFO - 20:23:17: (BlockchainScanner.cpp:650) scanned from height #320801 to #322433
-INFO - 20:24:02: (BlockchainScanner.cpp:650) scanned from height #322434 to #324006
-INFO - 20:24:35: (BlockchainScanner.cpp:650) scanned from height #324007 to #325820
-INFO - 20:24:54: (BlockchainScanner.cpp:650) scanned from height #325821 to #327083
-INFO - 20:25:16: (BlockchainScanner.cpp:650) scanned from height #327084 to #328212
-INFO - 20:25:34: (BlockchainScanner.cpp:650) scanned from height #328213 to #329595
-INFO - 20:25:56: (BlockchainScanner.cpp:650) scanned from height #329596 to #330086
-INFO - 20:26:04: (BlockchainScanner.cpp:650) scanned from height #330087 to #331368
-INFO - 20:26:27: (BlockchainScanner.cpp:650) scanned from height #331369 to #332713
-INFO - 20:26:47: (BlockchainScanner.cpp:650) scanned from height #332714 to #334029
-INFO - 20:27:05: (BlockchainScanner.cpp:650) scanned from height #334030 to #334881
-INFO - 20:27:23: (BlockchainScanner.cpp:650) scanned from height #334882 to #336152
-INFO - 20:27:44: (BlockchainScanner.cpp:650) scanned from height #336153 to #337607
-INFO - 20:28:04: (BlockchainScanner.cpp:650) scanned from height #337608 to #338410
-INFO - 20:28:17: (BlockchainScanner.cpp:650) scanned from height #338411 to #339300
-INFO - 20:28:38: (BlockchainScanner.cpp:650) scanned from height #339301 to #340423
-INFO - 20:28:58: (BlockchainScanner.cpp:650) scanned from height #340424 to #341717
-INFO - 20:29:19: (BlockchainScanner.cpp:650) scanned from height #341718 to #342902
-INFO - 20:29:39: (BlockchainScanner.cpp:650) scanned from height #342903 to #343200
-INFO - 20:30:07: (BlockchainScanner.cpp:650) scanned from height #343201 to #345010
-INFO - 20:30:27: (BlockchainScanner.cpp:650) scanned from height #345011 to #345546
-INFO - 20:30:33: (BlockchainScanner.cpp:650) scanned from height #345547 to #345733
-INFO - 20:30:42: (BlockchainScanner.cpp:650) scanned from height #345734 to #346856
-INFO - 20:31:03: (BlockchainScanner.cpp:650) scanned from height #346857 to #347739
-INFO - 20:31:23: (BlockchainScanner.cpp:650) scanned from height #347740 to #348828
-INFO - 20:31:50: (BlockchainScanner.cpp:650) scanned from height #348829 to #350419
-INFO - 20:32:16: (BlockchainScanner.cpp:650) scanned from height #350420 to #351480
-INFO - 20:32:36: (BlockchainScanner.cpp:650) scanned from height #351481 to #352455
-INFO - 20:32:51: (BlockchainScanner.cpp:650) scanned from height #352456 to #353256
-INFO - 20:33:12: (BlockchainScanner.cpp:650) scanned from height #353257 to #354220
-INFO - 20:33:34: (BlockchainScanner.cpp:650) scanned from height #354221 to #355224
-INFO - 20:33:54: (BlockchainScanner.cpp:650) scanned from height #355225 to #356202
-INFO - 20:34:14: (SocketObject.cpp:350) POLLIN recv return 0
-ERROR - 20:34:14: (BitcoinP2P.cpp:1037) caught StopBlockingLoop in processDataStackThread
-INFO - 20:34:14: (BitcoinP2P.cpp:969) Disconnected from Bitcoin node

Log file opened at 20:46:06: /home/username/.armory/dbLog.txt
-INFO - 20:46:06: (main.cpp:29) Running on 4 threads
-INFO - 20:46:06: (main.cpp:30) Ram usage level: 4
-INFO - 20:46:06: (BlockUtils.cpp:907) blkfile dir: /home/username/.bitcoin/blocks
-INFO - 20:46:06: (BlockUtils.cpp:908) lmdb dir: /home/username/.armory/databases
-INFO - 20:46:06: (lmdb_wrapper.cpp:388) Opening databases...
-INFO - 20:46:07: (BDM_Server.h:248) Listening on port 9001
-INFO - 20:46:07: (nodeRPC.cpp:59) RPC connection established
-INFO - 20:46:07: (nodeRPC.cpp:337) Node is ready
-INFO - 20:46:07: (BlockUtils.cpp:1091) Executing: doInitialSyncOnLoad
-INFO - 20:46:08: (BitcoinP2P.cpp:947) Connected to Bitcoin node
-INFO - 20:46:22: (DatabaseBuilder.cpp:169) Reading headers from db
-INFO - 20:47:13: (DatabaseBuilder.cpp:208) Found 468103 headers in db
-INFO - 20:47:14: (DatabaseBuilder.cpp:51) updating HEADERS db
-INFO - 20:47:21: (DatabaseBuilder.cpp:477) Found next block after skipping 519121bytes
-INFO - 20:47:22: (DatabaseBuilder.cpp:268) parsed block file #880
-DEBUG - 20:47:22: (Blockchain.cpp:242) Organizing chain
-INFO - 20:47:22: (DatabaseBuilder.cpp:56) updated HEADERS db in 0.64767s
-INFO - 20:47:22: (BDM_supportClasses.cpp:1841) Enabling zero-conf tracking
-WARN - 20:47:25: (BDM_supportClasses.cpp:1898) running 10 zc parser threads
-WARN - 20:47:25: (BDM_supportClasses.cpp:1898) running 15 zc parser threads
-WARN - 20:47:25: (BDM_supportClasses.cpp:1898) running 20 zc parser threads
-WARN - 20:47:25: (BDM_supportClasses.cpp:1898) running 25 zc parser threads
-WARN - 20:47:25: (BDM_supportClasses.cpp:1898) running 30 zc parser threads
-WARN - 20:47:25: (BDM_supportClasses.cpp:1898) running 35 zc parser threads
-WARN - 20:48:05: (BDM_supportClasses.cpp:1898) running 40 zc parser threads
-WARN - 20:48:05: (BDM_supportClasses.cpp:1898) running 45 zc parser threads
-WARN - 20:48:05: (BDM_supportClasses.cpp:1898) running 50 zc parser threads
-WARN - 20:48:05: (BDM_supportClasses.cpp:1898) running 55 zc parser threads
-WARN - 20:48:05: (BDM_supportClasses.cpp:1898) running 60 zc parser threads
-WARN - 20:48:05: (BDM_supportClasses.cpp:1898) running 65 zc parser threads
-WARN - 20:48:05: (BDM_supportClasses.cpp:1898) running 70 zc parser threads
-INFO - 20:48:55: (BlockchainScanner.cpp:52) no history to scan
-WARN - 20:50:00: (BDM_supportClasses.cpp:1898) running 75 zc parser threads
-WARN - 20:50:00: (BDM_supportClasses.cpp:1898) running 80 zc parser threads
-WARN - 20:50:00: (BDM_supportClasses.cpp:1898) running 85 zc parser threads
-WARN - 20:50:00: (BDM_supportClasses.cpp:1898) running 90 zc parser threads
-WARN - 20:50:00: (BDM_supportClasses.cpp:1898) running 95 zc parser threads
-WARN - 20:50:00: (BDM_supportClasses.cpp:1898) running 100 zc parser threads
-WARN - 20:50:00: (BDM_supportClasses.cpp:1898) running 105 zc parser threads
-INFO - 20:55:50: (BlockchainScanner.cpp:52) no history to scan
-INFO - 21:02:48: (BlockchainScanner.cpp:52) no history to scan
-INFO - 21:05:13: (BlockchainScanner.cpp:52) no history to scan
-INFO - 21:07:38: (BlockchainScanner.cpp:52) no history to scan
-INFO - 21:14:44: (BlockchainScanner.cpp:52) no history to scan
-INFO - 21:16:45: (BlockchainScanner.cpp:52) no history to scan
-INFO - 21:16:57: (BlockchainScanner.cpp:52) no history to scan
-INFO - 21:32:32: (BlockchainScanner.cpp:52) no history to scan

Mr.Vice

member

Activity: 96

Merit: 10

@goatpig: I just wanted to thank you for everything man, finally everything works with Armory 0.96.1-testing. There where multiple issues that have caused my unique problem.

1): McAfee AV was configured to (not only) real-time scanning, but also with the option of direct blocking "threats" before written on HDD.
2): Encrypted HDD with AES-CBC 256bit.
3): Custom bitcoin.conf with server=1 and the old rpcuser & rpcpasswords set that are deprecated now (cookie-auth).

Code:

## CONNECTION

#server=1

## Threshold for disconnecting misbehaving peers (default: 100)
banscore=80

## Number of seconds to keep misbehaving peers from reconnecting (default: 86400)
bantime=1814400

## TOR & PROXY SERVER

listen=1

proxy=127.0.0.1:9050

torcontrol=127.0.0.1:9051

torpassword=***

## HIDDEN SERVICE (TOR)

#listenonion=1

## Seperate SOCKS5-Proxy for Tor Hidden Service
#onion=127.0.0.1:50959

## OTHER

#min=1

So many thanks for your help goatpig! I was able to run McAfee together with Armory now by deactivating some settings, but it was one of the reasons why it didn't work in the first place.

Portnoy

legendary

Activity: 2030

Merit: 1000

My money; Our Bitcoin.

Quote from: goatpig on May 25, 2017, 06:20:10 PM

Quote from: Spieler636 on May 25, 2017, 05:56:23 PM

So I checked and I actually had clamav installed. I am pretty sure thought, that it didn't do anything, since I didn't let it delete anything.
I also have ufw installed, which also shouldn't do anything. Can I make Bitcoin Core check the blockchain maybe? I didn't find any option for that anywhere.

Not sure what the name of the arg is, something like "-checkchain". Make sure to delete your armory databases folder after that.

https://en.bitcoin.it/wiki/Running_Bitcoin#Command-line_arguments

Spieler636

brand new

Activity: 0

Merit: 0

So after I did the rebuild everything seemed fine, but I just noticed, that it stopped again. I am rebuilding right now but can I provide aditional information what could cause this issue?

Topic: 0.96.1 testing build #4 - page 7. (Read 8012 times)