Unexpected listpeers

Question

Unexpected listpeers

Opened this issue 6 months ago · 8 comments

I am running clboss df51d54 with cln version v24.05 possible compatibility issue with use of listpeers

2024-06-12T12:11:45.672Z **BROKEN** plugin-clboss: NodeBalanceSwapper: Unexpected listpeers: [\n\t{\n\t\t\"id\" : \"028ec70462207b57e3d4d9332d9e0aee676c92d89b7c9fb0850fc2a248
14d4d83c\",\n\t\t\"connected\" : true,\n\t\t\"num_channels\" : 0,\n\t\t\"netaddr\" : [\n\t\t\t\"71.171.123.161:9735\"\n\t\t],\n\t\t\"features\" : \"80000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000200088825161\"\n\t},\n\t{\n\t\t\"id\" : \"02312627fdf0
7fbdd7e5ddb136611bdde9b00d26821d14d94891395452f67af248\",\n\t\t\"connected\" : true,\n\t\t\"num_channels\" : 0,\n\t\t\"netaddr\" : [\n\t\t\t\"23.237.77.12:9735\"\n\t\t],\n\t\
t\"features\" : \"800000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000002000888252
a1\"\n\t}\n]
2024-06-12T12:11:45.672Z **BROKEN** plugin-clboss: EarningsRebalancer: Unexpected result from listpeers: [\n\t{\n\t\t\"id\" : \"028ec70462207b57e3d4d9332d9e0aee676c92d89b7c9f
b0850fc2a24814d4d83c\",\n\t\t\"connected\" : true,\n\t\t\"num_channels\" : 0,\n\t\t\"netaddr\" : [\n\t\t\t\"71.171.123.161:9735\"\n\t\t],\n\t\t\"features\" : \"80000000000000
000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000200088825161\"\n\t},\n\t{\n\t\t\"id\" : \"
02312627fdf07fbdd7e5ddb136611bdde9b00d26821d14d94891395452f67af248\",\n\t\t\"connected\" : true,\n\t\t\"num_channels\" : 0,\n\t\t\"netaddr\" : [\n\t\t\t\"23.237.77.12:9735\"\
n\t\t],\n\t\t\"features\" : \"800000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
002000888252a1\"\n\t}\n]

btchans commented 6 months ago

same here

Answer 1 · 2024-06-15T15:24:32.000Z

I'm also seeing these, but they only happened during the initial channel creation and don't seem to occur in the weeks afterwards.

@king-11 @btchans Were your occurrences during initial channel creation?

Answer 2 · 2024-06-15T19:18:24.000Z

I started a draft PR to debug / fix this problem. For starters it improves the diagnostics in the error case we are seeing. #215

Answer 3 · 2024-06-17T15:09:39.000Z

Yes am seeing it on a newly created node.

Answer 4 · 2024-06-17T18:37:27.000Z

I added some diagnostic improvements to clarify this situation: #215

I expected to see them in action in the new node I spun up 2 days ago but haven't seen the improved diagnostics yet. I think we should merge the improved diagnostics and keep an eye out for future occurrences.

There are some "blind" fixes I can make guessing at what is actually wrong, but I'd prefer to improve diagnostics first and then fix documented problems

Answer 5 · 2024-08-03T06:17:11.000Z

@eltoo-cln @btchans you can probably try https://github.com/vincenzopalazzo/clboss/tree/v0.14.0-rc1 it fixed things for me

Answer 6 · 2024-08-11T04:15:24.000Z

I'm seeing these on my node also.

2024-08-02T04:17:32.133Z **BROKEN** plugin-clboss: EarningsRebalancer: Unexpected result from listpeers: [\n\t{\n\t\t\"id\" : \"<redacted id>\",\n\t\t\"connected\" : true,\n\t\t\"num_channels\" : 0,\n\t\t\"netaddr\" : [\n\t\t\t\"<redacted ip address>\"\n\t\t],\n\t\t\"features\" : \"800000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000002000888a52a1\"\n\t},\n\t{\n\t\t\"id\" : \"<redacted id>\",\n\t\t\"connected\" : true,\n\t\t\"num_channels\" : 0,\n\t\t\"netaddr\" : [\n\t\t\t\"<redacted ip>:9735\"\n\t\t],\n\t\t\"features\" : \"800000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000002000888a52a1\"\n\t},\n\t{\n\t\t\"id\" : \"<redacted node id>\",\n\t\t\"connected\" : true,\n\t\t\"num_channels\" : 0,\n\t\t\"netaddr\" : [\n\t\t\t\"<redacted ip address>:9735\"\n\t\t],\n\t\t\"features\" : \"800000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000002000808252a1\"\n\t},\n\t{\n\t\t\"id\" : \"<redacted id>\",\n\t\t\"connected\" : true,\n\t\t\"num_channels\" : 1,\n\t\t\"netaddr\" : [\n\t\t\t\"<redacted ip addr>:9735\"\n\t\t],\n\t\t\"remote_addr\" : \"<redacted ip addr>:55544\",\n\t\t\"features\" : \"08a0000a8a59a1\"\n\t}\n]

Answer 7 · 2024-08-12T07:29:24.000Z

@niftynei This should be fixed by the latest release, what version are you running?

I think @ksedgwic made the correct version in cln of my branch #214 (comment)