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?