I do not accept donations.
Ok. Thanks again for helping.
Topic: 0.96.3 Bump Fee not working (Read 290 times)
Ok. Thanks again for helping.
I do not accept donations.
So, it looks like being a problem since September.
How to address the three sent tx stuck in the net?
TIA
Using Help > Clear All Unconfirmed, restarting Armory, then remake the transaction from scratch with a bigger fee, is a brute-force method that has worked for me. How to address the three sent tx stuck in the net?
TIA
Databases rebuilt from scratch.
Tx rescanned.
Wallets up and ready.
Fees now showing.
First tx will be a donation to you if you PM me your BTC address.
Thanks
Tx rescanned.
Wallets up and ready.
Fees now showing.
First tx will be a donation to you if you PM me your BTC address.
Thanks
goatpig, please explain a little more what I need to do, thanks!
It thinks your ZC output is worth 0. Did you try to empty your wallet in one go?
Yes, I was trying to move my funds to Ledger before all those forks. What is ZC output?
I'll start with RC1 from scratch and then I'll try to import the wallets. Learning curve, as always. I'll let you know. Donation for Armory development at the end if you'll accept that
You need server=1 for the RPC to be turned on. If you don't use the RPC log/pass for your own purposes, get rid of these lines too. Also, you should update to RC1.
RC1? Got it.
You need server=1 for the RPC to be turned on. If you don't use the RPC log/pass for your own purposes, get rid of these lines too. Also, you should update to RC1.
Then your setup is off. How did you enable the RPC on your node, and what version is it?
Version 0.15.1
peerbloomfilters=0
rpcuser=myusername
rpcpassword=mypassword
Yet I'll have to wait for Armory to end scanning TX history...something today went wrong as you can see from above logs
EDIT:
-ERROR - 19:14:48.188: (..\SocketObject.cpp:136) POLLERR in writeToSocket
-ERROR - 19:14:48.188: (..\SocketObject.cpp:290) POLLERR error in readFromSocketThread
Armorydb.exe closed abruptly. End
Thanks
Then your setup is off. How did you enable the RPC on your node, and what version is it?
Is the block counter at the bottom right green or purple?
Looks like there are some problems.
db log and armory one
Code:
Log file opened at 17:50:52.000: D:\Armory/dbLog.txt
-INFO - 17:50:52.016: (..\main.cpp:32) Running on 8 threads
-INFO - 17:50:52.016: (..\main.cpp:33) Ram usage level: 4
-INFO - 17:50:52.016: (..\BlockUtils.cpp:915) blkfile dir: d:\Bitcoin\Data/blocks
-INFO - 17:50:52.016: (..\BlockUtils.cpp:916) lmdb dir: D:\Armory/databases
-INFO - 17:50:52.032: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO - 17:50:52.594: (c:\users\goat\code\armory3\cppforswig\BDM_Server.h:263) Listening on port 9001
-INFO - 17:50:54.188: (..\BitcoinP2P.cpp:947) Connected to Bitcoin node
-INFO - 17:50:55.594: (..\BlockUtils.cpp:1108) Executing: doInitialSyncOnLoad
-INFO - 17:50:55.766: (..\DatabaseBuilder.cpp:199) Reading headers from db
-WARN - 17:52:05.719: (..\Blockchain.cpp:64) block id duplicate: 498935
-WARN - 17:52:53.657: (..\Blockchain.cpp:64) block id duplicate: 498322
-INFO - 17:53:25.766: (..\DatabaseBuilder.cpp:238) Found 500127 headers in db
-INFO - 17:53:30.016: (..\DatabaseBuilder.cpp:64) Rewinding 100 blocks
-INFO - 17:53:30.016: (..\DatabaseBuilder.cpp:71) updating HEADERS db
-INFO - 17:53:30.032: (..\DatabaseBuilder.cpp:493) Found next block after skipping 1078214bytes
-INFO - 17:53:32.250: (..\DatabaseBuilder.cpp:281) parsed block file #1109
-INFO - 17:53:34.391: (..\Blockchain.cpp:248) Organizing chain
-INFO - 17:53:34.516: (..\Blockchain.cpp:370) Organized chain in 0s
-INFO - 17:53:34.563: (..\DatabaseBuilder.cpp:76) updated HEADERS db in 4s
-INFO - 17:53:34.594: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO - 17:53:34.594: (..\DatabaseBuilder.cpp:1231) verifying txfilters integrity
-INFO - 17:55:20.688: (..\DatabaseBuilder.cpp:1314) done checking txfilters
-INFO - 17:55:20.860: (..\DatabaseBuilder.cpp:134) scanning new blocks from #500125 to #500420
-INFO - 17:55:21.532: (..\BlockchainScanner.cpp:852) scanned from block #500125 to #500420
-INFO - 17:55:21.813: (..\BlockchainScanner.cpp:214) scanned transaction history in 0s
-INFO - 17:55:21.860: (..\BlockchainScanner.cpp:1787) resolving txhashes
-INFO - 17:55:21.891: (..\BlockchainScanner.cpp:1846) 0 blocks hit by tx filters
-INFO - 17:55:21.891: (..\BlockchainScanner.cpp:1935) found 0 missing hashes
-INFO - 17:55:21.891: (..\BlockchainScanner.cpp:1980) Resolved missing hashes in 0s
-INFO - 17:55:22.047: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO - 17:55:22.079: (..\DatabaseBuilder.cpp:186) scanned new blocks in 1s
-INFO - 17:55:22.079: (..\DatabaseBuilder.cpp:190) init db in 266s
-INFO - 17:55:22.079: (..\BDM_supportClasses.cpp:1890) Enabling zero-conf tracking
-WARN - 17:55:23.860: (..\BDM_supportClasses.cpp:1943) running 5 zc parser threads
-WARN - 17:55:23.860: (..\BDM_supportClasses.cpp:1943) running 10 zc parser threads
-WARN - 17:55:23.875: (..\BDM_supportClasses.cpp:1943) running 15 zc parser threads
-WARN - 17:55:23.875: (..\BDM_supportClasses.cpp:1943) running 20 zc parser threads
-WARN - 17:55:30.313: (..\BDM_supportClasses.cpp:1943) running 25 zc parser threads
-WARN - 17:55:30.329: (..\BDM_supportClasses.cpp:1943) running 30 zc parser threads
-WARN - 17:55:55.110: (..\BDM_supportClasses.cpp:1943) running 35 zc parser threads
-WARN - 17:56:11.860: (..\BDM_supportClasses.cpp:1943) running 40 zc parser threads
-WARN - 17:56:11.860: (..\BDM_supportClasses.cpp:1943) running 45 zc parser threads
-WARN - 17:56:11.875: (..\BDM_supportClasses.cpp:1943) running 50 zc parser threads
-WARN - 17:56:52.282: (..\BDM_supportClasses.cpp:1943) running 55 zc parser threads
-WARN - 17:56:52.297: (..\BDM_supportClasses.cpp:1943) running 60 zc parser threads
-WARN - 17:56:52.297: (..\BDM_supportClasses.cpp:1943) running 65 zc parser threads
-WARN - 17:56:52.297: (..\BDM_supportClasses.cpp:1943) running 70 zc parser threads
-WARN - 17:56:54.782: (..\BDM_supportClasses.cpp:1943) running 75 zc parser threads
-WARN - 17:56:54.782: (..\BDM_supportClasses.cpp:1943) running 80 zc parser threads
-WARN - 17:56:54.797: (..\BDM_supportClasses.cpp:1943) running 85 zc parser threads
-WARN - 18:04:25.969: (..\BDM_supportClasses.cpp:1943) running 90 zc parser threads
-WARN - 18:04:25.969: (..\BDM_supportClasses.cpp:1943) running 95 zc parser threads
-WARN - 18:04:25.985: (..\BDM_supportClasses.cpp:1943) running 100 zc parser threads
-INFO - 18:05:24.844: (..\BlockchainScanner.cpp:857) scanned block #500421
-INFO - 18:05:50.375: (..\BlockchainScanner.cpp:857) scanned block #500422
-INFO - 18:07:35.016: (..\BlockchainScanner.cpp:857) scanned block #500423
-INFO - 18:14:32.954: (..\BlockchainScanner.cpp:852) scanned from block #500424 to #500425
-INFO - 18:19:50.907: (..\BlockchainScanner.cpp:857) scanned block #500426
-INFO - 18:19:55.000: (..\BDM_Server.cpp:1114) registered bdv: 12c9217bae94a9587c4d
-INFO - 18:19:55.079: (..\BDM_supportClasses.cpp:401) Starting address registration process
-INFO - 18:20:01.063: (..\BlockchainScanner.cpp:852) scanned from block #0 to #142691
-INFO - 18:20:09.219: (..\BlockchainScanner.cpp:852) scanned from block #142692 to #170004
-INFO - 18:20:21.313: (..\BlockchainScanner.cpp:852) scanned from block #170005 to #183110
-INFO - 18:20:38.188: (..\BlockchainScanner.cpp:852) scanned from block #183111 to #189230
-INFO - 18:20:52.516: (..\BlockchainScanner.cpp:852) scanned from block #189231 to #194895
-INFO - 18:21:10.532: (..\BlockchainScanner.cpp:852) scanned from block #194896 to #200879
-INFO - 18:21:26.891: (..\BlockchainScanner.cpp:852) scanned from block #200880 to #206654
-INFO - 18:21:44.750: (..\BlockchainScanner.cpp:852) scanned from block #206655 to #211835
-INFO - 18:22:03.438: (..\BlockchainScanner.cpp:852) scanned from block #211836 to #216013
-INFO - 18:22:20.204: (..\BlockchainScanner.cpp:852) scanned from block #216014 to #219400
-INFO - 18:22:38.438: (..\BlockchainScanner.cpp:852) scanned from block #219401 to #222889
-INFO - 18:22:58.969: (..\BlockchainScanner.cpp:852) scanned from block #222890 to #226014
-INFO - 18:23:18.516: (..\BlockchainScanner.cpp:852) scanned from block #226015 to #229700
-INFO - 18:23:39.204: (..\BlockchainScanner.cpp:852) scanned from block #229701 to #232827
-INFO - 18:24:00.829: (..\BlockchainScanner.cpp:852) scanned from block #232828 to #235987
-INFO - 18:24:21.797: (..\BlockchainScanner.cpp:852) scanned from block #235988 to #239311
-INFO - 18:24:42.657: (..\BlockchainScanner.cpp:852) scanned from block #239312 to #243501
-INFO - 18:25:03.032: (..\BlockchainScanner.cpp:852) scanned from block #243502 to #248592
-INFO - 18:25:24.407: (..\BlockchainScanner.cpp:852) scanned from block #248593 to #252921
-INFO - 18:25:44.719: (..\BlockchainScanner.cpp:852) scanned from block #252922 to #256835
-INFO - 18:26:08.329: (..\BlockchainScanner.cpp:852) scanned from block #256836 to #261047
-INFO - 18:26:28.625: (..\BlockchainScanner.cpp:852) scanned from block #261048 to #265286
-INFO - 18:26:49.563: (..\BlockchainScanner.cpp:852) scanned from block #265287 to #269039
-INFO - 18:27:12.500: (..\BlockchainScanner.cpp:852) scanned from block #269040 to #271688
-INFO - 18:27:37.704: (..\BlockchainScanner.cpp:852) scanned from block #271689 to #274362
-INFO - 18:27:57.657: (..\BlockchainScanner.cpp:852) scanned from block #274363 to #277493
-INFO - 18:28:21.485: (..\BlockchainScanner.cpp:852) scanned from block #277494 to #280827
-INFO - 18:28:45.141: (..\BlockchainScanner.cpp:852) scanned from block #280828 to #283888
-INFO - 18:28:58.125: (..\BlockchainScanner.cpp:857) scanned block #500427
-INFO - 18:29:05.860: (..\BlockchainScanner.cpp:852) scanned from block #283889 to #286454
-INFO - 18:29:30.469: (..\BlockchainScanner.cpp:852) scanned from block #286455 to #288768
-INFO - 18:29:55.579: (..\BlockchainScanner.cpp:852) scanned from block #288769 to #290929
-INFO - 18:30:19.860: (..\BlockchainScanner.cpp:852) scanned from block #290930 to #293434
-INFO - 18:30:43.735: (..\BlockchainScanner.cpp:852) scanned from block #293435 to #295975
-INFO - 18:31:08.532: (..\BlockchainScanner.cpp:852) scanned from block #295976 to #298384
-INFO - 18:31:31.860: (..\BlockchainScanner.cpp:852) scanned from block #298385 to #300751
-INFO - 18:31:58.141: (..\BlockchainScanner.cpp:852) scanned from block #300752 to #303081
-INFO - 18:32:25.875: (..\BlockchainScanner.cpp:852) scanned from block #303082 to #305430
-INFO - 18:32:52.407: (..\BlockchainScanner.cpp:852) scanned from block #305431 to #308113
-INFO - 18:33:19.250: (..\BlockchainScanner.cpp:852) scanned from block #308114 to #310316
-INFO - 18:33:45.016: (..\BlockchainScanner.cpp:852) scanned from block #310317 to #312595
-INFO - 18:34:04.610: (..\BlockchainScanner.cpp:852) scanned from block #312596 to #314796
-INFO - 18:34:31.000: (..\BlockchainScanner.cpp:852) scanned from block #314797 to #316977
-INFO - 18:34:56.766: (..\BlockchainScanner.cpp:852) scanned from block #316978 to #319245
-INFO - 18:35:24.750: (..\BlockchainScanner.cpp:852) scanned from block #319246 to #321314
-INFO - 18:35:54.485: (..\BlockchainScanner.cpp:852) scanned from block #321315 to #323277
-INFO - 18:36:22.860: (..\BlockchainScanner.cpp:852) scanned from block #323278 to #325141
-INFO - 18:36:53.094: (..\BlockchainScanner.cpp:852) scanned from block #325142 to #326947
and keeping scanning
****************
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1147 - C++ block utilities loaded successfully
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1264 -
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1265 -
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1266 -
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1267 - ************************************************************
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1268 - Invoked: D:\ArmoryStandalone-pre_0.96.3\ArmoryQt.exe --datadir=D:\Armory --satoshi-datadir=d:\Bitcoin\Data --rpcport=8332
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1269 - ************************************************************
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1270 - Loading Armory Engine:
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1271 - Armory Version : 0.96.3
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1272 - Armory Build: : 2b65ac0648
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1273 - PyBtcWallet Version : 1.35
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1274 - Detected Operating system: Windows
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1275 - OS Variant : 8-6.2.9200--Multiprocessor Free
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1276 - User home-directory : C:\Users\Dan\AppData\Roaming
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1277 - Satoshi BTC directory : d:\Bitcoin\Data
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1278 - Armory home dir : D:\Armory
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1279 - Detected System Specs :
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1280 - Total Available RAM : 23.89 GB
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1281 - CPU ID string : Intel64 Family 6 Model 158 Stepping 9, GenuineIntel
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1282 - Number of CPU cores : 8 cores
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1283 - System is 64-bit : True
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1284 - Preferred Encoding : cp1252
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1285 - Machine Arch : amd64
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1286 - Available HDD (ARM) : 423 GB
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1287 - Available HDD (BTC) : 423 GB
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1288 -
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1289 - Network Name: Main Network
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1290 - Satoshi Port: 8333
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1291 - Do wlt check: True
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1292 - Named options/arguments to armoryengine.py:
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1294 - thread_count : -1
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1294 - rescan : False
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1294 - ignoreAllZC : False
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1294 - rescanBalance : False
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1294 - disableModules : False
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1294 - port : None
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1294 - interport : 8223
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1294 - coverageOutputDir: None
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1294 - forceWalletCheck: False
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1294 - regtest : False
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1294 - rebuild : False
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1294 - nettimeout : 2
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1294 - datadir : D:\Armory
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1294 - clearMempool : False
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1294 - offline : False
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1294 - armoryDBDir : DEFAULT
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1294 - armorydb_port : 9001
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1294 - satoshiPort : DEFAULT
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1294 - useTorSettings : False
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1294 - netlog : False
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1294 - keypool : 100
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1294 - coverageInclude : None
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1294 - forceOnline : False
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1294 - redownload : False
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1294 - rpcBindAddr : 127.0.0.1
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1294 - armorydb_ip : 127.0.0.1
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1294 - multisigFile : DEFAULT
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1294 - ram_usage : -1
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1294 - mtdebug : False
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1294 - logDisable : False
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1294 - settingsPath : D:\Armory\ArmorySettings.txt
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1294 - language : en
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1294 - db_type : DB_FULL
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1294 - doDebug : False
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1294 - enableDetSign : True
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1294 - disableConfPermis: False
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1294 - testnet : False
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1294 - rpcport : 8332
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1294 - satoshiHome : d:\Bitcoin\Data
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1294 - satoshiRpcport : DEFAULT
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1294 - logFile : D:\Armory\ArmoryQt.exe.log.txt
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1294 - verbosity : None
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1295 - Other arguments:
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1298 - ************************************************************
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:1701 - C++ block utilities loaded successfully
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:3559 - Using settings file: D:\Armory\ArmorySettings.txt
2017-12-21 18:19:52 (ERROR) -- ArmoryUtils.pyc:3716 - Unsupported language specified. Defaulting to English (en)
2017-12-21 18:19:52 (INFO) -- ArmoryUtils.pyc:3719 - Using Language: en
2017-12-21 18:19:52 (INFO) -- BDM.pyc:355 - Using the asynchronous/multi-threaded BlockDataManager.
2017-12-21 18:19:52 (INFO) -- BDM.pyc:356 - Blockchain operations will happen in the background.
2017-12-21 18:19:52 (INFO) -- BDM.pyc:357 - Devs: check TheBDM.getState() before asking for data.
2017-12-21 18:19:52 (INFO) -- BDM.pyc:358 - Registering addresses during rescans will queue them for
2017-12-21 18:19:52 (INFO) -- BDM.pyc:359 - inclusion after the current scan is completed.
2017-12-21 18:19:53 (INFO) -- ArmoryUtils.pyc:3559 - Using settings file: D:\Armory\ArmorySettings.txt
2017-12-21 18:19:53 (INFO) -- ArmoryQt.py:2061 - loadWalletsAndSettings
2017-12-21 18:19:53 (INFO) -- ArmoryQt.py:2121 - Loading wallets...
2017-12-21 18:19:53 (INFO) -- ArmoryQt.py:2186 - Number of wallets read in: 5
2017-12-21 18:19:53 (INFO) -- ArmoryQt.py:2191 - Wallet (.....): "1 " (Encrypted)
2017-12-21 18:19:53 (INFO) -- ArmoryQt.py:2191 - Wallet (.....): "2 " (Encrypted)
2017-12-21 18:19:53 (INFO) -- ArmoryQt.py:2191 - Wallet (.....): "3 " (Encrypted)
2017-12-21 18:19:53 (INFO) -- ArmoryQt.py:2191 - Wallet (.....): "4 " (Encrypted)
2017-12-21 18:19:53 (INFO) -- ArmoryQt.py:2191 - Wallet (.....): "5 " (Encrypted)
2017-12-21 18:19:53 (INFO) -- ArmoryQt.py:2196 - Loading Multisig Lockboxes
2017-12-21 18:19:53 (INFO) -- ArmoryQt.py:1763 - acquiring process mutex...
2017-12-21 18:19:55 (INFO) -- ArmoryQt.py:1395 - setupUriRegistration
2017-12-21 18:19:55 (INFO) -- ArmoryQt.py:1463 - Armory already registered for current user. Done!
2017-12-21 18:19:55 (INFO) -- ArmoryQt.py:566 - Usermode: Expert
2017-12-21 18:19:55 (INFO) -- ArmoryQt.py:1698 - Changing usermode:
2017-12-21 18:19:55 (INFO) -- ArmoryQt.py:1699 - From: Expert
2017-12-21 18:19:55 (INFO) -- ArmoryQt.py:1707 - To: Expert
2017-12-21 18:19:55 (INFO) -- ArmoryQt.py:1836 - startBitcoindIfNecessary
2017-12-21 18:19:55 (INFO) -- ArmoryQt.py:1924 - Setting netmode: 1
2017-12-21 18:19:55 (INFO) -- ArmoryQt.py:1906 - loadBlockchainIfNecessary
2017-12-21 18:19:55 (ERROR) -- ArmoryQt.py:1198 - 3 attempts to load blockchain failed. Remove mempool.bin.
2017-12-21 18:19:55 (ERROR) -- ArmoryQt.py:1203 - File mempool.bin does not exist. Nothing deleted.
2017-12-21 18:19:55 (INFO) -- ArmoryQt.py:1924 - Setting netmode: 1
2017-12-21 18:19:55 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-21 18:19:55 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-21 18:19:55 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-21 18:20:01 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-21 18:20:09 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-21 18:20:21 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-21 18:20:38 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-21 18:20:52 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-21 18:21:10 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-21 18:21:26 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-21 18:21:44 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-21 18:22:03 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-21 18:22:20 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-21 18:22:38 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-21 18:22:58 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-21 18:23:18 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-21 18:23:39 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-21 18:24:00 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-21 18:24:21 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-21 18:24:42 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-21 18:25:03 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-21 18:25:24 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-21 18:25:44 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-21 18:26:08 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-21 18:26:28 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-21 18:26:49 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-21 18:27:12 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-21 18:27:37 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-21 18:27:57 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-21 18:28:21 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-21 18:28:45 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-21 18:29:05 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-21 18:29:30 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-21 18:29:55 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-21 18:30:19 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-21 18:30:43 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-21 18:31:08 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-21 18:31:31 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-21 18:31:58 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-21 18:32:25 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-21 18:32:52 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-21 18:33:19 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-21 18:33:45 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-21 18:34:04 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-21 18:34:31 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-21 18:34:56 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-21 18:35:24 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-21 18:35:54 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-21 18:36:22 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-21 18:36:53 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-21 18:37:23 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-21 18:37:52 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-21 18:38:24 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-21 18:38:55 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
Anyway it is violet
Thanks
goatpig, please explain a little more what I need to do, thanks!
It thinks your ZC output is worth 0. Did you try to empty your wallet in one go?
Quote
RPC on and Armory been told to handle Bitcoin Core, which is done, but yet Armory is not fetching dynamic fees. Any hint?
Is the block counter at the bottom right green or purple?
Quote
There's a fix in the testing branch, just haven't bothered putting out a build. Open source and all you know, build it yourself blah blah. If you can't build from source, you're at my mercy blah blah.
Progress! I built the testing branch, now, right clicking and selecting bump fee shows a dialog that says:
Quote
RBF Failure: You are trying to bump the fee of a broadcasted unconfirmed transaction. The process failed unexpectedly. To double spend your transaction, pick the relevant output from the RBF Control, found in the Send dialog in Expert User Mode.
Clicking "ok" leads to the send dialog. I clicked on the RBF Control button and reviewed the outputs, went back to the send dialog and lowered the send amount. Clicking send results in an error message:
Quote
Coin Selection Failure: Coin selection failed with error: Invalid spend value
goatpig, please explain a little more what I need to do, thanks!
Thanks for the updates.
EDIT:
RPC on and Armory been told to handle Bitcoin Core, which is done, but yet Armory is not fetching dynamic fees. Any hint?
Quote
There's a fix in the testing branch, just haven't bothered putting out a build. Open source and all you know, build it yourself blah blah. If you can't build from source, you're at my mercy blah blah.
Progress! I built the testing branch, now, right clicking and selecting bump fee shows a dialog that says:
Quote
RBF Failure: You are trying to bump the fee of a broadcasted unconfirmed transaction. The process failed unexpectedly. To double spend your transaction, pick the relevant output from the RBF Control, found in the Send dialog in Expert User Mode.
Clicking "ok" leads to the send dialog. I clicked on the RBF Control button and reviewed the outputs, went back to the send dialog and lowered the send amount. Clicking send results in an error message:
Quote
Coin Selection Failure: Coin selection failed with error: Invalid spend value
goatpig, please explain a little more what I need to do, thanks!
Maybe you hadn't noticed the extreme amount of transactions hitting the network in the past week? The transaction fee to be included in the next block has jumped to over 700 satoshis/byte. There isn't a wallet in existence which is capable of dealing with this, which is why Armory lets the user set his own fee, as a human is still going to outperform any software estimation at this point.
Sorry mate but such wallet exists and yes I noticed all of that.
af346b4d1d9f641e0abb39b9dcfe8261422a9e0e67828cc0f9a6cb85e0b9689c
Just to mention a test transaction I made today from another wallet, with fewer fees than mentioned by you and with 12 confirmations as I'm writing.
I'll simply calculate fees with either BTC Core or Electrum while my problem with Armory will be solved.
Thanks for helping
Godspeed.
RPC is on as rpcuser and rpcpassword are set and server=1
--rpcport=8332 has been set according to this
https://www.bitcoinarmory.com/troubleshooting/#command-line-options
Armory shows connected. Bitcoin-Core shows that Armory is connected to node.
No fees calculated.
EDIT:
I start node manually before starting Armory
Thanks mates. Looks like Armory crew is NOT putting that into the "urgent" todo list.
The fix is already in the testing branch, you can build it yourself if you want it today, or you will have to wait for the "crew" to make a build for you.
On top of that Armory 0.96.3 is NOT (dinamically) calculating fees appropriately.
Reverting to another RELIABLE wallet as yesterday I had 4 stuck tx with Bittrex in a row.
Reverting to another RELIABLE wallet as yesterday I had 4 stuck tx with Bittrex in a row.
Maybe you hadn't noticed the extreme amount of transactions hitting the network in the past week? The transaction fee to be included in the next block has jumped to over 700 satoshis/byte. There isn't a wallet in existence which is capable of dealing with this, which is why Armory lets the user set his own fee, as a human is still going to outperform any software estimation at this point.
Thanks mates. Looks like Armory crew is NOT putting that into the "urgent" todo list.
There's a fix in the testing branch, just haven't bothered putting out a build. Open source and all you know, build it yourself blah blah. If you can't build from source, you're at my mercy blah blah.
Quote
On top of that Armory 0.96.3 is NOT (dinamically) calculating fees appropriately.
It does, turn on your node's RPC. Also it warns you if your fee is <200 s/B. Next time don't just click through every message box.
Quote
Reverting to another RELIABLE wallet as yesterday I had 4 stuck tx with Bittrex in a row.
Godspeed.
Thanks mates. Looks like Armory crew is NOT putting that into the "urgent" todo list.
On top of that Armory 0.96.3 is NOT (dinamically) calculating fees appropriately.
Reverting to another RELIABLE wallet as yesterday I had 4 stuck tx with Bittrex in a row.
On top of that Armory 0.96.3 is NOT (dinamically) calculating fees appropriately.
Reverting to another RELIABLE wallet as yesterday I had 4 stuck tx with Bittrex in a row.
0.96.3.99 does not work too
edit: Scratch that. They're on the testing branch, not a released build. I guess either wait for an official build or build it yourself.
So, it looks like being a problem since September.
How to address the three sent tx stuck in the net?
TIA
How to address the three sent tx stuck in the net?
TIA
Jump to: