Post your logs.

You should import your wallets offline first, then start online so as to let Armory scan the new addresses in a bulk. The missing history indicates the addresses either need to be scanned, or your blockchain copy is missing some blocks (what'st he top block displaying in the bottom right of Armory?)

Let's see dbLog.txt and armorylog.txt

Bitcoin was running at least this one time, otherwise the DB wouldn't be able to connect.


That's ok, you can cd to the folder and start the Binary yourself.

The JSON issue you are getting is that Armory (the client) fails to talk to your Bitcoin node over the RPC. This shouldn't prevent the client from processing further unless auto bitcoind management is enabled, in which case the client wants to query the bitcoind status (through the JSON RPC) to know when it is ready, before moving on.

So right now I'm guessing you have auto bitcoind enabled.

You have 2 solutions:

1) Turn off auto bitcoind (in File -> Settings in the Armory client) and manage bitcoin-qt yourself.

2) Open this file:

/home/rojaslee/.bitcoin/bitcoin.conf

and add this line:

server=1

Save it and start armory (just client, not the DB).

There is no history whatsoever? What is the top block shown by Armory in the bottom right corner?

These are command names, not command line arguments. All cli arg for armory start with --. If the command is not found, it's just a caps issue or a typo.

Make sure ArmoryDB.exe isn't running.

Delete this folder:

C:\Users\x\AppData\Roaming\Armory\databases

i dont know where you got the idea that armory + some name would have any effect.

Run the following:

ArmoryDB
armory
bitcoin-qt

Ok I messed up. I want you to run 1 ArmoryDB and 1 ArmoryQt, not 2x ArmoryDB.

People have reported issues with lockboxes. I'll be looking into them for the next release.

Just start armorydb from another terminal now.

Is this your input when trying to run armorydb?

Show me the terminal output when running armorydb.

It should be.

For now, delete /home/rojaslee/armory/databases, then run ArmoryDB from the terminal. Then run ArmoryQt from another terminal instance.

It doesn't look like you are running Bitcoin Core. Try this:

1) In Armory, go to Files > Settings. Turn off auto bitcoind (section).

2) Open this file in the notepad: C:\\Users\\Zeeshan\\AppData\\Roaming\\Bitcoin\\bitcoin.conf

Add this line in there: disablewallet=1

3) Save & close the file and start BitcoinQt manually. Let it catch up. Set it on the Peers tab.

4) Start Armory, make sure it shows up in the BitcoinQt Peers tab.

5) Try to spend again.

In Windows, yes. Will take it down for next release.

Let's see dbLog.txt and armorylog.txt in full. What piece of log you isolated is RPC failure, this won't prevent Armory from running on its own.

That's the preferred mode in any case. You may be experiencing path mismatches with auto bitcoind. That mode will change a lot under the hood next release, and I will also improve on the pathing customization. For now, bear with this.

You don't need experience coding, just know how to fork a repo, modify a couple .md and create a PR. It can all be done from github's webpage, graphically.

I encourage people to PR for 2 reasons:

1) Makes the community aware that the web portal is open source and up for contributions.

2) To get users involved in the process. This is a community project now, after all.

For reference, this is what the PR looked like for this particular change:

https://github.com/goatpig/BitcoinArmory/pull/140/files

Fairly simple. You shouldn't let the lingo deter you. This is a perfect opportunity to learn a little git-fu.

I'll reproduce and let you know.