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

C-Lightning unable to start #2231

Closed
NicolasDorier opened this issue Jan 8, 2019 · 5 comments

Comments

Projects
None yet
3 participants
@NicolasDorier
Copy link
Contributor

commented Jan 8, 2019

On behalf of a user of BTCPay, it seems c-lightning crashes continuously now.

        ???:0
0x403618 ???
        ???:0
0xffffffffffffffff ???
        ???:0
2019-01-06T18:17:45.738Z lightningd(27349): FATAL SIGNAL 6 (version v0.6.2)
2019-01-06T18:17:45.738Z lightningd(27349): backtrace: common/daemon.c:42 (crashdump) 0x4344c0
2019-01-06T18:17:45.738Z lightningd(27349): backtrace: (null):0 ((null)) 0x7f6bb06d74af
2019-01-06T18:17:45.738Z lightningd(27349): backtrace: (null):0 ((null)) 0x7f6bb06d7428
2019-01-06T18:17:45.738Z lightningd(27349): backtrace: (null):0 ((null)) 0x7f6bb06d9029
2019-01-06T18:17:45.738Z lightningd(27349): backtrace: lightningd/log.c:614 (fatal) 0x419c49
2019-01-06T18:17:45.738Z lightningd(27349): backtrace: lightningd/htlc_end.c:70 (corrupt) 0x40fa09
2019-01-06T18:17:45.738Z lightningd(27349): backtrace: lightningd/htlc_end.c:155 (htlc_out_check) 0x40ff0b
2019-01-06T18:17:45.738Z lightningd(27349): backtrace: lightningd/htlc_end.c:269 (new_htlc_out) 0x4104a2
2019-01-06T18:17:45.738Z lightningd(27349): backtrace: lightningd/peer_htlcs.c:453 (send_htlc_out) 0x429bf5
2019-01-06T18:17:45.738Z lightningd(27349): backtrace: lightningd/peer_htlcs.c:548 (forward_htlc) 0x429f35
2019-01-06T18:17:45.738Z lightningd(27349): backtrace: lightningd/peer_htlcs.c:586 (channel_resolve_reply) 0x42a038
2019-01-06T18:17:45.738Z lightningd(27349): backtrace: lightningd/subd.c:282 (sd_msg_reply) 0x42e601
2019-01-06T18:17:45.738Z lightningd(27349): backtrace: lightningd/subd.c:421 (sd_msg_read) 0x42eb5c
2019-01-06T18:17:45.738Z lightningd(27349): backtrace: ccan/ccan/io/io.c:59 (next_plan) 0x46a828
2019-01-06T18:17:45.738Z lightningd(27349): backtrace: ccan/ccan/io/io.c:395 (do_plan) 0x46b31d
2019-01-06T18:17:45.738Z lightningd(27349): backtrace: ccan/ccan/io/io.c:405 (io_ready) 0x46b35b
2019-01-06T18:17:45.738Z lightningd(27349): backtrace: ccan/ccan/io/poll.c:310 (io_loop) 0x46cebb
2019-01-06T18:17:45.738Z lightningd(27349): backtrace: lightningd/lightningd.c:745 (main) 0x417e40
2019-01-06T18:17:45.738Z lightningd(27349): backtrace: (null):0 ((null)) 0x7f6bb06c282f
2019-01-06T18:17:45.738Z lightningd(27349): backtrace: (null):0 ((null)) 0x403618
2019-01-06T18:17:45.738Z lightningd(27349): backtrace: (null):0 ((null)) 0xffffffffffffffff
Log dumped in crash.log.20190106181745
lightning_channeld: lightning_channeld: lightning_channeld: lightning_channeld: Writing out status 65522Writing out status 65522Writing out status 65522: : lightning_channeld: lightning_channeld: Writing out status 65522Broken pipe
Writing out status 65522Writing out status 65522: Broken pipe
: : Broken pipe
Broken pipe
Broken pipe
lightning_channeld: Writing out status 65522lightning_channeld: Writing out status 65522: Broken pipe
lightning_channeld: Writing out status 65522: Broken pipe
lightning_channeld: Writing out status 65522: Broken pipe
: Broken pipe
Aborted
: Broken pipe
lightning_channeld: Writing out status 65522: Broken pipe
stufftech@ns508707:~/lightning$
lightning_channeld: Writing out status 65522: Broken pipe
stufftech@ns508707:~/lightning$ lightning_channeld: Writing out status 65522: Broken pipe
lightning_channeld: Writing out status 65522: Broken pipe
lightning_channeld: Writing out status 65522: Broken pipe
lightning_channeld: Writing out status 65522: Broken pipe
lightning_channeld: Writing out status 65522: lightning_channeld: Writing out status 65522: Broken pipe
lightning_channeld: Writing out status 65522Broken pipe
lightning_channeld: Writing out status 65522: Broken pipe
lightning_channeld: Writing out status 65522: Broken pipe
lightning_channeld: Writing out status 65522: Broken pipe
: Broken pipe
lightning_channeld: Writing out status 65522lightning_channeld: Writing out status 65522: Broken pipe
lightning_channeld: lightning_channeld: Writing out status 65522Writing out status 65522: Broken pipe
: Broken pipe
lightning_channeld: Writing out status 65522: Broken pipe
: Broken pipe
lightning_channeld: Writing out status 65522: Broken pipe
lightning_channeld: Writing out status 65522: lightning_channeld: Broken pipe
Writing out status 65522: Broken pipe
lightning_channeld: Writing out status 65522: Broken pipe
lightning_channeld: Writing out status 65522: Broken pipe
lightning_channeld: Writing out status 65520: Broken pipe

Based on https://github.com/btcpayserver/lightning/tree/basedon-v0.6.2

@NicolasDorier

This comment has been minimized.

Copy link
Contributor Author

commented Jan 8, 2019

I saw lot's of complain the last 2 or 3 days about c-lightning users of BTCPay. Unsure if this is the same root issue for everybody, but something is fishy.

@pavlenex

This comment has been minimized.

Copy link

commented Jan 8, 2019

Can confirm that on more than one occasion my c-lightning node on BTCPay kept crashing since December the 4th. Logs show similar errors, so here's shorter version.

2019-01-06T18:31:56.681Z lightningd(28): new_htlc_out:Input cltv_expiry 0 less than 557787?
lightningd: Fatal signal 6 (version 85e4d9e-modded)
0x5589ca4ca61e crashdump
	common/daemon.c:38
0x7fa74368e0e9 ???
	???:0
2019-01-06T18:31:56.699Z lightningd(28): FATAL SIGNAL 6 (version 85e4d9e-modded)
2019-01-06T18:31:56.699Z lightningd(28): backtrace: common/daemon.c:43 (crashdump) 0x5589ca4ca672
2019-01-06T18:31:56.699Z lightningd(28): backtrace: (null):0 ((null)) 0x7fa74368e0e9
Log dumped in crash.log.20190106183156
lightning_channeld: Writing out status 65522: Broken pipe
lightning_channeld: Writing out status 65522: Broken pipe
lightning_channeld: Writing out status 65522: Broken pipe
lightning_channeld: Writing out status 65522: Broken pipe
lightning_channeld: Writing out status 65522: Broken pipe
lightning_channeld: Writing out status 65522: Broken pipe
lightning_channeld: Writing out status 65522: Broken pipe
lightning_channeld: Writing out status 65522: Broken pipe
lightning_channeld: Writing out status 65522: Broken pipe
lightning_channeld: Writing out status 65522: Broken pipe
lightning_channeld: Writing out status 65522: Broken pipe
lightning_channeld: Writing out status 65522: Broken pipe
lightning_channeld: Writing out status 65522: Broken pipe
lightning_channeld: Writing out status 65522: Broken pipe
lightning_channeld: Writing out status 65522: Broken pipe
lightning_channeld: Writing out status 65522: Broken pipe
./entrypoint.sh: line 99:    28 Aborted                 (core dumped) lightningd "$@"
Waiting for the node to start and sync
BTC: Is fully synched
Node synched
Replaced network mainnet by bitcoin in /root/.lightning/config
2019-01-06T18:32:01.816Z lightningd(28): 02ad6fb8d693dc1e4569bcedefadf5f72a931ae027dc0f0c544b34c1c6f3b9a02b chan #4293: Failing old unprocessed HTLC #75
@rustyrussell

This comment has been minimized.

Copy link
Contributor

commented Jan 9, 2019

This looks very much like the problem fixed in 3006844. Latest master should fix this, but we may need to rush out a release as soon as possible.

@NicolasDorier

This comment has been minimized.

Copy link
Contributor Author

commented Jan 9, 2019

I made a new version based on master, I will keep up to date if this problem happen again.

@NicolasDorier

This comment has been minimized.

Copy link
Contributor Author

commented Jan 9, 2019

Closing, will reopen if still issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.