Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Fix scary INFO message on first connection to peer after startup #6140

Merged
merged 2 commits into from
Apr 5, 2023
Merged

Fix scary INFO message on first connection to peer after startup #6140

merged 2 commits into from
Apr 5, 2023

Commits on Apr 3, 2023

  1. pytest: add connection test for gratuitous transient failure message. 

    [Cleaned up a little to avoid the case where both sides race to reconnect --RR ]
    @m-schmoock @rustyrussell
    m-schmoock authored and rustyrussell committed Apr 3, 2023
    Configuration menu
    Copy the full SHA
    91fdee0 View commit details
    Browse the repository at this point in the history

  2. channel: don't log scary disconnect message on unowned channels. 

    We always call channel_fail_transient() on all channels when a peer
connects, to clean up any previous connections.  However, when
we startup, this channel doesn't have an owner yet, resulting in
a fairly weird INFO level message.

Reported-by: Michael Schmook @mschmook
Signed-off-by: Rusty Russell <[email protected]>
Changelog-Fixed: `lightningd`: don't log gratuitous "Peer transient failure" message on first connection after restart.
    @rustyrussell
    rustyrussell committed Apr 3, 2023
    Configuration menu
    Copy the full SHA
    4f3cfd7 View commit details
    Browse the repository at this point in the history