Armory stuck in offline mode...

[HCP]

Hello, I have the same problem. I start armory, it always says offline mode. Please healp. Here is my log file.

As achow101 mentioned to the previous poster, you shouldn't hijack other threads. You should really start your own thread!

Anyway, if you manually run Bitcoin-QT... then look under "Help -> Debug Window -> Information"... what is "DataDir" set to?



Looking at your debug, Armory is attempting to run bitcoind, and set it to use: C:\Users\Vitalii\AppData\Roaming/Bitcoin as the Bitcoin datadir... however, it doesn't seem to exist... so Armory cannot read the "blocks" from this datadir...

You may need to set Armory so that it doesn't control bitcoind (File -> Settings -> make sure "Let Armory run Bitcoin Core/bitcoind in the background" is unchecked)... then make sure that your bitcoind (or Bitcoin Core) is run manually and fully synced and then start Armory.

[1714258151]

1714258151

[1714258151]

1714258151

[danielecadeddu]

Me too my client always off line.
I have set the default directories but it doesn't work.
Where I can send my log file?

[happiestcow]

I got the same problem.   

Armory 0.96.5 on Windows 10.

Just downloaded whole blockchain by Bitcoin-qt.

I've installed everything into
D:\Armory
D:\Armory\bitcoin qt
D:\Armory\bitcoin qt\blocks

And so says bitcoin qt.

At the ArmorySettings.txt i've got:
ArmoryDbdir                         | D:\Armory\bitcoin qt\blocks
SatoshiDatadir                      | D:\Armory\bitcoin qt\blocks
SatoshiExe                           | D:\Armory\bitcoin qt


I think directory settings are ok, but still Armory is offline.

Is there any chance to take my offline wallet and log it into another instance of Armory, or another app?

[happiestcow]

OK, finally Armory has noticed Bitcoin qt. It started syncing, which took forever. After it downloaded ~270 GB of blockchain to my HDD, I ran out of space. So I started deleting the oldest part of it and did it a few times to keep it going until the end. No I got 229 GB of blockchain on my 270 GB HDD.

The situation right now is:
- bitcoin qt is running in the background
- at the Armory startup it says it does not have communication with bitcoin
- Node status is done
- Build databases is done, but with a disc symbol
- Scanning Transaction History  does not do anything
- wallet is offline again...

Is there any shortcut to my wallet that will not need me to download another hundreads of GB again?

my logs:
https://pastebin.com/8UAwJJ46

[nc50lc]

OK, finally Armory has noticed Bitcoin qt. It started syncing, which took forever. After it downloaded ~270 GB of blockchain to my HDD, I ran out of space. So I started deleting the oldest part of it and did it a few times to keep it going until the end. No I got 229 GB of blockchain on my 270 GB HDD.
-snip-

A 270GB HDD wont do, Armory requires the whole blockchain in your disk which will require about 400GB of data.
Even if Bitcoin Core is fully synced with pruned blockchain, Armory won't be able to build its database from the pruned blocks.

[HCP]

So I started deleting the oldest part of it and did it a few times to keep it going until the end.

You can't delete parts of the blockchain and expect Armory to work properly. It won't work properly with a "pruned" node, and it certainly won't work if you've simply been deleting block files manually.

You absolutely need the entire blockchain data available for Armory to work properly. If you don't have enough disk space, then unfortunately Armory is not an option. Buy an external drive and suffer through the slow sync speeds that external drives generally cause, or upgrade your internal storage to at least 1TB

[Carlton Banks]

maybe this needs it's own thread, but here goes....

got Armory 0.96.5 db synced in a Debian 10 VM, bitcoind 24.0

bitcoind I compiled myself using the depends build system
armory I also compiled myself standardly

• bitcoin-cli getpeerinfo | grep inbound tells me ArmoryDB isn't connected to bitcoind
• using default 8333 port for inbounds
• dbLog.txt says "RPC connection established" and "Node is ready"
• Armory footer says "Node disconnected"
• Armory dashboard says"Armory is online"

Armory is synced (as I say), but up to the block it queried at startup, it clearly reads bitcoin blocks from disk ok, but cannot receive new blocks once synced.

I'm using all the same config files from my old installation, and everything in them seems sensible (Armory isn't exec'ing bitcoind, bitcoin.conf has server=1)

I also tried running ArmoryDB with and without --cookie, hoping to elicit some kind of different error or change in behavior, but it didn't startup properly


is Bitcoin 24.0 the issue? I somehow doubt it. I've also checked to see that the VM isn't missing any dependencies, but it's hard to see what else those could be when networking is up (bitcoind is for sure connecting to the network and is currently at block 803610). building armory and bitcoind completed without any errors (I built them using Debian 10 build-essentials and standard dev packages)

mysterious, n'est pas?

[goatpig]

• bitcoin-cli getpeerinfo | grep inbound tells me ArmoryDB isn't connected to bitcoind

This is your issue. Armory connects to Bitcoin Core as a P2P node. It waits on new block broadcasts from your node to trigger the new block checks. If that connection isn't established, Armory won't see new blocks.

[Carlton Banks]

I was being a moron, bitcoin.conf needs explicit listen=1 also, as I'm setting proxy= in there too

all working, thanks gp

[blackhat]

just wanted to say "thank you carlton and goatpig" for pointing me to the right direction. got stuck a few days ago with this very issue after switching to my own big datacenter-hosted fullnodes that my armory client is being connected to with "connect= <ip>". unfortunately, doing this in bitcoin.conf eliminates listen=1 automagically and sets it to "0". bitcoind doesn't allow incoming connections anymore. that causes amory to stay in "node offline" forever. setting "listen=1" after "connect=<ip>" solved this issue almost immediately. thank you!! *being relieved*