-
Notifications
You must be signed in to change notification settings - Fork 907
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
gossipd spamming log, lightning_connectd eating all upload #7899
Comments
Probably related, alias are gone.
|
Thanks for the report!
We ask a random peer for all its gossip once an hour now. So your node should get gossip pretty fast. |
See: ElementsProject#7899 A node with 23 connections gets far too many debug messages. Changelog-Fixed: `gossipd` now does logging at trace, not debug level. Signed-off-by: Rusty Russell <[email protected]>
I get these:
|
Thank you for your software! These are the relevant parts I believe. Note that this rc2 had been running for 2 days, it did not happen right after updating.
gossip_store was getting bigger and bigger so yesterday I started a new one. Now it is 70M and looks like output of listnodes is now normal.
Can I set limits on this? The amount of data I was sending was definitely too much. BTW this is over, it stopped overnight. |
Issue and Steps to Reproduce
Noticed this today after upgrading to v24.11rc2 a couple of days ago.
Symptoms:
other outputs
The text was updated successfully, but these errors were encountered: