Pages:
Author

Topic: 0.96.1 testing build #4 - page 8. (Read 8032 times)

legendary
Activity: 3640
Merit: 1345
Armory Developer
May 25, 2017, 06:20:10 PM
#22
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.
legendary
Activity: 3640
Merit: 1345
Armory Developer
May 25, 2017, 04:25:15 PM
#21
This DB never got really far. Are you using an anti virus too? Your blockchain data keeps getting corrupted after the fact.
legendary
Activity: 3640
Merit: 1345
Armory Developer
May 23, 2017, 04:00:55 PM
#20
Need to see the log for the second build&scan
brand new
Activity: 0
Merit: 0
May 20, 2017, 07:33:13 AM
#19
Hi I noticed, that my Armory seems to not pick up new blocks. It seems to be stuck on Block 465695. It says Online but does not go any further. Starting core alone is fine and goes all the way to the top, so I tried running core manuely with no success. Then it says offline.

armorylog
Code:
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1135 - C++ block utilities loaded successfully
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:664 - Executing popen: free -m
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:664 - Executing popen: ['cat', '/proc/cpuinfo']
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1252 -
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1253 -
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1254 -
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1255 - ************************************************************
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1256 - Invoked: /usr/local/bin/../lib/armory/ArmoryQt.py
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1257 - ************************************************************
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1258 - Loading Armory Engine:
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1259 -    Armory Version        : 0.96.0.1
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1260 -    Armory Build:         : 654b380411
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1261 -    PyBtcWallet  Version  : 1.35
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1262 - Detected Operating system: Linux
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1263 -    OS Variant            : Ubuntu-16.04-xenial
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1264 -    User home-directory   : /home/username
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1265 -    Satoshi BTC directory : /home/username/.bitcoin/
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1266 -    Armory home dir       : /home/username/.armory/
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1267 - Detected System Specs    :
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1268 -    Total Available RAM   : 15.63 GB
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1269 -    CPU ID string         : Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1270 -    Number of CPU cores   : 4 cores
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1271 -    System is 64-bit      : True
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1272 -    Preferred Encoding    : UTF-8
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1273 -    Machine Arch          : x86_64
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1274 -    Available HDD (ARM)   : 389 GB
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1275 -    Available HDD (BTC)   : 389 GB
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1276 -
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1277 - Network Name: Main Network
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1278 - Satoshi Port: 8333
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1279 - Do wlt check: True
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1280 - Named options/arguments to armoryengine.py:
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1282 -     thread_count    : -1
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1282 -     rescan          : False
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1282 -     ignoreAllZC     : False
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1282 -     rescanBalance   : False
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1282 -     disableModules  : False
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1282 -     port            : None
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1282 -     interport       : 8223
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1282 -     coverageOutputDir: None
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1282 -     forceWalletCheck: False
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1282 -     regtest         : False
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1282 -     rebuild         : False
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1282 -     nettimeout      : 2
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1282 -     datadir         : DEFAULT
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1282 -     clearMempool    : False
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1282 -     offline         : False
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1282 -     armoryDBDir     : DEFAULT
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1282 -     armorydb_port   : 9001
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1282 -     satoshiPort     : DEFAULT
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1282 -     useTorSettings  : False
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1282 -     netlog          : False
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1282 -     keypool         : 100
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1282 -     coverageInclude : None
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1282 -     forceOnline     : False
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1282 -     redownload      : False
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1282 -     rpcBindAddr     : 127.0.0.1
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1282 -     armorydb_ip     : 127.0.0.1
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1282 -     multisigFile    : DEFAULT
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1282 -     ram_usage       : -1
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1282 -     mtdebug         : False
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1282 -     logDisable      : False
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1282 -     settingsPath    : /home/username/.armory/ArmorySettings.txt
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1282 -     language        : en
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1282 -     db_type         : DB_FULL
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1282 -     doDebug         : False
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1282 -     enableDetSign   : True
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1282 -     disableConfPermis: False
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1282 -     testnet         : False
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1282 -     rpcport         : DEFAULT
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1282 -     satoshiHome     : DEFAULT
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1282 -     satoshiRpcport  : DEFAULT
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1282 -     logFile         : /home/username/.armory/ArmoryQt.py.log.txt
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1282 -     verbosity       : None
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1283 - Other arguments:
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1286 - ************************************************************
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:1689 - C++ block utilities loaded successfully
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:3587 - Using settings file: /home/username/.armory/ArmorySettings.txt
2017-05-20 13:17:49 (INFO) -- ArmoryUtils.py:3747 - Using Language: de
2017-05-20 13:17:49 (INFO) -- BDM.py:365 - Using the asynchronous/multi-threaded BlockDataManager.
2017-05-20 13:17:49 (INFO) -- BDM.py:366 - Blockchain operations will happen in the background. 
2017-05-20 13:17:49 (INFO) -- BDM.py:367 - Devs: check TheBDM.getState() before asking for data.
2017-05-20 13:17:49 (INFO) -- BDM.py:368 - Registering addresses during rescans will queue them for
2017-05-20 13:17:49 (INFO) -- BDM.py:369 - inclusion after the current scan is completed.
2017-05-20 13:17:50 (INFO) -- ArmoryUtils.py:3587 - Using settings file: /home/username/.armory/ArmorySettings.txt
2017-05-20 13:17:50 (INFO) -- ArmoryQt.py:2047 - loadWalletsAndSettings
2017-05-20 13:17:50 (INFO) -- ArmoryQt.py:2107 - Loading wallets...
2017-05-20 13:17:50 (INFO) -- ArmoryQt.py:2172 - Number of wallets read in: 2
2017-05-20 13:17:50 (INFO) -- ArmoryQt.py:2177 -    Wallet (BbxgbkBH):    "Primary Wallet                  "   (Encrypted)
2017-05-20 13:17:50 (INFO) -- ArmoryQt.py:2177 -    Wallet (bQ6dchyR):    "Cold Storage (Watch)            "   (No Encryption)
2017-05-20 13:17:50 (INFO) -- ArmoryQt.py:2182 - Loading Multisig Lockboxes
2017-05-20 13:17:50 (INFO) -- ArmoryQt.py:1749 - acquiring process mutex...
2017-05-20 13:17:50 (INFO) -- ArmoryQt.py:1388 - setupUriRegistration
2017-05-20 13:17:50 (INFO) -- ArmoryUtils.py:664 - Executing popen: gconftool-2 --get /desktop/gnome/url-handlers/bitcoin/command
2017-05-20 13:17:50 (INFO) -- ArmoryUtils.py:664 - Executing popen: xdg-mime query default x-scheme-handler/bitcoin
2017-05-20 13:17:50 (INFO) -- ArmoryQt.py:562 - Usermode: Expert
2017-05-20 13:17:50 (INFO) -- ArmoryQt.py:1684 - Changing usermode:
2017-05-20 13:17:50 (INFO) -- ArmoryQt.py:1685 -    From: Expert
2017-05-20 13:17:50 (INFO) -- ArmoryQt.py:1693 -      To: Expert
2017-05-20 13:17:50 (INFO) -- ArmoryQt.py:1822 - startBitcoindIfNecessary
2017-05-20 13:17:50 (INFO) -- ArmoryQt.py:1858 - setSatoshiPaths
2017-05-20 13:17:50 (INFO) -- ArmoryUtils.py:664 - Executing popen: ['whereis', 'bitcoind']
2017-05-20 13:17:50 (INFO) -- SDM.py:289 - "whereis" returned: ['/usr/bin/bitcoind']
2017-05-20 13:17:50 (INFO) -- SDM.py:169 - Found bitcoind in the following places:
2017-05-20 13:17:50 (INFO) -- SDM.py:171 -    /usr/bin/bitcoind
2017-05-20 13:17:50 (INFO) -- SDM.py:171 -    /usr/bin/bitcoind
2017-05-20 13:17:50 (INFO) -- SDM.py:173 - Using: /usr/bin/bitcoind
2017-05-20 13:17:50 (INFO) -- SDM.py:337 - Called startBitcoind
2017-05-20 13:17:50 (INFO) -- ArmoryUtils.py:664 - Executing popen: ['/usr/bin/bitcoind', '-datadir=/home/username/.bitcoin/']
2017-05-20 13:17:50 (INFO) -- SDM.py:442 - PID of bitcoind: 16432
2017-05-20 13:17:50 (INFO) -- SDM.py:443 - PID of armory:   16400
2017-05-20 13:17:50 (INFO) -- ArmoryUtils.py:664 - Executing popen: ['python', '/usr/local/lib/armory/guardian.py', '16400', '16432']
2017-05-20 13:17:50 (INFO) -- ArmoryQt.py:1858 - setSatoshiPaths
2017-05-20 13:17:50 (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-20 13:17:50 (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-20 13:17:50 (INFO) -- ArmoryQt.py:1810 - Connecting on port 59036
2017-05-20 13:17:50 (INFO) -- ArmoryQt.py:1910 - Setting netmode: 1
2017-05-20 13:17:50 (INFO) -- ArmoryQt.py:1892 - loadBlockchainIfNecessary
2017-05-20 13:17:50 (INFO) -- ArmoryQt.py:1910 - Setting netmode: 1
2017-05-20 13:17:50 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-20 13:17:50 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-20 13:17:51 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-20 13:17:51 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-20 13:17:52 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-20 13:17:52 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-20 13:17:52 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-20 13:17:52 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-20 13:17:53 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-20 13:17:53 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-20 13:17:53 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-20 13:17:53 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-20 13:17:53 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-20 13:17:55 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-20 13:17:57 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-20 13:17:58 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-20 13:17:58 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-20 13:17:59 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-20 13:18:00 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-20 13:18:00 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-20 13:18:02 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-20 13:18:02 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-20 13:18:02 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-20 13:18:05 (INFO) -- ArmoryQt.py:4606 - Dashboard switched to "Scanning" mode
2017-05-20 13:18:05 (WARNING) -- ArmoryQt.py:4044 - Called updateSyncProgress while not sync'ing
2017-05-20 13:28:55 (INFO) -- ArmoryQt.py:5391 - BDM is safe for clean shutdown
2017-05-20 13:28:55 (INFO) -- SDM.py:456 - Called stopBitcoind
2017-05-20 13:28:56 (INFO) -- ArmoryQt.py:5404 - Attempting to close the main window!

dblog
Code:

Log file opened at 13:17:50: /home/username/.armory/dbLog.txt
-INFO  - 13:17:50: (main.cpp:29) Running on 4 threads
-INFO  - 13:17:50: (main.cpp:30) Ram usage level: 4
-INFO  - 13:17:50: (BlockUtils.cpp:907) blkfile dir: /home/username/.bitcoin/blocks
-INFO  - 13:17:50: (BlockUtils.cpp:908) lmdb dir: /home/username/.armory/databases
-INFO  - 13:17:50: (lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 13:17:50: (BDM_Server.h:248) Listening on port 59036
-INFO  - 13:17:50: (BDM_Server.cpp:996) registered bdv: a74ebc3d78d29ac8e33b
-INFO  - 13:17:51: (BlockUtils.cpp:1091) Executing: doInitialSyncOnLoad
-INFO  - 13:17:51: (DatabaseBuilder.cpp:169) Reading headers from db
-INFO  - 13:17:53: (DatabaseBuilder.cpp:208) Found 465700 headers in db
-INFO  - 13:17:55: (DatabaseBuilder.cpp:51) updating HEADERS db
-INFO  - 13:17:55: (DatabaseBuilder.cpp:477) Found next block after skipping 510159bytes
-INFO  - 13:17:57: (DatabaseBuilder.cpp:268) parsed block file #863
-INFO  - 13:17:58: (BitcoinP2P.cpp:947) Connected to Bitcoin node
-INFO  - 13:17:58: (DatabaseBuilder.cpp:268) parsed block file #865
-INFO  - 13:17:58: (DatabaseBuilder.cpp:268) parsed block file #866
-INFO  - 13:17:59: (DatabaseBuilder.cpp:268) parsed block file #867
-INFO  - 13:18:00: (DatabaseBuilder.cpp:268) parsed block file #868
-INFO  - 13:18:00: (DatabaseBuilder.cpp:268) parsed block file #870
-INFO  - 13:18:02: (DatabaseBuilder.cpp:268) parsed block file #871
-INFO  - 13:18:02: (DatabaseBuilder.cpp:268) parsed block file #874
-DEBUG - 13:18:02: (Blockchain.cpp:242) Organizing chain
-INFO  - 13:18:05: (DatabaseBuilder.cpp:56) updated HEADERS db in 22.5907s
-INFO  - 13:18:05: (DatabaseBuilder.cpp:106) scanning new blocks from #465696 to #465695
-INFO  - 13:18:05: (BlockchainScanner.cpp:52) no history to scan
-INFO  - 13:18:05: (BlockchainScanner.cpp:813) no SSH to scan
-INFO  - 13:18:05: (DatabaseBuilder.cpp:156) scanned new blocks in 0.001458s
-INFO  - 13:18:05: (DatabaseBuilder.cpp:160) init db in 26.6254s
-INFO  - 13:18:05: (BDM_supportClasses.cpp:1841) Enabling zero-conf tracking
-WARN  - 13:18:12: (BDM_supportClasses.cpp:1898) running 10 zc parser threads
-WARN  - 13:18:12: (BDM_supportClasses.cpp:1898) running 15 zc parser threads
-WARN  - 13:18:25: (BDM_supportClasses.cpp:1898) running 20 zc parser threads
-WARN  - 13:18:25: (BDM_supportClasses.cpp:1898) running 25 zc parser threads
-WARN  - 13:18:25: (BDM_supportClasses.cpp:1898) running 30 zc parser threads
-WARN  - 13:18:25: (BDM_supportClasses.cpp:1898) running 35 zc parser threads
-INFO  - 13:28:55: (nodeRPC.cpp:368) Bitcoin server stopping
-INFO  - 13:28:56: (SocketObject.cpp:350) POLLIN recv return 0
-ERROR - 13:28:56: (BitcoinP2P.cpp:1037) caught StopBlockingLoop in processDataStackThread
-INFO  - 13:28:56: (BitcoinP2P.cpp:969) Disconnected from Bitcoin node
-INFO  - 13:28:56: (BDM_Server.cpp:1025) unregistered bdv: a74ebc3d78d29ac8e33b
-INFO  - 13:28:56: (BDM_Server.cpp:936) proceeding to shutdown
-ERROR - 13:28:57: (BitcoinP2P.cpp:1027) caught SocketError exception in processDataStackThread: POLLNVAL in readFromSocketThread
-INFO  - 13:28:59: (BitcoinP2P.cpp:969) Disconnected from Bitcoin node
-ERROR - 13:28:59: (BDM_mainthread.cpp:287) caught exception in main thread: terminate
legendary
Activity: 3640
Merit: 1345
Armory Developer
May 20, 2017, 09:15:29 AM
#19
Hi I noticed, that my Armory seems to not pick up new blocks. It seems to be stuck on Block 465695. It says Online but does not go any further. Starting core alone is fine and goes all the way to the top, so I tried running core manuely with no success. Then it says offline.

Code:
-INFO  - 13:17:55: (DatabaseBuilder.cpp:477) Found next block after skipping 510159bytes

It's skipping a block for some reason. Try a rebuild & rescan, if that doesn't fix it, you'll have to delete all your blkXXXXX.dat files starting #860
legendary
Activity: 3640
Merit: 1345
Armory Developer
May 20, 2017, 09:12:46 AM
#18
Quote
Yes, it pretty much seems that there is some kind of unique condition. So, the only thing that's so harsh on executing programs could only be my McAfee Anti-Virus software. Although it has worked fine up to 0.95.1 together with Core 0.13.1. Hmmm, anyway I have deinstalled that and I'm using now windows defender only (also added exceptions for the real-time scanner at C:\..\AppData\Armory & AppData\Bitcoin Core directories). I'm currently at rebuid&rescan because I have read it too late that it would not be nesassary. If this is still not working I'll maybe format my HDD and after fresh installing Win10 Armory will be the only program that's executed at first.

@goatpig: I finally knew what was causing this issues! I've found 3 virues/trojans that tried to prevent core from connecting to other clients, armorydb from connecting with core and where hiding in my blockchain files! They where sleeping in my old recovery folder (that I imported from my old laptop) and spreaded in my account. My hole laptop was so incedibly slow from day to day even slower... I have wiped out my hole app data of armory and bitcoin and afterwards boom.. everything was running smooth again. I'm now downloading the hole blockchain, but everything goes extremly fast now.
I had excluded certain folders from scanning because I fought they might corrupt the blockchain... anyway thanks for helping me goatpig!

How can I change to usse tor settings, the button in the GUI is broken... what do I have to write in the config file and how is it named?... pls..

#JOHN MCAFEE ROCKS! =D

There are a few false positives in the blockchain, where people pushed virus signatures in transactions. That's enough to get your antivirus to freak out. These cases were reported as false positives but who knows what the AV companies did with those reports.

Consider that a resident AV's heuristics alone can nuke on disk content post flush basically at its own whim. Chances are the AV created issues where they were none to begin with. Objectively, an AV is no different from a virus: it resides on your system, constantly eats resources and damages the user experience.

My advice to you, whether you let the AV run or not, is to make periodical copies of a valid blockchain data folder on external storage to restore faster.

As for the config files, they are named armoryqt.conf and armorydb.conf and go in your Armory datadir (where your wallets reside). Any command line you can give to either process you can put in the relevant config file. If you are running with default paths, there isn't anything you need to put in there. If you want to run the lighter DB, use --dbtype=DB_BARE.

There is no more "use tor setting" per se. There is no more phone home code in Armory, the only piece of software in the stack that uses the WAN is your node.
member
Activity: 96
Merit: 10
May 19, 2017, 05:53:22 PM
#17
Quote
Yes, it pretty much seems that there is some kind of unique condition. So, the only thing that's so harsh on executing programs could only be my McAfee Anti-Virus software. Although it has worked fine up to 0.95.1 together with Core 0.13.1. Hmmm, anyway I have deinstalled that and I'm using now windows defender only (also added exceptions for the real-time scanner at C:\..\AppData\Armory & AppData\Bitcoin Core directories). I'm currently at rebuid&rescan because I have read it too late that it would not be nesassary. If this is still not working I'll maybe format my HDD and after fresh installing Win10 Armory will be the only program that's executed at first.

@goatpig: I finally knew what was causing this issues! I've found 3 virues/trojans that tried to prevent core from connecting to other clients, armorydb from connecting with core and where hiding in my blockchain files! They where sleeping in my old recovery folder (that I imported from my old laptop) and spreaded in my account. My hole laptop was so incedibly slow from day to day even slower... I have wiped out my hole app data of armory and bitcoin and afterwards boom.. everything was running smooth again. I'm now downloading the hole blockchain, but everything goes extremly fast now.
I had excluded certain folders from scanning because I fought they might corrupt the blockchain... anyway thanks for helping me goatpig!

How can I change to usse tor settings, the button in the GUI is broken... what do I have to write in the config file and how is it named?... pls..

#JOHN MCAFEE ROCKS! =D
member
Activity: 178
Merit: 10
May 19, 2017, 03:32:37 PM
#16
987d1a262cb92a9bb70ce85ec75b15a4ef20f90c9ac322c00e7908fe086f2bf2  armory_0.96-gcc5.4_amd64.deb
25357d717452972030fa8b42017e4adf4684c354498c39002d89ee18ae551783  armory_0.96.0.1-testing_amd64.deb

thank you.
legendary
Activity: 3640
Merit: 1345
Armory Developer
May 19, 2017, 02:58:51 PM
#15
987d1a262cb92a9bb70ce85ec75b15a4ef20f90c9ac322c00e7908fe086f2bf2  armory_0.96-gcc5.4_amd64.deb
25357d717452972030fa8b42017e4adf4684c354498c39002d89ee18ae551783  armory_0.96.0.1-testing_amd64.deb
member
Activity: 178
Merit: 10
May 19, 2017, 02:30:44 PM
#14
is the hashed *.deb correct?  i can't get them to match.  what's the "gcc" build?:

Hash: SHA256

64f4b4295210bbe65ce9e3b485f78f06e723fa7e7209d5f244d1265a175ed6f1  armory_0.96-gcc4.7_amd64.deb
987d1a262cb92a9bb70ce85ec75b15a4ef20f90c9ac322c00e7908fe086f2bf2  armory_0.96-gcc5.4_amd64.deb
fce84bd0964a43a677b1be689e321c562c10a202a35fd052975f3c3536055dd7  armory_0.96_win64.exe
dfa1dec7590e2cfc3dfe718a9fc0104108795fe9a55cdb43edf4de56e396caa7  armory_0.96_win64.zip

debian@debian:~/Downloads$ sha256sum armory_0.96.0.1-testing_amd64.deb
25357d717452972030fa8b42017e4adf4684c354498c39002d89ee18ae551783  armory_0.96.0.1-testing_amd64.deb


Version mismatch

not sure i understand.

is there an error in the hashes of the sha256sum.txt.asc file that are indeed mismatched with the hash of the *.deb file?  if so, how are we supposed to verify that we have an original build?
legendary
Activity: 3640
Merit: 1345
Armory Developer
May 19, 2017, 01:03:27 PM
#13
is the hashed *.deb correct?  i can't get them to match.  what's the "gcc" build?:

Hash: SHA256

64f4b4295210bbe65ce9e3b485f78f06e723fa7e7209d5f244d1265a175ed6f1  armory_0.96-gcc4.7_amd64.deb
987d1a262cb92a9bb70ce85ec75b15a4ef20f90c9ac322c00e7908fe086f2bf2  armory_0.96-gcc5.4_amd64.deb
fce84bd0964a43a677b1be689e321c562c10a202a35fd052975f3c3536055dd7  armory_0.96_win64.exe
dfa1dec7590e2cfc3dfe718a9fc0104108795fe9a55cdb43edf4de56e396caa7  armory_0.96_win64.zip

debian@debian:~/Downloads$ sha256sum armory_0.96.0.1-testing_amd64.deb
25357d717452972030fa8b42017e4adf4684c354498c39002d89ee18ae551783  armory_0.96.0.1-testing_amd64.deb


Version mismatch
member
Activity: 178
Merit: 10
May 19, 2017, 11:19:58 AM
#12
is the hashed *.deb correct?  i can't get them to match.  what's the "gcc" build?:

Hash: SHA256

64f4b4295210bbe65ce9e3b485f78f06e723fa7e7209d5f244d1265a175ed6f1  armory_0.96-gcc4.7_amd64.deb
987d1a262cb92a9bb70ce85ec75b15a4ef20f90c9ac322c00e7908fe086f2bf2  armory_0.96-gcc5.4_amd64.deb
fce84bd0964a43a677b1be689e321c562c10a202a35fd052975f3c3536055dd7  armory_0.96_win64.exe
dfa1dec7590e2cfc3dfe718a9fc0104108795fe9a55cdb43edf4de56e396caa7  armory_0.96_win64.zip

debian@debian:~/Downloads$ sha256sum armory_0.96.0.1-testing_amd64.deb
25357d717452972030fa8b42017e4adf4684c354498c39002d89ee18ae551783  armory_0.96.0.1-testing_amd64.deb
member
Activity: 96
Merit: 10
May 19, 2017, 11:03:19 AM
#11
ArmoryDB always loses connection after StopBlockingLoop Exception in ProcessDataThread and can't re-establish it.

Code:
-ERROR - 11:05:40.515: (..\BitcoinP2P.cpp:1037) caught StopBlockingLoop in processDataStackThread
-INFO  - 11:05:40.531: (..\BitcoinP2P.cpp:969) Disconnected from Bitcoin node

This means your node dropped the DB p2p connection. Usually that's because the node was shutdown. Unless you enforce a node limit, there is no reason for your node to just kick the DB out of its peer node. If you are triggering this, you need to figure out how.

Quote
Afterward I exit ArmoryQt normally and after restarting it the GUI can not update anymore (ArmoryDB won't even start again in Background)

That suggests the DB is still running and didn't shutdown with the client. When this happens, try to run the DB on its own, see how it behaves.

Quote
I always have to do a rebuid and rescan and to be serious I just can not do that anymore (goatpig knows what I mean).

What you are describing does not require a rebuild of the db.

Yes, it pretty much seems that there is some kind of unique condition. So, the only thing that's so harsh on executing programs could only be my McAfee Anti-Virus software. Although it has worked fine up to 0.95.1 together with Core 0.13.1. Hmmm, anyway I have deinstalled that and I'm using now windows defender only (also added exceptions for the real-time scanner at C:\..\AppData\Armory & AppData\Bitcoin Core directories). I'm currently at rebuid&rescan because I have read it too late that it would not be nesassary. If this is still not working I'll maybe format my HDD and after fresh installing Win10 Armory will be the only program that's executed at first.
legendary
Activity: 3640
Merit: 1345
Armory Developer
May 19, 2017, 07:42:05 AM
#10
ArmoryDB always loses connection after StopBlockingLoop Exception in ProcessDataThread and can't re-establish it.

Code:
-ERROR - 11:05:40.515: (..\BitcoinP2P.cpp:1037) caught StopBlockingLoop in processDataStackThread
-INFO  - 11:05:40.531: (..\BitcoinP2P.cpp:969) Disconnected from Bitcoin node

This means your node dropped the DB p2p connection. Usually that's because the node was shutdown. Unless you enforce a node limit, there is no reason for your node to just kick the DB out of its peer node. If you are triggering this, you need to figure out how.

Quote
Afterward I exit ArmoryQt normally and after restarting it the GUI can not update anymore (ArmoryDB won't even start again in Background)

That suggests the DB is still running and didn't shutdown with the client. When this happens, try to run the DB on its own, see how it behaves.

Quote
I always have to do a rebuid and rescan and to be serious I just can not do that anymore (goatpig knows what I mean).

What you are describing does not require a rebuild of the db.
member
Activity: 96
Merit: 10
May 19, 2017, 05:37:14 AM
#9
Code:
-INFO  - 11:28:30.016: (c:\users\goat\code\armory3\cppforswig\BDM_Server.h:248) Listening on port 9001
Why do I have the above absolute path in my ArmoryDB log?

I'm using Bitcoin Core 0.14.1 together with 0.96.0.1-testing but anyway this issue with the StopBlockingLoop exception I also ha running 0.96 (also with unencrpyted HDD). So normally this shows up when terminating ArmoryQt, but while it's actually running is also strange to me.
member
Activity: 96
Merit: 10
May 19, 2017, 05:14:58 AM
#8
ArmoryDB always loses connection after StopBlockingLoop Exception in ProcessDataThread and can't re-establish it.
Afterward I exit ArmoryQt normally and after restarting it the GUI can not update anymore (ArmoryDB won't even start again in Background)! My Laptop is completely unencrypted now, so that can not be the issue.
It seems this is happening always when ArmoryDB is loading the hashes of new blocks, while Bitcoin Core hasn't got the complete blocks yet. I always have to do a rebuid and rescan and to be serious I just can not do that anymore (goatpig knows what I mean).

Code:
-ERROR - 11:05:40.515: (..\BitcoinP2P.cpp:1037) caught StopBlockingLoop in processDataStackThread
-INFO  - 11:05:40.531: (..\BitcoinP2P.cpp:969) Disconnected from Bitcoin node

newbie
Activity: 43
Merit: 0
May 18, 2017, 05:04:45 PM
#7
A minor bug in sending/coin control I noticed.

If you go into "Coin Control" and deselect everything (or only select things that have a 0.00 balance), you can still successfully create a transaction if your amount sent is below your wallet balance. You are not prompted with the "Coin Selection Failure: Coin selection failed with error: spend value > usable balance" as expected.

I'm not sure the logic but it seems to just pick from any coins in the wallet, although to be fair there is only P2PKH outputs in what I'm testing.
full member
Activity: 159
Merit: 100
May 17, 2017, 04:36:38 PM
#6
Use the testing branch. Building on macs right now may not work though, but you can try.

Same problem as with the master branch:  It builds just fine, but cannot run.  Starting it on the command line gives this error:
Code:
22:28 workspace$ Armory.app/Contents/MacOS/Armory
/Users/****/development/BitcoinArmory/osxbuild/workspace/Armory.app/Contents/MacOS/Python: can't open file '/Users/****/development/BitcoinArmory/osxbuild/workspace/Armory.app/Contents/MacOS/py/usr/local/lib/armory/ArmoryQt.py': [Errno 2] No such file or directory

Manually copying ArmoryQt.py into that location gives a new error:
Code:
22:29 workspace$ Armory.app/Contents/MacOS/Armory
Traceback (most recent call last):
  File "/Users/****/development/BitcoinArmory/osxbuild/workspace/Armory.app/Contents/MacOS/py/usr/local/lib/armory/ArmoryQt.py", line 37, in
    from PyQt4.QtGui import *
ImportError: dlopen(/Users/****/development/BitcoinArmory/osxbuild/workspace/Armory.app/Contents/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/PyQt4/QtGui.so, 2): Library not loaded: /usr/local/opt/libpng/lib/libpng16.16.dylib
  Referenced from: /Users/****/development/BitcoinArmory/osxbuild/workspace/Armory.app/Contents/Frameworks/QtGui.framework/Versions/4/QtGui
  Reason: Incompatible library version: QtGui requires version 46.0.0 or later, but libpng16.16.dylib provides version 45.0.0
As you can see, I have libpng installed through homebrew.  That is pretty common, though, so Armory should pick up its own version anyway.  Uninstalling libpng does not change the error, although /usr/local/opt/libpng is then gone.
staff
Activity: 3374
Merit: 6530
Just writing some code
May 17, 2017, 09:40:16 AM
#5
Does it make sense to attempt a build on my Macbook?

If so, which git branch should I use?
Use the testing branch. Building on macs right now may not work though, but you can try.
full member
Activity: 159
Merit: 100
May 17, 2017, 03:32:10 AM
#4
Does it make sense to attempt a build on my Macbook?

If so, which git branch should I use?
Pages:
Jump to: