-
Notifications
You must be signed in to change notification settings - Fork 912
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
v23.05 gossipd related crash #6270
Comments
This is a weird one. How long was your node up before this happened? |
Host uptime is 6 days so probably a bit less than that. |
Reported in ElementsProject#6270, there was an attempt to delete gossip overrunning the end of the gossip_store. This logs the gossip type that was attempted to be deleted and avoids an immediate crash (tombstones would be fine to skip over at least.) Changelog-None
@grubles, is it possible to have the gossip file in some way? I would like to take a look at it |
Reported in ElementsProject#6270, there was an attempt to delete gossip overrunning the end of the gossip_store. This logs the gossip type that was attempted to be deleted and avoids an immediate crash (tombstones would be fine to skip over at least.) Changelog-None
Max file size for github is 25 MB and the gossip store is 41 MB. Know of a place I can upload to? |
Maybe on google drive or something similar? |
Reported in #6270, there was an attempt to delete gossip overrunning the end of the gossip_store. This logs the gossip type that was attempted to be deleted and avoids an immediate crash (tombstones would be fine to skip over at least.) Changelog-None
Reported in ElementsProject#6270, there was an attempt to delete gossip overrunning the end of the gossip_store. This logs the gossip type that was attempted to be deleted and avoids an immediate crash (tombstones would be fine to skip over at least.) Changelog-None
Thanks! Ok, this looks literally impossible: ... The record is indeed at 58913714. The pread call should not fail. Are you on some weird filesystem?
|
We no longer crash on this, though we haven't root-caused it. So I'm closing, given we worked around it in master. |
OS: Rocky Linux 9 ppc64le
CLN v23.05
The text was updated successfully, but these errors were encountered: