[RESOLVED] BTC sent to generated address doesn't show up in wallet

[EddieRock]

I generated 13EXvbiNLz4tU6S9WQ54P8PbxuSiYqH27B in Armory to send some BTC from coinbase to my Armory wallet. It was generated while it was loading the blockchain. The transaction has over 300 confirmations but never showed up in my wallet. I've shutdown Armory and started Bitcoin Core (64bit) and have verified that it's caught up.

I've also verified that the address is the same that was generated from the wallet.

What can I do to get this BTC to show up in my wallet?

Not sure if it's related but I also had sent BTC and didn't provide enough network fee's so it got stuck in limbo. About 2-3 weeks later, I resent the BTC and it made it but it showed that it was a duplicate transaction. Now, Armory still shows 1 BTC in it but I know it's not spendable. Could this be related?

Currently, I'm showing "Connected (465366 blocks)"

thanks as always for your help!

Ed

[HCP]

Given that the current block height for BTC chain is: 478,788... then either your BitcoinCore is not synced up properly... OR Armory is not talking to your Bitcoin Core properly and has not synced up it's database...

You'll need to post the db.log and armorydebug.log files (use pastebin.com and provide the links )

[EddieRock]

Given that the current block height for BTC chain is: 478,788... then either your BitcoinCore is not synced up properly... OR Armory is not talking to your Bitcoin Core properly and has not synced up it's database...

You'll need to post the db.log and armorydebug.log files (use pastebin.com and provide the links )

I located the db.log file in the bitcoin directory but it was empty. In the armory directory, there is no armorydebug.log but a debug.log in %appdata%\bitcoin file that is 8,576KB in size. Is that the one you're looking for? If so, here are the logs from 7/31: https://pastebin.com/qpcXUN4u

This file contains many lines like this but the research indicates that it can be ignored. Unsure...:
2017-08-03 23:12:50 UpdateTip: new best=000000000000000000d97e53664d17967bd4ee50b23abb92e54a34eb222d15ae height=478913 version=0x20000002 log2_work=86.874865 tx=243756039 date='2017-08-03 23:12:05' progress=1.000000 cache=110.5MiB(33219tx) warning='12 of last 100 blocks have unexpected version'

Let me know where I should go next. Finding the Bitcoin Core db.log log may have the answer.

Here is a log called armorylog.txt: https://pastebin.com/Q7Qq7Z6B

Ed

[EddieRock]

Bump!

[EddieRock]

I upgraded Bitcoin Core to Version v0.14.2 and Armory to 0.96.0. Bitcoin Core shows the correct number of blocks (479110) but Armory only shows 465366.

Is there a way to force Armory to read all the blocks?

Ed

[skyhawk]

I upgraded Bitcoin Core to Version v0.14.2 and Armory to 0.96.0. Bitcoin Core shows the correct number of blocks (479110) but Armory only shows 465366.

Is there a way to force Armory to read all the blocks?

Ed

Check permissions? If Armory and Bitcoind are running as different users on unix-like systems, there can be issues because of Bitcoin's default owner-only permissions.  If you're running as different users, you'll need to fix Bitcoin's blocks/ directory to have an other-read (or group-read, if you put them in the same group) bit, then set sysperms=1 in bitcoin.conf

[EddieRock]

I upgraded Bitcoin Core to Version v0.14.2 and Armory to 0.96.0. Bitcoin Core shows the correct number of blocks (479110) but Armory only shows 465366.

Is there a way to force Armory to read all the blocks?

Ed

Check permissions? If Armory and Bitcoind are running as different users on unix-like systems, there can be issues because of Bitcoin's default owner-only permissions.  If you're running as different users, you'll need to fix Bitcoin's blocks/ directory to have an other-read (or group-read, if you put them in the same group) bit, then set sysperms=1 in bitcoin.conf

It's running on windows. I have admin rights on my computer. I've right clicked and "run as administrator". without success.

this has run fine for years and now (since 2013), the last transaction was May 7th. Last block showing in Armory is 465366 which was may 8th according to the block chain: https://blockchain.info/block/000000000000000000d6d1e36e02f62264e8b4973dd8aa73374764a05527bf13


Ed

[EddieRock]

Fixed it myself...

In Armory, select Help >> Rebuild and Rescan Databases

Restart Armory...

Done.