Topic: Armory 0.94 is out - page 2. (Read 7124 times)
What do you mean by offline mode? Why can't .94 be used offline without a mode like the old ones? Just do it offline.
can i rename the label removing the ***MEMPOOL REPLACEABLE*** 
Yes
@goatpig . . .
i have an add that i never used before on my offline wallet & my friend sent me some BTC but when armory received the BTC, it says:
***MEMPOOL REPLACEABLE***(together with the label i made)
highlighted in RED
pls update. thx. i'm using 094 win7
i have an add that i never used before on my offline wallet & my friend sent me some BTC but when armory received the BTC, it says:
***MEMPOOL REPLACEABLE***(together with the label i made)
highlighted in RED
pls update. thx. i'm using 094 win7
It means the coins you received are RBF enabled or spend a utxo still in the ZC mempool. This means you should wait for at least one conf before acknowledging this tx as a payment, regardless of how small the value is.
thx for the quick reply, u got PM. got me worried for a while. it has at least 1 conf now.
can i rename the label removing the ***MEMPOOL REPLACEABLE***
much TIA
@goatpig . . .
i have an add that i never used before on my offline wallet & my friend sent me some BTC but when armory received the BTC, it says:
***MEMPOOL REPLACEABLE***(together with the label i made)
highlighted in RED
pls update. thx. i'm using 094 win7
i have an add that i never used before on my offline wallet & my friend sent me some BTC but when armory received the BTC, it says:
***MEMPOOL REPLACEABLE***(together with the label i made)
highlighted in RED
pls update. thx. i'm using 094 win7
It means the coins you received are RBF enabled or spend a utxo still in the ZC mempool. This means you should wait for at least one conf before acknowledging this tx as a payment, regardless of how small the value is.
@goatpig . . .
i have an add that i never used before on my offline wallet & my friend sent me some BTC but when armory received the BTC, it says:
***MEMPOOL REPLACEABLE***(together with the label i made)
highlighted in RED
pls update. thx. i'm using 094 win7
i have an add that i never used before on my offline wallet & my friend sent me some BTC but when armory received the BTC, it says:
***MEMPOOL REPLACEABLE***(together with the label i made)
highlighted in RED
pls update. thx. i'm using 094 win7
0.94 DB format is different from 0.93, you can't have them both running in the same folder. I'd recommend you use a different DB folder (add --dbdir="some/new/folder" to your shortcut target) and make sure 0.94 is stable before completely replacing 0.93's DB.
From 0.94 onward the "--datadir=" argument is now "--dbdir=" or are they different?
Thank you for this release!
--datadir sets the datadir, which is your wallets, log files, settings file and database folder
--dbdir sets the database folder independently
--datadir="folder1" along with --dbdir="folder2" will result in wallets, logs and settings to go into folder1 and db into folder2.
Hmm I was using "--satoshi-datadir=" all along instead of the "--dbdir=" argument. Thanks!
I get the following on the task bar after closing Armory in all my W7 machines. I started noticing it since 0.93 (or perhaps even the one before that). The notification bubble fades and eventually disappears as expected but the Armory icon lingers and would only disappear with a mouse pointer hover. No biggie really but I guess I was hoping they'd go away in 0.94:
https://i.imgur.com/VNSjkdq.png
I get this message all the time since I started using Armory, about a year ago if I'm not mistaken, with every version released. I only need Chrome + bitcoind + Armory running to top up 2GB of RAM
You're most likely low on resources at the exact moment the error occurs. Armory reconnects right after (never seen it take more than a couple of minutes to reconnect).We can definitely eliminate "low on resources" as the cause. As I indicated on the previous page, it doesn't matter if I run Core/Armory standalone (by themselves) in different and very capable W7 machines (dual, quad and octo core and a Haswell machine with RAMs between 4GB and 16GB), they all get it every time I close Armory. Note that I never got this until around 92.3 or the early iteration of 0.93 (I think - I don't remember exactly which one but thereabouts anyway) and I've been using Armory since 2012.
Anyway, it's not a deal breaker as it never affects Armory's functionality. Nevertheless, it's an interesting quirk of Armory to discuss in here.
This happens via armoryd as well:
Quote
(ERROR) Networking.py:350 - ***Connection to Satoshi client LOST! Attempting to reconnect...
Looks like Networking simply needs to be told a shutdown is imminent so it doesn't trigger a reconnect.
Which in practice means that P2SH transactions should be represented properly again, no?
I'm unaware that they aren't. Can you elaborate?
Ah, well now that I look at it, I'm not 100% that P2SH is the source of the problem. But I have a recent transaction (I think it may have been a withdrawal from an exchange) where none of the inputs are listed (even though only one is relevant to my transaction). I seem to remember the problem first occurring with the introduction of the 0.93 stage of the Db.
Which in practice means that P2SH transactions should be represented properly again, no?
I'm unaware that they aren't. Can you elaborate?
You may choose the delete the DB, in which case, if 0.94 turns out to fail in some major way, you will have to rebuild the 0.93 DB from scratch, or wait for a fix. The choice is yours.
Thanks for the input. This is what I understood to be the worst-case scenario. I'm willing to rebuild the 0.93 DB from scratch if absolutely necessary (knock on wood that it won't be) so I went ahead and deleted it.
At least some of those reasons disappear once goatpig brings about the vaunted tx hints Db.
I've decided to introduce a new DB type in between fullnode and supernode. Additionally to your wallet's history, it will keep track of all txhints and utxos. It won't be quite as heavy or powerful as supernode, but it will fill the power user niche ideally (supernode is more targetted at enterprise requirements and workloads).
Which in practice means that P2SH transactions should be represented properly again, no?
Is there any reason at this point in time to keep the 60GB database from 0.93.3? I'd prefer to delete it and reclaim the HD space.
0.94 was released a week ago as of this writing. There are always more bugs revealed at release than during testing phases. This is why I recommend keeping the 0.93 DB at hand in case some major issue shows up a week from now. You may choose the delete the DB, in which case, if 0.94 turns out to fail in some major way, you will have to rebuild the 0.93 DB from scratch, or wait for a fix. The choice is yours.
At least some of those reasons disappear once goatpig brings about the vaunted tx hints Db.
I've decided to introduce a new DB type in between fullnode and supernode. Additionally to your wallet's history, it will keep track of all txhints and utxos. It won't be quite as heavy or powerful as supernode, but it will fill the power user niche ideally (supernode is more targetted at enterprise requirements and workloads).
Is there any reason at this point in time to keep the 60GB database from 0.93.3? I'd prefer to delete it and reclaim the HD space.
Not really. You can delete it if you want, the only point of keeping it is just in case something fails horribly, which I don't think will happen.
Despite how much thought and work went into the overall design for 0.94, I'll be keeping my 0.93 Db files for a little while after it rolls out, on a "just in case" basis. In the medium term, other than wanting to use the supernode mode, I can't think of a compelling reason to keep the 0.93 Db files. At least some of those reasons disappear once goatpig brings about the vaunted tx hints Db.
Hey all, this is my 1st post on BTCtalk. Been using bitcoin for about a year now, and Armory as my primary wallet. Which means I was quite excited to read that goatpig will be carrying on the torch.
One quick question:
I'm running Windows 10 and had a smooth cutover from 0.93.3 to 0.94. I have tested sending/receiving transactions and everything appears to be working fine. Following advice in this thread, the 0.94 DB is in a separate directory from 0.93.3.
Is there any reason at this point in time to keep the 60GB database from 0.93.3? I'd prefer to delete it and reclaim the HD space.
Thanks again for your hard work.
One quick question:
I'm running Windows 10 and had a smooth cutover from 0.93.3 to 0.94. I have tested sending/receiving transactions and everything appears to be working fine. Following advice in this thread, the 0.94 DB is in a separate directory from 0.93.3.
Is there any reason at this point in time to keep the 60GB database from 0.93.3? I'd prefer to delete it and reclaim the HD space.
Thanks again for your hard work.
Interesting... Just booted Armory to see if I could capture a logfile with the "connection lost" toast and Armory stopped syncing out of the blue. Just opened it and it got stuck here:
Opening it again while writing this. Meanwhile here's the logfile. The connection lost error occurred once and can be seen there:
Full file:
edit: synced perfectly after opening it again.
Opening it again while writing this. Meanwhile here's the logfile. The connection lost error occurred once and can be seen there:
Code:
(ERROR) -- Networking.pyc:359 - ***Connection to Satoshi client LOST! Attempting to reconnect...
Full file:
Code:
(INFO) -- ArmoryUtils.pyc:1083 - C++ block utilities loaded successfully
(INFO) -- ArmoryUtils.pyc:1193 -
(INFO) -- ArmoryUtils.pyc:1194 -
(INFO) -- ArmoryUtils.pyc:1195 -
(INFO) -- ArmoryUtils.pyc:1196 - ************************************************************
(INFO) -- ArmoryUtils.pyc:1197 - Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe --satoshi-datadir=D:\Bitcoin --datadir=D:\Armory
(INFO) -- ArmoryUtils.pyc:1198 - ************************************************************
(INFO) -- ArmoryUtils.pyc:1199 - Loading Armory Engine:
(INFO) -- ArmoryUtils.pyc:1200 - Armory Version : 0.94
(INFO) -- ArmoryUtils.pyc:1201 - Armory Build: : b0033fb356
(INFO) -- ArmoryUtils.pyc:1202 - PyBtcWallet Version : 1.35
(INFO) -- ArmoryUtils.pyc:1203 - Detected Operating system: Windows
(INFO) -- ArmoryUtils.pyc:1204 - OS Variant : 8-6.2.9200--Multiprocessor Free
(INFO) -- ArmoryUtils.pyc:1205 - User home-directory : C:\Users\**********\AppData\Roaming
(INFO) -- ArmoryUtils.pyc:1206 - Satoshi BTC directory : D:\Bitcoin
(INFO) -- ArmoryUtils.pyc:1207 - Armory home dir : D:\Armory
(INFO) -- ArmoryUtils.pyc:1208 - Detected System Specs :
(INFO) -- ArmoryUtils.pyc:1209 - Total Available RAM : 2.00 GB
(INFO) -- ArmoryUtils.pyc:1210 - CPU ID string : Intel64 Family 6 Model 15 Stepping 11, GenuineIntel
(INFO) -- ArmoryUtils.pyc:1211 - Number of CPU cores : 2 cores
(INFO) -- ArmoryUtils.pyc:1212 - System is 64-bit : True
(INFO) -- ArmoryUtils.pyc:1213 - Preferred Encoding : cp1252
(INFO) -- ArmoryUtils.pyc:1214 - Machine Arch : amd64
(INFO) -- ArmoryUtils.pyc:1215 - Available HDD (ARM) : 11 GB
(INFO) -- ArmoryUtils.pyc:1216 - Available HDD (BTC) : 11 GB
(INFO) -- ArmoryUtils.pyc:1217 -
(INFO) -- ArmoryUtils.pyc:1218 - Network Name: Main Network
(INFO) -- ArmoryUtils.pyc:1219 - Satoshi Port: 8333
(INFO) -- ArmoryUtils.pyc:1220 - Do wlt check: True
(INFO) -- ArmoryUtils.pyc:1221 - Named options/arguments to armoryengine.py:
(INFO) -- ArmoryUtils.pyc:1223 - nettimeout : 2
(INFO) -- ArmoryUtils.pyc:1223 - rescan : False
(INFO) -- ArmoryUtils.pyc:1223 - ignoreAllZC : False
(INFO) -- ArmoryUtils.pyc:1223 - rescanBalance : False
(INFO) -- ArmoryUtils.pyc:1223 - disableModules : False
(INFO) -- ArmoryUtils.pyc:1223 - port : None
(INFO) -- ArmoryUtils.pyc:1223 - interport : 8223
(INFO) -- ArmoryUtils.pyc:1223 - skipStatsReport : False
(INFO) -- ArmoryUtils.pyc:1223 - forceWalletCheck: False
(INFO) -- ArmoryUtils.pyc:1223 - rebuild : False
(INFO) -- ArmoryUtils.pyc:1223 - datadir : D:\Armory
(INFO) -- ArmoryUtils.pyc:1223 - clearMempool : False
(INFO) -- ArmoryUtils.pyc:1223 - offline : False
(INFO) -- ArmoryUtils.pyc:1223 - coverageOutputDir: None
(INFO) -- ArmoryUtils.pyc:1223 - armoryDBDir : DEFAULT
(INFO) -- ArmoryUtils.pyc:1223 - satoshiPort : DEFAULT
(INFO) -- ArmoryUtils.pyc:1223 - useTorSettings : False
(INFO) -- ArmoryUtils.pyc:1223 - netlog : False
(INFO) -- ArmoryUtils.pyc:1223 - keypool : 100
(INFO) -- ArmoryUtils.pyc:1223 - coverageInclude : None
(INFO) -- ArmoryUtils.pyc:1223 - forceOnline : False
(INFO) -- ArmoryUtils.pyc:1223 - skipAnnounceCheck: False
(INFO) -- ArmoryUtils.pyc:1223 - redownload : False
(INFO) -- ArmoryUtils.pyc:1223 - multisigFile : DEFAULT
(INFO) -- ArmoryUtils.pyc:1223 - disableTorrent : False
(INFO) -- ArmoryUtils.pyc:1223 - testAnnounceCode: False
(INFO) -- ArmoryUtils.pyc:1223 - mtdebug : False
(INFO) -- ArmoryUtils.pyc:1223 - logDisable : False
(INFO) -- ArmoryUtils.pyc:1223 - settingsPath : D:\Armory\ArmorySettings.txt
(INFO) -- ArmoryUtils.pyc:1223 - verbosity : None
(INFO) -- ArmoryUtils.pyc:1223 - doDebug : False
(INFO) -- ArmoryUtils.pyc:1223 - enableDetSign : True
(INFO) -- ArmoryUtils.pyc:1223 - testnet : False
(INFO) -- ArmoryUtils.pyc:1223 - rpcport : DEFAULT
(INFO) -- ArmoryUtils.pyc:1223 - satoshiHome : D:\Bitcoin
(INFO) -- ArmoryUtils.pyc:1223 - satoshiRpcport : DEFAULT
(INFO) -- ArmoryUtils.pyc:1223 - logFile : D:\Armory\ArmoryQt.exe.log.txt
(INFO) -- ArmoryUtils.pyc:1223 - disableConfPermis: False
(INFO) -- ArmoryUtils.pyc:1223 - enableSupernode : False
(INFO) -- ArmoryUtils.pyc:1224 - Other arguments:
(INFO) -- ArmoryUtils.pyc:1227 - ************************************************************
(INFO) -- ArmoryUtils.pyc:1627 - C++ block utilities loaded successfully
(INFO) -- BDM.pyc:420 - Using the asynchronous/multi-threaded BlockDataManager.
(INFO) -- BDM.pyc:421 - Blockchain operations will happen in the background.
(INFO) -- BDM.pyc:422 - Devs: check TheBDM.getState() before asking for data.
(INFO) -- BDM.pyc:423 - Registering addresses during rescans will queue them for
(INFO) -- BDM.pyc:424 - inclusion after the current scan is completed.
(INFO) -- ArmoryUtils.pyc:3538 - Using settings file: D:\Armory\ArmorySettings.txt
(INFO) -- ArmoryQt.py:2752 - loadWalletsAndSettings
(INFO) -- ArmoryQt.py:2806 - Loading wallets...
(INFO) -- ArmoryQt.py:2865 - Number of wallets read in: 1
(INFO) -- ArmoryQt.py:2870 - Wallet (**********): "********** (Watch) " (No Encryption)
(INFO) -- ArmoryQt.py:2879 - Loading Multisig Lockboxes
(INFO) -- ArmoryQt.py:2311 - Setting up networking...
(INFO) -- ArmoryQt.py:2340 - Internet status: 0
(INFO) -- ArmoryQt.py:2455 - startBitcoindIfNecessary
(INFO) -- ArmoryQt.py:2504 - setSatoshiPaths
(INFO) -- SDM.pyc:321 - Found bitcoind in the following places:
(INFO) -- SDM.pyc:323 - C:\Program Files\Bitcoin\daemon\bitcoind.exe
(INFO) -- SDM.pyc:325 - Using: C:\Program Files\Bitcoin\daemon\bitcoind.exe
(INFO) -- SDM.pyc:496 - Reading bitcoin.conf file
(INFO) -- SDM.pyc:515 - Setting permissions on bitcoin.conf
(INFO) -- SDM.pyc:524 - Setting permissions on bitcoin.conf
(INFO) -- ArmoryUtils.pyc:596 - Executing popen: [u'icacls', u'D:\\Bitcoin\\bitcoin.conf', u'/inheritance:r', u'/grant:r', u'**********:F']
(INFO) -- SDM.pyc:530 - icacls returned:
(INFO) -- SDM.pyc:597 - Called startBitcoind
(INFO) -- ArmoryUtils.pyc:596 - Executing popen: ['C:\\Program Files\\Bitcoin\\daemon\\bitcoind.exe', u'-datadir=D:\\Bitcoin']
(INFO) -- SDM.pyc:669 - PID of bitcoind: 6284
(INFO) -- SDM.pyc:670 - PID of armory: 7072
(INFO) -- ArmoryUtils.pyc:596 - Executing popen: ['.\\guardian.exe', '7072', '6284']
(INFO) -- SDM.pyc:848 - Creating proxy in SDM: host=127.0.0.1, port=8332
(INFO) -- ArmoryQt.py:1527 - setupUriRegistration
(INFO) -- ArmoryQt.py:1595 - Armory already registered for current user. Done!
(INFO) -- ArmoryQt.py:664 - Usermode: Expert
(INFO) -- ArmoryQt.py:1823 - Changing usermode:
(INFO) -- ArmoryQt.py:1824 - From: Expert
(INFO) -- ArmoryQt.py:1832 - To: Expert
(INFO) -- ArmoryQt.py:5855 - Dashboard switched to auto-InitSync
(WARNING) -- SDM.pyc:768 - Overriding not-available state. This should happen 0-5 times
(WARNING) -- SDM.pyc:768 - Overriding not-available state. This should happen 0-5 times
(WARNING) -- SDM.pyc:768 - Overriding not-available state. This should happen 0-5 times
(INFO) -- ArmoryQt.py:2541 - loadBlockchainIfNecessary
(INFO) -- ArmoryQt.py:2562 - Setting netmode: 1
(INFO) -- ArmoryQt.py:5978 - Dashboard switched to "Scanning" mode
(INFO) -- Networking.pyc:65 - Connection initiated. Start handshake
(INFO) -- ArmoryQt.py:5978 - Dashboard switched to "Scanning" mode
(INFO) -- ArmoryQt.py:5844 - Dashboard switched to auto-BadConnection
(INFO) -- ArmoryQt.py:3164 - Current block number: 405445
(ERROR) -- Networking.pyc:359 - ***Connection to Satoshi client LOST! Attempting to reconnect...
(INFO) -- ArmoryQt.py:2562 - Setting netmode: 1
(INFO) -- Networking.pyc:65 - Connection initiated. Start handshake
(INFO) -- ArmoryQt.py:4285 - Log saved to C:/Users/**********/Desktop/armorylog_20160402_2320.txt
(INFO) -- Networking.pyc:156 - Received version message from peer:
(INFO) -- Networking.pyc:157 - Version: 70012
(INFO) -- Networking.pyc:158 - SubVersion: /Satoshi:0.12.0/
(INFO) -- Networking.pyc:159 - TimeStamp: 1459635624
(INFO) -- Networking.pyc:160 - StartHeight: 405445
(INFO) -- Networking.pyc:350 - Handshake finished, connection open!
(INFO) -- ArmoryQt.py:6206 - New Block! : 405446
(INFO) -- ArmoryQt.py:6214 - Current block number: 405446
(INFO) -- ArmoryQt.py:6206 - New Block! : 405447
(INFO) -- ArmoryQt.py:6214 - Current block number: 405447
(INFO) -- ArmoryQt.py:6206 - New Block! : 405448
(INFO) -- ArmoryQt.py:6214 - Current block number: 405448
(INFO) -- ArmoryQt.py:4285 - Log saved to C:/Users/**********/Desktop/armorylog_20160402_2322 2.txt
(INFO) -- ArmoryQt.py:6206 - New Block! : 405449
(INFO) -- ArmoryQt.py:6214 - Current block number: 405449
(INFO) -- ArmoryQt.py:6206 - New Block! : 405450
(INFO) -- ArmoryQt.py:6214 - Current block number: 405450
(INFO) -- ArmoryQt.py:6206 - New Block! : 405452
(INFO) -- ArmoryQt.py:6214 - Current block number: 405452
(INFO) -- Networking.pyc:215 - Received new block. 0000000000000000004651faa345a3df8753a5000ba47b01b4b11b6e0a80171f
(INFO) -- ArmoryQt.py:6206 - New Block! : 405453
(INFO) -- ArmoryQt.py:6214 - Current block number: 405453
(INFO) -- ArmoryQt.py:6206 - New Block! : 405454
(INFO) -- ArmoryQt.py:6214 - Current block number: 405454
(INFO) -- ArmoryQt.py:6206 - New Block! : 405455
(INFO) -- ArmoryQt.py:6214 - Current block number: 405455
(INFO) -- ArmoryQt.py:6206 - New Block! : 405456
(INFO) -- ArmoryQt.py:6214 - Current block number: 405456
(INFO) -- ArmoryQt.py:6206 - New Block! : 405457
(INFO) -- ArmoryQt.py:6214 - Current block number: 405457
(INFO) -- ArmoryQt.py:6206 - New Block! : 405458
(INFO) -- ArmoryQt.py:6214 - Current block number: 405458
(INFO) -- ArmoryQt.py:6206 - New Block! : 405459
(INFO) -- ArmoryQt.py:6214 - Current block number: 405459
(INFO) -- ArmoryQt.py:6206 - New Block! : 405460
(INFO) -- ArmoryQt.py:6214 - Current block number: 405460
(INFO) -- ArmoryQt.py:6206 - New Block! : 405464
(INFO) -- ArmoryQt.py:6214 - Current block number: 405464
(INFO) -- ArmoryQt.py:4285 - Log saved to C:/Users/**********/Desktop/armorylog_20160402_2334 3.txt
(INFO) -- ArmoryQt.py:6206 - New Block! : 405465
(INFO) -- ArmoryQt.py:6214 - Current block number: 405465
(INFO) -- ArmoryQt.py:6206 - New Block! : 405466
(INFO) -- ArmoryQt.py:6214 - Current block number: 405466
(INFO) -- ArmoryQt.py:4285 - Log saved to C:/Users/**********/Desktop/armorylog_20160402_2342 4.txt
(INFO) -- ArmoryQt.py:6731 - BDM is safe for clean shutdown
(INFO) -- SDM.pyc:683 - Called stopBitcoind
(ERROR) -- SDM.pyc:894 - generic error
Traceback (most recent call last):
File "SDM.pyc", line 859, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 97, in __call__
File "httplib.pyc", line 1074, in getresponse
File "httplib.pyc", line 415, in begin
File "httplib.pyc", line 379, in _read_status
BadStatusLine: ''
(ERROR) -- ArmoryUtils.pyc:3171 - Error in pybkgdthread: ''
Traceback (most recent call last):
File "armoryengine\ArmoryUtils.pyc", line 3169, in run
File "armoryengine\ArmoryUtils.pyc", line 3106, in funcPartial
File "SDM.pyc", line 859, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 97, in __call__
File "httplib.pyc", line 1074, in getresponse
File "httplib.pyc", line 415, in begin
File "httplib.pyc", line 379, in _read_status
BadStatusLine: ''
(ERROR) -- Networking.pyc:359 - ***Connection to Satoshi client LOST! Attempting to reconnect...
(INFO) -- ArmoryQt.py:6773 - Attempting to close the main window!
edit: synced perfectly after opening it again.
Quote from: visdude link=topic=1414243.msg14395542#msg14395542
I get this message all the time since I started using Armory, about a year ago if I'm not mistaken, with every version released. I only need Chrome + bitcoind + Armory running to top up 2GB of RAM
You're most likely low on resources at the exact moment the error occurs. Armory reconnects right after (never seen it take more than a couple of minutes to reconnect).lol also my mistake. he says this happens reliably after Armory is shut down
The warning/notification is an oxymoron considering the fact that it appears after Armory has already closed.
"Of course Armory cannot send nor receive bitcoins...it's already closed, foo!"
I get the following on the task bar after closing Armory in all my W7 machines. I started noticing it since 0.93 (or perhaps even the one before that). The notification bubble fades and eventually disappears as expected but the Armory icon lingers and would only disappear with a mouse pointer hover. No biggie really but I guess I was hoping they'd go away in 0.94:
I get this message all the time since I started using Armory, about a year ago if I'm not mistaken, with every version released. I only need Chrome + bitcoind + Armory running to top up 2GB of RAM
You're most likely low on resources at the exact moment the error occurs. Armory reconnects right after (never seen it take more than a couple of minutes to reconnect).We can definitely eliminate "low on resources" as the cause. As I indicated on the previous page, it doesn't matter if I run Core/Armory standalone (by themselves) in different and very capable W7 machines (dual, quad and octo core and a Haswell machine with RAMs between 4GB and 16GB), they all get it every time I close Armory. Note that I never got this until around 92.3 or the early iteration of 0.93 (I think - I don't remember exactly which one but thereabouts anyway) and I've been using Armory since 2012.
Anyway, it's not a deal breaker as it never affects Armory's functionality. Nevertheless, it's an interesting quirk of Armory to discuss in here.
hi,
0.93 has filled my HD. only 400MB left.
in which folder is the DB stored? i think deleting the DB, upgrading to 0.94.1 might be the best solution.
Platform?
For Windows it is C:\Users
For Linux it is /home/
For OS X it is /Library/Application Support/Armory (I think)
hi,
0.93 has filled my HD. only 400MB left.
in which folder is the DB stored? i think deleting the DB, upgrading to 0.94.1 might be the best solution.
Jump to: