#Hey, our node is segfaulting right after

1 messages · Page 1 of 1 (latest)

gusty yew
# 
Nov 12 16:10:31 namada[790623]: 2024-11-12T16:10:31.133421Z  INFO namada_node::storage::rocksdb: Using 12 compactions threads for RocksDB.
Nov 12 16:10:31 namada[790623]: 2024-11-12T16:10:31.134314Z DEBUG namada_node::storage::rocksdb::imp: Current NOFILE limit, soft=65535, hard=65535
Nov 12 16:10:31 namada[790623]: 2024-11-12T16:10:31.134323Z DEBUG namada_node::storage::rocksdb::imp: NOFILE limit already large enough, not attempting to increase
Nov 12 16:10:31 namada[790623]: 2024-11-12T16:10:31.153128Z  INFO namada_node::broadcaster: Starting broadcaster.
Nov 12 16:10:31 namada[790623]: 2024-11-12T16:10:31.153157Z DEBUG tendermint_rpc::client::transport::http: outgoing request url=http://127.0.0.1:26657/ body={
Nov 12 16:10:31 namada[790623]:   "jsonrpc": "2.0",
Nov 12 16:10:31 namada[790623]:   "id": "6e6a93d5-6f4e-4cb8-b299-55c51e09903d",
Nov 12 16:10:31 namada[790623]:   "method": "status",
Nov 12 16:10:31 namada[790623]:   "params": null
Nov 12 16:10:31 namada[790623]: }
Nov 12 16:10:31 namada[790623]: 2024-11-12T16:10:31.153237Z DEBUG reqwest::connect: starting new connection: http://127.0.0.1:26657/
Nov 12 16:10:31 namada[790623]: 2024-11-12T16:10:31.153259Z DEBUG hyper::client::connect::http: connecting to 127.0.0.1:26657
Nov 12 16:10:32 systemd[1]: namada.service: Main process exited, code=killed, status=11/SEGV```
inner remnant
#

hmm I've not seen that

worn knot
#

and your basic vps spec

gusty yew
#

hmm, nvm, looks like it is an issue with our build system as with upstream binaries it seems to work...

inner remnant
#

you can try cargo clean, making sure you're on the right branch, are you building with --release?

gusty yew
#

we just run make build-release but this runs on CI not on the target machine where we run the node, so will have to dig into it what is the issue. We faced similar thing with one other chain before.

inner remnant