Closed ksedgwic closed 7 months ago
Hm, very interesting. The logs do not show any backtrace, which I would have expected in the journald
logs. Do you happen to have a core
file somewhere on that system that might tell us more about what happened?
I do not see crash logs associated with this event, and do see them in other cases
Saw it again, log has 5 min before and 5 after: 2024-02-21-home4-journalctl.log
And no crash logs
If you set the --log-level
to io
you should be able to see all messages being sent between the various processes. I wonder what the last thing coming into the pay
plugin was. It might be malformed somehow, and cause a crash that way?
I have a core dump for a similar crash but I might need sometime to generate the backtrace from it. If it would be helpful I can provide the core dump for now.
I have a core dump for a similar crash but I might need sometime to generate the backtrace from it. If it would be helpful I can provide the core dump for now.
Yes this will be very helpful thanks
docker container exec lightningd-test gdb --batch -ex "file /usr/libexec/c-lightning/plugins/pay" -ex "core-file /home/lightning/.lightning/testnet/core" -ex "bt"
[New LWP 22]
warning: Section `.reg-xstate/22' in core file too small.
Core was generated by `/usr/libexec/c-lightning/plugins/pay'.
Program terminated with signal SIGSEGV, Segmentation fault.
warning: Section `.reg-xstate/22' in core file too small.
#0 0x00007f4d3dcdee1f in ?? () from /lib/ld-musl-x86_64.so.1
#0 0x00007f4d3dcdee1f in ?? () from /lib/ld-musl-x86_64.so.1
Backtrace stopped: Cannot access memory at address 0x7ffd18c38ff0
The container uses alpine docker image not sure if it bothers gdb
Got a backtrace! plugin-pay-backtrace.txt
Hopefully the relevant state files: plugin-pay-state.tar.gz
Issue and Steps to Reproduce
Observed an unexpected restart, from the log:
Here is the log for the minute preceding, log was gathered using
journalctl
, should have all system services ... journalctl.logInstalled versions:
The
lightning
version isv23.11
plus 16 VLS mods (mostly hacks to allow integration tests to work w/ VLS)