-
Notifications
You must be signed in to change notification settings - Fork 6
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
lightningd crashes with folgore #88
Comments
can you post also your lightning configuration? or command line? I need to see what kind of configuration are you using P.S: probably nakamoto? Thanks, |
This is my config:
|
Running with debug logging, will update here when it crashes. |
Keep me posted, in this way, we try to reproduce. I will run also mine with Nakamoto for a bit |
@vincenzopalazzo Can we nudge it to spawn more processes? Maybe the crashing might be related to CPU exhaustion? How to I make it spawn two more processes so it again utilizes all 4 cores that system has? It is sitting on 2 cores 100% this time.. I would like to push it to 4 cores again... |
You can't because folgore is a single process (maybe with nakamoto no because it required to be spawn) If folgore is consuming the 100 CPU usually means that it is not attached to any cor lightning instance, and the only thing that you can do is kill it |
We have another crash, here is end of the log:
|
thanks for reporting, any rust logs somewhere? I think the plugin crashed for some reason. However, I want to take a look at it. Are you on Mainet? |
Yes mainnet. |
another crash, but I think there's not much new in these logs
|
To see the rust backtrace you should enable the env variable before running lightningd
I see, sorry for this experience, idk why you are using nakamoto on mainet, it required some iteration as the readme claims, but you can use other backend like esplora or bitcoin core in prune mode with nakamoto as fallback backend. |
Not sure if this is the same problem as this #87 ?
This is end of my lightningd crashlog:
The text was updated successfully, but these errors were encountered: