-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Segmentation Violation #59
Comments
Hi @charlespetchsy, I've just hotfixed a bug for newly initialized cores in the latest version master. Try that and let me know. |
I'm getting a new error combined with the original segmentation violation:
There are also two errors in the console and was wondering how this can be resolved?
and
NetstatI have all the necessary ports open and this is what my network looks like with the chainpoint services:
Edit: Added reply quote |
The last two errors will resolve themselves as the API and LND node come online. As for the first error, be sure that there's a keyfile at |
Hello,
I recently went through the quick start section of the guide in the
README.md
and after setting it up and trying to run the core on my local VM, I get the following error after it provides me the committed state:Am I missing something here?
VM Specs
OS: Ubuntu 20.04.3 LTS (Linux ubuntu 5.4.0-88-generic)
IPv4: I'm using my private network for testing
CPU: 4 cores
RAM: 8 GB
Disk: 256 GB
The text was updated successfully, but these errors were encountered: