looking inside .bitcoin, the only differences i see btwn the contents of this BCH blockchain and my currently working BTC blockchain, both inside Ubuntu VM's on different machines, are two additional files inside the BTC blockchain; .cookie and bitcoind.pid. anyone recognize those two and what they are? are they critical to getting this Node Online?
@HCP: there is no bitcoin.conf inside my working .bitcoin directory on my BTC blockchain.
How do you launch the BTC "bitcoind"?
Are you using any commandline parameters?
The .cookie file is used for RPC Authentication... without it, you probably won't be able to connect to bitcoind via RPC. You might want to check some of the commandline options as specified here:
https://en.bitcoin.it/wiki/Running_BitcoinI would think that, at the very least,
-server would be required so that it accepts the RPC commands. It's also possible you're running into some weird behaviour with them in VMs relating to ports and networking...
i'm launching bitcoind different ways; either directly in CLI with "bitcoind" first, then launching Armory or launching bitcoind via letting Armory do it. either way Node Offline. bitcoind by itself will update when launched alone as assessed by "bitcoin-cli getblockcount". like i said, my other instance of a VM based BTC blockchain works just fine on my other computer that doesn't have another blockchain on the host. so i know this setup runs inside a VM just fine. that setup also does NOT have a bitcoin.conf file. i also read somewhere that bitcoin.conf is not necessary. this problematic computer does have the BTC blockchain on the host (which i don't run simultaneously of course). i don't see how that could be interfering with BCH client communicating with Armory in the VM however.
as an aside, when i start up Armory with either bitcoind started by itself first or by letting Armory control it, the block count at bottom right in Armory shows the updated correct number. it just won't advance beyond that both in the GUI and in the terminal (stuck at "BDM ready!").