search

lightningnetwork / lnd

Lightning Network Daemon ⚡️
MIT License
7.69k stars 2.08k forks source link

[bug]: Channel opening show as pending open, despite transaction already being minet #8357

Open bvolution opened 9 months ago

bvolution commented 9 months ago

Background

I tried opening a channel via RTL, the channel is showing in pending open. lncli pendingchannels gives me the following output

    "pending_open_channels": [
        {
            "channel": {
                "remote_node_pub": "0243ed6aaee7d2dd05aaec629fc169b7aa0b113295339e67968b247764f8d31b98",
                "channel_point": "b0955d02a985fb4eeaf3bb87e3f378dfa90891e2c071402f2f63546b6a9f2136:0",
                "capacity": "500000",
                "local_balance": "485060",
                "remote_balance": "0",
                "local_chan_reserve_sat": "5000",
                "remote_chan_reserve_sat": "5000",
                "initiator": "INITIATOR_LOCAL",
                "commitment_type": "ANCHORS",
                "num_forwarding_packages": "0",
                "chan_status_flags": "",
                "private": false
            },
            "commit_fee": "14280",
            "commit_weight": "772",
            "fee_per_kw": "12705"
        }
    ],

However the transaction was already mined over 100 blocks ago https://mempool.space/de/tx/b0955d02a985fb4eeaf3bb87e3f378dfa90891e2c071402f2f63546b6a9f2136#vout=0

Your environment

Steps to reproduce

I am not quite sure, I just tried to open a channel via RTL it previously as well as afterwards worked fine.

ziggie1984 commented 9 months ago

can you check with lncli getinfo whether you are synced to chain ?

bvolution commented 9 months ago

Sure, looks good to me

{
    "version": "0.16.4-beta commit=v0.16.4-beta",
    "commit_hash": "6bd30047c1b1188029e8af6ee8a135cf86e7dc4b",
    "identity_pubkey": "020dc414b3d1853316d926496c6a226149a34dee021131620cf0a0dc498f8f4a5d",
    "alias": "b.volution",
    "color": "#68f442",
    "num_pending_channels": 1,
    "num_active_channels": 9,
    "num_inactive_channels": 0,
    "num_peers": 12,
    "block_height": 824960,
    "block_hash": "0000000000000000000064d5b82ff2f8252a3058e18d998583d7267a92b551e8",
    "best_header_timestamp": "1704782041",
    "synced_to_chain": true,
    "synced_to_graph": true,
    "testnet": false,
    "chains": [
        {
            "chain": "bitcoin",
            "network": "mainnet"
        }
    ],
    "uris": [
        "020dc414b3d1853316d926496c6a226149a34dee021131620cf0a0dc498f8f4a5d@159.69.32.62:21220",
        "020dc414b3d1853316d926496c6a226149a34dee021131620cf0a0dc498f8f4a5d@vsyaeazg5qssz3c54655cpuwt2vpwx2su3qnjbtb7sebaxcwjbwhdmad.onion:9735"
    ],
ziggie1984 commented 9 months ago

Can you check for the chan_point: b0955d02a985fb4eeaf3bb87e3f378dfa90891e2c071402f2f63546b6a9f2136:0 in your logs and see what the latest entries are for this channel ?

bvolution commented 9 months ago

Hi sure that are just the latest entries but it seem repetetive...

2024-01-09 22:00:38.555 [DBG] CNCT: ChannelArbitrator(b0955d02a985fb4eeaf3bb87e3f378dfa90891e2c071402f2f63546b6a9f2136:0): checking commit chain actions at height=825058, in_htlc_count=0, out_htlc_count=0
2024-01-09 22:00:38.556 [DBG] CNCT: ChannelArbitrator(b0955d02a985fb4eeaf3bb87e3f378dfa90891e2c071402f2f63546b6a9f2136:0): no actions for chain trigger, terminating
2024-01-09 22:00:38.556 [DBG] CNCT: ChannelArbitrator(b0955d02a985fb4eeaf3bb87e3f378dfa90891e2c071402f2f63546b6a9f2136:0): terminating at state=StateDefault
2024-01-09 22:02:02.373 [DBG] CNCT: ChannelArbitrator(b0955d02a985fb4eeaf3bb87e3f378dfa90891e2c071402f2f63546b6a9f2136:0): attempting state step with trigger=chainTrigger from state=StateDefault
2024-01-09 22:02:02.375 [DBG] CNCT: ChannelArbitrator(b0955d02a985fb4eeaf3bb87e3f378dfa90891e2c071402f2f63546b6a9f2136:0): new block (height=825059) examining active HTLC's
2024-01-09 22:02:02.375 [DBG] CNCT: ChannelArbitrator(b0955d02a985fb4eeaf3bb87e3f378dfa90891e2c071402f2f63546b6a9f2136:0): checking commit chain actions at height=825059, in_htlc_count=0, out_htlc_count=0
2024-01-09 22:02:02.375 [DBG] CNCT: ChannelArbitrator(b0955d02a985fb4eeaf3bb87e3f378dfa90891e2c071402f2f63546b6a9f2136:0): no actions for chain trigger, terminating
2024-01-09 22:02:02.375 [DBG] CNCT: ChannelArbitrator(b0955d02a985fb4eeaf3bb87e3f378dfa90891e2c071402f2f63546b6a9f2136:0): terminating at state=StateDefault
Roasbeef commented 9 months ago

Can you search for logs of NTFN?

yyforyongyu commented 9 months ago

Looked in onchain and it seems that b0955d02a985fb4eeaf3bb87e3f378dfa90891e2c071402f2f63546b6a9f2136 has two outputs, output 1 is used to create this funding tx, while output 0 is not used. I'd a bit confused why b0955d02a985fb4eeaf3bb87e3f378dfa90891e2c071402f2f63546b6a9f2136:0 is considered as a chan point - could you share more details about how this channel was created?

polespinasa commented 9 months ago

I think output 0 is the funding tx. As you can see is a P2WSH while output 1 is a P2TR. Moreover, the channel capacity is 500k sats, corresponding to output 0. So output 1 (P2TR) is just a normal change address to the on-chain wallet of the node.

bvolution commented 9 months ago

Can you search for logs of NTFN?

You mean in the lnd log? Sure here you go

admin@xx.xx.xx.xx:~ ₿ sudo cat /mnt/hdd/lnd/logs/bitcoin/mainnet/lnd.log | grep NTFN | head -n 10
2024-01-10 18:22:11.071 [INF] NTFN: New block epoch subscription
2024-01-10 18:22:27.174 [INF] NTFN: Cancelling epoch notification, epoch_id=109
2024-01-10 18:22:27.918 [INF] NTFN: New block epoch subscription
2024-01-10 18:34:46.594 [INF] NTFN: Cancelling epoch notification, epoch_id=110
2024-01-10 18:45:38.333 [INF] NTFN: New block epoch subscription
2024-01-10 18:45:43.521 [INF] NTFN: Cancelling epoch notification, epoch_id=111
2024-01-10 18:45:43.827 [INF] NTFN: New block epoch subscription
2024-01-10 18:45:58.866 [INF] NTFN: Cancelling epoch notification, epoch_id=112
2024-01-10 18:58:06.706 [DBG] NTFN: Filtering 3185 txns for 10 spend requests at height 825174
2024-01-10 18:58:06.865 [INF] NTFN: New block: height=825174, sha=0000000000000000000167f359c21a75c462de1fbcb31be89251b3ceac20dd99

What exactly does NTFN mean and what do we see here?

Is the channel lost or you guys think I can recover it?

So output 1 (P2TR) is just a normal change address to the on-chain wallet of the node.

Yes this was also my perception of the transaction

could you share more details about how this channel was created?

Actually I do not have much more information, I went to RTL -> Lightning -> Peers/Channels -> Peers -> Add Peer Added the pubkey and in step 2 created the channel with 500.000 sats grafik

Its still shown as pending open in RTL (matching to the lncli output). Via RTL I can not even force close. In worst case is not only the channel lost but the funds aswell?

grafik

Roasbeef commented 9 months ago

What exactly does NTFN mean and what do we see here?

Can you run it over all the logs you have? That same grep. NTFN is the logging sub-system that'll show when we detect that something has been confirmed or spent.

After you provide that, you can try: --height-hint-cache-query-disable. That'll reset an internal cache to force it to drop any prior assumptions about the conf/spend state of UTXOs at prior heights.

bvolution commented 9 months ago

I am afraid my implementation of LND (via raspiblitz) only keeps logs for a certain amount of time by default.

2024-01-10 18:22:11.071 [INF] NTFN: New block epoch subscription
2024-01-10 18:22:27.174 [INF] NTFN: Cancelling epoch notification, epoch_id=109
2024-01-10 18:22:27.918 [INF] NTFN: New block epoch subscription
2024-01-10 18:34:46.594 [INF] NTFN: Cancelling epoch notification, epoch_id=110
2024-01-10 18:45:38.333 [INF] NTFN: New block epoch subscription
2024-01-10 18:45:43.521 [INF] NTFN: Cancelling epoch notification, epoch_id=111
2024-01-10 18:45:43.827 [INF] NTFN: New block epoch subscription
2024-01-10 18:45:58.866 [INF] NTFN: Cancelling epoch notification, epoch_id=112
2024-01-10 18:58:06.706 [DBG] NTFN: Filtering 3185 txns for 10 spend requests at height 825174
2024-01-10 18:58:06.865 [INF] NTFN: New block: height=825174, sha=0000000000000000000167f359c21a75c462de1fbcb31be89251b3ceac20dd99
2024-01-10 19:19:19.199 [DBG] NTFN: Filtering 3323 txns for 10 spend requests at height 825175
2024-01-10 19:19:19.408 [INF] NTFN: New block: height=825175, sha=000000000000000000023e72934738fa9e1618a6462967d6844fbf38cee6f6f2
2024-01-10 19:29:31.543 [DBG] NTFN: Filtering 3525 txns for 10 spend requests at height 825176
2024-01-10 19:29:31.975 [INF] NTFN: New block: height=825176, sha=000000000000000000035826f63c892190389daae72ef70cb0a75be0fc143559
2024-01-10 19:41:05.102 [DBG] NTFN: Filtering 3174 txns for 10 spend requests at height 825177
2024-01-10 19:41:05.255 [INF] NTFN: New block: height=825177, sha=000000000000000000009075a598ead1dd2ada99ec2c272513cfac5dbdbb1ad7
2024-01-10 19:48:05.155 [DBG] NTFN: Filtering 3601 txns for 10 spend requests at height 825178
2024-01-10 19:48:05.362 [INF] NTFN: New block: height=825178, sha=0000000000000000000048767483a3267d8aaf2969ef7f4d500df3f5dab3582f
2024-01-10 19:53:43.327 [DBG] NTFN: Filtering 4863 txns for 10 spend requests at height 825179
2024-01-10 19:53:43.550 [INF] NTFN: New block: height=825179, sha=00000000000000000002776d0e43411a88cae45efd0278caf6dbd207262374f3
2024-01-10 19:54:23.472 [DBG] NTFN: Filtering 2915 txns for 10 spend requests at height 825180
2024-01-10 19:54:23.673 [INF] NTFN: New block: height=825180, sha=00000000000000000002f7bb235ee2512d969e49628a203c886207a15bce7fa1
2024-01-10 20:08:02.885 [DBG] NTFN: Filtering 3567 txns for 10 spend requests at height 825181
2024-01-10 20:08:03.017 [INF] NTFN: New block: height=825181, sha=00000000000000000001a79d1975ec91e1b56d917ba0b7d512d85f7ba2987b9c
2024-01-10 20:08:12.454 [DBG] NTFN: Filtering 2644 txns for 10 spend requests at height 825182
2024-01-10 20:08:12.594 [INF] NTFN: New block: height=825182, sha=00000000000000000001aa98b78670bc8fb580212ec267073b4a3d72aa47328c
2024-01-10 20:21:58.006 [DBG] NTFN: Filtering 3623 txns for 10 spend requests at height 825183
2024-01-10 20:21:58.191 [INF] NTFN: New block: height=825183, sha=00000000000000000003cc0d7d51b84a87ed5b436b2f030bb4aa4bd76ad7cea9
2024-01-10 20:22:21.887 [DBG] NTFN: Filtering 1306 txns for 10 spend requests at height 825184
2024-01-10 20:22:22.055 [INF] NTFN: New block: height=825184, sha=0000000000000000000061a146d29236cb77cfff4cc676d44989e5e5ffa0714e
2024-01-10 20:23:19.602 [INF] NTFN: New block epoch subscription
2024-01-10 20:23:29.934 [INF] NTFN: Cancelling epoch notification, epoch_id=113
2024-01-10 20:23:30.192 [INF] NTFN: New block epoch subscription
2024-01-10 20:26:16.215 [INF] NTFN: Cancelling epoch notification, epoch_id=106
2024-01-10 20:26:24.472 [INF] NTFN: New block epoch subscription
2024-01-10 20:29:01.159 [DBG] NTFN: Filtering 3100 txns for 10 spend requests at height 825185
2024-01-10 20:29:01.496 [INF] NTFN: New block: height=825185, sha=00000000000000000000267e363d2fb62ce3d8984437ccc21cc6a1005e3bf033
2024-01-10 20:32:30.431 [INF] NTFN: Cancelling epoch notification, epoch_id=115
2024-01-10 20:32:30.642 [INF] NTFN: New block epoch subscription
2024-01-10 20:42:19.121 [DBG] NTFN: Filtering 2991 txns for 10 spend requests at height 825186
2024-01-10 20:42:19.415 [INF] NTFN: New block: height=825186, sha=00000000000000000000d7ebd8bd8d73b1d27674e13b62598eff54c99243b7fe
2024-01-10 20:49:26.492 [INF] NTFN: Cancelling epoch notification, epoch_id=99
2024-01-10 20:50:59.825 [INF] NTFN: New block epoch subscription
2024-01-10 20:58:26.314 [DBG] NTFN: Filtering 3346 txns for 10 spend requests at height 825187
2024-01-10 20:58:26.444 [INF] NTFN: New block: height=825187, sha=000000000000000000012a300541c9071c19c7cb1c19bdbd8a55a2b1379af5b2
2024-01-10 21:03:34.151 [DBG] NTFN: Filtering 2375 txns for 10 spend requests at height 825188
2024-01-10 21:03:34.316 [INF] NTFN: New block: height=825188, sha=00000000000000000001527bba28f7b5652599a2d4213d1fa2b69eecafe90b82
2024-01-10 21:07:23.258 [INF] NTFN: Cancelling epoch notification, epoch_id=117
2024-01-10 21:07:29.611 [INF] NTFN: New block epoch subscription
2024-01-10 21:14:23.342 [INF] NTFN: Cancelling epoch notification, epoch_id=118
2024-01-10 21:14:30.794 [INF] NTFN: New block epoch subscription
2024-01-10 21:17:11.411 [INF] NTFN: Cancelling epoch notification, epoch_id=88
2024-01-10 21:25:17.765 [DBG] NTFN: Filtering 3127 txns for 10 spend requests at height 825189
2024-01-10 21:25:17.893 [INF] NTFN: New block: height=825189, sha=00000000000000000000937d11fe3185110ce4244f70bb39782b4c3ed6484a3a
2024-01-10 21:25:41.490 [DBG] NTFN: Filtering 2794 txns for 10 spend requests at height 825190
2024-01-10 21:25:41.725 [INF] NTFN: New block: height=825190, sha=00000000000000000002d5fe7210cb25254a576f4fd8adc3cdf876d6a8415cfc
2024-01-10 21:26:23.967 [INF] NTFN: Cancelling epoch notification, epoch_id=105
2024-01-10 21:28:16.804 [DBG] NTFN: Filtering 1989 txns for 10 spend requests at height 825191
2024-01-10 21:28:16.950 [INF] NTFN: New block: height=825191, sha=00000000000000000001b089235da09389605d89acf1a4470fdf221a73cb269f
2024-01-10 21:47:30.946 [DBG] NTFN: Filtering 3162 txns for 10 spend requests at height 825192
2024-01-10 21:47:31.089 [INF] NTFN: New block: height=825192, sha=000000000000000000019939f9292452cfb218bfcfecff170cf2912f40591501
2024-01-10 22:01:36.803 [INF] NTFN: Cancelling epoch notification, epoch_id=114
2024-01-10 22:19:25.868 [DBG] NTFN: Filtering 3026 txns for 10 spend requests at height 825193
2024-01-10 22:19:26.033 [INF] NTFN: New block: height=825193, sha=00000000000000000001aed0771e28c8a6f5a7aab63bbcf8c7a97112527f4c3e
2024-01-10 22:23:14.674 [DBG] NTFN: Filtering 3330 txns for 10 spend requests at height 825194
2024-01-10 22:23:14.800 [INF] NTFN: New block: height=825194, sha=0000000000000000000090bfd435255462933284f0632545d5e7b8fa655255ef
2024-01-10 22:31:47.615 [DBG] NTFN: Filtering 3451 txns for 10 spend requests at height 825195
2024-01-10 22:31:47.778 [INF] NTFN: New block: height=825195, sha=00000000000000000002739ff88007a9d0e2b5d58ba21950ddab0feaa8f6790e
2024-01-10 22:34:52.386 [DBG] NTFN: Filtering 2833 txns for 10 spend requests at height 825196
2024-01-10 22:34:52.508 [INF] NTFN: New block: height=825196, sha=00000000000000000001d4530c76dce495e17095663b51508d23a6e5cc201338
2024-01-10 22:35:31.973 [DBG] NTFN: Filtering 1528 txns for 10 spend requests at height 825197
2024-01-10 22:35:32.085 [INF] NTFN: New block: height=825197, sha=0000000000000000000251ce500c7092ed52b5971919e903576abdc0f28739d8
2024-01-10 22:55:39.028 [INF] NTFN: New block epoch subscription
2024-01-10 22:55:39.098 [INF] NTFN: Cancelling epoch notification, epoch_id=120
2024-01-10 22:56:29.157 [DBG] NTFN: Filtering 3507 txns for 10 spend requests at height 825198
2024-01-10 22:56:29.373 [INF] NTFN: New block: height=825198, sha=000000000000000000039e47376d02f85666bcdc0072477f676abfb8cedc490a
2024-01-10 22:58:37.140 [DBG] NTFN: Filtering 2462 txns for 10 spend requests at height 825199
2024-01-10 22:58:37.250 [INF] NTFN: New block: height=825199, sha=0000000000000000000056407ba45b95b4697e0b78bc96be0d9439f8c9ff76d6
2024-01-10 23:04:22.335 [DBG] NTFN: Filtering 3351 txns for 10 spend requests at height 825200
2024-01-10 23:04:22.531 [INF] NTFN: New block: height=825200, sha=0000000000000000000195e521b2ee04d52bdac56069de06a38955b49235d041
bvolution commented 9 months ago

Well is there at least any hope on force closing it? How could I do it? Via RTL it is not possible. Appreciate any help to recover my funds!

bvolution commented 9 months ago

After you provide that, you can try: --height-hint-cache-query-disable. That'll reset an internal cache to force it to drop any prior assumptions about the conf/spend state of UTXOs at prior heights.

To which command do I provide this --height-hint-cache-query-disable flag?

ziggie1984 commented 9 months ago

Just set it in your lnd.conf (height-hint-cache-query-disable=true) or as a start parameter to the lnd cmd, like e.g. lnd --height-hint-cache-query-disable

bvolution commented 9 months ago

Just set it in your lnd.conf (height-hint-cache-query-disable=true) or as a start parameter to the lnd cmd, like e.g. lnd --height-hint-cache-query-disable

I will try this first but is it correct that otherwise I can try to force close the chan via

lncli closechannel --force b0955d02a985fb4eeaf3bb87e3f378dfa90891e2c071402f2f63546b6a9f2136 0

ziggie1984 commented 9 months ago

yes lncli closechannel --force --chan_point b0955d02a985fb4eeaf3bb87e3f378dfa90891e2c071402f2f63546b6a9f2136:0

but I am pretty sure your channel is recoverable, so don't force close it yet.

Can you set your logs to: lncli debuglevel --level debug so that we can find out the reason why it is happening ?

bvolution commented 9 months ago

Can you set your logs to: lncli debuglevel --level debug so that we can find out the reason why it is happening ?

Done aswell as added height-hint-cache-query-disable=true to lnd.conf. + Restartet sudo systemctl restart lnd do I need to anything else to restart a rescan?

ziggie1984 commented 9 months ago

this is not a rescan to be specific, so did it fix your issue if not can you share the logs ?

bvolution commented 9 months ago

No the problem is still the same the channel is still pending open. Do you want something specific from the log or just the tail? This is tail 100

admin@xx.xx.xx.xx:~ ₿ sudo cat /mnt/hdd/lnd/logs/bitcoin/mainnet/lnd.log | tail -n 100
2024-01-13 18:51:20.641 [DBG] RPCS: [/lnrpc.Lightning/ForwardingHistory] requested
2024-01-13 18:51:20.650 [DBG] RPCS: [/lnrpc.Lightning/GetTransactions] requested
2024-01-13 18:51:20.653 [DBG] RPCS: [/lnrpc.Lightning/ClosedChannels] requested
2024-01-13 18:51:25.273 [DBG] PEER: Peer(03864ef025fde8fb587d989186ce6a4a186895ee44a926bfc370e2c366597a3f8f): Received Ping(ping_bytes=000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000) from 03864ef025fde8fb587d989186ce6a4a186895ee44a926bfc370e2c366597a3f8f@3.33.236.230:9735
2024-01-13 18:51:25.274 [DBG] PEER: Peer(03864ef025fde8fb587d989186ce6a4a186895ee44a926bfc370e2c366597a3f8f): Sending Pong(pong_bytes=000000000000000000000000000000000000000000000000) to 03864ef025fde8fb587d989186ce6a4a186895ee44a926bfc370e2c366597a3f8f@3.33.236.230:9735
2024-01-13 18:51:25.349 [DBG] RPCS: [/lnrpc.Lightning/FeeReport] requested
2024-01-13 18:51:27.148 [DBG] RPCS: [/lnrpc.Lightning/GetInfo] requested
2024-01-13 18:51:34.113 [DBG] RPCS: [/lnrpc.Lightning/GetInfo] requested
2024-01-13 18:51:37.874 [INF] WTCL: (legacy) Client stats: tasks(received=0 accepted=0 ineligible=0) sessions(acquired=0 exhausted=0)
2024-01-13 18:51:37.892 [INF] WTCL: (anchor) Client stats: tasks(received=0 accepted=3 ineligible=0) sessions(acquired=0 exhausted=0)
2024-01-13 18:51:39.671 [DBG] PEER: Peer(0337cef39c908cf11699284dffbe4a13f777e8685b14e186b217bdcd53be494d08): Sending Ping(ping_bytes=000000203dc952f321d4ccffc0681ef858040947cd111318c55600000000000000000000fb19931cb9ea250bc04df17717a38e6c3016a6eca7ef2f65802bd3bdc76a7982b8d7a26569d8031702ab2d7c) to 0337cef39c908cf11699284dffbe4a13f777e8685b14e186b217bdcd53be494d08@127.0.0.1:36000
2024-01-13 18:51:41.057 [DBG] RPCS: [/lnrpc.Lightning/GetInfo] requested
2024-01-13 18:51:41.380 [DBG] PEER: Peer(0337cef39c908cf11699284dffbe4a13f777e8685b14e186b217bdcd53be494d08): Received Ping(ping_bytes=000000203dc952f321d4ccffc0681ef858040947cd111318c55600000000000000000000fb19931cb9ea250bc04df17717a38e6c3016a6eca7ef2f65802bd3bdc76a7982b8d7a26569d8031702ab2d7c) from 0337cef39c908cf11699284dffbe4a13f777e8685b14e186b217bdcd53be494d08@127.0.0.1:36000
2024-01-13 18:51:41.381 [DBG] PEER: Peer(0337cef39c908cf11699284dffbe4a13f777e8685b14e186b217bdcd53be494d08): Sending Pong(pong_bytes=00000000000000000000000000000000) to 0337cef39c908cf11699284dffbe4a13f777e8685b14e186b217bdcd53be494d08@127.0.0.1:36000
2024-01-13 18:51:41.937 [DBG] RPCS: [/lnrpc.Lightning/ListPeers] requested
2024-01-13 18:51:41.938 [DBG] RPCS: [listpeers] yielded [02765a281bd188e80a89e6ea5092dcb8ebaaa5c5da341e64327e3fadbadcbc686c@34.65.45.157:9735 028268dcb4c68311613dd3bbb0164f7685b6710022bfa6dcce639acd44695049a2@62.2.188.232:39354 02d96eadea3d780104449aca5c93461ce67c1564e2e1d73225fa67dd3b997a6018@45.86.229.190:36042 02e176348c4aac2a2fe2210272dab9e64d578a8ab3485f122692a8bba3afc57f67@101.36.105.28:10764 0260fab633066ed7b1d9b9b8a0fac87e1579d1709e874d28a0d171a1f5c43bb877@104.192.3.74:51150 02c1f09ec838d3125c9ac39bcdb0e71e272f7cd11fb0e4c8daa920df2ec119eb80@80.254.174.149:60240 0337cef39c908cf11699284dffbe4a13f777e8685b14e186b217bdcd53be494d08@127.0.0.1:36000 024bfaf0cabe7f874fd33ebf7c6f4e5385971fc504ef3f492432e9e3ec77e1b5cf@52.1.72.207:9735 0243ed6aaee7d2dd05aaec629fc169b7aa0b113295339e67968b247764f8d31b98@107.189.13.93:38702 03864ef025fde8fb587d989186ce6a4a186895ee44a926bfc370e2c366597a3f8f@3.33.236.230:9735 024bbcd3120ada0763f7203d60c7504a51e53484fd37413ef229f833b02cc3d36d@44.229.55.237:32854] peers
2024-01-13 18:51:42.021 [DBG] RPCS: [/lnrpc.Lightning/ListChannels] requested
2024-01-13 18:51:42.031 [DBG] RPCS: [listchannels] fetched 10 channels from DB
2024-01-13 18:51:42.118 [DBG] RPCS: [/lnrpc.Lightning/GetChanInfo] requested
2024-01-13 18:51:42.130 [DBG] RPCS: [/lnrpc.Lightning/GetChanInfo] requested
2024-01-13 18:51:42.143 [DBG] RPCS: [/lnrpc.Lightning/GetChanInfo] requested
2024-01-13 18:51:42.155 [DBG] RPCS: [/lnrpc.Lightning/GetChanInfo] requested
2024-01-13 18:51:42.168 [DBG] RPCS: [/lnrpc.Lightning/GetChanInfo] requested
2024-01-13 18:51:42.180 [DBG] RPCS: [/lnrpc.Lightning/GetChanInfo] requested
2024-01-13 18:51:42.193 [DBG] RPCS: [/lnrpc.Lightning/GetChanInfo] requested
2024-01-13 18:51:42.206 [DBG] RPCS: [/lnrpc.Lightning/GetChanInfo] requested
2024-01-13 18:51:42.216 [DBG] RPCS: [/lnrpc.Lightning/GetChanInfo] requested
2024-01-13 18:51:42.228 [DBG] RPCS: [/lnrpc.Lightning/GetChanInfo] requested
2024-01-13 18:51:42.254 [DBG] RPCS: [/lnrpc.Lightning/ListInvoices] requested
2024-01-13 18:51:42.257 [DBG] RPCS: [/lnrpc.Lightning/GetInfo] requested
2024-01-13 18:51:42.300 [DBG] RPCS: [/lnrpc.Lightning/ListPayments] requested
2024-01-13 18:51:42.305 [DBG] RPCS: [/lnrpc.Lightning/ForwardingHistory] requested
2024-01-13 18:51:42.314 [DBG] RPCS: [/lnrpc.Lightning/GetTransactions] requested
2024-01-13 18:51:42.317 [DBG] RPCS: [/lnrpc.Lightning/ClosedChannels] requested
2024-01-13 18:51:42.536 [DBG] PEER: Peer(0337cef39c908cf11699284dffbe4a13f777e8685b14e186b217bdcd53be494d08): Received Pong(pong_bytes=00000000000000000000000000000000) from 0337cef39c908cf11699284dffbe4a13f777e8685b14e186b217bdcd53be494d08@127.0.0.1:36000
2024-01-13 18:51:44.644 [DBG] RPCS: [/lnrpc.Lightning/GetInfo] requested
2024-01-13 18:51:46.937 [DBG] RPCS: [/lnrpc.Lightning/WalletBalance] requested
2024-01-13 18:51:46.953 [DBG] RPCS: [walletbalance] CENSORED
2024-01-13 18:51:47.246 [DBG] RPCS: [/lnrpc.Lightning/ChannelBalance] requested
2024-01-13 18:51:47.262 [DBG] RPCS: [channelbalance]  CENSORED
2024-01-13 18:51:54.479 [DBG] RPCS: [/lnrpc.Lightning/GetInfo] requested
2024-01-13 18:51:54.760 [DBG] PEER: Peer(02e176348c4aac2a2fe2210272dab9e64d578a8ab3485f122692a8bba3afc57f67): Sending Ping(ping_bytes=000000203dc952f321d4ccffc0681ef858040947cd111318c55600000000000000000000fb19931cb9ea250bc04df17717a38e6c3016a6eca7ef2f65802bd3bdc76a7982b8d7a26569d8031702ab2d7c) to 02e176348c4aac2a2fe2210272dab9e64d578a8ab3485f122692a8bba3afc57f67@101.36.105.28:10764
2024-01-13 18:51:54.768 [DBG] PEER: Peer(0260fab633066ed7b1d9b9b8a0fac87e1579d1709e874d28a0d171a1f5c43bb877): Sending Ping(ping_bytes=000000203dc952f321d4ccffc0681ef858040947cd111318c55600000000000000000000fb19931cb9ea250bc04df17717a38e6c3016a6eca7ef2f65802bd3bdc76a7982b8d7a26569d8031702ab2d7c) to 0260fab633066ed7b1d9b9b8a0fac87e1579d1709e874d28a0d171a1f5c43bb877@104.192.3.74:51150
2024-01-13 18:51:54.774 [DBG] PEER: Peer(0243ed6aaee7d2dd05aaec629fc169b7aa0b113295339e67968b247764f8d31b98): Sending Ping(ping_bytes=000000203dc952f321d4ccffc0681ef858040947cd111318c55600000000000000000000fb19931cb9ea250bc04df17717a38e6c3016a6eca7ef2f65802bd3bdc76a7982b8d7a26569d8031702ab2d7c) to 0243ed6aaee7d2dd05aaec629fc169b7aa0b113295339e67968b247764f8d31b98@107.189.13.93:38702
2024-01-13 18:51:54.780 [DBG] PEER: Peer(02d96eadea3d780104449aca5c93461ce67c1564e2e1d73225fa67dd3b997a6018): Sending Ping(ping_bytes=000000203dc952f321d4ccffc0681ef858040947cd111318c55600000000000000000000fb19931cb9ea250bc04df17717a38e6c3016a6eca7ef2f65802bd3bdc76a7982b8d7a26569d8031702ab2d7c) to 02d96eadea3d780104449aca5c93461ce67c1564e2e1d73225fa67dd3b997a6018@45.86.229.190:36042
2024-01-13 18:51:54.964 [DBG] PEER: Peer(0243ed6aaee7d2dd05aaec629fc169b7aa0b113295339e67968b247764f8d31b98): Received Pong(pong_bytes=00000000000000000000000000000000) from 0243ed6aaee7d2dd05aaec629fc169b7aa0b113295339e67968b247764f8d31b98@107.189.13.93:38702
2024-01-13 18:51:55.008 [DBG] PEER: Peer(02e176348c4aac2a2fe2210272dab9e64d578a8ab3485f122692a8bba3afc57f67): Received Ping(ping_bytes=000000203dc952f321d4ccffc0681ef858040947cd111318c55600000000000000000000fb19931cb9ea250bc04df17717a38e6c3016a6eca7ef2f65802bd3bdc76a7982b8d7a26569d8031702ab2d7c) from 02e176348c4aac2a2fe2210272dab9e64d578a8ab3485f122692a8bba3afc57f67@101.36.105.28:10764
2024-01-13 18:51:55.008 [DBG] PEER: Peer(02e176348c4aac2a2fe2210272dab9e64d578a8ab3485f122692a8bba3afc57f67): Sending Pong(pong_bytes=00000000000000000000000000000000) to 02e176348c4aac2a2fe2210272dab9e64d578a8ab3485f122692a8bba3afc57f67@101.36.105.28:10764
2024-01-13 18:51:55.018 [DBG] PEER: Peer(02e176348c4aac2a2fe2210272dab9e64d578a8ab3485f122692a8bba3afc57f67): Received Pong(pong_bytes=00000000000000000000000000000000) from 02e176348c4aac2a2fe2210272dab9e64d578a8ab3485f122692a8bba3afc57f67@101.36.105.28:10764
2024-01-13 18:51:55.024 [DBG] PEER: Peer(0243ed6aaee7d2dd05aaec629fc169b7aa0b113295339e67968b247764f8d31b98): Received Ping(ping_bytes=000000203dc952f321d4ccffc0681ef858040947cd111318c55600000000000000000000fb19931cb9ea250bc04df17717a38e6c3016a6eca7ef2f65802bd3bdc76a7982b8d7a26569d8031702ab2d7c) from 0243ed6aaee7d2dd05aaec629fc169b7aa0b113295339e67968b247764f8d31b98@107.189.13.93:38702
2024-01-13 18:51:55.025 [DBG] PEER: Peer(0243ed6aaee7d2dd05aaec629fc169b7aa0b113295339e67968b247764f8d31b98): Sending Pong(pong_bytes=00000000000000000000000000000000) to 0243ed6aaee7d2dd05aaec629fc169b7aa0b113295339e67968b247764f8d31b98@107.189.13.93:38702
2024-01-13 18:51:55.132 [DBG] PEER: Peer(024bfaf0cabe7f874fd33ebf7c6f4e5385971fc504ef3f492432e9e3ec77e1b5cf): Received Ping(ping_bytes=000000203dc952f321d4ccffc0681ef858040947cd111318c55600000000000000000000fb19931cb9ea250bc04df17717a38e6c3016a6eca7ef2f65802bd3bdc76a7982b8d7a26569d8031702ab2d7c) from 024bfaf0cabe7f874fd33ebf7c6f4e5385971fc504ef3f492432e9e3ec77e1b5cf@52.1.72.207:9735
2024-01-13 18:51:55.132 [DBG] PEER: Peer(024bfaf0cabe7f874fd33ebf7c6f4e5385971fc504ef3f492432e9e3ec77e1b5cf): Sending Pong(pong_bytes=00000000000000000000000000000000) to 024bfaf0cabe7f874fd33ebf7c6f4e5385971fc504ef3f492432e9e3ec77e1b5cf@52.1.72.207:9735
2024-01-13 18:51:55.141 [DBG] PEER: Peer(024bfaf0cabe7f874fd33ebf7c6f4e5385971fc504ef3f492432e9e3ec77e1b5cf): Sending Ping(ping_bytes=000000203dc952f321d4ccffc0681ef858040947cd111318c55600000000000000000000fb19931cb9ea250bc04df17717a38e6c3016a6eca7ef2f65802bd3bdc76a7982b8d7a26569d8031702ab2d7c) to 024bfaf0cabe7f874fd33ebf7c6f4e5385971fc504ef3f492432e9e3ec77e1b5cf@52.1.72.207:9735
2024-01-13 18:51:55.150 [DBG] PEER: Peer(03864ef025fde8fb587d989186ce6a4a186895ee44a926bfc370e2c366597a3f8f): Sending Ping(ping_bytes=000000203dc952f321d4ccffc0681ef858040947cd111318c55600000000000000000000fb19931cb9ea250bc04df17717a38e6c3016a6eca7ef2f65802bd3bdc76a7982b8d7a26569d8031702ab2d7c) to 03864ef025fde8fb587d989186ce6a4a186895ee44a926bfc370e2c366597a3f8f@3.33.236.230:9735
2024-01-13 18:51:55.243 [DBG] PEER: Peer(024bfaf0cabe7f874fd33ebf7c6f4e5385971fc504ef3f492432e9e3ec77e1b5cf): Received Pong(pong_bytes=00000000000000000000000000000000) from 024bfaf0cabe7f874fd33ebf7c6f4e5385971fc504ef3f492432e9e3ec77e1b5cf@52.1.72.207:9735
2024-01-13 18:51:55.255 [DBG] PEER: Peer(03864ef025fde8fb587d989186ce6a4a186895ee44a926bfc370e2c366597a3f8f): Received Pong(pong_bytes=00000000000000000000000000000000) from 03864ef025fde8fb587d989186ce6a4a186895ee44a926bfc370e2c366597a3f8f@3.33.236.230:9735
2024-01-13 18:51:55.321 [DBG] PEER: Peer(028268dcb4c68311613dd3bbb0164f7685b6710022bfa6dcce639acd44695049a2): Sending Ping(ping_bytes=000000203dc952f321d4ccffc0681ef858040947cd111318c55600000000000000000000fb19931cb9ea250bc04df17717a38e6c3016a6eca7ef2f65802bd3bdc76a7982b8d7a26569d8031702ab2d7c) to 028268dcb4c68311613dd3bbb0164f7685b6710022bfa6dcce639acd44695049a2@62.2.188.232:39354
2024-01-13 18:51:55.344 [DBG] PEER: Peer(028268dcb4c68311613dd3bbb0164f7685b6710022bfa6dcce639acd44695049a2): Received Ping(ping_bytes=000000203dc952f321d4ccffc0681ef858040947cd111318c55600000000000000000000fb19931cb9ea250bc04df17717a38e6c3016a6eca7ef2f65802bd3bdc76a7982b8d7a26569d8031702ab2d7c) from 028268dcb4c68311613dd3bbb0164f7685b6710022bfa6dcce639acd44695049a2@62.2.188.232:39354
2024-01-13 18:51:55.344 [DBG] PEER: Peer(028268dcb4c68311613dd3bbb0164f7685b6710022bfa6dcce639acd44695049a2): Sending Pong(pong_bytes=00000000000000000000000000000000) to 028268dcb4c68311613dd3bbb0164f7685b6710022bfa6dcce639acd44695049a2@62.2.188.232:39354
2024-01-13 18:51:55.364 [DBG] PEER: Peer(028268dcb4c68311613dd3bbb0164f7685b6710022bfa6dcce639acd44695049a2): Received Pong(pong_bytes=00000000000000000000000000000000) from 028268dcb4c68311613dd3bbb0164f7685b6710022bfa6dcce639acd44695049a2@62.2.188.232:39354
2024-01-13 18:51:55.430 [DBG] PEER: Peer(02d96eadea3d780104449aca5c93461ce67c1564e2e1d73225fa67dd3b997a6018): Received Pong(pong_bytes=00000000000000000000000000000000) from 02d96eadea3d780104449aca5c93461ce67c1564e2e1d73225fa67dd3b997a6018@45.86.229.190:36042
2024-01-13 18:51:55.472 [DBG] PEER: Peer(0260fab633066ed7b1d9b9b8a0fac87e1579d1709e874d28a0d171a1f5c43bb877): Received Pong(pong_bytes=00000000000000000000000000000000) from 0260fab633066ed7b1d9b9b8a0fac87e1579d1709e874d28a0d171a1f5c43bb877@104.192.3.74:51150
2024-01-13 18:51:55.472 [DBG] PEER: Peer(0260fab633066ed7b1d9b9b8a0fac87e1579d1709e874d28a0d171a1f5c43bb877): Received Ping(ping_bytes=000000203dc952f321d4ccffc0681ef858040947cd111318c55600000000000000000000fb19931cb9ea250bc04df17717a38e6c3016a6eca7ef2f65802bd3bdc76a7982b8d7a26569d8031702ab2d7c) from 0260fab633066ed7b1d9b9b8a0fac87e1579d1709e874d28a0d171a1f5c43bb877@104.192.3.74:51150
2024-01-13 18:51:55.472 [DBG] PEER: Peer(0260fab633066ed7b1d9b9b8a0fac87e1579d1709e874d28a0d171a1f5c43bb877): Sending Pong(pong_bytes=00000000000000000000000000000000) to 0260fab633066ed7b1d9b9b8a0fac87e1579d1709e874d28a0d171a1f5c43bb877@104.192.3.74:51150
2024-01-13 18:51:55.723 [DBG] PEER: Peer(024bbcd3120ada0763f7203d60c7504a51e53484fd37413ef229f833b02cc3d36d): Sending Ping(ping_bytes=000000203dc952f321d4ccffc0681ef858040947cd111318c55600000000000000000000fb19931cb9ea250bc04df17717a38e6c3016a6eca7ef2f65802bd3bdc76a7982b8d7a26569d8031702ab2d7c) to 024bbcd3120ada0763f7203d60c7504a51e53484fd37413ef229f833b02cc3d36d@44.229.55.237:32854
2024-01-13 18:51:55.902 [DBG] PEER: Peer(024bbcd3120ada0763f7203d60c7504a51e53484fd37413ef229f833b02cc3d36d): Received Ping(ping_bytes=000000203dc952f321d4ccffc0681ef858040947cd111318c55600000000000000000000fb19931cb9ea250bc04df17717a38e6c3016a6eca7ef2f65802bd3bdc76a7982b8d7a26569d8031702ab2d7c) from 024bbcd3120ada0763f7203d60c7504a51e53484fd37413ef229f833b02cc3d36d@44.229.55.237:32854
2024-01-13 18:51:55.902 [DBG] PEER: Peer(024bbcd3120ada0763f7203d60c7504a51e53484fd37413ef229f833b02cc3d36d): Sending Pong(pong_bytes=00000000000000000000000000000000) to 024bbcd3120ada0763f7203d60c7504a51e53484fd37413ef229f833b02cc3d36d@44.229.55.237:32854
2024-01-13 18:51:55.909 [DBG] PEER: Peer(024bbcd3120ada0763f7203d60c7504a51e53484fd37413ef229f833b02cc3d36d): Received Pong(pong_bytes=00000000000000000000000000000000) from 024bbcd3120ada0763f7203d60c7504a51e53484fd37413ef229f833b02cc3d36d@44.229.55.237:32854
2024-01-13 18:51:57.094 [DBG] PEER: Peer(02c1f09ec838d3125c9ac39bcdb0e71e272f7cd11fb0e4c8daa920df2ec119eb80): Sending Ping(ping_bytes=000000203dc952f321d4ccffc0681ef858040947cd111318c55600000000000000000000fb19931cb9ea250bc04df17717a38e6c3016a6eca7ef2f65802bd3bdc76a7982b8d7a26569d8031702ab2d7c) to 02c1f09ec838d3125c9ac39bcdb0e71e272f7cd11fb0e4c8daa920df2ec119eb80@80.254.174.149:60240
2024-01-13 18:51:57.123 [DBG] PEER: Peer(02c1f09ec838d3125c9ac39bcdb0e71e272f7cd11fb0e4c8daa920df2ec119eb80): Received Pong(pong_bytes=00000000000000000000000000000000) from 02c1f09ec838d3125c9ac39bcdb0e71e272f7cd11fb0e4c8daa920df2ec119eb80@80.254.174.149:60240
2024-01-13 18:51:57.125 [DBG] PEER: Peer(02c1f09ec838d3125c9ac39bcdb0e71e272f7cd11fb0e4c8daa920df2ec119eb80): Received Ping(ping_bytes=000000203dc952f321d4ccffc0681ef858040947cd111318c55600000000000000000000fb19931cb9ea250bc04df17717a38e6c3016a6eca7ef2f65802bd3bdc76a7982b8d7a26569d8031702ab2d7c) from 02c1f09ec838d3125c9ac39bcdb0e71e272f7cd11fb0e4c8daa920df2ec119eb80@80.254.174.149:60240
2024-01-13 18:51:57.126 [DBG] PEER: Peer(02c1f09ec838d3125c9ac39bcdb0e71e272f7cd11fb0e4c8daa920df2ec119eb80): Sending Pong(pong_bytes=00000000000000000000000000000000) to 02c1f09ec838d3125c9ac39bcdb0e71e272f7cd11fb0e4c8daa920df2ec119eb80@80.254.174.149:60240
2024-01-13 18:51:57.143 [DBG] PEER: Peer(02765a281bd188e80a89e6ea5092dcb8ebaaa5c5da341e64327e3fadbadcbc686c): Sending Ping(ping_bytes=000000203dc952f321d4ccffc0681ef858040947cd111318c55600000000000000000000fb19931cb9ea250bc04df17717a38e6c3016a6eca7ef2f65802bd3bdc76a7982b8d7a26569d8031702ab2d7c) to 02765a281bd188e80a89e6ea5092dcb8ebaaa5c5da341e64327e3fadbadcbc686c@34.65.45.157:9735
2024-01-13 18:51:57.148 [DBG] PEER: Peer(02765a281bd188e80a89e6ea5092dcb8ebaaa5c5da341e64327e3fadbadcbc686c): Received Ping(ping_bytes=000000203dc952f321d4ccffc0681ef858040947cd111318c55600000000000000000000fb19931cb9ea250bc04df17717a38e6c3016a6eca7ef2f65802bd3bdc76a7982b8d7a26569d8031702ab2d7c) from 02765a281bd188e80a89e6ea5092dcb8ebaaa5c5da341e64327e3fadbadcbc686c@34.65.45.157:9735
2024-01-13 18:51:57.148 [DBG] PEER: Peer(02765a281bd188e80a89e6ea5092dcb8ebaaa5c5da341e64327e3fadbadcbc686c): Sending Pong(pong_bytes=00000000000000000000000000000000) to 02765a281bd188e80a89e6ea5092dcb8ebaaa5c5da341e64327e3fadbadcbc686c@34.65.45.157:9735
2024-01-13 18:51:57.162 [DBG] PEER: Peer(02765a281bd188e80a89e6ea5092dcb8ebaaa5c5da341e64327e3fadbadcbc686c): Received Pong(pong_bytes=00000000000000000000000000000000) from 02765a281bd188e80a89e6ea5092dcb8ebaaa5c5da341e64327e3fadbadcbc686c@34.65.45.157:9735
2024-01-13 18:51:59.779 [DBG] BTCN: Failed to connect to 02e176348c4aac2a2fe2210272dab9e64d578a8ab3485f122692a8bba3afc57f67@101.36.105.28:56120 (reqid 18): dial proxy failed: dial tcp 101.36.105.28:56120: i/o timeout
2024-01-13 18:51:59.779 [DBG] BTCN: Retrying connection to 02e176348c4aac2a2fe2210272dab9e64d578a8ab3485f122692a8bba3afc57f67@101.36.105.28:56120 (reqid 18) in 50s
2024-01-13 18:52:02.470 [DBG] RPCS: [/lnrpc.Lightning/ListPeers] requested
2024-01-13 18:52:02.470 [DBG] RPCS: [listpeers] yielded [0337cef39c908cf11699284dffbe4a13f777e8685b14e186b217bdcd53be494d08@127.0.0.1:36000 024bfaf0cabe7f874fd33ebf7c6f4e5385971fc504ef3f492432e9e3ec77e1b5cf@52.1.72.207:9735 0243ed6aaee7d2dd05aaec629fc169b7aa0b113295339e67968b247764f8d31b98@107.189.13.93:38702 03864ef025fde8fb587d989186ce6a4a186895ee44a926bfc370e2c366597a3f8f@3.33.236.230:9735 024bbcd3120ada0763f7203d60c7504a51e53484fd37413ef229f833b02cc3d36d@44.229.55.237:32854 02c1f09ec838d3125c9ac39bcdb0e71e272f7cd11fb0e4c8daa920df2ec119eb80@80.254.174.149:60240 028268dcb4c68311613dd3bbb0164f7685b6710022bfa6dcce639acd44695049a2@62.2.188.232:39354 02d96eadea3d780104449aca5c93461ce67c1564e2e1d73225fa67dd3b997a6018@45.86.229.190:36042 02e176348c4aac2a2fe2210272dab9e64d578a8ab3485f122692a8bba3afc57f67@101.36.105.28:10764 0260fab633066ed7b1d9b9b8a0fac87e1579d1709e874d28a0d171a1f5c43bb877@104.192.3.74:51150 02765a281bd188e80a89e6ea5092dcb8ebaaa5c5da341e64327e3fadbadcbc686c@34.65.45.157:9735] peers
2024-01-13 18:52:03.496 [DBG] RPCS: [/lnrpc.Lightning/ListChannels] requested
2024-01-13 18:52:03.505 [DBG] RPCS: [listchannels] fetched 10 channels from DB
2024-01-13 18:52:03.727 [DBG] RPCS: [/lnrpc.Lightning/GetChanInfo] requested
2024-01-13 18:52:03.738 [DBG] RPCS: [/lnrpc.Lightning/GetChanInfo] requested
2024-01-13 18:52:03.749 [DBG] RPCS: [/lnrpc.Lightning/GetChanInfo] requested
2024-01-13 18:52:03.759 [DBG] RPCS: [/lnrpc.Lightning/GetChanInfo] requested
2024-01-13 18:52:03.770 [DBG] RPCS: [/lnrpc.Lightning/GetChanInfo] requested
2024-01-13 18:52:03.781 [DBG] RPCS: [/lnrpc.Lightning/GetChanInfo] requested
2024-01-13 18:52:03.791 [DBG] RPCS: [/lnrpc.Lightning/GetChanInfo] requested
2024-01-13 18:52:03.802 [DBG] RPCS: [/lnrpc.Lightning/GetChanInfo] requested
2024-01-13 18:52:03.812 [DBG] RPCS: [/lnrpc.Lightning/GetChanInfo] requested
2024-01-13 18:52:03.823 [DBG] RPCS: [/lnrpc.Lightning/GetChanInfo] requested
2024-01-13 18:52:03.848 [DBG] RPCS: [/lnrpc.Lightning/ListInvoices] requested
2024-01-13 18:52:03.851 [DBG] RPCS: [/lnrpc.Lightning/GetInfo] requested
2024-01-13 18:52:03.892 [DBG] RPCS: [/lnrpc.Lightning/ListPayments] requested
2024-01-13 18:52:03.898 [DBG] RPCS: [/lnrpc.Lightning/ForwardingHistory] requested
2024-01-13 18:52:03.912 [DBG] RPCS: [/lnrpc.Lightning/GetTransactions] requested
2024-01-13 18:52:03.916 [DBG] RPCS: [/lnrpc.Lightning/ClosedChannels] requested
2024-01-13 18:52:07.984 [DBG] RPCS: [/lnrpc.Lightning/GetInfo] requested
ziggie1984 commented 9 months ago

Can you search for: Dispatching historical confirmation rescan for txid=b0955d02a985fb4eeaf3bb87e3f378dfa90891e2c071402f2f63546b6a9f2136, keep tail running and see if after quite some time still nothing is found

bvolution commented 9 months ago

admin@xx.xx.xx.xx:~ ₿ sudo tail -f /mnt/hdd/lnd/logs/bitcoin/mainnet/lnd.log | grep "Dispatching historical confirmation rescan for txid=b0955d02a985fb4eeaf3bb87e3f378dfa90891e2c071402f2f63546b6a9f213"

I also stopped and started lnd again in another ssh session. Nothing happened yet.

ziggie1984 commented 9 months ago

the loglevel is still set to debug either in the lnd.conf or in via the above command debuglevel ... ? This resets everytime after a restart, and this output will most likely be shown when a new block is found.

bvolution commented 9 months ago

I reset it back to debug, or do we might need trace? I ran two filters in two sessions. Just the chan point in one and the full string you posted in the other nothing for now. There where multiple (I think 3) blocks found in the meantime.

Found something just for the chanpoint

2024-01-13 20:05:10.531 [DBG] CNCT: ChannelArbitrator(b0955d02a985fb4eeaf3bb87e3f378dfa90891e2c071402f2f63546b6a9f2136:0): attempting state step with trigger=chainTrigger from state=StateDefault
2024-01-13 20:05:10.533 [DBG] CNCT: ChannelArbitrator(b0955d02a985fb4eeaf3bb87e3f378dfa90891e2c071402f2f63546b6a9f2136:0): new block (height=825673) examining active HTLC's
2024-01-13 20:05:10.534 [DBG] CNCT: ChannelArbitrator(b0955d02a985fb4eeaf3bb87e3f378dfa90891e2c071402f2f63546b6a9f2136:0): checking commit chain actions at height=825673, in_htlc_count=0, out_htlc_count=0
2024-01-13 20:05:10.534 [DBG] CNCT: ChannelArbitrator(b0955d02a985fb4eeaf3bb87e3f378dfa90891e2c071402f2f63546b6a9f2136:0): no actions for chain trigger, terminating
2024-01-13 20:05:10.534 [DBG] CNCT: ChannelArbitrator(b0955d02a985fb4eeaf3bb87e3f378dfa90891e2c071402f2f63546b6a9f2136:0): terminating at state=StateDefault
ziggie1984 commented 9 months ago

Ok its difficult to debug this from remote, I would recommend to either provide the whole debug logs from restart on, or force close the channel, because it really seems like an edge case.

Can you ask the peer whether he sees the channel not as pending ?