It's been 3 days and 263 confirmations and it's still not showing in Armory.

[66tbird]

 It's a simple .009 btc from virwox and it's been 3 days. No idea what to do next   Suggestions?

[HCP]

Your username looks familiar... you previously had issues with Bitcoin Core right? Is it currently installed and fully synced?

Are you running the latest 0.96.4 version of Armory? (available here: https://github.com/goatpig/BitcoinArmory/releases)

[66tbird]

Yep, that was me. I'm all synced and did a few transactions. I'm downloading 96.4 now. I was on 96.3-99beta. Hope it works.

I have no idea why the bitcoin core issue was an issue. I did nothing different in the steps to repair the install that I hadn't done three times before. It just started working like it should.

Now this little test purchase of btc and this problem.

It's now at 347 confirmations and listed in the Unspent Outputs of the Blockchain

No luck on the Armory update. It's been 4 days. Hope it's not time to kiss that $85 goodbye.

[droark]

What exactly are you seeing on the Armory splash screen? Does it say "Online (521051 blocks)" in green in the lower-right corner? (The number of blocks will be different, mind you.) If not, Armory isn't properly connected to Core. You'll probably have to add a bitcoin.conf file to Core in order to get it to talk to Armory, along with turning off auto-management of Core in Armory if that's turned on. This is discussed in multiple earlier threads here.

[66tbird]

connected (510893 blocks) in green. I've made recent transactions via send but not a receive since I stopped mining in 14

Did the virwox Pp to btc purchase thing and provided a receive address through Armory. virwox said it would take 48hrs but its actually been close to double that.

[PhoenixFire]

Block #510893 was mined back in late February, so you're not going to see any transactions since then. If that number isn't going up at all, something is wrong with Bitcoin Core's sync.

[66tbird]

uhg and what command fixes that pray-tell? Last time I hit rescan it took weeks.

[PhoenixFire]

uhg and what command fixes that pray-tell? Last time I hit rescan it took weeks.

Hopefully just Bitcoin Core itself that is running behind, but Armory needs that data. Close Armory down and start up Bitcoin Core. Go to Help -> Debug Window -> Information.
Look for the figure next to "Current number of blocks". More or less than 510893?

[66tbird]

521109 via bitcoin core debug info and 510893  via Armory. Both linked to the same directory.(default- i.e. roaming etc  ) Armory does the moving green bar node/status/parcing check each time.

[droark]

Looks like Core's up to date. In Armory, Help -> Rebuild and Rescan Databases

[66tbird]

Okay, I'll push that button. Last time I did it took weeks to return to normal. So I'm a little apprehensive. Here goes

[66tbird]

Yep, it jacked it. wants to reindex from day one again (fourth time). Last time it took weeks at my dsl speed.

[droark]

Yep, it jacked it. wants to reindex from day one again (fourth time). Last time it took weeks at my dsl speed.

Rebuilding the DB has nothing to do with re-downloading the blockchain. It just scans the blockchain and rebuilds the DB. What kind of computer do you have that requires weeks to do this? A reasonably modern computer shouldn't take more than an hour (assuming you have an SSD instead of a hard drive), and even that's a bit high from what I've observed.

[stevegee58]

After you sort your issues out, you might consider switching to a thin client like Electrum (sorry Armory guys).  If you're on DSL then you're right about syncing a full node taking forever.  With a thin client you don't have to worry about running a full node any more.

I'm sure Armory is a good client but your situation is such that running a full node is too burdensome.

[HCP]

Yep, it jacked it. wants to reindex from day one again (fourth time). Last time it took weeks at my dsl speed.

You're not running your node in "pruned" mode are you?

As droak said... rebuilding the Armory DB does not force a redownload of the blockchain. It simply scans the blockchain files which you already have on disk and rebuilds it's DB from those. The only reason I can think of as to why Bitcoin Core might want to reindex from day 1 when rebuilding in Armory is if you don't actually have the full blockchain on disk because you've been running in "pruned" mode.

Seems very odd... 

[66tbird]

Well,, I'm not very fluent in the computer lingo of this facet. I run an i7 machine setup for CAD (SSD, 32Gb ram, water cooled etc..) so speed of the system is good. My DSL is maxed at 5Mbs because I'm out in the sticks and fiber optics won't be here in my life time.

BT core seems to sync to the correct number of blocks. But my wallet is in Armory and after hitting the rebuild rescan button it ran through one progress bar in a few minutes then switched to  an ''Initializing Bitcoin Engine'' and  ''Organizing Blockchain'' green flashing progress bars without  a completion percentage read out. I figured that may take time so I went to bed. This morning it doesn't appear to of done anything. It's doing the same scrolling two green bars. My task manager shows Armory is doing something at 13% cpu.

The only thing I know is when this finally update I'm ditching Amrory. Been nothing but trouble.

[66tbird]

Yep, it jacked it. wants to reindex from day one again (fourth time). Last time it took weeks at my dsl speed.

You're not running your node in "pruned" mode are you?

As droak said... rebuilding the Armory DB does not force a redownload of the blockchain. It simply scans the blockchain files which you already have on disk and rebuilds it's DB from those. The only reason I can think of as to why Bitcoin Core might want to reindex from day 1 when rebuilding in Armory is if you don't actually have the full blockchain on disk because you've been running in "pruned" mode.

Seems very odd... 

I've not heard of pruned mode. My Bitcoin core file is 181Gb

[HCP]

So what exactly is "reindexing"? Your Bitcoin Core or Armory?

If it's just the green bars in Armory, then that is what you want... Although it really should not take that long with the setup you have.

Possibly an issue with your blockchain files being corrupt.

Can you post the Armorylog.txt and dbLog.txt now?

[66tbird]

This is my only txt file in my Armory standalone.

(ERROR) ArmoryUtils.pyc:3723 - Unsupported language  specified. Defaulting to English (en)
(WARNING) SDM.pyc:441 - Spawning bitcoind with command: C:\Users\john-asus\AppData\Roaming\Bitcoin\bitcoind.exe -datadir=C:\Users\john-asus\AppData\Roaming\Bitcoin
(WARNING) SDM.pyc:398 - Spawning DB with command: L:\apps in transfer\bitcoin\armory_0.96.4-win64\ArmoryStandalone\ArmoryDB.exe --db-type="DB_FULL" --cookie --satoshi-datadir="C:\Users\john-asus\AppData\Roaming\Bitcoin\blocks" --datadir="C:\Users\john-asus\AppData\Roaming\Armory\" --dbdir="C:\Users\john-asus\AppData\Roaming\Armory\databases"
(WARNING) ArmoryQt.py:4111 - Called updateSyncProgress while not sync'ing
(ERROR) Traceback (most recent call last):
  File "qtdialogs.pyc", line 13263, in SRD
TypeError: unsupported operand type(s) for %: 'QString' and 'int'

Traceback (most recent call last):
  File "qtdialogs.pyc", line 13263, in SRD
TypeError: unsupported operand type(s) for %: 'QString' and 'int'
(ERROR) ArmoryUtils.pyc:3723 - Unsupported language  specified. Defaulting to English (en)
(WARNING) SDM.pyc:441 - Spawning bitcoind with command: K:\Bitcoin\bitcoind.exe -datadir=C:\Users\john-asus\AppData\Roaming\Bitcoin
(WARNING) SDM.pyc:398 - Spawning DB with command: L:\apps in transfer\bitcoin\armory_0.96.4-win64\ArmoryStandalone\ArmoryDB.exe --db-type="DB_FULL" --cookie --satoshi-datadir="C:\Users\john-asus\AppData\Roaming\Bitcoin\blocks" --datadir="C:\Users\john-asus\AppData\Roaming\Armory\" --dbdir="C:\Users\john-asus\AppData\Roaming\Armory\databases" --rebuild
(WARNING) ArmoryQt.py:4111 - Called updateSyncProgress while not sync'ing
(WARNING) ArmoryQt.py:4111 - Called updateSyncProgress while not sync'ing
(WARNING) ArmoryQt.py:4111 - Called updateSyncProgress while not sync'ing
(WARNING) ArmoryQt.py:4111 - Called updateSyncProgress while not sync'ing
(WARNING) ArmoryQt.py:4111 - Called updateSyncProgress while not sync'ing
(WARNING) ArmoryQt.py:4111 - Called updateSyncProgress while not sync'ing
(WARNING) ArmoryQt.py:4111 - Called updateSyncProgress while not sync'ing
(WARNING) ArmoryQt.py:4111 - Called updateSyncProgress while not sync'ing
(WARNING) ArmoryQt.py:4111 - Called updateSyncProgress while not sync'ing
(WARNING) ArmoryQt.py:4111 - Called updateSyncProgress while not sync'ing
(WARNING) ArmoryQt.py:4111 - Called updateSyncProgress while not sync'ing
(WARNING) ArmoryQt.py:4111 - Called updateSyncProgress while not sync'ing
(WARNING) ArmoryQt.py:4111 - Called updateSyncProgress while not sync'ing
(WARNING) ArmoryQt.py:4111 - Called updateSyncProgress while not sync'ing
(WARNING) ArmoryQt.py:4111 - Called updateSyncProgress while not sync'ing
(WARNING) ArmoryQt.py:4111 - Called updateSyncProgress while not sync'ing
(WARNING) ArmoryQt.py:4111 - Called updateSyncProgress while not sync'ing
(WARNING) ArmoryQt.py:4111 - Called updateSyncProgress while not sync'ing
(WARNING) ArmoryQt.py:4111 - Called updateSyncProgress while not sync'ing
(ERROR) ArmoryUtils.pyc:3723 - Unsupported language  specified. Defaulting to English (en)
(WARNING) SDM.pyc:441 - Spawning bitcoind with command: C:\Users\john-asus\AppData\Roaming\Bitcoin\bitcoind.exe -datadir=C:\Users\john-asus\AppData\Roaming\Bitcoin
(WARNING) SDM.pyc:398 - Spawning DB with command: L:\apps in transfer\bitcoin\armory_0.96.4-win64\ArmoryStandalone\ArmoryDB.exe --db-type="DB_FULL" --cookie --satoshi-datadir="C:\Users\john-asus\AppData\Roaming\Bitcoin\blocks" --datadir="C:\Users\john-asus\AppData\Roaming\Armory\" --dbdir="C:\Users\john-asus\AppData\Roaming\Armory\databases"
(WARNING) ArmoryQt.py:4111 - Called updateSyncProgress while not sync'ing
  File "ArmoryQt.py", line 6005, in <module>
  File "ArmoryQt.py", line 5406, in closeEvent
  File "ArmoryQt.py", line 5480, in closeForReal
  File "SDM.pyc", line 487, in stopBitcoind
  File "armoryengine\ArmoryUtils.pyc", line 845, in LOGERROR
(ERROR) ArmoryQt.py:5489 - Strange error during shutdown
Traceback (most recent call last):
  File "ArmoryQt.py", line 5480, in closeForReal
  File "SDM.pyc", line 487, in stopBitcoind
  File "armoryengine\ArmoryUtils.pyc", line 843, in LOGERROR
TypeError: cannot concatenate 'str' and 'exceptions.RuntimeError' objects
(ERROR) ArmoryUtils.pyc:3723 - Unsupported language  specified. Defaulting to English (en)
(WARNING) SDM.pyc:441 - Spawning bitcoind with command: C:\Users\john-asus\AppData\Roaming\Bitcoin\bitcoind.exe -datadir=C:\Users\john-asus\AppData\Roaming\Bitcoin
(WARNING) SDM.pyc:398 - Spawning DB with command: L:\apps in transfer\bitcoin\armory_0.96.4-win64\ArmoryStandalone\ArmoryDB.exe --db-type="DB_FULL" --cookie --satoshi-datadir="C:\Users\john-asus\AppData\Roaming\Bitcoin\blocks" --datadir="C:\Users\john-asus\AppData\Roaming\Armory\" --dbdir="C:\Users\john-asus\AppData\Roaming\Armory\databases"
(ERROR) ArmoryQt.py:1198 - 3 attempts to load blockchain failed.  Remove mempool.bin.
(ERROR) ArmoryQt.py:1203 - File mempool.bin does not exist. Nothing deleted.
  File "ArmoryQt.py", line 6005, in <module>
  File "ArmoryQt.py", line 5406, in closeEvent
  File "ArmoryQt.py", line 5480, in closeForReal
  File "SDM.pyc", line 487, in stopBitcoind
  File "armoryengine\ArmoryUtils.pyc", line 845, in LOGERROR
(ERROR) ArmoryQt.py:5489 - Strange error during shutdown
Traceback (most recent call last):
  File "ArmoryQt.py", line 5480, in closeForReal
  File "SDM.pyc", line 487, in stopBitcoind
  File "armoryengine\ArmoryUtils.pyc", line 843, in LOGERROR
TypeError: cannot concatenate 'str' and 'exceptions.RuntimeError' objects
(ERROR) ArmoryUtils.pyc:3723 - Unsupported language  specified. Defaulting to English (en)
(WARNING) SDM.pyc:441 - Spawning bitcoind with command: C:\Users\john-asus\AppData\Roaming\Bitcoin\bitcoind.exe -datadir=C:\Users\john-asus\AppData\Roaming\Bitcoin
(WARNING) SDM.pyc:398 - Spawning DB with command: L:\apps in transfer\bitcoin\ArmoryStandalone\ArmoryDB.exe --db-type="DB_FULL" --cookie --satoshi-datadir="C:\Users\john-asus\AppData\Roaming\Bitcoin\blocks" --datadir="C:\Users\john-asus\AppData\Roaming\Armory\" --dbdir="C:\Users\john-asus\AppData\Roaming\Armory\databases"
(ERROR) ArmoryQt.py:1198 - 4 attempts to load blockchain failed.  Remove mempool.bin.
(ERROR) ArmoryQt.py:1203 - File mempool.bin does not exist. Nothing deleted.
(WARNING) ArmoryQt.py:4111 - Called updateSyncProgress while not sync'ing
  File "ArmoryQt.py", line 6005, in <module>
  File "ArmoryQt.py", line 5406, in closeEvent
  File "ArmoryQt.py", line 5480, in closeForReal
  File "SDM.pyc", line 487, in stopBitcoind
  File "armoryengine\ArmoryUtils.pyc", line 845, in LOGERROR
(ERROR) ArmoryQt.py:5489 - Strange error during shutdown
Traceback (most recent call last):
  File "ArmoryQt.py", line 5480, in closeForReal
  File "SDM.pyc", line 487, in stopBitcoind
  File "armoryengine\ArmoryUtils.pyc", line 843, in LOGERROR
TypeError: cannot concatenate 'str' and 'exceptions.RuntimeError' objects
(ERROR) ArmoryUtils.pyc:3723 - Unsupported language  specified. Defaulting to English (en)
(WARNING) SDM.pyc:441 - Spawning bitcoind with command: C:\Users\john-asus\AppData\Roaming\Bitcoin\bitcoind.exe -datadir=C:\Users\john-asus\AppData\Roaming\Bitcoin
(WARNING) SDM.pyc:398 - Spawning DB with command: L:\apps in transfer\bitcoin\ArmoryStandalone\ArmoryDB.exe --db-type="DB_FULL" --cookie --satoshi-datadir="C:\Users\john-asus\AppData\Roaming\Bitcoin\blocks" --datadir="C:\Users\john-asus\AppData\Roaming\Armory\" --dbdir="C:\Users\john-asus\AppData\Roaming\Armory\databases"
(ERROR) ArmoryQt.py:1198 - 6 attempts to load blockchain failed.  Remove mempool.bin.
(ERROR) ArmoryQt.py:1203 - File mempool.bin does not exist. Nothing deleted.

[66tbird]

The dbLog shows a size of 1307kb but it opens empty.