Topic: Armory 0.95.1 is out - page 4. (Read 12938 times)

Multiple possibilities. Could be bad block data, unstable CPU, running out of RAM, some unknown bug.

You should create your own thread and post armorylog.txt and dbLog.txt. This thread is too long to track this issue here.

Hi goatpig,

I am having big problems with armory 95.1 on Ubuntu 64bit 16.04.
Firstly, running armory while it opens bitcoind itself, gives the errors that others have posted on here which is:
'No JSON object could be decoded' in the armorylog.txt
as well as constant errors in bitcoin debug.log file such as:
'ThreadRPCServer incorrect password attempt from 127.0.0.1:36132'

So i tried to run armory by itself after running bitcoind manually, it scans transaction history and freezes at 97% all the time.
I deleted the armory DB folder, and when restarting armory (while bitcoind is running), it will eventually freeze again at a different %, at a specific block everytime (as far as i can see in the dbLog.txt).
If i repeat this process again, and if i let it run, it would eventually finish, but the block it was stuck on will show at the bottom right hand corner of armory, the block it always freezes on.  So in other words, it is not up to date or does not communicate with bitcoind blocks.

Please help and tell me what i can do to solve this issue? should i revert back to armory 93.3?

https://bitcointalksearch.org/topic/the-new-armory-website-1588510

This stickied btw. As for why the site for my fork doesn't use the old domain: that domain belongs to ATI, the former Armory maintainer.


There was code in ATI's Armory (up to 0.93.x) that phoned home. During that process, it would grab the links to the latest Core version, download and install if for you. The phone home server is down and that bit won't work anymore.

As for my versions of Armory (0.94+), I've gotten rid of all phone home code to begin with.

Thanks for the information.
Having a different web address than: https://www.bitcoinarmory.com/download/
makes this a bit scary. Shouldn't this information be on that page? Which is the official armory site ?
Hope you understand my fear.

One question also: If I install armory on ubuntu, do I also have to install bitcoin core first or will armory do that for me?

Armory hasn't been signed like this in a long time.

Follow this guide instead:

https://btcarmory.com/docs/verify

Hi, trying to verify ubuntu download as per instructions on your site (https://www.bitcoinarmory.com/download/)

When I get to this step:
 $ dpkg-sig --verify *.deb > Processing armory_0.85-beta_amd64.deb... > GOODSIG _gpgbuilder 821F122936BDD565366AC36A4AB16AEA**98832223** 1353699840

I only get:
dpkg-sig --verify *.deb
Processing armory_0.95.1_amd64.deb...

not the part after that "> GOODSIG..."

Please help, using Ubuntu 14.04

Thanks

Ask droark, I don't do OSX.

Hi I have a problem on MacOS Sierra 10.12.3 with Armory 0.95.1. It doesn't launch at all. Just jump 3-4 times in doc and disappear. I have no idea where to dig to fix this problem. Can u help me?

Edit:

I found out this solution but it doesn't help. Same problem. And my log file is clear... no problem report's at all

Ideally it will go in testing sometimes during the upcoming week.

Any Idea when 0.96 will be released?
A vage timeframe would be enought Informationen
like "within a month" or "somewhat between 30 and 90 days"

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.

No, I don't. I just downloaded the installer version from armory website

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

Is the OS 32 bit or 64 bit?

Since you are using a virtual machine, you should try allocating it more than 1 core.

It happens with the password "123456" as well

If you think it could solve it a reinstall of windows would be no big thing.

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

Adding --testnet and starting with admin privileges does not change it: https://dl.dropboxusercontent.com/u/7416262/armorylog-testnet.txt
It only creates a subfolder "testnet3" where the log files are located.

It is a clean Win10 Prof Installation, only Windows updates so far, beside the Bitcoin Client + Armory. It is installed on a virtual machine since I only want to start it when access to my wallet is required. Win10 is also activated.

I could try another version of armory if this could help. I have an older version of armory installed on my notebook and I would like to import those wallets into this Virtual Machine once it is working.
Kind regards

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

Hello,
thank you very much for this detailed explanation. I think this time the offline mode worked, but it crashes the same moment (Step 3 on creating a wallet).
Here is the log file (I overwrite it every time): https://dl.dropboxusercontent.com/u/7416262/armorylog.txt

There is no .log-file in C:\Program Files (x86)\Armory

Greetings!

Edit: If helpful I could give you Teamviewer access.

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.