Help with armory update on macOs

[plecoup]

I have recently upgraded to v0.15.1 of bitcoin core on my mac, it is currently synced and running.
I was previously running v0.12 together with armory v0.93.3
After the upgrade I cannot run armory since it gives me an error (BDM error?), I am guessing it is due to segwit being implemented on bitcoin core?
I tried downloading the latest version of the armory client (v0.96.3.99), but when I try to run it it doesn't even start (I just see the armory icon for a second on the dock before it disappears without anything appearing on screen). I would have posted a log or something but I do not know where to find it, forgive me.
I also tried to delete the data folder before running the armory client, but I get the same result.
Any help would be greatly appreciated, thanks.

Bitcoin Client Software and Version Number:v0.15.1
Operating System:Mac OS X 10.11.6
System Hardware Specs:2,66 GHz Intel Core 2 Duo 8 GB 1067 MHz DDR3


edit:
Actually found the logs, but it seems that starting up the client doesn't change them, no useful info is logged during startup

[droark]

Read me.

[plecoup]

Thank you.

I Followed all the instructions, still no luck. Any other suggestions?

[droark]

Please run Armory from the terminal line (/*Armory location*/Armory.app/Contents/MacOS/Armory) and report back with what comes up on the command line. This is for the latest version (0.96.4 RC1, aka 0.96.3.99).

[plecoup]

The terminal gives me the following error:

  Illegal instruction: 4

I tried searching for some explanation, so far to no avail...though I suspect the trouble lies with my particular configuration...
Thank you for your help.

[droark]

Hmmm. I ran that build for a bit on my 10.11 VM. No problems. Are you running on an actual Mac or on a Hackintosh? Do you have to stick to 10.11 for some reason or are you able to upgrade? The error seems to have to do with some minutiae that I thought had been dealt with, at least on my VM. (I only have one Mac, which I keep up-to-date.)

[plecoup]

I have an actual Mac, and I tried upgrading to the latest os version (10.13) but nothing changed unfortunately..
Thank you.

[droark]

Which model Mac are you using?

[plecoup]

MacBook Pro (13-inch, Mid 2010)

[droark]

Hmmm. Not sure why this would fail. I suppose a support package could have an instruction that isn't supported by your CPU (Penryn microarchitecture, AFAIK). I thought I accounted for that in the build system, though.

If you don't mind getting your hands a little dirty, you can always compile your own version of Armory. It's actually not that scary, although you may want to wait for 0.96.4 RC2 if at all possible. (There's a PR I need to get goatpig to pull that'll get the build working again.) The instructions and such will be very thorough and should walk you through the process. Once you compile for your own system, it should work.

[goatpig]

Illegal instructions usually mean your CPU is lacking the silicon for specialized ASM calls. You'd have to build yourself.

[plecoup]

Ok, thank you both, should I follow these instructions?

https://github.com/goatpig/BitcoinArmory/blob/master/osxbuild/OSX_build_notes.md

[droark]

Ok, thank you both, should I follow these instructions?

https://github.com/goatpig/BitcoinArmory/blob/master/osxbuild/OSX_build_notes.md

Almost. The instructions here are the preferred directions. I'm hoping this will all get accepted into RC2, along with these files (necessary to re-enable the build) and this file (macOS bug fix). I'd recommend waiting if possible, as goatpig will compile a nice tarball with all the files you need. Making this your first experience with Git would be a recipe for disaster.

[plecoup]

Ok then, I guess I will wait a while then, although I will probably try to poke around and try to build it myself,
Thank you

[droark]

Gaaaaaah. Please disregard what I said about the macOS build not working. You should be able to build 0.96.4 RC1 without issues. I'd hurry, though. The script will be out-of-date any day now. (I have a short-term fix PRed and a long-term fix for this in the works. As is, things work the way they do due to technical debt.)

[plecoup]

Ok, I managed to build armory, now here is the situation:

The first time I start it after booting up my mac, armory works, but it stays in offline mode (the "preparing databases" bar doesn't move). I also tried to start it via terminal and this is what is returned:

Code:

(ERROR) ArmoryUtils.py:3720 - Unsupported language  specified. Defaulting to English (en)
(WARNING) SDM.py:396 - Spawning DB with command: /Users/plecoup/Desktop/armory_0.96.3.99-src/osxbuild/workspace/Armory.app/Contents/MacOS/py/usr/local/lib/armory/../../bin/ArmoryDB --db-type="DB_FULL" --cookie --satoshi-datadir="/Users/plecoup/Library/Application Support/Bitcoin/blocks" --datadir="/Users/plecoup/Library/Application Support/Armory/" --dbdir="/Users/plecoup/Library/Application Support/Armory/databases"
(ERROR) BDM.py:201 - DB error: DB version mismatch. Use another dbdir!

Note that armory still opens up despite the errors.

If I then try to quit armory and restart it it crashes without actually starting, and if I try to launch it (restart it) via terminal here is what is returned:

Code:

(ERROR) ArmoryUtils.py:3720 - Unsupported language  specified. Defaulting to English (en)
(ERROR) ArmoryQt.py:5955 - Socket already in use.  Sent CLI args to existing proc.
(ERROR) ArmoryQt.py:5956 - Exiting...

And here no matter what armory doesn't start.

Hence I am guessing some process isn't exiting correctly?

Any suggestion?
Should I post some logs?
Thank you once again, and sorry for troubling you.


EDIT:
Ok so I deleted everything in armory's data folder, now it seems to be building the databases, will update when done.
Once again, sorry.

[droark]

For unknown reasons, ArmoryDB sometimes hangs when you exit Armory. I believe things have gotten better but it can still happen. If you run into more issues with the DB when trying to restart Armory, you'll want to check the Activity Monitor and close ArmoryDB if it's still running.

[plecoup]

Ok then, armory is up and running, everything looks good, I'll just use activity monitor when ArmoryDB doesn't close.
Thanks a lot for your help and time and all your work!