Latest posts of: sabretache

Show Posts
Pages: [1]

Bitcoin / Armory / Re: Transaction status "Not in blockchain yet"

on: September 11, 2016, 04:04:23 PM

Quote from: achow101 on September 10, 2016, 09:40:24 PM For some reason your Armory has not been in sync. It is stuck at block 425773. To fix this, I think you need to rebuild and rescan the databases. Go the Help > Rebuild and Rescan Databases. Click yes then restart Armory. Thanks for that achow101. Job done. Amazing how easy it is to miss a solution when it is staring you in the face eh? Thanks for the additional tips too - and to others for progressing this

Bitcoin / Armory / Re: Transaction status "Not in blockchain yet"

on: September 10, 2016, 08:24:57 PM

I've had to trim the file to get under the 512K limit for guest users but there a lot either side of the offending transaction time. http://pastebin.com/hkMVzj0t FFI. I have been leaving the Bitcoin core GUI running constantly to keep the db utd and provide a full network node, then shutting it down before periodically loading Armory to check for incoming payments and/or send payments (I'm nervous about leaving a wallet with upwards of 50 BTC sitting online all the time). On occasion I have forgotten to close the BTC GUI before loading Armory and thus been prompted to close it first. Also, I have suffered the odd 'unexpected closure' of the BTC GUI which remain unsolved. When that has happened it has left bitcoind running and I've had to shut it down with the OS terminal before starting Armory again.

Bitcoin / Armory / Re: Transaction status "Not in blockchain yet"

on: September 10, 2016, 06:54:14 AM

Quote from: achow101 on September 09, 2016, 06:35:43 PM Quote from: sabretache on September 09, 2016, 06:29:01 PM Here is the portion of the log file that seems appropriate - ie the lines following successful loading of Armory, thru sending the transaction, to closing Armory. Please show the entire log, or at least the portion containing the run where this happened. There may be some other issue reported in the log that you did not see. The portion already posted IS 'the run where this happened'. Trying to post the runs either side of that already posted results in an 'allowed characters exceeded' message. My suspicion is that the bitcoin core database is compromised in some way but I don't relish the prospect of downloading the whole damn thing yet again. If Goatpig and/or other techie-competent folk here agree, then might it be possible to delete that portion of the database prior to 20 August (the offending transaction date) and simply download the from there? If so How?

Bitcoin / Armory / Re: Transaction status "Not in blockchain yet"

on: September 09, 2016, 06:29:01 PM

Quote from: goatpig on September 07, 2016, 09:38:36 AM

Let's see some log files first.

I have done 2 x restores from a paper backup. The first using the repair option; the second using the overwrite option. In both cases the wallet restored OK but that transaction remains greyed out with zero confirmations, per original message.

Here is the portion of the log file that seems appropriate - ie the lines following successful loading of Armory, thru sending the transaction, to closing Armory.

Code:

2016-08-20 22:34 (INFO) -- Networking.py:341 - Handshake finished, connection open!
2016-08-20 22:34 (INFO) -- ArmoryQt.py:3121 - Current block number: 425773
2016-08-20 22:36 (INFO) -- TxFrames.py:720 - Change address behavior: NewAddr
2016-08-20 22:36 (INFO) -- (PPRINT from /usr/lib/armory/ArmoryQt.py:3705)

  01000000 01d8dedf fad4fa85 1514c440 5c0ee242 fdbb9726 e5d64c5b bc4f3ae2 
  142bc759 8d010000 008a4730 44022042 2fd70bab 20fcf753 3b995225 3bd7ef55 
  5a25cc11 d90289ff d075b010 40a21202 20689c17 75e26496 beaadcf4 c320aaf4 
  84dad0d7 1b4af28c 227c2154 98e3f877 ff014104 3edaf684 b36adaca b3c78b68 
  315707a4 74fa2931 98cda94c a2d617c6 d48b05ad e1d829da 22f925cd eccc1456 
  f48a930a 1900e212 0d34c274 5c8abd5b d8bcf841 ffffffff 0298b1ef 02000000 
  001976a9 145dba83 296f3395 06fb208d e1d14f70 7ebbc59f ac88ac3e caaf1a00 
  00000019 76a914f6 91e90e08 1db7a626 7ee19d0f d63b4f56 565bf288 ac000000 
  00 
2016-08-20 22:36 (INFO) -- (PPRINT from /usr/lib/armory/ArmoryQt.py:3706)
Transaction:
   TxHash:    1ed12b046d7fe0edde347faf24852b9be38d60e4637af5e3b179d70094f11b57 (BE)
   Version:   1
   nInputs:   1
   nOutputs:  2
   LockTime:  0
   Inputs: 
      PyTxIn:
         PrevTxHash: 8d59c72b14e23a4fbc5b4cd6e52697bbfd42e20e5c40c4141585fad4fadfded8 (BE)
         TxOutIndex: 1
         Script:     (4730440220422fd70bab20fcf7533b9952253bd7ef555a25cc11d90289ffd075)
         Sender:     1PUk2DnvQrQrZAqqAMvswqk3rTCkHET6KK
         Seq:        4294967295
   Outputs: 
      TxOut:
         Value:   49263000 (0.49263)
         Script:  OP_DUP OP_HASH160 (19YbGwqsuAYyEByPo3vvs3Kr3XJcvwH9DN) OP_EQUALVERIFY OP_CHECKSIG
      TxOut:
         Value:   447728190 (4.4772819)
         Script:  OP_DUP OP_HASH160 (1PUk2DnvQrQrZAqqAMvswqk3rTCkHET6KK) OP_EQUALVERIFY OP_CHECKSIG

2016-08-20 22:36 (INFO) -- ArmoryQt.py:3708 - Sending Tx, 571bf19400d779b1e3f57a63e4608de39b2b8524af7f34deede07f6d042bd11e
2016-08-20 22:36 (INFO) -- Networking.py:279 - sendTx called...
2016-08-20 22:36 (INFO) -- ArmoryQt.py:3710 - Transaction sent to Satoshi client...!
2016-08-20 22:36 (INFO) -- ArmoryQt.py:6584 - Bitcoins Sent!
Amount:  0.49314684 BTC
From:    Wallet "Main" (9WS2gufD)
To:      19YbGwqsuAYyEByPo3vvs3Kr3XJcvwH9DN
2016-08-20 22:37 (INFO) -- ArmoryQt.py:6685 - BDM is safe for clean shutdown
2016-08-20 22:37 (INFO) -- SDM.py:683 - Called stopBitcoind
2016-08-20 22:37 (ERROR) -- Networking.py:350 - ***Connection to Satoshi client LOST!  Attempting to reconnect...
2016-08-20 22:37 (INFO) -- ArmoryQt.py:6727 - Attempting to close the main window!

Bitcoin / Armory / Transaction status "Not in blockchain yet"

on: September 07, 2016, 08:11:06 AM

On 20 August I sent a small btc amount to another (Electrum) wallet of mine. The transaction arrived OK and was reported by Electrum as confirmed within an hour. It can be viewed on the Blockchain at: https://blockchain.info/tx/1ed12b046d7fe0edde347faf24852b9be38d60e4637af5e3b179d70094f11b57 To date the transaction is still reported by Armory as "Not in the blockchain yet" and appears in light grey with zero confirmations in the transactions list. However, the link to the blockchain entry from Armory works OK and the reported wallet balance is correct.. Can someone suggest what has gone wrong here - and how to fix it. FI. Using 0.94.1 on Ubuntu 16.04 LTS - also I'm light on techie skills. Thanks in advance.

Bitcoin / Armory / Re: Armory 0.94.1 is out

on: April 22, 2016, 06:16:17 PM

Another daft question: How do I get the Armory icon to show on the launcher? - that's using the standard Ubuntu Gnome GUI At present the launcher shows a grey '?'. Otherwise everything working fine.

Bitcoin / Armory / Re: Armory 0.94.1 is out

on: April 22, 2016, 02:11:20 PM

Quote from: goatpig on April 22, 2016, 10:54:07 AM You can't use the same DB as 0.93 for 0.94. Point to another folder using the --dbdir command line argument Thanks gp. I renamed the 93.1 db folder then created a new one with standard name. All purring along fine now. If all remains well, I'll delete the old one in a day or two and get back 60+Gb of space

Bitcoin / Armory / Re: Armory 0.94.1 is out

on: April 22, 2016, 10:38:16 AM

I've been using Armory for a couple years now. I'm 'techie-light' so please bare with me & apologies if this has already been answered.

System: OS - Ubuntu 15.1 15Gb real memory 15Gb virtual memory

Initially I installed 0.94.1 on top of 0.93.1 using the Git clone + make + make install instructions.

That resulted in the Armory GUI showing a successful Wallet consistency check + successful Bitcoin Engine init; then the GUI turned grey and I got a program not responding message requiring a manual close which left Bitcoind running but no Armory process running. I then uninstalled Armory leaving the settings as was and re-installed.

Result: As above except that, instead of the GUI freezing, it simply disappears.

All looks fine in the log (to me anyway - ie no errors) until the last few lines as follows:

Code:

2016-04-22 10:44 (INFO) -- ArmoryQt.py:5812 - Dashboard switched to auto-InitSync
2016-04-22 10:44 (INFO) -- ArmoryQt.py:2498 - loadBlockchainIfNecessary
2016-04-22 10:44 (ERROR) -- ArmoryQt.py:1336 - 4 attempts to load blockchain failed.  Remove mempool.bin.
2016-04-22 10:44 (ERROR) -- ArmoryQt.py:1341 - File mempool.bin does not exist. Nothing deleted.
2016-04-22 10:44 (INFO) -- ArmoryQt.py:2519 - Setting netmode: 1
2016-04-22 10:44 (INFO) -- ArmoryQt.py:5935 - Dashboard switched to "Scanning" mode
2016-04-22 10:44 (INFO) -- Networking.py:64 - Connection initiated.  Start handshake
2016-04-22 10:44 (INFO) -- ArmoryQt.py:5935 - Dashboard switched to "Scanning" mode
2016-04-22 10:44 (INFO) -- Networking.py:155 - Received version message from peer:
2016-04-22 10:44 (INFO) -- Networking.py:156 -    Version:     70012
2016-04-22 10:44 (INFO) -- Networking.py:157 -    SubVersion:  /Satoshi:0.12.0/
2016-04-22 10:44 (INFO) -- Networking.py:158 -    TimeStamp:   1461318297
2016-04-22 10:44 (INFO) -- Networking.py:159 -    StartHeight: 408421
2016-04-22 10:44 (INFO) -- Networking.py:341 - Handshake finished, connection open!

Any pointers much appreciated

Other / Beginners & Help / Bitcoin prospects

on: June 22, 2011, 07:03:26 PM

As a relative newcomer to Bitcoin, having completed just a dozen or so transactions through a couple of exchanges plus a couple of actual purchases, I have to say I wish it success. I've read through a couple of threads here about the biggest challenges to seriously widespread take-up that it faces and it has all helped consolidate my technical understanding. However, I do not recall seeing any discussion about what seems to me to be one of its biggest challenges/threats - in fact arguably THE biggest of all - namely being PERCEIVED as a serious threat to the existing currency regime by those whose wealth and power is defined by it. Short of cataclysmic breakdown of the present Dollar-defined fiat system, the traded volumes of Bitcoin are likely to remain so minute by comparison, that it will always be a simple - almost trivial - undertaking for the Central Banking cartel (through their existing primary Broker/Dealer network) to engineer vast Bitcoin/Dollar (or whatever) volatility sufficient to forever cripple it as both a reasonably predictable store of value and reliable medium of goods exchange. If it really is seen as a threat, then that is probably exactly what will be done. IOW, so long as it remains on the margins, it may be tolerated; but if deemed a serious threat then, one way or another, it will be dealt with - or so it seems to me anyway.

Other / Beginners & Help / Re: Introduce yourself :)

on: June 13, 2011, 12:21:54 PM

UK based. Ready to support any viable-looking initiative that offers the prospect of weakening the stranglehold of the banking cartels on the creation and control of the means of exchange.

Pages: [1]