Pages:
Author

Topic: MAC EXPERT NEEDED! BDM Error and Can't Open 0.95.1 / Rebuilt, STILL ERROR! (Read 1691 times)

sr. member
Activity: 525
Merit: 282
Okay. As part of my PR to let Armory build on 10.13, I clarified the build notes a bit. Look here and make sure you're following them. I think these are relatively bulletproof for newbs but feedback is appreciated. In any event, it's important that people know how to get around via the terminal. If they don't know what they're doing, it's still going to be painful.
member
Activity: 270
Merit: 36
Did you actually download the source code? And if so, where did you download and/or clone it to?

Seconded. DigitalCrypto, you need to follow all the instructions Sad
HCP
legendary
Activity: 2086
Merit: 4361
Did you actually download the source code? And if so, where did you download and/or clone it to?
HCP
legendary
Activity: 2086
Merit: 4361
Can you please enter this command and take a screenshot of the output:
Code:
ls -la

You're attempting to run these commands from your "user home directory" at the moment... you won't be able to build from that location. You will need to be in the directory where the Armory git was cloned to
member
Activity: 63
Merit: 10
member
Activity: 270
Merit: 36
I followed every step and I still got this...

No such file directory
Code:
cd osxbuild

https://prnt.sc/gmr3e1

Nearly there. If you haven't downloaded a copy of the Armory git repo (the code), you'll need to do that. Can either grab the zip and extract it or git clone if you're familiar with that.

Either way, once you have a copy of the code, cd to wherever the Armory code is.
Then run step 7 again:
Code:
cd osxbuild
python build-app.py > /dev/null

Compiling may take a little while Smiley
Fingers crossed!
member
Activity: 63
Merit: 10
Hmmm. I really don't know what could be happening here. What the system is telling you is that there are instructions that your CPU doesn't recognize. I don't know why that would happen. Others seem to be running the binaries without issues. One thing I'll look into is my VM settings. It's possible my build VM needs to be told it has access to a different processor, or some other obscure setting. Hang tight. I'll do what I can.

In the meantime, if you don't mind getting your hands a little dirty, you can build your own version. I need to update the notes slightly but this should get you past the finish line.

I followed every step and I still got this...

No such file directory
Code:
cd osxbuild

https://prnt.sc/gmr3e1
sr. member
Activity: 525
Merit: 282
Hmmm. I really don't know what could be happening here. What the system is telling you is that there are instructions that your CPU doesn't recognize. I don't know why that would happen. Others seem to be running the binaries without issues. One thing I'll look into is my VM settings. It's possible my build VM needs to be told it has access to a different processor, or some other obscure setting. Hang tight. I'll do what I can.

In the meantime, if you don't mind getting your hands a little dirty, you can build your own version. I need to update the notes slightly but this should get you past the finish line.
member
Activity: 63
Merit: 10
MacBook Pro (13-inch, Mid 2012)
2.5 GHz Intel Core i5
8 GB 1600 MHz DDR3
Intel HD Graphics 4000 1536 MB
1TB SSD
sr. member
Activity: 525
Merit: 282
Interesting. Which model Macbook Pro are you using?
member
Activity: 63
Merit: 10
No, what I mean is run the latest version from the command line, like I mentioned earlier. I listed it as being under /Applications but it can be anywhere. I need to know what it's saying when you try to launch a later version of Armory.

Tried with 0.96.1 (Didn't launch and gave me this message)

Last login: Sat Sep 16 04:54:29 on ttys000
Admins-MacBook-Pro:~ Admin$ /Applications/Armory.app/Contents/MacOS/Armory ; exit;
/Users/Admin
Illegal instruction: 4
logout
Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.

[Process completed]
sr. member
Activity: 525
Merit: 282
No, what I mean is run the latest version from the command line, like I mentioned earlier. I listed it as being under /Applications but it can be anywhere. I need to know what it's saying when you try to launch a later version of Armory.
member
Activity: 63
Merit: 10
Please use the latest version and try again. I don't think 0.95.1 is supported anymore.

Nothing launches. The only version that launches is 0.92.1/3.
legendary
Activity: 3766
Merit: 1364
Armory Developer
What version of Armory are you using? What version of Armory where you using before that? If you updated recently, did you clear your previous database folder? The error you are getting is a trademark of running a new version of Armory on an older DB (0.94 vs 0.93 DB) or (0.95+ vs 0.94 DB).
newbie
Activity: 16
Merit: 0

When you go under /Applications/Armory.app/Contents/MacOS and run Armory ("./Armory"), what's the output?

 


 In this case I get a pop-up with a yellow triangle holding an exclamation mark, and the message "The DB has returned the following error:

DB version mismatch. Use another dbdir!

Armory will now shutdown.


]Here's what I get in the terminal:

/Users/julianthurston
-->cd Aplicativos
-bash: cd: Aplicativos: No such file or directory
-->cd Applications
-->ls
Armory.app                   Chrome Canary Apps.localized
Chrome Apps.localized
-->cd Armory.app
-->ls
Contents
-->cd Contents
-->ls
Dependencies Frameworks   Info.plist   MacOS        Resources
-->cd MacOS
-->./Armory
/Users/julianthurston/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/armoryengine/Transaction.py:2760: SyntaxWarning: import * only allowed at module level
  def PyCreateAndSignTx_old(srcTxOuts, dstAddrsVals):
(WARNING) ArmoryQt.py:2565 - ***WARNING: Duplicate wallet detected, 2f68UeoBm
(WARNING) ArmoryQt.py:2575 - Second wallet is more useful than the first one...
(WARNING) ArmoryQt.py:2576 -      Wallet 1 (skipped): /Users/julianthurston/Library/Application Support/Armory/armory_2f68UeoBm_.watchonly.wallet
(WARNING) ArmoryQt.py:2577 -      Wallet 2 (loaded):  /Users/julianthurston/Library/Application Support/Armory/armory_2f68UeoBm_.wallet
(WARNING) ArmoryQt.py:2565 - ***WARNING: Duplicate wallet detected, 36vn4TDvo
(WARNING) ArmoryQt.py:2575 - Second wallet is more useful than the first one...
(WARNING) ArmoryQt.py:2576 -      Wallet 1 (skipped): /Users/julianthurston/Library/Application Support/Armory/armory_36vn4TDvo_.watchonly.wallet
(WARNING) ArmoryQt.py:2577 -      Wallet 2 (loaded):  /Users/julianthurston/Library/Application Support/Armory/armory_36vn4TDvo_.wallet
(WARNING) ArmoryQt.py:2565 - ***WARNING: Duplicate wallet detected, YXdMHf2o
(WARNING) ArmoryQt.py:2575 - Second wallet is more useful than the first one...
(WARNING) ArmoryQt.py:2576 -      Wallet 1 (skipped): /Users/julianthurston/Library/Application Support/Armory/armory_YXdMHf2o_.watchonly.wallet
(WARNING) ArmoryQt.py:2577 -      Wallet 2 (loaded):  /Users/julianthurston/Library/Application Support/Armory/armory_YXdMHf2o_.wallet
(ERROR) BDM.py:184 - DB error: DB version mismatch. Use another dbdir!
-->
newbie
Activity: 16
Merit: 0
 I have been following this thread, and doing the various terminal gymnastics requested by goatpig and DRoark, and I too get hte BDM error!, after everything has loaded and scanned, apparently correctly....except, I get this BDM error! pop-up that won't let me DO anything with my wallets.  I cannot access my wallets, even though all info is present on the screen, wallet name, amount of bitcoin held in wallet, and so on.  Maybe I should BLOCK POP-UPS?Huh


I am quite frustrated. What happened?Huh This is occurring with multiple users, so there must be something that changed on your end!

I love you goatpig, don't be angry with me. Also, Hi goatpig and DRoark... long time no talk.
                       
sr. member
Activity: 525
Merit: 282
Please use the latest version and try again. I don't think 0.95.1 is supported anymore.
member
Activity: 63
Merit: 10
sr. member
Activity: 525
Merit: 282
Okay. Which version are you running? Twisted is being used in the version you're running. It was removed in 0.96.1.
Pages:
Jump to: