Quote
So the URL issue is a known bug or something?
Yes.
Quote
Can you PM an email address I can forward you my logs to?
Thanks.
Thanks.
Use the ticket system or [email protected]
Thanks, I did create a ticket.
Topic: Sending BTC keeps failing... (Read 842 times)
Yes.
Use the ticket system or [email protected]
Thanks, I did create a ticket.
Quote
So the URL issue is a known bug or something?
Yes.
Quote
Can you PM an email address I can forward you my logs to?
Thanks.
Thanks.
Use the ticket system or [email protected]
The URL issue is not related to your case in any way.
I'm thinking of 2 possible culprits:
1) You are trying to broadcast a transaction with no fee. Starting 11.1 or 11.2 (can't remember which version), Core will essentially not relay 0 fee transactions anymore.
2) Your current DB is somehow corrupt. It doesn't see some of the spends and is trying to spend invalid TxOuts. A rescan would fix that issue.
If it's neither one nor the other, I'll need to look at your log files.
I'm thinking of 2 possible culprits:
1) You are trying to broadcast a transaction with no fee. Starting 11.1 or 11.2 (can't remember which version), Core will essentially not relay 0 fee transactions anymore.
2) Your current DB is somehow corrupt. It doesn't see some of the spends and is trying to spend invalid TxOuts. A rescan would fix that issue.
If it's neither one nor the other, I'll need to look at your log files.
So the URL issue is a known bug or something?
Can you PM an email address I can forward you my logs to?
Thanks.
The URL issue is not related to your case in any way.
I'm thinking of 2 possible culprits:
1) You are trying to broadcast a transaction with no fee. Starting 11.1 or 11.2 (can't remember which version), Core will essentially not relay 0 fee transactions anymore.
2) Your current DB is somehow corrupt. It doesn't see some of the spends and is trying to spend invalid TxOuts. A rescan would fix that issue.
If it's neither one nor the other, I'll need to look at your log files.
I'm thinking of 2 possible culprits:
1) You are trying to broadcast a transaction with no fee. Starting 11.1 or 11.2 (can't remember which version), Core will essentially not relay 0 fee transactions anymore.
2) Your current DB is somehow corrupt. It doesn't see some of the spends and is trying to spend invalid TxOuts. A rescan would fix that issue.
If it's neither one nor the other, I'll need to look at your log files.
Did you pay a fee on these transactions?
If the default transaction fee was selected could the network deny the transaction somehow and make things look weird? The BTC address I sent the coins to indicates a 0 balance, but the wallet I sent the coins to still has the coins in them. I may have selected the default transaction fee. If that may make things look a little odd that would explain "some" of the issues.
Still not sure why Armory isn't letting me know there is an updated Core.
I can directly send you my log if that may make it easier to check? Little hard to decipher the log if not a developer. I can re-generate the URL issue at will by hitting check update button. I don't want to blindly just reinstall/update. I'd rather try to see why these things are happening, to avoid them later.
Thank you.
2016-01-18 20:06 (INFO) -- announcefetch.pyc:271 - Fetching: https://bitcoinarmory.com/announce.txt
2016-01-18 20:06 (ERROR) -- announcefetch.pyc:283 - Specified URL was inaccessible
2016-01-18 20:06 (ERROR) -- announcefetch.pyc:284 - Tried: https://bitcoinarmory.com/announce.txt
2016-01-18 20:06 (INFO) -- announcefetch.pyc:271 - Fetching: https://s3.amazonaws.com/bitcoinarmory-media/announce.txt
2016-01-18 20:15 (INFO) -- announcefetch.pyc:389 - Forcing announce data fetch
2016-01-18 20:15 (INFO) -- announcefetch.pyc:271 - Fetching: https://bitcoinarmory.com/announce.txt
2016-01-18 20:15 (ERROR) -- announcefetch.pyc:283 - Specified URL was inaccessible
2016-01-18 20:15 (ERROR) -- announcefetch.pyc:284 - Tried: https://bitcoinarmory.com/announce.txt
2016-01-18 20:15 (INFO) -- announcefetch.pyc:271 - Fetching: https://s3.amazonaws.com/bitcoinarmory-media/announce.txt
2016-01-18 20:15 (INFO) -- ArmoryQt.py:6763 - BDM is safe for clean shutdown
2016-01-18 20:15 (INFO) -- SDM.pyc:683 - Called stopBitcoind
2016-01-18 20:15 (ERROR) -- Networking.pyc:359 - ***Connection to Satoshi client LOST! Attempting to reconnect...
2016-01-18 20:15 (INFO) -- ArmoryQt.py:6805 - Attempting to close the main window!
Did you pay a fee on these transactions?
You will see this message when your own Bitcoin node fails to relay the transaction Armory broadcasted back to it.
This is the Armory broadcast process:
1) Armory is connected to your local Bitcoin node as a peer.
2) You create a tx with Armory. Armory broadcasts it to your local node (and only your local node) through the P2P Bitcoin protocol. As far as your node is concerned, it received a tx from another node.
3) Armory, still through the P2P protocol, asks your node for that transaction it just broadcasted by hash.
4.a) If your node returns that tx, Armory considers the tx has been broadcasted succesfully and will display it in your GUI.
4.b) If your node fails to return that tx, Armory will keep polling your local node for that tx for a few seconds. If it runs out of attempts, it will prompt you with that message, which summarizes what I just explained: Armory tried to broadcast the tx but failed to verify the broadcast was successful.
However if any of the steps fail prior to 4) fails, you will get the same message.
The more significant marker of a failure a step 4) is getting a message from Armory that it lost its connection to your local node after you get the failure message. Baring that, the issue is somewhere between 1) and 3).
A failure at step 4) indicates the tx is invalid in some way, a failure somewhere else means something is wrong with your setup.
This is the Armory broadcast process:
1) Armory is connected to your local Bitcoin node as a peer.
2) You create a tx with Armory. Armory broadcasts it to your local node (and only your local node) through the P2P Bitcoin protocol. As far as your node is concerned, it received a tx from another node.
3) Armory, still through the P2P protocol, asks your node for that transaction it just broadcasted by hash.
4.a) If your node returns that tx, Armory considers the tx has been broadcasted succesfully and will display it in your GUI.
4.b) If your node fails to return that tx, Armory will keep polling your local node for that tx for a few seconds. If it runs out of attempts, it will prompt you with that message, which summarizes what I just explained: Armory tried to broadcast the tx but failed to verify the broadcast was successful.
However if any of the steps fail prior to 4) fails, you will get the same message.
The more significant marker of a failure a step 4) is getting a message from Armory that it lost its connection to your local node after you get the failure message. Baring that, the issue is somewhere between 1) and 3).
A failure at step 4) indicates the tx is invalid in some way, a failure somewhere else means something is wrong with your setup.
The only changes I have made was moving the monster DB to a 120GB SSD drive. Using the special startup switch satoshi-datadir. I just ran Armory, loads up just fine. Indicates "online". If I click "Check for Updates" tells me announcements are up-to-date, but still indicates 11.1 core. This is me loading up Armory, letting it go online and sync, trying to check for an update then shutting down. When I get some food in me I'll look into BTC weirdness. I'll gather up the BTC addresses in the log for the past few days, since I only made 2 transmits and check them against the blockchain. My math is telling me 4 BTC vanished, but I have to look further.
Code:
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1076 - C++ block utilities loaded successfully
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1186 -
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1187 -
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1188 -
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1189 - ************************************************************
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1190 - Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe --satoshi-datadir=J:\Armory
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1191 - ************************************************************
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1192 - Loading Armory Engine:
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1193 - Armory Version : 0.93.3
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1194 - Armory Build: : e59e10d38c
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1195 - PyBtcWallet Version : 1.35
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1196 - Detected Operating system: Windows
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1197 - OS Variant : 8-6.2.9200--Multiprocessor Free
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1198 - User home-directory : C:\Users\ME\AppData\Roaming
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1199 - Satoshi BTC directory : J:\Armory
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1200 - Armory home dir : C:\Users\ME\AppData\Roaming\Armory\
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1201 - Detected System Specs :
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1202 - Total Available RAM : 63.90 GB
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1203 - CPU ID string : Intel64 Family 6 Model 63 Stepping 2, GenuineIntel
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1204 - Number of CPU cores : 12 cores
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1205 - System is 64-bit : True
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1206 - Preferred Encoding : cp1252
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1207 - Machine Arch : amd64
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1208 - Available HDD (ARM) : 226 GB
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1209 - Available HDD (BTC) : 5 GB
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1210 -
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1211 - Network Name: Main Network
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1212 - Satoshi Port: 8333
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1213 - Do wlt check: True
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1214 - Named options/arguments to armoryengine.py:
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - nettimeout : 2
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - rescan : False
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - ignoreAllZC : False
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - enableSupernode : False
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - disableModules : False
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - port : None
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - interport : 8223
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - skipStatsReport : False
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - forceWalletCheck: False
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - rebuild : False
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - datadir : DEFAULT
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - clearMempool : False
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - offline : False
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - coverageOutputDir: None
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - armoryDBDir : DEFAULT
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - satoshiPort : DEFAULT
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - useTorSettings : False
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - netlog : False
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - keypool : 100
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - coverageInclude : None
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - forceOnline : False
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - skipAnnounceCheck: False
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - redownload : False
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - multisigFile : DEFAULT
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - disableTorrent : False
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - testAnnounceCode: False
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - mtdebug : False
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - logDisable : False
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - settingsPath : C:\Users\ME\AppData\Roaming\Armory\ArmorySettings.txt
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - verbosity : None
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - doDebug : False
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - enableDetSign : True
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - testnet : False
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - rpcport : DEFAULT
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - satoshiHome : J:\Armory
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - satoshiRpcport : DEFAULT
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - logFile : C:\Users\ME\AppData\Roaming\Armory\ArmoryQt.exe.log.txt
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - disableConfPermis: False
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1217 - Other arguments:
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1220 - ************************************************************
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1620 - C++ block utilities loaded successfully
2016-01-18 19:02 (INFO) -- BDM.pyc:418 - Using the asynchronous/multi-threaded BlockDataManager.
2016-01-18 19:02 (INFO) -- BDM.pyc:419 - Blockchain operations will happen in the background.
2016-01-18 19:02 (INFO) -- BDM.pyc:420 - Devs: check TheBDM.getState() before asking for data.
2016-01-18 19:02 (INFO) -- BDM.pyc:421 - Registering addresses during rescans will queue them for
2016-01-18 19:02 (INFO) -- BDM.pyc:422 - inclusion after the current scan is completed.
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:3531 - Using settings file: C:\Users\ME\AppData\Roaming\Armory\ArmorySettings.txt
2016-01-18 19:02 (INFO) -- announcefetch.pyc:95 - Reading files in fetcher directory:
2016-01-18 19:02 (INFO) -- announcefetch.pyc:104 - announce : 96f5d5f4253bac5528333c4fef3afd5fa0e931816bfd4c4c8b43d85cee002bb9
2016-01-18 19:02 (INFO) -- announcefetch.pyc:104 - bootstrap : b62c08932668ce162d51226135940724e90f4c71704ac936f74cc153b34cc251
2016-01-18 19:02 (INFO) -- announcefetch.pyc:104 - changelog : 1c01304b876de3e75672c8b13d9a00157556b86612afac1c88ffc40a8d7dfb90
2016-01-18 19:02 (INFO) -- announcefetch.pyc:104 - downloads : 28efee8047ee0a2c26ac9f785d93566fb5a45c20a794da6f972aa48db50ec35a
2016-01-18 19:02 (INFO) -- announcefetch.pyc:104 - notify : 87fa1adcd555be83a71b4f5935a6d4f85178ccbf5043531fdd71432b57d127ca
2016-01-18 19:02 (INFO) -- announcefetch.pyc:271 - Fetching: https://bitcoinarmory.com/announce.txt?osvar=8&os=win&ver=0.93.3&id=b00fe8a1
2016-01-18 19:02 (INFO) -- ArmoryQt.py:2736 - loadWalletsAndSettings
2016-01-18 19:02 (INFO) -- ArmoryQt.py:2790 - Loading wallets...
2016-01-18 19:02 (INFO) -- ArmoryQt.py:2849 - Number of wallets read in: 1
2016-01-18 19:02 (INFO) -- ArmoryQt.py:2854 - Wallet (26X1pw3LB): "Primary Wallet Armory " (Encrypted)
2016-01-18 19:02 (INFO) -- ArmoryQt.py:2863 - Loading Multisig Lockboxes
2016-01-18 19:02 (INFO) -- ArmoryQt.py:2298 - Setting up networking...
2016-01-18 19:02 (INFO) -- ArmoryQt.py:2327 - Internet status: 0
2016-01-18 19:02 (INFO) -- ArmoryQt.py:2442 - startBitcoindIfNecessary
2016-01-18 19:02 (INFO) -- ArmoryQt.py:2491 - setSatoshiPaths
2016-01-18 19:02 (INFO) -- SDM.pyc:282 - Total size of files in J:\Armory\blocks is 52.5 GB
2016-01-18 19:02 (INFO) -- SDM.pyc:415 - Found Bitcoin-Qt link on desktop: C:\Program Files (x86)\Armory
2016-01-18 19:02 (INFO) -- SDM.pyc:415 - Found Bitcoin-Qt link on desktop: C:\Program Files\Bitcoin
2016-01-18 19:02 (INFO) -- SDM.pyc:321 - Found bitcoind in the following places:
2016-01-18 19:02 (INFO) -- SDM.pyc:323 - C:\Program Files\Bitcoin\daemon\bitcoind.exe
2016-01-18 19:02 (INFO) -- SDM.pyc:323 - C:\Program Files\Bitcoin\daemon\bitcoind.exe
2016-01-18 19:02 (INFO) -- SDM.pyc:325 - Using: C:\Program Files\Bitcoin\daemon\bitcoind.exe
2016-01-18 19:02 (INFO) -- SDM.pyc:496 - Reading bitcoin.conf file
2016-01-18 19:02 (INFO) -- SDM.pyc:515 - Setting permissions on bitcoin.conf
2016-01-18 19:02 (INFO) -- SDM.pyc:524 - Setting permissions on bitcoin.conf
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:600 - Executing popen: [u'icacls', u'J:\\Armory\\bitcoin.conf', u'/inheritance:r', u'/grant:r', u'ME:F']
2016-01-18 19:02 (INFO) -- SDM.pyc:530 - icacls returned:
2016-01-18 19:02 (INFO) -- SDM.pyc:597 - Called startBitcoind
2016-01-18 19:02 (INFO) -- SDM.pyc:282 - Total size of files in J:\Armory\blocks is 52.5 GB
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:600 - Executing popen: ['C:\\Program Files\\Bitcoin\\daemon\\bitcoind.exe', u'-datadir=J:\\Armory']
2016-01-18 19:02 (INFO) -- SDM.pyc:669 - PID of bitcoind: 4324
2016-01-18 19:02 (INFO) -- SDM.pyc:670 - PID of armory: 9692
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:600 - Executing popen: ['.\\guardian.exe', '9692', '4324']
2016-01-18 19:02 (INFO) -- SDM.pyc:848 - Creating proxy in SDM: host=127.0.0.1, port=8332
2016-01-18 19:02 (INFO) -- ArmoryQt.py:1514 - setupUriRegistration
2016-01-18 19:02 (INFO) -- ArmoryQt.py:1582 - Armory already registered for current user. Done!
2016-01-18 19:02 (INFO) -- ArmoryQt.py:664 - Usermode: Expert
2016-01-18 19:02 (INFO) -- ArmoryQt.py:1810 - Changing usermode:
2016-01-18 19:02 (INFO) -- ArmoryQt.py:1811 - From: Expert
2016-01-18 19:02 (INFO) -- ArmoryQt.py:1819 - To: Expert
2016-01-18 19:02 (ERROR) -- announcefetch.pyc:283 - Specified URL was inaccessible
2016-01-18 19:02 (ERROR) -- announcefetch.pyc:284 - Tried: https://bitcoinarmory.com/announce.txt?osvar=8&os=win&ver=0.93.3&id=b00fe8a1
2016-01-18 19:02 (INFO) -- announcefetch.pyc:271 - Fetching: https://s3.amazonaws.com/bitcoinarmory-media/announce.txt
2016-01-18 19:02 (INFO) -- ArmoryQt.py:5887 - Dashboard switched to auto-InitSync
2016-01-18 19:02 (INFO) -- ArmoryQt.py:2525 - loadBlockchainIfNecessary
2016-01-18 19:02 (INFO) -- ArmoryQt.py:2546 - Setting netmode: 1
2016-01-18 19:02 (INFO) -- ArmoryQt.py:6010 - Dashboard switched to "Scanning" mode
2016-01-18 19:02 (INFO) -- Networking.pyc:65 - Connection initiated. Start handshake
2016-01-18 19:02 (INFO) -- ArmoryQt.py:6010 - Dashboard switched to "Scanning" mode
2016-01-18 19:02 (INFO) -- Networking.pyc:156 - Received version message from peer:
2016-01-18 19:02 (INFO) -- Networking.pyc:157 - Version: 70002
2016-01-18 19:02 (INFO) -- Networking.pyc:158 - SubVersion: /Satoshi:0.11.1/
2016-01-18 19:02 (INFO) -- Networking.pyc:159 - TimeStamp: 1453161769
2016-01-18 19:02 (INFO) -- Networking.pyc:160 - StartHeight: 393937
2016-01-18 19:02 (INFO) -- Networking.pyc:350 - Handshake finished, connection open!
2016-01-18 19:02 (INFO) -- ArmoryQt.py:3148 - Current block number: 393937
2016-01-18 19:03 (INFO) -- ArmoryQt.py:6238 - New Block! : 393938
2016-01-18 19:03 (INFO) -- ArmoryQt.py:6246 - Current block number: 393938
2016-01-18 19:03 (INFO) -- ArmoryQt.py:6238 - New Block! : 393939
2016-01-18 19:03 (INFO) -- ArmoryQt.py:6246 - Current block number: 393939
2016-01-18 19:03 (INFO) -- Networking.pyc:215 - Received new block. 000000000000000002914d619f82f9becd9cdbca341cd4ddb9ab2f4f0e4efc9a
2016-01-18 19:03 (INFO) -- ArmoryQt.py:6238 - New Block! : 393940
2016-01-18 19:03 (INFO) -- ArmoryQt.py:6246 - Current block number: 393940
2016-01-18 19:03 (INFO) -- Networking.pyc:215 - Received new block. 0000000000000000074078c4a5e95c260c00ed3dd55ee43268b659b69c258187
2016-01-18 19:03 (INFO) -- ArmoryQt.py:6238 - New Block! : 393941
2016-01-18 19:03 (INFO) -- ArmoryQt.py:6246 - Current block number: 393941
2016-01-18 19:04 (INFO) -- announcefetch.pyc:389 - Forcing announce data fetch
2016-01-18 19:04 (INFO) -- announcefetch.pyc:271 - Fetching: https://bitcoinarmory.com/announce.txt
2016-01-18 19:04 (ERROR) -- announcefetch.pyc:283 - Specified URL was inaccessible
2016-01-18 19:04 (ERROR) -- announcefetch.pyc:284 - Tried: https://bitcoinarmory.com/announce.txt
2016-01-18 19:04 (INFO) -- announcefetch.pyc:271 - Fetching: https://s3.amazonaws.com/bitcoinarmory-media/announce.txt
2016-01-18 19:04 (INFO) -- ArmoryQt.py:6763 - BDM is safe for clean shutdown
2016-01-18 19:04 (INFO) -- SDM.pyc:683 - Called stopBitcoind
2016-01-18 19:04 (ERROR) -- Networking.pyc:359 - ***Connection to Satoshi client LOST! Attempting to reconnect...
2016-01-18 19:04 (INFO) -- ArmoryQt.py:6805 - Attempting to close the main window!
You will see this message when your own Bitcoin node fails to relay the transaction Armory broadcasted back to it.
This is the Armory broadcast process:
1) Armory is connected to your local Bitcoin node as a peer.
2) You create a tx with Armory. Armory broadcasts it to your local node (and only your local node) through the P2P Bitcoin protocol. As far as your node is concerned, it received a tx from another node.
3) Armory, still through the P2P protocol, asks your node for that transaction it just broadcasted by hash.
4.a) If your node returns that tx, Armory considers the tx has been broadcasted succesfully and will display it in your GUI.
4.b) If your node fails to return that tx, Armory will keep polling your local node for that tx for a few seconds. If it runs out of attempts, it will prompt you with that message, which summarizes what I just explained: Armory tried to broadcast the tx but failed to verify the broadcast was successful.
However if any of the steps fail prior to 4) fails, you will get the same message.
The more significant marker of a failure a step 4) is getting a message from Armory that it lost its connection to your local node after you get the failure message. Baring that, the issue is somewhere between 1) and 3).
A failure at step 4) indicates the tx is invalid in some way, a failure somewhere else means something is wrong with your setup.
This is the Armory broadcast process:
1) Armory is connected to your local Bitcoin node as a peer.
2) You create a tx with Armory. Armory broadcasts it to your local node (and only your local node) through the P2P Bitcoin protocol. As far as your node is concerned, it received a tx from another node.
3) Armory, still through the P2P protocol, asks your node for that transaction it just broadcasted by hash.
4.a) If your node returns that tx, Armory considers the tx has been broadcasted succesfully and will display it in your GUI.
4.b) If your node fails to return that tx, Armory will keep polling your local node for that tx for a few seconds. If it runs out of attempts, it will prompt you with that message, which summarizes what I just explained: Armory tried to broadcast the tx but failed to verify the broadcast was successful.
However if any of the steps fail prior to 4) fails, you will get the same message.
The more significant marker of a failure a step 4) is getting a message from Armory that it lost its connection to your local node after you get the failure message. Baring that, the issue is somewhere between 1) and 3).
A failure at step 4) indicates the tx is invalid in some way, a failure somewhere else means something is wrong with your setup.
Screenshot of the error? Can you post the logs?
I didn't want to initially randomly post the logs due to security issues. Here is what I have so far. Looks like Armory is not letting me know there is a new version of core (11.2) out there. Still says 11.1 on the dashboard. I have a small balance in my wallet, so I may try to send that out. Before I post more information I want to make sure my pending transaction confirms. If I search the log for "Bitcoins Sent" or "ArmoryQt.py:6662" there isn't even an entry for the coins I sent yesterday but they are in my other wallet. I just emptied out my Armory wallet and will wait for more confirmations. Something doesn't look right. Obvious errors about notifying me about the new core version isn't working.
Line 13767: 2016-01-18 17:47 (ERROR) -- announcefetch.pyc:283 - Specified URL was inaccessible
Line 13768: 2016-01-18 17:47 (ERROR) -- announcefetch.pyc:284 - Tried: https://bitcoinarmory.com/announce.txt?osvar=8&os=win&ver=0.93.3&id=b00fe8a1
Line 13807: 2016-01-18 18:17 (ERROR) -- announcefetch.pyc:283 - Specified URL was inaccessible
Line 13808: 2016-01-18 18:17 (ERROR) -- announcefetch.pyc:284 - Tried: https://bitcoinarmory.com/announce.txt
Line 13820: 2016-01-18 18:22 (ERROR) -- announcefetch.pyc:283 - Specified URL was inaccessible
Line 13821: 2016-01-18 18:22 (ERROR) -- announcefetch.pyc:284 - Tried: https://bitcoinarmory.com/announce.txt
Screenshot of the error? Can you post the logs?
I'm updated with the latest core and Armory version. Armory indicated "online" and I tried to send some Bitcoin to an address and Armory came up with a snag screen saying it could not send the coin and gave me the transaction URL to check the blockchain. Took me 5 attempts and one transaction finally made it. Anyone else see this? I'm asking before I start dumping time into spending time on checking logs.
Jump to: