lighthouse: tokio-runtime segfault

Description

I encountered some db corruption and I believe the root cause is lighthouse crashes regularly due to an issue with the tokio runtime. I’m continuing to debug. One concern is that the VPS I am running on doesn’t have stellar stability reviews. I’m wondering if that is causing the runtime to go awry. However, I have managed to maintain 100% uptime on my go-ethereum nodes.

Version

I’ve run into this issue on both 5828ff1, v1.0, and v1.0.1.

Present Behaviour

The tokio-runtime segfaults after a period of time:

tokio-runtime-w[3460]: segfault at 470ba01feea ip 00005641f1424f1b sp 00007f59e8ee21f8 error 6 in lighthouse[5641ef75e000+1d9e000]

About this issue

Original URL
State: closed
Created 4 years ago
Reactions: 3
Comments: 15 (15 by maintainers)

Most upvoted comments

I’m running on Contabo VPS.

$ ./slabbed-or-not
Not running under any known container type
Hypervisor: KVM

I’ll keep an eye for the Tokio 0.3 release 😃

lightclient on Nov 27, 2020

@pawanjay176 I’ve run all of the following: 5828ff1, v1.0 (c6baa0e) , v1.0.1 (5a3b94cb), cut-v1.0.2 (2383bfe), and v1.0.2 (f718309).

lightclient on Nov 30, 2020