You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Seid version
name: sei
server_name:
version: v4.1.7-evm-devnet
commit: 6e0c934
build_tags: netgo ledger,
go: go version go1.22.4 linux/amd64
build_deps:
cosmossdk.io/errors@v1.0.0
filippo.io/edwards25519@v1.0.0-rc.1
github.com/99designs/keyring@v1.2.1
Chain ID
Local 4-docker-node chain
Describe the bug
I changed the value of node-key-file in the config.toml file to a path that does not contain the node key file. After restarting the node, it panicked during runtime with the error: panic: runtime error: invalid memory address or nil pointer dereference.
To Reproduce
Steps to reproduce the behavior:
Changed the value of node-key-file in the config.toml file to a path that does not contain the node key file
Expected behavior
SEI should properly handle exceptions related to the node-key-file and provide users with a friendly error message, rather than panicking at runtime.
Screenshots
Here is the code snippet with the bug:
Additional context
Here is the panic log. seid-3.log
Seid version
name: sei
server_name:
version: v4.1.7-evm-devnet
commit: 6e0c934
build_tags: netgo ledger,
go: go version go1.22.4 linux/amd64
build_deps:
Chain ID
Local 4-docker-node chain
Describe the bug
I changed the value of
node-key-file
in the config.toml file to a path that does not contain the node key file. After restarting the node, it panicked during runtime with the error:panic: runtime error: invalid memory address or nil pointer dereference
.To Reproduce
Steps to reproduce the behavior:
node-key-file
in the config.toml file to a path that does not contain the node key filepanic: runtime error: invalid memory address or nil pointer dereference
occurExpected behavior
SEI should properly handle exceptions related to the
node-key-file
and provide users with a friendly error message, rather than panicking at runtime.Screenshots

Here is the code snippet with the bug:
Additional context
Here is the panic log.
seid-3.log
Here is the config file
The text was updated successfully, but these errors were encountered: