rebuild & rescan should fix it

Yes. I don't have either of these set in my .conf, I just let my node create a cookie file on each run and have Armory use that.

It doesn't have to be bitcoind, you can also run BitcoinQt to the same effect.


It's failing to establish a RPC connection with bitcoind. Make sure your user can read and write bitcoin.conf, add server=1 in there and wipe the current log&pass for the good measure.

You're supposed to start the DB first, I have not fixed it the other way around yet.

You want to see the DB output, you can just run ArmoryDB on its own in a command line prompt/terminal.

That's going away next version. You can't have nice things.

It used to do that, I have not restored that feature yet.

I changed a lot of code around wallets this upcoming version, I'll have to rework imports basically from the ground up, so the code is gonna change completely (and well, work)

Won't change anything.

In the broadcast dialog, you can copy the raw tx as hex. Grab that and try to broadcast it straight from Core, you'll get a error message giving you an idea as to why it's failing.

Do a rescan and try again.

auto bitcoind has always been the biggest source of bugs in Armory's history. This isn't unheard of.

Post armorylog.txt and dblog.txt

Then your immediate solution is to install/VM a Debian based Linux distro to create your wallets with. Otherwise, you'll have to wait for the 0.96 testing phase to participate and help me debug the issue if it has persisted until then.

I don't think it would achieve anything. Do you build your own binaries? I'd have you test it with 0.96

Are you using non ascii characters in your password? Try creating a wallet with a very simple password for testing purposes.

I'll try to reproduce on my own, although I doubt I will manage. You are the first one to report an issue of this nature on 0.95, and there has not been significant changes in that code across versions to justify such failure.

Maybe try to run offline Armory with admin privilege, in the off case it is a permission issue.

Also teamviewer on its own won't help, as I'd need to install a whole suite of development tools to debug the issue.

P.S: Give it a try in testnet by adding --testnet to the offline shortcut target

Yes


I have not built any offline bundle myself. These are just carryovers from the ATI era, since I have not changed the signing code yet.

There is new signer code to cover the new address types for 0.96. This code is only active when spending from the new address types, this means you can use the old offline signers to sign for the legacy addresses funded with 0.96 and later.

If you use the new address formats, you'll need a 0.96+ signer. For that purpose I'll put out a new set of offline bundles.

Offline bundles aren't just builds however. They come with the packages needed to install Armory offline on the fresh install of the target OS. Assembling and testing the packages is a demanding task on its own, which is why you won't see offline bundles for every release, and only a few OS supported.

I use a different process than Alan for builds however. For each package, he would build the binaries directly on the target OS. I build all *nix binaries on Debian Wheezy. These binaries are compatible with everything Debian x64 based.

This leaves the question of OSes and arch. Obviously there will be at least one Ubuntu LTS. Other OSes are still up in the air atm. As for Tails, afaik they run on Debian Jessie, so a Jessie offline bundle should work, although I believe they use x86 and not x64, which is annoying in its own right.

You didn't start Armory in offline mode, it just happens to be offline because it failed to auto start bitcoind.

Let's take it from the top.

1) Make sure no instance of ArmoryDB.exe is running. If there are, just kill the process in the task manager.

2) Create a shortcut of ArmoryQt.exe. In the shortcut properties, add this to the target field:"--offline", then rename the shortcut to something like "Armory offline". Your target should look like this:


3) Delete your log file again, the constant RPC errors make it hard to make sense of anything.

4) Start Armory through the offline shortcut, repeat the process.

P.S: is there an ArmoryQt.exe.log file in C:\Program Files (x86)\Armory ? If so, post it.

Delete the log, start Armory in offline mode and try again. If it fails, post the fresh log.

Post your logs.