Skip to content
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

Open
charlespetchsy opened this issue Oct 18, 2021 · 3 comments
Open

Segmentation Violation #59

charlespetchsy opened this issue Oct 18, 2021 · 3 comments

Comments

@charlespetchsy
Copy link

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:

I[2021-10-18|17:44:22.118] Finished LND Monitor
I[2021-10-18|17:44:22.119] BTC Height record is 0, waiting for update from btc chain...
2021-10-18 17:44:51.250 [ERR] SRVR: Unable to connect to 025b48f844b6b639ebcf807dedffb8deb84f3f8c494967ecb6cc4203df2dfc4fa1@217.173.236.78:17735: EOF
2021-10-18 17:44:51.250 [ERR] SRVR: Unable to connect to 025b48f844b6b639ebcf807dedffb8deb84f3f8c494967ecb6cc4203df2dfc4fa1@217.173.236.78:17735: EOF
I[2021-10-18|17:44:51.458] StakeIdentity state loading...
I[2021-10-18|17:45:21.458] StakeIdentity state loading...
I[2021-10-18|17:45:21.482] Executed block                               module=state height=6 validTxs=0 invalidTxs=0
I[2021-10-18|17:45:21.483] Committed state                              module=state height=6 txs=0 appHash=0A00000000000000
I[2021-10-18|17:45:21.483] aggregation threads stopped
I[2021-10-18|17:45:21.483] Retrieved aggregation tree of 0 items and resetting
I[2021-10-18|17:45:21.483] Starting LND Monitor...
I[2021-10-18|17:45:21.488] LND state retrieved currHeight: 0 vs newHeight: 2099637
I[2021-10-18|17:45:21.488] New Blocks detected from LND
I[2021-10-18|17:45:21.488] New BTC Block 2099637
I[2021-10-18|17:45:21.488] Finished LND Monitor
2021-10-18 17:45:30.460 [ERR] BTCN: Unable to parse IP network for peer 4zhkir2ofl7orfom.onion:18333: unsupported IP type
2021/10/18 17:45:31 http: TLS handshake error from 91.232.30.115:35222: EOF
2021-10-18 17:45:34.271 [ERR] SRVR: Unable to connect to 027a392be63e3057609931b0cc8fdc90b2913796f97e0ab366417cd3c87d459150@217.173.236.78:12735: EOF
2021-10-18 17:45:34.271 [ERR] SRVR: Unable to connect to 027a392be63e3057609931b0cc8fdc90b2913796f97e0ab366417cd3c87d459150@217.173.236.78:12735: EOF
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x30 pc=0x545ba6]

goroutine 67 [running]:
crypto/elliptic.Marshal(0x0, 0x0, 0x0, 0x0, 0x2c595e0, 0x5, 0xc000eb0870)
	/home/charles/.go/src/crypto/elliptic/elliptic.go:316 +0x26
github.com/chainpoint/chainpoint-core/abci.(*AnchorApplication).StakeIdentity(0xc000e26f00)
	/home/charles/chainpoint-core/abci/tasks.go:79 +0x325
created by github.com/chainpoint/chainpoint-core/abci.NewAnchorApplication
	/home/charles/chainpoint-core/abci/abci.go:171 +0x97a

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

@jacohend
Copy link
Collaborator

Hi @charlespetchsy,

I've just hotfixed a bug for newly initialized cores in the latest version master. Try that and let me know.

@charlespetchsy
Copy link
Author

charlespetchsy commented Oct 18, 2021

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:

2021-10-18 18:59:43.111 [ERR] DISC: Unable to query bootstrapper BOLT-0010 DNS Seed: [[test.nodes.lightning.directory soa.nodes.lightning.directory]]: lookup ln1q0hg8mp9l3pu78tg80j8l40z4suhzwjgnvpla4p4pktz80sl7rvpw86qccj.test.nodes.lightning.directory.: Temporary failure in name resolution
2021-10-18 18:59:43.111 [ERR] SRVR: Unable to retrieve initial bootstrap peers: no addresses found
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x30 pc=0x545ba6]

goroutine 65 [running]:
crypto/elliptic.Marshal(0x0, 0x0, 0x0, 0x0, 0x2c595e0, 0x5, 0xc000ec3cb0)
	/home/charles/.go/src/crypto/elliptic/elliptic.go:316 +0x26
github.com/chainpoint/chainpoint-core/abci.(*AnchorApplication).StakeIdentity(0xc000e92f00)
	/home/charles/chainpoint-core/abci/tasks.go:79 +0x325
created by github.com/chainpoint/chainpoint-core/abci.NewAnchorApplication
	/home/charles/chainpoint-core/abci/abci.go:171 +0x97a

There are also two errors in the console and was wondering how this can be resolved?

E[2021-10-18|18:57:18.667] Error in github.com/chainpoint/chainpoint-core/tendermint_rpc.(*RPC).GetStatus: Status: Post failed: Post "http://127.0.0.1:26657": dial tcp 127.0.0.1:26657: connect: connection refused

and

E[2021-10-18|18:58:19.377] Error in github.com/chainpoint/chainpoint-core/anchor/bitcoin.(*AnchorBTC).BlockSyncMonitor: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp 127.0.0.1:10009: connect: connection refused"

Netstat

I have all the necessary ports open and this is what my network looks like with the chainpoint services:

Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 0.0.0.0:8080            0.0.0.0:*               LISTEN      26405/chainpoint-co
tcp        0      0 0.0.0.0:10009           0.0.0.0:*               LISTEN      26405/chainpoint-co
tcp6       0      0 :::9735                 :::*                    LISTEN      26405/chainpoint-co
tcp6       0      0 :::80                   :::*                    LISTEN      26405/chainpoint-co
tcp6       0      0 :::26656                :::*                    LISTEN      26405/chainpoint-co
tcp6       0      0 :::26657                :::*                    LISTEN      26405/chainpoint-co

Edit: Added reply quote

@jacohend
Copy link
Collaborator

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 ~/.chainpoint/core/data/keys/ecdsa_key.pem. I've also pushed another update which should hopefully address this issue in cases where the node hasn't fully initialized yet. Private nodes haven't yet been a big priority, so thanks for working with us on this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants