Bitcoin Forum>Bitcoin>Development & Technical Discussion>Wallet software>Armory
Pages:
Author

Topic: Armory 0.96 is out - page 4. (Read 13794 times)

naska21
hero member
Activity: 1358
Merit: 635
Re: Armory 0.96 is out
June 26, 2017, 05:04:20 AM
#207
Quote from: goldstrk on June 26, 2017, 04:48:22 AM
Hello everyone,

First gratz for the developers for another Armory release.

I'm writting to ask for some help here since it's the 1st time I'm attempting to use it (as it was highly recomendated). The issue here is that I'm stuck into preparing databases for ages and, a bit bored, of waiting for the spiining wheel to end (which looks that it never will).







I had such issue a few days ago. The system has changed F:/ to H:/ somehow so there was no connectivity to DB. When I put the correct letter  for drive, closed mannualy ArmoryDB.exe via Task Manager and lanched Armory again everything went smoothly
goldstrk
newbie
Activity: 18
Merit: 0
Re: Armory 0.96 is out
June 26, 2017, 04:48:22 AM
#206
Hello everyone,

First gratz for the developers for another Armory release.

I'm writting to ask for some help here since it's the 1st time I'm attempting to use it (as it was highly recomendated). The issue here is that I'm stuck into preparing databases for ages and, a bit bored, of waiting for the spiining wheel to end (which looks that it never will).

My system runs in Windows 10 x64 and seems to be unable to sync with BTC network.

Please help.

Running as Admin with

"F:\Utils\Crypto Miners\Armory\ArmoryQt.exe" --datadir="F:\Utils\Crypto\Armory" --satoshi-datadir="F:\Utils\Crypto\Bitcoin"

armorycpplog
Code:
Log file opened at 1498466465: F:\Utils\Crypto\Armory\armorycpplog.txt
-ERROR - 1498466477: (..\SocketObject.cpp:440) POLLERR error in readAndWrite

armorylog
Code:
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1138 - C++ block utilities loaded successfully
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1255 -
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1256 -
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1257 -
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1258 - ************************************************************
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1259 - Invoked: F:\Crypto Miners\Armory\ArmoryQt.exe --datadir=F:\Utils\Crypto\Armory --satoshi-datadir=F:\Utils\Crypto\Bitcoin
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1260 - ************************************************************
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1261 - Loading Armory Engine:
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1262 -    Armory Version        : 0.96
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1263 -    Armory Build:         : a3d01aa722
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1264 -    PyBtcWallet  Version  : 1.35
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1265 - Detected Operating system: Windows
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1266 -    OS Variant            : 8-6.2.9200--Multiprocessor Free
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1267 -    User home-directory   : C:\Users\Joao Rocha\AppData\Roaming
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1268 -    Satoshi BTC directory : F:\Utils\Crypto\Bitcoin
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1269 -    Armory home dir       : F:\Utils\Crypto\Armory
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1270 - Detected System Specs    :
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1271 -    Total Available RAM   : 15.87 GB
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1272 -    CPU ID string         : Intel64 Family 6 Model 60 Stepping 3, GenuineIntel
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1273 -    Number of CPU cores   : 8 cores
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1274 -    System is 64-bit      : True
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1275 -    Preferred Encoding    : cp1252
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1276 -    Machine Arch          : amd64
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1277 -    Available HDD (ARM)   : 439 GB
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1278 -    Available HDD (BTC)   : 439 GB
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1279 -
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1280 - Network Name: Main Network
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1281 - Satoshi Port: 8333
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1282 - Do wlt check: True
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1283 - Named options/arguments to armoryengine.py:
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     thread_count    : -1
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     rescan          : False
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     ignoreAllZC     : False
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     rescanBalance   : False
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     disableModules  : False
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     port            : None
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     interport       : 8223
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     coverageOutputDir: None
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     forceWalletCheck: False
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     regtest         : False
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     rebuild         : False
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     nettimeout      : 2
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     datadir         : F:\Utils\Crypto\Armory
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     clearMempool    : False
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     offline         : False
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     armoryDBDir     : DEFAULT
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     armorydb_port   : 9001
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     satoshiPort     : DEFAULT
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     useTorSettings  : False
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     netlog          : False
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     keypool         : 100
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     coverageInclude : None
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     forceOnline     : False
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     redownload      : False
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     rpcBindAddr     : 127.0.0.1
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     armorydb_ip     : 127.0.0.1
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     multisigFile    : DEFAULT
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     ram_usage       : -1
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     mtdebug         : False
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     logDisable      : False
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     settingsPath    : F:\Utils\Crypto\Armory\ArmorySettings.txt
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     language        : en
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     db_type         : DB_FULL
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     doDebug         : False
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     enableDetSign   : True
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     disableConfPermis: False
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     testnet         : False
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     rpcport         : DEFAULT
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     satoshiHome     : F:\Utils\Crypto\Bitcoin
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     satoshiRpcport  : DEFAULT
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     logFile         : F:\Utils\Crypto\Armory\ArmoryQt.exe.log.txt
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     verbosity       : None
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1286 - Other arguments:
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1289 - ************************************************************
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1692 - C++ block utilities loaded successfully
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:3590 - Using settings file: F:\Utils\Crypto\Armory\ArmorySettings.txt
2017-06-26 09:41 (ERROR) -- ArmoryUtils.pyc:3747 - Unsupported language  specified. Defaulting to English (en)
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:3750 - Using Language: en
2017-06-26 09:41 (INFO) -- BDM.pyc:368 - Using the asynchronous/multi-threaded BlockDataManager.
2017-06-26 09:41 (INFO) -- BDM.pyc:369 - Blockchain operations will happen in the background.  
2017-06-26 09:41 (INFO) -- BDM.pyc:370 - Devs: check TheBDM.getState() before asking for data.
2017-06-26 09:41 (INFO) -- BDM.pyc:371 - Registering addresses during rescans will queue them for
2017-06-26 09:41 (INFO) -- BDM.pyc:372 - inclusion after the current scan is completed.
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:3590 - Using settings file: F:\Utils\Crypto\Armory\ArmorySettings.txt
2017-06-26 09:41 (INFO) -- ArmoryQt.py:2042 - loadWalletsAndSettings
2017-06-26 09:41 (INFO) -- ArmoryQt.py:2102 - Loading wallets...
2017-06-26 09:41 (INFO) -- ArmoryQt.py:2167 - Number of wallets read in: 3
2017-06-26 09:41 (INFO) -- ArmoryQt.py:2172 -    Wallet (24htVgvZM):   "Family Wallet                   "   (Encrypted)
2017-06-26 09:41 (INFO) -- ArmoryQt.py:2172 -    Wallet (6k1eP47y):    "Venture BTC                     "   (Encrypted)
2017-06-26 09:41 (INFO) -- ArmoryQt.py:2172 -    Wallet (2E5wFWu5Z):   "Personal Wallet                 "   (Encrypted)
2017-06-26 09:41 (INFO) -- ArmoryQt.py:1747 - acquiring process mutex...
2017-06-26 09:41 (INFO) -- ArmoryQt.py:1385 - setupUriRegistration
2017-06-26 09:41 (INFO) -- ArmoryQt.py:1453 - Armory already registered for current user.  Done!
2017-06-26 09:41 (INFO) -- ArmoryQt.py:558 - Usermode: Advanced
2017-06-26 09:41 (INFO) -- ArmoryQt.py:1681 - Changing usermode:
2017-06-26 09:41 (INFO) -- ArmoryQt.py:1682 -    From: Advanced
2017-06-26 09:41 (INFO) -- ArmoryQt.py:1690 -      To: Advanced
2017-06-26 09:41 (INFO) -- ArmoryQt.py:1814 - startBitcoindIfNecessary
2017-06-26 09:41 (INFO) -- ArmoryQt.py:1850 - setSatoshiPaths
2017-06-26 09:41 (INFO) -- SDM.pyc:251 - Found Bitcoin Core link on desktop: F:\Crypto Miners\Armory
2017-06-26 09:41 (ERROR) -- ArmoryQt.py:1840 - Failed to setup SDM
Traceback (most recent call last):
  File "ArmoryQt.py", line 1835, in startBitcoindIfNecessary
  File "SDM.pyc", line 188, in setupSDM
BitcoindError: bitcoind not found
2017-06-26 09:41 (INFO) -- ArmoryQt.py:1900 - Setting netmode: 0
2017-06-26 09:41 (INFO) -- ArmoryQt.py:1850 - setSatoshiPaths
2017-06-26 09:41 (WARNING) -- SDM.pyc:396 - Spawning DB with command:./ArmoryDB.exe --db-type="DB_FULL" --cookie --satoshi-datadir="F:\Utils\Crypto\Bitcoin\blocks" --datadir="F:\Utils\Crypto\Armory" --dbdir="F:\Utils\Crypto\Armory\databases"
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:665 - Executing popen: ['./ArmoryDB.exe', '--db-type="DB_FULL"', '--cookie', u'--satoshi-datadir="F:\\Utils\\Crypto\\Bitcoin\\blocks"', u'--datadir="F:\\Utils\\Crypto\\Armory"', u'--dbdir="F:\\Utils\\Crypto\\Armory\\databases"']
2017-06-26 09:41 (INFO) -- ArmoryQt.py:1900 - Setting netmode: 1
2017-06-26 09:41 (INFO) -- ArmoryQt.py:1882 - loadBlockchainIfNecessary
2017-06-26 09:41 (INFO) -- ArmoryQt.py:1900 - Setting netmode: 1
2017-06-26 09:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-06-26 09:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode

Code:
Log file opened at 1498466472: F:\Utils\Crypto\Armory/dbLog.txt
-INFO  - 1498466472: (..\main.cpp:23) Running on 8 threads
-INFO  - 1498466472: (..\main.cpp:24) Ram usage level: 4
-INFO  - 1498466472: (..\BlockUtils.cpp:907) blkfile dir: F:\Utils\Crypto\Bitcoin\blocks
-INFO  - 1498466472: (..\BlockUtils.cpp:908) lmdb dir: F:\Utils\Crypto\Armory\databases
-INFO  - 1498466472: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 1498466474: (..\BDM_Server.cpp:996) registered bdv: 5c3bc8b519cfc5ff0d90
-INFO  - 1498466475: (..\BlockUtils.cpp:1091) Executing: doInitialSyncOnLoad
-INFO  - 1498466475: (..\DatabaseBuilder.cpp:169) Reading headers from db
-WARN  - 1498466475: (..\lmdb_wrapper.cpp:1175) No headers in DB yet!
-INFO  - 1498466475: (..\DatabaseBuilder.cpp:208) Found 1 headers in db
-INFO  - 1498466475: (..\DatabaseBuilder.cpp:51) updating HEADERS db
-DEBUG - 1498466475: (..\Blockchain.cpp:242) Organizing chain
-INFO  - 1498466475: (..\DatabaseBuilder.cpp:56) updated HEADERS db in 0.003s
-INFO  - 1498466475: (..\BlockUtils.cpp:1206) Enabling zero-conf tracking
-INFO  - 1498466475: (..\BDM_supportClasses.cpp:366) Starting address registration process
-ERROR - 1498466475: (..\lmdb_wrapper.cpp:1435) Headers DB has no block at height: 0
-ERROR - 1498466475: (..\lmdb_wrapper.cpp:1415) No headers at height 0


ArmorySettings
Code:
ManageSatoshi                        | True
LastDirectory                        | F:\Utils\Crypto\Armory
Agreed_to_EULA                       | True
UseTorSettings                       | False
DNAA_UnlockTimeout                   | False
First_Load_Date                      | 1498466466
NotifyIgnore                         |
DNAA_IntroDialog                     | False
AdvFeature_UseCt                     | 0
UnlockTimeout                        | 10
Wallet_6k1eP47y_LedgerShow           | True
FailedLoadCount                      | 1
User_Mode                            | Advanced
SkipOnlineCheck                      | False
MinimizeOnOpen                       | False
First_Load                           | False
Wallet_2E5wFWu5Z_LedgerShow          | True
LastFilterState                      | 0
Wallet_24htVgvZM_LedgerShow          | True
IgnoreAlerts                         |
DNAA_DeleteLevelDB                   | False
Load_Count                           | 1
LastVersionLoad                      | v0.96
goatpig
legendary
Activity: 3640
Merit: 1345
Armory Developer
Re: Armory 0.96 is out
June 26, 2017, 03:05:14 AM
#205
Quote from: visdude on June 26, 2017, 02:52:39 AM
1. Otherwise, 0.96 is good to use as a cold/offline wallet on a 64-bit machine then?

Yes

Quote
2. Such procedure is even more complicated than it already is. I don't even know where to look for those config files to begin with let alone tinkering with them involving more command line arguments which I am trying to avoid in the first place. I'm just thinking that since Armory has a GUI, why not incorporate such a feature in it. There's already one for specifying an explicit Bitcoin Core data directory location in Settings, so why not for Armory's too? I thought that's what GUIs are for -- to make things easy and simple so that even gramps can do it without screwing up. It would be a foolproof method for regular Joes like me. Not everyone involved in cryptos is an astute techie; and I'm a fine example of that.

BTW, on a W7 x64 machine running 0.96 with explicit Armory data directory using a shortcut arg (--satoshi-datadir="D:\Bitcoin" --datadir="D:\Armory"), the "databases" folder, wallets, settings and log files are together in the "Armory" folder and ths setup has been working for a while now through several updates. So your explanation above about the "datadir" being separate from "blockchain and db folder" has confused the heck out of me even further.

https://btcarmory.com/docs/pathing

I wrote a tutorial explaining what paths Armory uses and how to set them up in the config files. This is simpler than you are imagining it.

Quote
If it's too complicated to include such a feature in GUI (for us regular folks) such that it would jeopardize the existing working code and possibly break it, then forget I mentioned it. But thanks just the same for your time replying to my query.

GUI development is very time consuming, and GUI features such as pathing end up conflicting with the existing code which was never written with the intent to allow for modularity. On top of that, it is all in Python, which is particularly indisposed to the maintenance of expensive GUI code, so all in all, I put in the config setup cause it's the solution down the middle. When I have time and the appetite for it, I improve UX where I can. I do not often have that appetite.

TLDR: technical debt.
visdude
legendary
Activity: 1081
Merit: 1001
Re: Armory 0.96 is out
June 26, 2017, 02:52:39 AM
#204
Quote from: goatpig on June 25, 2017, 08:58:57 PM
Quote from: visdude on June 25, 2017, 03:56:20 PM
1. I still have 0.92.3 as my cold/offline wallet on a Windows 7 32-bit machine. Can I simply just install 0.96 (or future releases from here on for that matter) over 0.92.3 to update and bring it up to speed?

If/When I put out 32bit builds for 0.96.1, sure.

Quote
2. Will an option in Settings to define an explicit Armory data directory location be included in the next release? There is already such option to point Armory to an explicit Bitcoin Core data directory so providing one for the Armory data directory as well would be very helpful...and makes sense. At this point, one still has to do some CLI arg gymnastics to effectuate such a setting. It's not fun and quite stressful for us who suffer from CLI phobia especially in Linux (Mint) wherein I still have to edit the executable with "sudo vi /usr/share/applications/armory.desktop" (credit to Carlton Banks for the instruction/guide) which I currently couldn't get it to work anymore. I guess I am requesting such a feature.

The datadir is where your wallets and setting/log files go.The blockchain and db folder have their own independant cli arg. If your goal is manage space allocation, you can avoid the CLI magic by putting your custom dbdir and satoshi-datadir folders in armoryqt.conf (this is a new thing in 0.96):

https://github.com/goatpig/BitcoinArmory/blob/master/changelog.txt#L111

1. Otherwise, 0.96 is good to use as a cold/offline wallet on a 64-bit machine then?

2. Such procedure is even more complicated than it already is. I don't even know where to look for those config files to begin with let alone tinkering with them involving more command line arguments which I am trying to avoid in the first place. I'm just thinking that since Armory has a GUI, why not incorporate such a feature in it. There's already one for specifying an explicit Bitcoin Core data directory location in Settings, so why not for Armory's too? I thought that's what GUIs are for -- to make things easy and simple so that even gramps can do it without screwing up. It would be a foolproof method for regular Joes like me. Not everyone involved in cryptos is an astute techie; and I'm a fine example of that.

BTW, on a W7 x64 machine running 0.96 with explicit Armory data directory using a shortcut arg (--satoshi-datadir="D:\Bitcoin" --datadir="D:\Armory"), the "databases" folder, wallets, settings and log files are together in the "Armory" folder and ths setup has been working for a while now through several updates. So your explanation above about the "datadir" being separate from "blockchain and db folder" has confused the heck out of me even further.

If it's too complicated to include such a feature in GUI (for us regular folks) such that it would jeopardize the existing working code and possibly break it, then forget I mentioned it. But thanks just the same for your time replying to my query.

goatpig
legendary
Activity: 3640
Merit: 1345
Armory Developer
Re: Armory 0.96 is out
June 25, 2017, 08:58:57 PM
#203
Quote from: visdude on June 25, 2017, 03:56:20 PM
1. I still have 0.92.3 as my cold/offline wallet on a Windows 7 32-bit machine. Can I simply just install 0.96 (or future releases from here on for that matter) over 0.92.3 to update and bring it up to speed?

If/When I put out 32bit builds for 0.96.1, sure.

Quote
2. Will an option in Settings to define an explicit Armory data directory location be included in the next release? There is already such option to point Armory to an explicit Bitcoin Core data directory so providing one for the Armory data directory as well would be very helpful...and makes sense. At this point, one still has to do some CLI arg gymnastics to effectuate such a setting. It's not fun and quite stressful for us who suffer from CLI phobia especially in Linux (Mint) wherein I still have to edit the executable with "sudo vi /usr/share/applications/armory.desktop" (credit to Carlton Banks for the instruction/guide) which I currently couldn't get it to work anymore. I guess I am requesting such a feature.

The datadir is where your wallets and setting/log files go.The blockchain and db folder have their own independant cli arg. If your goal is manage space allocation, you can avoid the CLI magic by putting your custom dbdir and satoshi-datadir folders in armoryqt.conf (this is a new thing in 0.96):

https://github.com/goatpig/BitcoinArmory/blob/master/changelog.txt#L111
visdude
legendary
Activity: 1081
Merit: 1001
Re: Armory 0.96 is out
June 25, 2017, 03:56:20 PM
#202

1. I still have 0.92.3 as my cold/offline wallet on a Windows 7 32-bit machine. Can I simply just install 0.96 (or future releases from here on for that matter) over 0.92.3 to update and bring it up to speed?

2. Will an option in Settings to define an explicit Armory data directory location be included in the next release? There is already such option to point Armory to an explicit Bitcoin Core data directory so providing one for the Armory data directory as well would be very helpful...and makes sense. At this point, one still has to do some CLI arg gymnastics to effectuate such a setting. It's not fun and quite stressful for us who suffer from CLI phobia especially in Linux (Mint) wherein I still have to edit the executable with "sudo vi /usr/share/applications/armory.desktop" (credit to Carlton Banks for the instruction/guide) which I currently couldn't get it to work anymore. I guess I am requesting such a feature.

Tim R
newbie
Activity: 15
Merit: 0
Re: Armory 0.96 is out
June 21, 2017, 12:01:01 PM
#201
Okay, great! Will wait for your post where to download that build fix. Thanks again.
goatpig
legendary
Activity: 3640
Merit: 1345
Armory Developer
Re: Armory 0.96 is out
June 20, 2017, 08:10:42 PM
#200
You can try to build the testing branch if you want to use the fix right now. Otherwise, sometimes this weekend.
Tim R
newbie
Activity: 15
Merit: 0
Re: Armory 0.96 is out
June 20, 2017, 07:43:15 PM
#199
goatpig:  Many thanks for checking it out!
Tim R
newbie
Activity: 15
Merit: 0
Re: Armory 0.96 is out
June 20, 2017, 07:12:50 PM
#198
Any guess on timing? Had planned to utilize for upcoming ICO. What actions would I need to do once testing build is online, or will tx automatically just become confirmed?
goatpig
legendary
Activity: 3640
Merit: 1345
Armory Developer
Re: Armory 0.96 is out
June 20, 2017, 07:08:26 PM
#197
After log file inspection, you will have to wait for new testing build to get the fix.
Tim R
newbie
Activity: 15
Merit: 0
Re: Armory 0.96 is out
June 20, 2017, 07:05:32 PM
#196
yes, still unconfirmed. FYI I am on the 6 minute gap for posting due to newbie to site.
goatpig
legendary
Activity: 3640
Merit: 1345
Armory Developer
Re: Armory 0.96 is out
June 20, 2017, 07:03:05 PM
#195
So your tx still appears as unconfirmed in Armory?
Tim R
newbie
Activity: 15
Merit: 0
Re: Armory 0.96 is out
June 20, 2017, 06:47:03 PM
#194
Just saw your pastebin comment after sending last one. My apologies.
https://pastebin.com/usdT2f8Q
goatpig
legendary
Activity: 3640
Merit: 1345
Armory Developer
Re: Armory 0.96 is out
June 20, 2017, 06:13:18 PM
#193
TimR: use pastebin!
goatpig
legendary
Activity: 3640
Merit: 1345
Armory Developer
Re: Armory 0.96 is out
June 19, 2017, 07:46:24 PM
#192
Post your logs.
Tim R
newbie
Activity: 15
Merit: 0
Re: Armory 0.96 is out
June 19, 2017, 07:11:44 PM
#191
I installed Armory 0.96 and Bitcoin Core 14.1 onto a new computer. Got wallets set up in Armory. Blockchain fully synced. Moved part of balance from Armory to Coinbase to test and Coinbase shows balance available to use, so was node processed. Went to send rest of Armory balance to Coinbase and remaining Armory balance shows unconfirmed. Closed Armory. Deleted mempool.dat, then restarted Armory. Synced. Still shows unconfirmed. The remaining balance is not actually a received transaction awaiting node processing, rather just the total of my wallet balances. How do I get my Armory wallet balances confirmed when there was no transaction sending the remaining balance there? I was going to try running Armory with "-rescan" but don't know how to do that - if that is a potential solution.
goatpig
legendary
Activity: 3640
Merit: 1345
Armory Developer
Re: Armory 0.96 is out
June 19, 2017, 02:34:35 PM
#190
Quote from: Brangdon on June 19, 2017, 11:59:31 AM
(469262 blocks)

You're trailing over 1000 blocks.
Brangdon
sr. member
Activity: 365
Merit: 251
Re: Armory 0.96 is out
June 19, 2017, 11:59:31 AM
#189
I tried to send transaction 8f124355f16f6df69aa3985d464b817bcfa4190a95bedb96ecff6090dc29d2af back on 4th June, and it got zero confirmations. I figured my fee was too low and it would eventually either confirm or disappear, but it still shows as 0 confirmations now, with Armory claiming "Connected" and "(469262 blocks)". I checked on Blockchain Info which says is confirmed after 9 minutes. Why is Armory still saying it is unconfirmed?

I am using Armory 0.96.0.2 and Bitcoin Core v0.14.1. I recently updated both after a long period of not using Bitcoin, but my wallets and older transactions show up fine.
goatpig
legendary
Activity: 3640
Merit: 1345
Armory Developer
Re: Armory 0.96 is out
June 15, 2017, 11:41:18 AM
#188
Quote from: naska21 on June 15, 2017, 05:08:24 AM
what is this?

In fact I has put a bit lower fee than suggested one (200 Sat/B instead of suggested 400 Sat/B). However it was included into the 1st following block , but such error was a bit  distracting to me

Means your node has bad connectivity/is overloaded. Update to 0.96.0.3 for better verbose.

Quote
Could you specify this dir more presicely, is it this ....Roaming/Armory/databaseses ?

https://btcarmory.com/docs/pathing
Pages:
Bitcoin Forum>Bitcoin>Development & Technical Discussion>Wallet software>Armory
Jump to: