Can't remove remote watchtower that is reporting error "StateUpdateCodeSeqNumOutOfOrder in StateUpdateReply for seqnum=1021". #6397
Assignees
Labels
Comments
|
We definitely need more control over towers and a few bug fixes too in that area. |
|
Removing wtclient.db fixed the problem. |
|
Hi, I've been having this issue for awhile myself, I can provide logs if at all helpful. Main issue for me is not being able to remove a faulty/offline tower, error: |
|
@knox203 - what version of LND are you running? |
Currently running v0.17.0-beta. |
|
hmm ok - could you please provide some extra logs @knox203 ? This should have been fixed with the last release |
Hey @ellemouton, sorry about the delay. One additional thing I should mention is that the problematic tower in question went down a long time ago (used to be the public lightningnetwork.plus tower service). Here are some logs, I filtered out all the duplicates. It seems to repeat the The logs don't look particularly useful to me, but hopefully something may stick out to you! |
|
@knox203 - are these logs taken from the time where you are calling "Remove Tower"? |
Running: Returns: And in the log I see: |
|
@knox203 - do you see any logs (after the
Also, does this "tower has unacked updates" error appear consistently? ie, if you retry the call, does it still fail with that? |
|
ahhh ok I think i might know why this could happen. Gonna investigate a bit more & try re-produce & fix 👍 |
@ellemouton,
That's great to hear! Please let me know if there's anything else I can provide or do to assist. Thanks! |
|
That's great to hear, thanks for the update and hard work, Elle! It's
greatly appreciated -- I'll look forward to the new version.
…On Thu, Jan 11, 2024, 11:51 PM Elle ***@***.***> wrote:
@knox203 <https://github.com/knox203> - the fix for the issue you were
seeing has been merged in #8233
<#8233> & so should fix your
problem in the next release :)
—
Reply to this email directly, view it on GitHub
<#6397 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AVZJMBHOL2ZD6JMGPIIY6XTYODTQTAVCNFSM5S3CQO52U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOBYHA2TQOJWGU2Q>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Hi all, Once #8239 makes it into a release (likely 0.18.0), then if you experience something like this issue (the OG issue here from the OP), you should be able to manually terminate the problem session using the new Please comment here if the issue persists (once 0.18.0 has been released and the new command has been tried) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Background
Remote watchtower has Sequence number error and no longer accepting updates.
2022-04-08 11:01:58.104 [WRN] WTCL: (legacy) SessionQueue(02b72d81698744befe8326d24068213a5c01e57d3c0aa624e40b7b3eb096e4f298) unable to upload state update to tower=02d651a0e8ca200c2b6933029044ff75dafe44363cfc58b8c41de0bbcd7b1150f7@212.86.32.106:9911: received error code StateUpdateCodeSeqNumOutOfOrder in StateUpdateReply for seqnum=1021
2022-04-08 11:01:58.104 [ERR] WTCL: (legacy) SessionQueue(02b72d81698744befe8326d24068213a5c01e57d3c0aa624e40b7b3eb096e4f298) unable to send state update: received error code StateUpdateCodeSeqNumOutOfOrder in StateUpdateReply for seqnum=1021
Trying to remove the misbehaving watchtower gives the following error:
lightning@Lightning:~$ lncli wtclient remove 02d651a0e8ca200c2b6933029044ff75dafe44363cfc58b8c41de0bbcd7b1150f7
[lncli] rpc error: code = Unknown desc = tower has unacked updates
Your environment
version of
lndLND 0.14.2-beta
which operating system (
uname -aon *Nix)Ubuntu 20.04LTS
version of
btcd,bitcoind, or other backendBitcoin Core 22.0
Watchtower no longer accepting channel state updates. Can't remove the misbehaving watchtower. LND only uses the first watchtower in the list, so the other watchtowers aren't being used, so, not being able to remove the misbehaving watchtower, leaves me with no watchtower support.
List of watchtowers I have.
{
"towers": [
{
"pubkey": "02d651a0e8ca200c2b6933029044ff75dafe44363cfc58b8c41de0bbcd7b1150f7",
"addresses": [
"212.86.32.106:9911"
],
"active_session_candidate": true,
"num_sessions": 45,
"sessions": [
]
},
{
"pubkey": "03ab82d182a7a2f2a0ecbb0c73ff35adf2211b3adc5cf83cd5b5781cd6c168b4a8",
"addresses": [
"173.50.76.53:9911"
],
"active_session_candidate": true,
"num_sessions": 0,
"sessions": [
]
},
{
"pubkey": "0201fb7bc85498408b1b3d915b1a7af18e189bcbdb0b608870555d7ca7c529b153",
"addresses": [
"177.204.239.6:9911"
],
"active_session_candidate": true,
"num_sessions": 0,
"sessions": [
]
}
]
}
The text was updated successfully, but these errors were encountered: