Lisk-sdk: Segmentation fault

[lrestagno]

Expected behavior

node app.js to start

Actual behavior

Segmentation fault (core dumped)

Steps to reproduce

Execute all the steps required to run lisk, run node app.js at the end

Which version(s) does this affect? (Environment, OS, etc...)

Ubuntu Server 18.04 guest VM, 1GB RAM, 1 core CPU

[pcdinh]

Which Node did you use?

[ikoichi]

I am using node v6.14.1

[nazarhussain]

@ikoichi I use the same node version, but didn't face this issue.

➜  lisk git:(master) ✗ node -v
v6.14.1

How did you installed it? Compiled from source or used binary distribution?

[lrestagno]

@nazarhussain I compiled everything from source, following the instructions of the main README file of the repo. I am running Ubuntu (and Debian, I tried both) on a guest virtual machine using VirtualBox.
Ubuntu 18.04
Debian 9 Stretch

Both OS result with the same Segmentation Fault issue.
I tried using a cloud server with Ubuntu Xenial and it worked, therefore I suppose it is something related to VirtualBox and not to lisk itself.

[fchavant]

I can reproduce the segfault by building from source on Ubuntu 18.04 LTS using nodejs 6.14.1.
@lrestagno we recommend building on Ubuntu 14.04 LTS at the moment.

[Nazgolze]

It works for me if node is installed with nvm
Looking at node.js's website, installing through the package manager is unsupported in Ubuntu 18.04
https://nodejs.org/en/download/package-manager/#debian-and-ubuntu-based-linux-distributions

It doesn't even mention node 6. I bet that's not supported either on either Ubuntu 18.04 or Debian 9 Stretch

Possible options:

• Going the nvm or n route is
• Download and install nodejs from here https://nodejs.org/en/download/releases/

[Nazgolze]

The README should be updated as well as the documentation :)

[Nazgolze]

https://github.com/LiskHQ/lisk/issues/2128