BUG: Paloma crashes with fatal error: unexpected signal during runtime execution signal SIGSEGV: segmentation violation

[taariq]

What is happening?

Section description

Provide as much context as you can. Provide relevant software versions, screenshots, copy & paste error messages and so on. Give as much context as you can to make it easier for the developers to figure what is happening.

Paloma crashes with fatal error: unexpected signal during runtime execution Sep 13 18:04:08 n6d1174 palomad[169399]: [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x7f78eef707fb]

Error logs and config files are here: https://gist.github.com/kj89/2ac4ee6e2484ab5620f3c81a1948a2a7

How to reproduce?

Section description

Please write detailed steps of what you were doing for this bug to appear.

No repro at this ticket.

What is the expected behaviour?

Section description

If you know, please write down what is the expected behaviour. If you don't know, that's ok. We can have a discussion in comments.

LevelDB should function.

[k4b3z4]

Error logs and config from FedNet node:

https://gist.github.com/k4b3z4/19fd601071535117594f5ec7c9ee2597

[taariq]

@Vizualni feedback has been that this is LevelDB issue and recommendations are that we switch over to https://dgraph.io/docs/badger/ as it is written in go.

1. Change makefile
2. Change config.toml

[Vizualni]

@taariq I am seeing that badgerdb is still in experimental phase (can be found in ~/.paloma/config/config.toml. It doesn't really scream confidence when I read this.

[taariq]

Closing as we will stick with leveldb for now. Unsafe reset for validators to fix.

[taariq]

We are seeing these again.

[taariq]

Closing until we see them again.