Bitcoin Forum
May 05, 2024, 12:41:57 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Illegal instruction (core dumped)  (Read 377 times)
calebcjh (OP)
Newbie
*
Offline Offline

Activity: 16
Merit: 0


View Profile
November 23, 2017, 07:15:33 AM
Last edit: November 23, 2017, 07:52:25 AM by calebcjh
 #1

I tried Armory 0.96.3 Ubuntu/Debian 64-bit with GCC 5.4 but it would not start at all:

Code:
/home/caleb
Illegal instruction (core dumped)

Armory 0.96.3 Ubuntu/Debian 64-bit with GCC 4.7 starts but crashes when restoring from paper backup.

I then built from source, v0.96.3, same thing, crashes when restoring from unencrypted paper backup.

I read some threads in this forum and it was mentioned that my CPU might not support SSE4, but it is a Celeron J3455 which supports SSE4.

Then, I tried the testing branch, same results.

Code:
/home/caleb
(ERROR) ArmoryUtils.py:3716 - Unsupported language  specified. Defaulting to English (en)
/usr/lib/armory/armoryengine/Transaction.py:2882: SyntaxWarning: import * only allowed at module level
  def PyCreateAndSignTx_old(srcTxOuts, dstAddrsVals):
(WARNING) SDM.py:439 - Spawning bitcoind with command: /usr/bin/bitcoind -datadir=/home/caleb/.bitcoin
(WARNING) SDM.py:396 - Spawning DB with command: ArmoryDB --db-type="DB_FULL" --cookie --satoshi-datadir="/home/caleb/.bitcoin/blocks" --datadir="/home/caleb/.armory/" --dbdir="/home/caleb/.armory/databases"
Illegal instruction (core dumped)

The wallet I was trying to restore was created a while ago using Armory 0.93.3 (really old, before btcarmory).

For good measure, I tried to create a new wallet on the testing branch installation. Crashes.

Code:
/home/caleb
(ERROR) ArmoryUtils.py:3716 - Unsupported language  specified. Defaulting to English (en)
/usr/lib/armory/armoryengine/Transaction.py:2882: SyntaxWarning: import * only allowed at module level
  def PyCreateAndSignTx_old(srcTxOuts, dstAddrsVals):
(WARNING) SDM.py:439 - Spawning bitcoind with command: /usr/bin/bitcoind -datadir=/home/caleb/.bitcoin
(WARNING) SDM.py:396 - Spawning DB with command: ArmoryDB --db-type="DB_FULL" --cookie --satoshi-datadir="/home/caleb/.bitcoin/blocks" --datadir="/home/caleb/.armory/" --dbdir="/home/caleb/.armory/databases"
BDM is ready!
Illegal instruction (core dumped)

Ideas?
1714912917
Hero Member
*
Offline Offline

Posts: 1714912917

View Profile Personal Message (Offline)

Ignore
1714912917
Reply with quote  #2

1714912917
Report to moderator
1714912917
Hero Member
*
Offline Offline

Posts: 1714912917

View Profile Personal Message (Offline)

Ignore
1714912917
Reply with quote  #2

1714912917
Report to moderator
1714912917
Hero Member
*
Offline Offline

Posts: 1714912917

View Profile Personal Message (Offline)

Ignore
1714912917
Reply with quote  #2

1714912917
Report to moderator
There are several different types of Bitcoin clients. The most secure are full nodes like Bitcoin Core, but full nodes are more resource-heavy, and they must do a lengthy initial syncing process. As a result, lightweight clients with somewhat less security are commonly used.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
calebcjh (OP)
Newbie
*
Offline Offline

Activity: 16
Merit: 0


View Profile
November 23, 2017, 11:06:54 AM
 #2

Update:

Running Armory uncompiled results in something slightly different:

Code:
$ python ArmoryQt.py
/home/caleb
********************************************************************************
Loading Armory Engine:
   Armory Version:       0.96.3.99
   Armory Build:         e47d6641aa
   PyBtcWallet  Version: 1.35
Detected Operating system: Linux
   OS Variant            : ('Ubuntu', '16.04', 'xenial')
   User home-directory   : /home/caleb
   Satoshi BTC directory : /home/caleb/.bitcoin
   Armory home dir       : /home/caleb/.armory/
   ArmoryDB directory     : /home/caleb/.armory/databases
   Armory settings file  : /home/caleb/.armory/ArmorySettings.txt
   Armory log file       : /home/caleb/.armory/armorylog.txt
   Do wallet checking    : True
(ERROR) ArmoryUtils.py:3720 - Unsupported language  specified. Defaulting to English (en)
/home/caleb/Documents/BitcoinArmory/armoryengine/Transaction.py:3075: SyntaxWarning: import * only allowed at module level
  def PyCreateAndSignTx_old(srcTxOuts, dstAddrsVals):
(WARNING) SDM.py:439 - Spawning bitcoind with command: /usr/bin/bitcoind -datadir=/home/caleb/.bitcoin
(WARNING) SDM.py:396 - Spawning DB with command: /home/caleb/Documents/BitcoinArmory/ArmoryDB --db-type="DB_FULL" --cookie --satoshi-datadir="/home/caleb/.bitcoin/blocks" --datadir="/home/caleb/.armory/" --dbdir="/home/caleb/.armory/databases"
BDM is ready!

At wallet creation, instead of crashing, it freezes. Progress.

I hit CTRL-C

Code:
^C(ERROR) Traceback (most recent call last):
  File "/home/caleb/Documents/BitcoinArmory/ui/Wizards.py", line 127, in initializePage
    self.createNewWalletFromWizard()
  File "/home/caleb/Documents/BitcoinArmory/ui/Wizards.py", line 180, in createNewWalletFromWizard
    extraEntropy=entropy,
  File "/home/caleb/Documents/BitcoinArmory/armoryengine/PyBtcWallet.py", line 992, in createNewWallet
    Progress=Progress, doRegister=doRegisterWithBDM)
  File "/home/caleb/Documents/BitcoinArmory/armoryengine/PyBtcWallet.py", line 1107, in fillAddressPool
    doRegister=False)))
  File "/home/caleb/Documents/BitcoinArmory/armoryengine/PyBtcWallet.py", line 1054, in computeNextAddress
    [[WLT_UPDATE_ADD, WLT_DATATYPE_KEYDATA, new160, newAddr]])
  File "/home/caleb/Documents/BitcoinArmory/armoryengine/Decorators.py", line 124, in inner
    rt = func(self, *args, **kwargs)
  File "/home/caleb/Documents/BitcoinArmory/armoryengine/PyBtcWallet.py", line 2336, in walletFileSafeUpdate
    touchFile(mainUpdateFlag)
  File "/home/caleb/Documents/BitcoinArmory/armoryengine/ArmoryUtils.py", line 3732, in touchFile
    os.fsync(f.fileno())
KeyboardInterrupt

Traceback (most recent call last):
  File "/home/caleb/Documents/BitcoinArmory/ui/Wizards.py", line 127, in initializePage
    self.createNewWalletFromWizard()
  File "/home/caleb/Documents/BitcoinArmory/ui/Wizards.py", line 180, in createNewWalletFromWizard
    extraEntropy=entropy,
  File "/home/caleb/Documents/BitcoinArmory/armoryengine/PyBtcWallet.py", line 992, in createNewWallet
    Progress=Progress, doRegister=doRegisterWithBDM)
  File "/home/caleb/Documents/BitcoinArmory/armoryengine/PyBtcWallet.py", line 1107, in fillAddressPool
    doRegister=False)))
  File "/home/caleb/Documents/BitcoinArmory/armoryengine/PyBtcWallet.py", line 1054, in computeNextAddress
    [[WLT_UPDATE_ADD, WLT_DATATYPE_KEYDATA, new160, newAddr]])
  File "/home/caleb/Documents/BitcoinArmory/armoryengine/Decorators.py", line 124, in inner
    rt = func(self, *args, **kwargs)
  File "/home/caleb/Documents/BitcoinArmory/armoryengine/PyBtcWallet.py", line 2336, in walletFileSafeUpdate
    touchFile(mainUpdateFlag)
  File "/home/caleb/Documents/BitcoinArmory/armoryengine/ArmoryUtils.py", line 3732, in touchFile
    os.fsync(f.fileno())
KeyboardInterrupt
-ERROR - : (StringSockets.cpp:351) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version
(ERROR) Traceback (most recent call last):
  File "/home/caleb/Documents/BitcoinArmory/ui/QtExecuteSignal.py", line 31, in methodSlot
    _callable(*args)
  File "ArmoryQt.py", line 4910, in handleCppNotification
    self.nodeStatus = TheBDM.bdv().getNodeStatus()
  File "/home/caleb/Documents/BitcoinArmory/CppBlockUtils.py", line 3027, in getNodeStatus
    return _CppBlockUtils.BlockDataViewer_getNodeStatus(self)
RuntimeError: can't connect socket

Traceback (most recent call last):
  File "/home/caleb/Documents/BitcoinArmory/ui/QtExecuteSignal.py", line 31, in methodSlot
    _callable(*args)
  File "ArmoryQt.py", line 4910, in handleCppNotification
    self.nodeStatus = TheBDM.bdv().getNodeStatus()
  File "/home/caleb/Documents/BitcoinArmory/CppBlockUtils.py", line 3027, in getNodeStatus
    return _CppBlockUtils.BlockDataViewer_getNodeStatus(self)
RuntimeError: can't connect socket
New Block:  495701
New Block:  495701
New Block:  495701
New Block:  495701
New Block:  495701
-ERROR - : (StringSockets.cpp:351) FcgiSocket::writeAndRead FcgiError: unknown fcgi header request byte
-ERROR - : (StringSockets.cpp:351) FcgiSocket::writeAndRead FcgiError: unknown fcgi header request byte

Btw, noticed a typo in that dialog: "No one can help you recover you bitcoins if you forget the passphrase and don't have a paper backup!"
calebcjh (OP)
Newbie
*
Offline Offline

Activity: 16
Merit: 0


View Profile
November 23, 2017, 11:49:20 AM
 #3

After trying a few more times, Armory managed to unfreeze itself, going unresponsive for long stretches of time, but I managed to create a new wallet. Restoring the old wallet worked too, though it shows a zero balance. I then restarted armory using the compiled version, but it failed:

Code:
$ armory
/home/caleb
(ERROR) ArmoryUtils.py:3716 - Unsupported language  specified. Defaulting to English (en)
/usr/lib/armory/armoryengine/Transaction.py:2882: SyntaxWarning: import * only allowed at module level
  def PyCreateAndSignTx_old(srcTxOuts, dstAddrsVals):
(WARNING) PyBtcWallet.py:2448 - ***WARNING: last file operation failed!  Restoring wallet from backup
Illegal instruction (core dumped)

Code:
$ armory
/home/caleb
(ERROR) ArmoryUtils.py:3716 - Unsupported language  specified. Defaulting to English (en)
/usr/lib/armory/armoryengine/Transaction.py:2882: SyntaxWarning: import * only allowed at module level
  def PyCreateAndSignTx_old(srcTxOuts, dstAddrsVals):
-ERROR - ;�: (WalletManager.cpp:78) Failed to open wallet with error:
missing main wallet entry
Illegal instruction (core dumped)

Starting again using uncompiled version, finally scanning transactions history, with thousands of the following error:

Code:
(python:6945): Gtk-CRITICAL **: IA__gtk_progress_configure: assertion 'value >= min && value <= max' failed

High hopes that it will finally work after it finishes scanning.
calebcjh (OP)
Newbie
*
Offline Offline

Activity: 16
Merit: 0


View Profile
November 23, 2017, 01:30:14 PM
 #4

It works Smiley

But I'd like to not have to run the uncompiled version all the time. Any help to resolve this will be appreciated. Thanks.
goatpig
Moderator
Legendary
*
Offline Offline

Activity: 3668
Merit: 1345

Armory Developer


View Profile
November 23, 2017, 02:04:58 PM
 #5

Quote
I read some threads in this forum and it was mentioned that my CPU might not support SSE4, but it is a Celeron J3455 which supports SSE4.

It's more than just SSE4, there's also pclmul and AES. Also washed down iteration, such as SSE4.a won't cut it.

Quote
But I'd like to not have to run the uncompiled version all the time. Any help to resolve this will be appreciated. Thanks.

What is an "uncompiled" version? The fix to this is to build yourself from source, or use the noasm .deb (https://github.com/goatpig/BitcoinArmory/releases/download/v0.96.3.99/armory_0.96.3.99-gcc4.7-noasm_amd64.deb)

Code:
-ERROR - ;�: (WalletManager.cpp:78) Failed to open wallet with error:
missing main wallet entry

This means you need to delete .lmdb mirror wallets in your Armory datadir.

calebcjh (OP)
Newbie
*
Offline Offline

Activity: 16
Merit: 0


View Profile
November 23, 2017, 07:00:13 PM
 #6

Quote
It's more than just SSE4, there's also pclmul and AES. Also washed down iteration, such as SSE4.a won't cut it.

Thanks for the explanation. Do you have a recommended list of proccessors? (so I can buy one that will work well next time)

Quote
What is an "uncompiled" version? The fix to this is to build yourself from source, or use the noasm .deb (https://github.com/goatpig/BitcoinArmory/releases/download/v0.96.3.99/armory_0.96.3.99-gcc4.7-noasm_amd64.deb)

Perhaps "not installed" would be a more appropriate phrasing. Basically, running Armory by doing:

Code:
python ArmoryQt.py

Btw, noasm works great!

Quote
This means you need to delete .lmdb mirror wallets in your Armory datadir.

I am not seeing this error any more. This tip will be helpful if it comes up again.

Thank you so much for clearing this up.
goatpig
Moderator
Legendary
*
Offline Offline

Activity: 3668
Merit: 1345

Armory Developer


View Profile
November 23, 2017, 07:37:07 PM
 #7

Quote
Thanks for the explanation. Do you have a recommended list of proccessors? (so I can buy one that will work well next time)

Just use the noasm builds. If you're looking to update, you'll need a stronger CPU anyways (seeing you're going online with this machine), blockchain ain't getting smaller! But I digress. Generally, laptop CPUs have much less silicon to save on power, so only mid-high end laptop CPUs will have all the good stuff. Desktop CPUs are different, basically any i3 from 2010 will have all that you need.

Quote
Perhaps "not installed" would be a more appropriate phrasing. Basically, running Armory by doing:

You can 'sudo make install' after building from source.

calebcjh (OP)
Newbie
*
Offline Offline

Activity: 16
Merit: 0


View Profile
November 24, 2017, 02:04:31 AM
 #8

Just use the noasm builds. If you're looking to update, you'll need a stronger CPU anyways (seeing you're going online with this machine), blockchain ain't getting smaller! But I digress. Generally, laptop CPUs have much less silicon to save on power, so only mid-high end laptop CPUs will have all the good stuff. Desktop CPUs are different, basically any i3 from 2010 will have all that you need.

Got it. Thanks

Quote
You can 'sudo make install' after building from source.

That does not work, the installed version crashes (did that in my first post, for v0.96.3 branch and testing branch). Or maybe I did something wrong or got confused.
goatpig
Moderator
Legendary
*
Offline Offline

Activity: 3668
Merit: 1345

Armory Developer


View Profile
November 24, 2017, 03:19:22 PM
 #9

That does not work, the installed version crashes (did that in my first post, for v0.96.3 branch and testing branch). Or maybe I did something wrong or got confused.

You'd want to do that on the binaries you built from source.

Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!