-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
[bug]: Channels are disconnected after an "unknown message" error #7273
Comments
@ekimber, is this the full log line? |
The disconnect seems to be from something else:
We'll parse unknown messages and just ignore them and have for some time now. If you run w/ the trace debug level, then you'll be able to see the message itself. We should update this log to print useful info tho: Line 138 in c03de26
|
@ellemouton The message type is @Roasbeef So I am guessing that ignoring the message is somehow causing the peer to disconnect because it happens right after the unknown message. What module do I need to run with trace level to see the message itself? It does not log the messages with PEER set to trace. |
I believe the reason I do not see the message in the logs is because in |
Could this be related to #7290? Is your peer a cln node? |
@ekimber you can try the following patch to see the warning message:
|
@yaslama I suspect that I am seeing the same issue. Thanks for the patch, however, I do stick to a policy of only running released binaries on mainnet |
I (CLN 22.11.1) have a LND peer (v0.15.5-beta) who executed the SCB. My node received the invalid revocation number but somehow it did not automatically fire the force close, I guess because the connection was terminated by "unknow message" error. in my log
in his log
|
Thanks for all the info y'all! I think we traced things down to a CLN change that modified behavior to send a warning then close the connection after they get the bad chan reest message. Because they close the connection, this means they might not actually read our incoming We're looking into a workaround that should allow things to work as normal no matter which implementation/version we're connected to. |
If you are experiencing this issue on
If you are uncomfortable with using my personal branch and would instead prefer a temporary release, please let us know. Or if you don't know how to perform any of the steps above, leave a comment and I can help out. |
Background
Channels with core lightning nodes (most recent 22.11 version and master) frequently disconnect after an "unknown message" error
Your environment
lnd
0.15.5-betaSteps to reproduce
Dec 25 00:06:55 lnd[538311]: 2022-12-25 00:06:55.363 [INF] PEER: Peer(02e8f0717f412f455bbcafabc7119f3e3bc1e6c7efeff3df14c98f4da14278dc95): unable to read message from peer: unable to parse message of unknown> Dec 25 00:06:55 lnd[538311]: 2022-12-25 00:06:55.364 [INF] PEER: Peer(02e8f0717f412f455bbcafabc7119f3e3bc1e6c7efeff3df14c98f4da14278dc95): unable to read message from peer: EOF Dec 25 00:06:55 lnd[538311]: 2022-12-25 00:06:55.364 [INF] PEER: Peer(02e8f0717f412f455bbcafabc7119f3e3bc1e6c7efeff3df14c98f4da14278dc95): disconnecting 02e8f0717f412f455bbcafabc7119f3e3bc1e6c7efeff3df14c98f> Dec 25 00:06:55 lnd[538311]: 2022-12-25 00:06:55.364 [INF] NTFN: Cancelling epoch notification, epoch_id=6259
This happens frequently, perhaps several times in an hour.
Expected behaviour
Not disconnecting, or providing more information about the parse error so that it might be investigated
Actual behaviour
Peers frequently disconnect. I cannot exclude the possibility that some of them are LND peers but so far I have identified two of them as core lightning nodes
The text was updated successfully, but these errors were encountered: