AWAITING_UNILATERAL bug #2684
Comments
|
High CPU load is probably not related to the |
|
I managed to close out around 20 channels two weeks ago, force-closed a couple, recovered funds from most channels ok, but then noticed a stuck peer and two active channels they are not force-closing, as this seems stuck a few more logs, if that helps C-Lightning starting, listening on port 9735 btcpayserver_bitcoind btcpayserver/lightning:v0.7.0-3 |
|
|
|
nits: You can use the About your problem, what was the capacity of your channel ? It seems that the unilateral close transaction is created with no output ( == all capacity is consumed by fees) |
|
https://1ml.com/node/0265e5791c617b6e1dfe04137e71c0c959201592bd7fe3f1bb085c35595b72646c |
|
https://1ml.com/channel/623511053896056832 been trying to close this channel for the last couple of weeks, also this seem to be the node I can't disconnect AWAITING_UNILATERAL .. |
|
This is the relevant part:
This can happen if the HTLC and channel values are so low that mining fees dominate over it. Looking at your channels:
The first is 5000 satoshi, or 0.05 mBTC, which is rather small. The other one is 1mBTC though. And the invalid Bitcoin transaction seems to be only a single one, so it is likely to be the smaller channel. This bug is already supposedly fixed #632 and #1171 ; this was a spec-level bug I believe. @cdecker @rustyrussell do you have idea why this is apparently happening again? Even so, it probably is not related to the CPU load problem, because if we look at timestamps:
It's one and a half minutes between attempts to broadcast, so it should not be the cause of the CPU load. |
|
Thanks for the information I will check my CPU spikes timeline to find the cause of this with my BTCPAY Server Cheers |
AWAITING_UNILATERAL channels stuck and seems. to crash my node. at different times,
my node is over a year and 3 months. old, I guess it seems related to old nodes ,
how c-lightning can knock out my node due to a CPU spike is strange to me;
would love some overstanding on this issue
info:
id: 0265e5791c617b6e1dfe04137e71c0c959201592bd7fe3f1bb085c35595b72646c
alias: btcpayjungle-lightning-node
color: 0265e5
num_peers: 2
num_pending_channels: 1
num_active_channels: 2
num_inactive_channels: 0
address:
- type: ipv4
address: 51.144.112.185
port: 9735
binding:
- type: ipv4
address: 0.0.0.0
port: 9735
version: basedon-v0.7.0-3
blockheight: 578161
network: bitcoin
msatoshi_fees_collected: 11293
fees_collected_msat: 11293msat
peers:
connected: false
channels:
scratch_txid: 8aefc94e1eae524625a1cab2c275c1ce3678d56a89de2e27a4bc22e9ecf0098e
short_channel_id: 522794x2541x0
direction: 1
channel_id: ae1f73f634fd7ec23a95f0fba17f3bc3d8d582f346e8e423641e1c04ca283a57
funding_txid: 573a28ca041c1e6423e4e846f382d5d8c33b7fa1fbf0953ac27efd34f6731fae
private: false
funding_allocation_msat:
0265e5791c617b6e1dfe04137e71c0c959201592bd7fe3f1bb085c35595b72646c: 0
022d73890548be3625f822f0294d1c30934c6063df8904bafc70224920e14f10e7: 5000000
funding_msat:
0265e5791c617b6e1dfe04137e71c0c959201592bd7fe3f1bb085c35595b72646c: 0msat
022d73890548be3625f822f0294d1c30934c6063df8904bafc70224920e14f10e7: 5000000msat
msatoshi_to_us: 0
to_us_msat: 0msat
msatoshi_to_us_min: 0
min_to_us_msat: 0msat
msatoshi_to_us_max: 0
max_to_us_msat: 0msat
msatoshi_total: 5000000
total_msat: 5000000msat
dust_limit_satoshis: 546
dust_limit_msat: 546000msat
max_htlc_value_in_flight_msat: '18446744073709551615'
max_total_htlc_in_msat: 18446744073709551615msat
their_channel_reserve_satoshis: 0
their_reserve_msat: 0msat
our_channel_reserve_satoshis: 546
our_reserve_msat: 546000msat
spendable_msatoshi: 0
spendable_msat: 0msat
htlc_minimum_msat: 0
minimum_htlc_in_msat: 0msat
their_to_self_delay: 144
our_to_self_delay: 144
max_accepted_htlcs: 483
status:
in_payments_offered: 0
in_msatoshi_offered: 0
in_offered_msat: 0msat
in_payments_fulfilled: 0
in_msatoshi_fulfilled: 0
in_fulfilled_msat: 0msat
out_payments_offered: 0
out_msatoshi_offered: 0
out_offered_msat: 0msat
out_payments_fulfilled: 0
out_msatoshi_fulfilled: 0
out_fulfilled_msat: 0msat
htlcs: []
connected: true
netaddr:
global_features: ''
local_features: '81'
globalfeatures: ''
localfeatures: '81'
channels:
scratch_txid: d2cb2266ac4b3487d42f57b6e70142222a4c0b283a6de161acc98832868c4e36
short_channel_id: 567080x257x0
direction: 0
channel_id: e53623375ea4a467e5476ddd132d9fd80a95e213aa51b493319e8bd8da6c6564
funding_txid: 64656cdad88b9e3193b451aa13e2950ad89f2d13dd6d47e567a4a45e372336e5
private: false
funding_allocation_msat:
0265e5791c617b6e1dfe04137e71c0c959201592bd7fe3f1bb085c35595b72646c: 0
02809e936f0e82dfce13bcc47c77112db068f569e1db29e7bf98bcdd68b838ee84: 100000000
funding_msat:
0265e5791c617b6e1dfe04137e71c0c959201592bd7fe3f1bb085c35595b72646c: 0msat
02809e936f0e82dfce13bcc47c77112db068f569e1db29e7bf98bcdd68b838ee84: 100000000msat
msatoshi_to_us: 0
to_us_msat: 0msat
msatoshi_to_us_min: 0
min_to_us_msat: 0msat
msatoshi_to_us_max: 0
max_to_us_msat: 0msat
msatoshi_total: 100000000
total_msat: 100000000msat
dust_limit_satoshis: 546
dust_limit_msat: 546000msat
max_htlc_value_in_flight_msat: '18446744073709551615'
max_total_htlc_in_msat: 18446744073709551615msat
their_channel_reserve_satoshis: 1000
their_reserve_msat: 1000000msat
our_channel_reserve_satoshis: 1000
our_reserve_msat: 1000000msat
spendable_msatoshi: 0
spendable_msat: 0msat
htlc_minimum_msat: 0
minimum_htlc_in_msat: 0msat
their_to_self_delay: 144
our_to_self_delay: 144
max_accepted_htlcs: 483
status:
in_payments_offered: 0
in_msatoshi_offered: 0
in_offered_msat: 0msat
in_payments_fulfilled: 0
in_msatoshi_fulfilled: 0
in_fulfilled_msat: 0msat
out_payments_offered: 0
out_msatoshi_offered: 0
out_offered_msat: 0msat
out_payments_fulfilled: 0
out_msatoshi_fulfilled: 0
out_fulfilled_msat: 0msat
htlcs: []
My Node!!
getinfooutput{
"id": "0265e5791c617b6e1dfe04137e71c0c959201592bd7fe3f1bb085c35595b72646c",
"alias": "btcpayjungle-lightning-node",
"color": "0265e5",
"num_peers": 3,
"num_pending_channels": 2,
"num_active_channels": 2,
"num_inactive_channels": 0,
"address": [
{
"type": "ipv4",
"address": "51.144.112.185",
"port": 9735
}
],
"binding": [
{
"type": "ipv4",
"address": "0.0.0.0",
"port": 9735
}
],
"version": "basedon-v0.7.0-3",
"blockheight": 578161,
"network": "bitcoin",
"msatoshi_fees_collected": 11293,
"fees_collected_msat": "11293msat"
}
Channel "AWAITING_UNILATERAL" since days. Attempted force closing, CPU 100% this happen about two weeks ago to me,
tried closing out all channels to clear the problem, and force close,
but this has come back again, seems I can't get rid of the last channels
posted this issue in btcpay server GitHub incase others discover this problem,
2019-05-27T14:55:43.696Z lightningd(5): lightning_openingd-03ec201d396cc68d34360a13eee019189860006db990bfe85791f42fa9c00e8df1 chan #13924: Peer connection lost
2019-05-27T14:55:43.697Z lightningd(5): 03ec201d396cc68d34360a13eee019189860006db990bfe85791f42fa9c00e8df1 chan #13924: Owning subdaemon lightning_openingd died (9)
2019-05-27T15:15:43.527Z lightningd(5): lightning_openingd-03ec201d396cc68d34360a13eee019189860006db990bfe85791f42fa9c00e8df1 chan #13925: Peer connection lost
2019-05-27T15:15:43.528Z lightningd(5): 03ec201d396cc68d34360a13eee019189860006db990bfe85791f42fa9c00e8df1 chan #13925: Owning subdaemon lightning_openingd died (9)
2019-05-27T15:28:12.532Z lightningd(5): bitcoin-cli: finished bitcoin-cli -datadir=/etc/bitcoin -rpcconnect=bitcoind estimatesmartfee 100 ECONOMICAL (31251 ms)
2019-05-27T15:28:12.633Z lightningd(5): bitcoin-cli -datadir=/etc/bitcoin -rpcconnect=bitcoind estimatesmartfee 100 ECONOMICAL exited with status 1
2019-05-27T15:29:20.734Z lightningd(5): bitcoin-cli: finished bitcoin-cli -datadir=/etc/bitcoin -rpcconnect=bitcoind getblockhash 578048 (80002 ms)
2019-05-27T15:29:28.336Z lightningd(5): bitcoin-cli -datadir=/etc/bitcoin -rpcconnect=bitcoind getblockhash 578048 exited 1 (after 1 other errors) 'error: Could not connect to the server bitcoind:43782 (error code 1 - "EOF reached")??Make sure the bitcoind server is running and that you are connecting to the correct RPC port.?'
2019-05-27T15:29:53.836Z lightningd(5): FATAL SIGNAL 6 (version basedon-v0.7.0-3)
2019-05-27T15:29:57.136Z lightningd(5): backtrace: common/daemon.c:45 (crashdump) 0x55bd0884276c
2019-05-27T15:30:00.287Z lightningd(5): backtrace: (null):0 ((null)) 0x7f525ed0c0e9
bitcoin-cli -datadir=/etc/bitcoin -rpcconnect=bitcoind getblockhash 578048 exited 1 (after 1 other errors) 'error: Could not connect to the server bitcoind:43782 (error code 1 - "EOF reached")
Make sure the bitcoind server is running and that you are connecting to the correct RPC port.
'
lightningd: Fatal signal 6 (version basedon-v0.7.0-3)
0x55bd08842718 crashdump
common/daemon.c:40
0x7f525ed0c0e9 ???
???:0
Log dumped in crash.log.20190527153000
network=bitcoin added in /root/.lightning/config
alias=btcpayjungle-lightning-node added to /root/.lightning/config
Waiting /root/.nbxplorer/btc_fully_synched to be created...
The chain is fully synched
C-Lightning starting, listening on port 9735
2019-05-27T20:32:59.215Z lightningd(5): --------------------------------------------------
2019-05-27T20:32:59.215Z lightningd(5): Server started with public key 0265e5791c617b6e1dfe04137e71c0c959201592bd7fe3f1bb085c35595b72646c, alias btcpayjungle-lightning-node (color #0265e5) and lightningd basedon-v0.7.0-3
2019-05-27T20:34:20.238Z lightningd(5): lightning_openingd-02efb7d9ddb5e7c05a3b5e6fce5d919390512b4e108e9bce850b206ab39bc32268 chan #13519: Peer connection lost
2019-05-27T20:34:20.239Z lightningd(5): 02efb7d9ddb5e7c05a3b5e6fce5d919390512b4e108e9bce850b206ab39bc32268 chan #13519: Owning subdaemon lightning_openingd died (9)
2019-05-27T20:35:43.955Z lightningd(5): lightning_openingd-03ec201d396cc68d34360a13eee019189860006db990bfe85791f42fa9c00e8df1 chan #13518: Peer connection lost
2019-05-27T20:35:43.955Z lightningd(5): 03ec201d396cc68d34360a13eee019189860006db990bfe85791f42fa9c00e8df1 chan #13518: Owning subdaemon lightning_openingd died (62208)
2019-05-27T20:45:43.419Z lightningd(5): lightning_openingd-03ec201d396cc68d34360a13eee019189860006db990bfe85791f42fa9c00e8df1 chan #13521: Peer connection lost
2019-05-27T20:45:43.420Z lightningd(5): 03ec201d396cc68d34360a13eee019189860006db990bfe85791f42fa9c00e8df1 chan #13521: Owning subdaemon lightning_openingd died (62208)
btcpayserver/btcpayserver#839
The text was updated successfully, but these errors were encountered: