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.

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]: Neutrino-using node is not seeing a channel open #9185

Open
jamessullivan2285 opened this issue Oct 14, 2024 · 0 comments
Open

[bug]: Neutrino-using node is not seeing a channel open #9185

jamessullivan2285 opened this issue Oct 14, 2024 · 0 comments
Labels
bug Unintended code behaviour needs triage

Comments

@jamessullivan2285
Copy link

jamessullivan2285 commented Oct 14, 2024

Background

My neutrino-using node is not seeing a channel open, with the channel stuck in pending state, even though the transaction has confirmed. --reset-wallet-transactions seems to fail with the following:

2024-10-14 14:58:26.841 [WRN] LNWL: Query(0) from peer <redacted>:8333 failed, rescheduling: did not get response before timeout
2024-10-14 14:58:30.841 [WRN] LNWL: Query(0) from peer <redacted>:8333 failed and reached maximum number of retries, not rescheduling: did not get response before timeout
2024-10-14 14:58:30.842 [ERR] LNWL: Neutrino rescan ended with error: did not get response before timeout
[Neutrino]
neutrino.connect=<redacted>
neutrino.persistfilters=false # I previously had this set to true and tried turning it off. No difference.

The node in question works fine. So I don't understand why the neutrino rescan fails. Also connecting to other neutrino nodes fails as well with the same error message.

$ lncli neutrino status
{
    "active":  true,
    "synced":  true,
    "block_height":  865614,
    "block_hash":  "0000000000000000000052580442928bbfaa1fd4b08d7620ae9bfd092d7cbbfd",
    "peers":  [
        "<redacted>:8333"
    ]
}

Your environment

  • lnd version 0.18.3-beta commit=v0.18.3-beta
  • Linux btc 6.1.75-1.qubes.fc32.x86_64 #1 SMP PREEMPT_DYNAMIC Mon Feb 5 06:49:25 CET 2024 x86_64 GNU/Linux

Steps to reproduce

Unclear.

@jamessullivan2285 jamessullivan2285 added bug Unintended code behaviour needs triage labels Oct 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Unintended code behaviour needs triage
Projects
None yet
Development

No branches or pull requests

1 participant