Topic: Armory does not appear to be scanning chain (Read 3740 times)

Glad it worked!   I actually do have someone helping me to create better documentation.  The first thing will be an illustrated tutorial for offline transactions, with screenshots.  Then we're going to try to add better general documentation.  For now, if you're curious, you can run with --help to see a list of all the command line options.

Hi etotheipi,

Thx, It worked now!

Armory is online, connected (229988 Blocks) and shows the right balance.

I was looking everywhere to find this bit of info (this forum, github, your bitcoinarmory.com, google,..) but didnt find anything (yes there is something in this thread but you really have to look closely on page XX to find it).

I guess it would help a lot of users if you could provide documentation for your client that also states those commands, such as "--satoshi-datadir=" and similar, also giving step by step advice on how to correctly apply them.

Thx for your quick response!

Cheers,
Spekulatius

Thanks for the detailed report.  I appreciate it!

You didn't mention starting Armory with "--satoshi-datadir=D:\Programme\Bitcoin\Blockchain".  Have you done that?  If not, that would explain it ... it's probably reading whatever super-old blockfiles you have in your C:\Users\username\AppData\Roaming\Bitcoin directory, which is why it went online but didn't show any transactions.

The zero-confirmation tx showed up because Bitocin-Qt passed it on to Armory, which recognized it as being part of the wallet.  But it stayed at zero conf, because Armory never saw it get into a block.  Or it disappeared between restarts, because Armory can't seem to keep that data persistent between loads in Windows...

I have similar issues as OP:

My system:
Win 7 64bit
3 GB RAM (2,87 GB usable)
Intel Pentium Dual CPU T3400 @ 2.16 GHz and 2.17 GHz
Bitcoin v0.8.0-beta (Satoshi Client)
Armory 0.87.2-beta

Other:
I store the blockchain files of my Satoshi Client in a non-standard directory using the "-datadir=D:\Programme\Bitcoin\Blockchain" command in the bitcoin-qt.exe shortcut. This way the "Target"-field in the shortcut's properties looks like this:
"D:\Programme\Bitcoin\bitcoin-qt.exe -datadir=D:\Programme\Bitcoin\Blockchain"
The "Execute in:"-field looks like this: "D:\Programme\Bitcoin"
It works for the Satoshi Client but I guess my Armory client cant find the blockchain files on my hard drive and thus doesnt synch with the network. Im posting because I couldnt find any advice on how to tell it where to look, so Im stuck with "Connected (0 Blocks)".

My story:
I installed the Armory Offline Wallet on a separate Linux Laptop. Imported a priv key thats loaded with some 0.001 BTC.
Made a watch-only copy and saved the wallet to USB stick.
Then installed the Armory client on my other laptop (Windows 7) that also runs the Bitcoin Client and imported the watch-only wallet from the USB stick. Closed it down after the import worked alright and waited for the Bitcoin Client to synch with the blockchain. Rebooted Computer, then first started the Satoshi Client, waited for the green check mark, then started the Armory and waited for the correct balance to show in the Armory. It never showed up. It says in the dash board: "Armory is online!" but shows in the bottom right corner of the window: "Connected (0 Blocks)". It doesnt seem to synch with the blockchain.
Then I sent another 0.01 BTC to the Address from the imported watch-only wallet and surprise! It showed up, hence with 0 confirmations.
Now I rebooted and everything but the final balance is again displayed as 0.00 BTC. Blockchain.info shows 23 confirmations though.

How can I get my online wallet to synch with the blockchain!?
Thx

Ok, I deleted all files except for blk00003.dat-blk00050.dat and compiled Armory from managesatoshi branch and after reindex, Armory now sees all transactions. But settings can`t be accessed. See here
https://bitcointalksearch.org/topic/m.1756505

I did that already when I said I reindex database. Now I deleted blk00052.dat and blk00051.dat, started bitcoin-qt, it told me to rebuild database, which I did. Bitcoin-qt now shows that it is completely synced...Armory thinks that it is only 228672 blocks

I`ll dig more, please give ideas if you have such, I really don`t want to redownload all blockchain...

It looks to me like a corrupted blockchain file.  Most likely, block 229673 in your blockfiles is corrupt, and thus Armory doesn't see any blocks beyond that, because they all trace back to an orphan block.  I don't know if you can just delete blk00052.dat and restart bitcoind and it will figure out what happened...?  If you don't mind redownloading the blockchain, you may have nothing to lose... (just delete everything in the .bitcoin directory except wallet.dat and let bitcoind redownload everything.  Armory will work after that, I promise

Yes, my`n too. But here what I have then
And many lines like that, which I suppose represent missing blocks

Somehow Armory isn't reading past Block 229672.  Can you do something for me.  When you start Armory and it starts scanning, you'll see a bunch of lines like this:


On my system, the last one is blk00052.dat. 

Can you check which is the last one listed there, and then check your /home/user/.bitcoin/blocks directory and make sure you have the same number.  It's almost like it's not seeing the last blockfile...

No, I haven`t changed anything. Checked with 'ps aux', Armory and bitcoind get the same path in --datadir and --satoshi-datadir. I also start bitcoind with -reindex - it didn`t change anything. I killed bitcoind while Armory is run, then started, that is in the log:

@steamboat

Can you PM me the full log file?  I can't see the context I need from that snippet.  It's obviously abnormal behavior, but I need more info.

Update:

So after installing and running. Armory sync's 100% with the network, but scanning transaction history gets stuck at 99%. The bottom says Connected (0 blocks), and the logs is a bunch of stuff like this:


2013-04-04 20:16 (INFO) -- armoryengine.pyc:9963 - Received version message from peer:
2013-04-04 20:16 (INFO) -- armoryengine.pyc:9964 -    Version:     70001
2013-04-04 20:16 (INFO) -- armoryengine.pyc:9965 -    SubVersion:  /Satoshi:0.8.1/
2013-04-04 20:16 (INFO) -- armoryengine.pyc:9966 -    TimeStamp:   1365121007
2013-04-04 20:16 (INFO) -- armoryengine.pyc:9967 -    StartHeight: 229717
2013-04-04 20:16 (INFO) -- armoryengine.pyc:10124 - Handshake finished, connection open!
2013-04-04 20:20 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode
2013-04-04 20:20 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets
2013-04-04 20:20 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning"
2013-04-04 20:23 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode
2013-04-04 20:23 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets
2013-04-04 20:23 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning"
2013-04-04 20:23 (INFO) -- armoryengine.pyc:9998 - New block broadcast received
2013-04-04 20:23 (INFO) -- armoryengine.pyc:9998 - New block broadcast received
2013-04-04 20:23 (INFO) -- armoryengine.pyc:9998 - New block broadcast received
2013-04-04 20:23 (INFO) -- armoryengine.pyc:9998 - New block broadcast received
2013-04-04 20:23 (INFO) -- armoryengine.pyc:9998 - New block broadcast received
2013-04-04 20:23 (INFO) -- armoryengine.pyc:9998 - New block broadcast received
2013-04-04 20:23 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode
2013-04-04 20:23 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets
2013-04-04 20:23 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning"
2013-04-04 20:26 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode
2013-04-04 20:26 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets
2013-04-04 20:26 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning"
2013-04-04 20:26 (INFO) -- armoryengine.pyc:9998 - New block broadcast received
2013-04-04 20:26 (INFO) -- armoryengine.pyc:9998 - New block broadcast received
2013-04-04 20:26 (INFO) -- armoryengine.pyc:9998 - New block broadcast received
2013-04-04 20:26 (INFO) -- armoryengine.pyc:9998 - New block broadcast received
2013-04-04 20:26 (INFO) -- armoryengine.pyc:9998 - New block broadcast received
2013-04-04 20:26 (INFO) -- armoryengine.pyc:9998 - New block broadcast received
2013-04-04 20:37 (INFO) -- armoryengine.pyc:9998 - New block broadcast received
2013-04-04 20:37 (INFO) -- armoryengine.pyc:9998 - New block broadcast received
2013-04-04 20:37 (INFO) -- armoryengine.pyc:9998 - New block broadcast received
2013-04-04 20:37 (INFO) -- armoryengine.pyc:9998 - New block broadcast received
2013-04-04 20:37 (INFO) -- armoryengine.pyc:9998 - New block broadcast received
2013-04-04 20:37 (INFO) -- armoryengine.pyc:9998 - New block broadcast received
2013-04-04 20:44 (INFO) -- armoryengine.pyc:9998 - New block broadcast received
2013-04-04 20:44 (INFO) -- armoryengine.pyc:9998 - New block broadcast received
2013-04-04 20:44 (INFO) -- armoryengine.pyc:9998 - New block broadcast received
2013-04-04 20:44 (INFO) -- armoryengine.pyc:9998 - New block broadcast received
2013-04-04 20:44 (INFO) -- armoryengine.pyc:9998 - New block broadcast received
2013-04-04 20:44 (INFO) -- armoryengine.pyc:9998 - New block broadcast received
2013-04-04 20:46 (INFO) -- armoryengine.pyc:9998 - New block broadcast received
2013-04-04 20:46 (INFO) -- armoryengine.pyc:9998 - New block broadcast received
2013-04-04 20:46 (INFO) -- armoryengine.pyc:9998 - New block broadcast received
2013-04-04 20:46 (INFO) -- armoryengine.pyc:9998 - New block broadcast received
2013-04-04 20:46 (INFO) -- armoryengine.pyc:9998 - New block broadcast received
2013-04-04 20:46 (INFO) -- armoryengine.pyc:9998 - New block broadcast received
2013-04-04 20:56 (INFO) -- armoryengine.pyc:9998 - New block broadcast received
2013-04-04 20:56 (INFO) -- armoryengine.pyc:9998 - New block broadcast received
2013-04-04 20:56 (INFO) -- armoryengine.pyc:9998 - New block broadcast received
2013-04-04 20:56 (INFO) -- armoryengine.pyc:9998 - New block broadcast received
2013-04-04 20:56 (INFO) -- armoryengine.pyc:9998 - New block broadcast received
2013-04-04 20:56 (INFO) -- armoryengine.pyc:9998 - New block broadcast received
2013-04-04 20:57 (INFO) -- armoryengine.pyc:9998 - New block broadcast received
2013-04-04 20:57 (INFO) -- armoryengine.pyc:9998 - New block broadcast received
2013-04-04 20:57 (INFO) -- armoryengine.pyc:9998 - New block broadcast received
2013-04-04 20:57 (INFO) -- armoryengine.pyc:9998 - New block broadcast received
2013-04-04 20:57 (INFO) -- armoryengine.pyc:9998 - New block broadcast received
2013-04-04 20:57 (INFO) -- armoryengine.pyc:9998 - New block broadcast received
2013-04-04 21:02 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode
2013-04-04 21:02 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets
2013-04-04 21:02 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning"
2013-04-04 21:02 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode
2013-04-04 21:02 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets
2013-04-04 21:02 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning"
2013-04-04 21:16 (INFO) -- armoryengine.pyc:9998 - New block broadcast received
2013-04-04 21:16 (INFO) -- armoryengine.pyc:9998 - New block broadcast received
2013-04-04 21:16 (INFO) -- armoryengine.pyc:9998 - New block broadcast received
2013-04-04 21:16 (INFO) -- armoryengine.pyc:9998 - New block broadcast received
2013-04-04 21:16 (INFO) -- armoryengine.pyc:9998 - New block broadcast received
2013-04-04 21:16 (INFO) -- armoryengine.pyc:9998 - New block broadcast received
2013-04-04 21:17 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode
2013-04-04 21:17 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets
2013-04-04 21:17 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning"
2013-04-04 21:22 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode
2013-04-04 21:22 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets
2013-04-04 21:22 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning"
2013-04-04 21:26 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode
2013-04-04 21:26 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets
2013-04-04 21:26 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning"
2013-04-04 21:30 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode
2013-04-04 21:30 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets
2013-04-04 21:30 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning"
2013-04-04 21:42 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode
2013-04-04 21:42 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets
2013-04-04 21:42 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning"
2013-04-04 21:46 (ERROR) -- armoryengine.pyc:10134 - ***Connection to Satoshi client LOST!  Attempting to reconnect...
2013-04-04 21:46 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode
2013-04-04 21:46 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets
2013-04-04 21:46 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning"
2013-04-04 21:46 (INFO) -- ArmoryQt.py:1254 - Setting netmode: 1
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9874 - Connection initiated.  Start handshake
2013-04-04 21:46 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode
2013-04-04 21:46 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets
2013-04-04 21:46 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning"
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9963 - Received version message from peer:
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9964 -    Version:     70001
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9965 -    SubVersion:  /Satoshi:0.8.1/
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9966 -    TimeStamp:   1365126375
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9967 -    StartHeight: 229725
2013-04-04 21:46 (INFO) -- armoryengine.pyc:10124 - Handshake finished, connection open!
2013-04-04 21:46 (ERROR) -- armoryengine.pyc:10134 - ***Connection to Satoshi client LOST!  Attempting to reconnect...
2013-04-04 21:46 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode
2013-04-04 21:46 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets
2013-04-04 21:46 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning"
2013-04-04 21:46 (INFO) -- ArmoryQt.py:1254 - Setting netmode: 1
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9874 - Connection initiated.  Start handshake
2013-04-04 21:46 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode
2013-04-04 21:46 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets
2013-04-04 21:46 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning"
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9874 - Connection initiated.  Start handshake
2013-04-04 21:46 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode
2013-04-04 21:46 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets
2013-04-04 21:46 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning"
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9963 - Received version message from peer:
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9964 -    Version:     70001
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9965 -    SubVersion:  /Satoshi:0.8.1/
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9966 -    TimeStamp:   1365126377
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9967 -    StartHeight: 229725
2013-04-04 21:46 (INFO) -- armoryengine.pyc:10124 - Handshake finished, connection open!
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9963 - Received version message from peer:
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9964 -    Version:     70001
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9965 -    SubVersion:  /Satoshi:0.8.1/
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9966 -    TimeStamp:   1365126377
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9967 -    StartHeight: 229725
2013-04-04 21:46 (INFO) -- armoryengine.pyc:10124 - Handshake finished, connection open!
2013-04-04 21:46 (ERROR) -- armoryengine.pyc:10134 - ***Connection to Satoshi client LOST!  Attempting to reconnect...
2013-04-04 21:46 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode
2013-04-04 21:46 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets
2013-04-04 21:46 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning"
2013-04-04 21:46 (INFO) -- ArmoryQt.py:1254 - Setting netmode: 1
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9874 - Connection initiated.  Start handshake
2013-04-04 21:46 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode
2013-04-04 21:46 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets
2013-04-04 21:46 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning"
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9963 - Received version message from peer:
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9964 -    Version:     70001
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9965 -    SubVersion:  /Satoshi:0.8.1/
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9966 -    TimeStamp:   1365126378
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9967 -    StartHeight: 229725
2013-04-04 21:46 (INFO) -- armoryengine.pyc:10124 - Handshake finished, connection open!
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9874 - Connection initiated.  Start handshake
2013-04-04 21:46 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode
2013-04-04 21:46 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets
2013-04-04 21:46 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning"
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9963 - Received version message from peer:
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9964 -    Version:     70001
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9965 -    SubVersion:  /Satoshi:0.8.1/
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9966 -    TimeStamp:   1365126380
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9967 -    StartHeight: 229725
2013-04-04 21:46 (INFO) -- armoryengine.pyc:10124 - Handshake finished, connection open!
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9874 - Connection initiated.  Start handshake
2013-04-04 21:46 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode
2013-04-04 21:46 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets
2013-04-04 21:46 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning"
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9963 - Received version message from peer:
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9964 -    Version:     70001
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9965 -    SubVersion:  /Satoshi:0.8.1/
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9966 -    TimeStamp:   1365126385
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9967 -    StartHeight: 229725
2013-04-04 21:46 (INFO) -- armoryengine.pyc:10124 - Handshake finished, connection open!
2013-04-04 21:46 (ERROR) -- armoryengine.pyc:10134 - ***Connection to Satoshi client LOST!  Attempting to reconnect...
2013-04-04 21:46 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode
2013-04-04 21:46 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets
2013-04-04 21:46 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning"
2013-04-04 21:46 (INFO) -- ArmoryQt.py:1254 - Setting netmode: 1
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9874 - Connection initiated.  Start handshake
2013-04-04 21:46 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode
2013-04-04 21:46 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets
2013-04-04 21:46 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning"
2013-04-04 21:46 (ERROR) -- armoryengine.pyc:10134 - ***Connection to Satoshi client LOST!  Attempting to reconnect...
2013-04-04 21:46 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode
2013-04-04 21:46 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets
2013-04-04 21:46 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning"
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9963 - Received version message from peer:
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9964 -    Version:     70001
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9965 -    SubVersion:  /Satoshi:0.8.1/
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9966 -    TimeStamp:   1365126387
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9967 -    StartHeight: 229725
2013-04-04 21:46 (INFO) -- armoryengine.pyc:10124 - Handshake finished, connection open!
2013-04-04 21:46 (INFO) -- ArmoryQt.py:1254 - Setting netmode: 1
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9874 - Connection initiated.  Start handshake
2013-04-04 21:46 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode
2013-04-04 21:46 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets
2013-04-04 21:46 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning"
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9963 - Received version message from peer:
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9964 -    Version:     70001
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9965 -    SubVersion:  /Satoshi:0.8.1/
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9966 -    TimeStamp:   1365126387
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9967 -    StartHeight: 229725
2013-04-04 21:46 (INFO) -- armoryengine.pyc:10124 - Handshake finished, connection open!
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9874 - Connection initiated.  Start handshake
2013-04-04 21:46 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode
2013-04-04 21:46 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets
2013-04-04 21:46 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning"
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9963 - Received version message from peer:
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9964 -    Version:     70001
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9965 -    SubVersion:  /Satoshi:0.8.1/
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9966 -    TimeStamp:   1365126388
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9967 -    StartHeight: 229725
2013-04-04 21:46 (INFO) -- armoryengine.pyc:10124 - Handshake finished, connection open!
2013-04-04 21:46 (ERROR) -- armoryengine.pyc:10134 - ***Connection to Satoshi client LOST!  Attempting to reconnect...
2013-04-04 21:46 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode
2013-04-04 21:46 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets
2013-04-04 21:46 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning"
2013-04-04 21:46 (INFO) -- ArmoryQt.py:1254 - Setting netmode: 1
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9874 - Connection initiated.  Start handshake
2013-04-04 21:46 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode
2013-04-04 21:46 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets
2013-04-04 21:46 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning"
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9963 - Received version message from peer:
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9964 -    Version:     70001
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9965 -    SubVersion:  /Satoshi:0.8.1/
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9966 -    TimeStamp:   1365126408
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9967 -    StartHeight: 229725
2013-04-04 21:46 (INFO) -- armoryengine.pyc:10124 - Handshake finished, connection open!
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9874 - Connection initiated.  Start handshake
2013-04-04 21:46 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode
2013-04-04 21:46 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets
2013-04-04 21:46 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning"
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9963 - Received version message from peer:
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9964 -    Version:     70001
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9965 -    SubVersion:  /Satoshi:0.8.1/
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9966 -    TimeStamp:   1365126409
2013-04-04 21:46 (INFO) -- armoryengine.pyc:9967 -    StartHeight: 229725
2013-04-04 21:46 (INFO) -- armoryengine.pyc:10124 - Handshake finished, connection open!
2013-04-04 21:47 (INFO) -- armoryengine.pyc:9874 - Connection initiated.  Start handshake
2013-04-04 21:47 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode
2013-04-04 21:47 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets
2013-04-04 21:47 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning"
2013-04-04 21:47 (INFO) -- armoryengine.pyc:9963 - Received version message from peer:
2013-04-04 21:47 (INFO) -- armoryengine.pyc:9964 -    Version:     70001
2013-04-04 21:47 (INFO) -- armoryengine.pyc:9965 -    SubVersion:  /Satoshi:0.8.1/
2013-04-04 21:47 (INFO) -- armoryengine.pyc:9966 -    TimeStamp:   1365126477
2013-04-04 21:47 (INFO) -- armoryengine.pyc:9967 -    StartHeight: 229725
2013-04-04 21:47 (INFO) -- armoryengine.pyc:10124 - Handshake finished, connection open!
2013-04-04 21:51 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode
2013-04-04 21:51 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets
2013-04-04 21:51 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning"
2013-04-04 21:51 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode
2013-04-04 21:51 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets
2013-04-04 21:51 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning"

That usually means Armory couldn't access the correct/updated block files.  Frequently happens if you change your bitcoind --datadir=X, but don't start Armory with the --satoshi-datadir=X.  Then Armory is talking to the current bitcoind, but using the old blockfiles.

Hm...strange thing is happening-2. I start Armory, after scanning, it shows Connected (228672 blocks) at the bottom right corner. While 'bitcoind getinfo' telling '"blocks" : 229725'. WTF?

Ok, I`ll try git thing it a bit later.

Do the following:


That should spit out the log and show you the signature.  My personal GPG key is 0xFB596985. 

You bring up an interesting point.   I have been "inconvenienced" by having to go to the offline computer for signing.  But there's no reason I can't sign the intermediate commits with my personal, less-secure key that is on my online computer, and switch to the offline key for major releases... hmmm

Let me see what I can do...

I`d like to, but I`m a little bit paranoid Can you sign package somehow, since git checkout from github is not done even with ssl. Maybe I`m wrong, I am not really good at compiling and programming stuff.

No worries!  The new version will actually avoid that... Armory won't go online until that download is complete.

Help me test it!

https://bitcointalksearch.org/topic/m.1723770

Damn! Blockchain wasn`t completely downloaded I need some sleep. Sorry for bothering with dumb questions and thank you

Can you find the transaction on Blockchain.info or blockexplorer?  Make sure it wasn't a double-spend.  Transactions don't usually disappear from the ledger, unless a block came in with a conflicting transaction.

Next, when it's online, can you see that the block-count in the bottom-right corner is the latest?  Make sure the number matches the latest block on the network (latest seen on blockchain.info).  If it's behind, that's why it's missing ... Armory doesn't have access to all the blocks for some reason...

mempool just holds zero-confirmation transactions.  If you delete it when there's a zero-confirmation transaction in your ledger, it will disappear on the next load.