[c-lightning] [Announce] CLBOSS Automated C-Lightning Node Manager

Christian Decker decker.christian at gmail.com
Fri Jul 15 18:04:31 AEST 2022


Ciao Andrea,

this appears to be the same issue reported in issues #5395 [1] and
#5387 [3], and addressed in PR #5400.
Can you check out the latest version and see if that solves the issue?

Cheers,
Christian

[1] https://github.com/ElementsProject/lightning/issues/5395
[2] https://github.com/ElementsProject/lightning/pull/5400
[3] https://github.com/ElementsProject/lightning/issues/5387

On Fri, Jul 15, 2022 at 9:59 AM Andrea Proia <andrea.proia at gmail.com> wrote:
>
> Hello,
> I recently started a new CLN (v0.11.0.1-189-g87a66c1)node on a Debian 11 machine, installed following the https://lightning.readthedocs.io/INSTALL.html#to-build-on-ubuntu documentation, and opened a few channels. I wanted to have automatic fees so I installed CLBOSS 0.13A from the official source release, following the readme.
> When I restarted (after adding plugin=/usr/local/bin/clboss to .lightning/config file) lightningd crashed so I quickly commented the plugin path in config, saved and restarted again. Now every few hours it happens that lightningd crashes, and I can’t figure out why, I saved the txt it gave me the last time, you can see it below. I am very excited about CLBOSS and would very much appreciate your help in making it work for me.
> Thank you
> Andrea
>
> gossipd/gossip_store.c:644: delete_by_index: Assertion `(be32_to_cpu(belen) & GOSSIP_STORE_LEN_DELETED_BIT) == 0' failed.
> lightning_gossipd: FATAL SIGNAL 6 (version v0.11.0.1-189-g87a66c1)
> 0x55babf153cea send_backtrace
>         common/daemon.c:33
> 0x55babf153d72 crashdump
>         common/daemon.c:46
> 0x7fc00915cd5f ???
>         ./signal/../sysdeps/unix/sysv/linux/x86_64/sigaction.c:0
> 0x7fc00915cce1 __GI_raise
>         ../sysdeps/unix/sysv/linux/raise.c:51
> 0x7fc009146536 __GI_abort
>         ./stdlib/abort.c:79
> 0x7fc00914640e __assert_fail_base
>         ./assert/assert.c:92
> 0x7fc009155661 __GI___assert_fail
>         ./assert/assert.c:101
> 0x55babf147852 delete_by_index
>         gossipd/gossip_store.c:644
> 0x55babf14834c gossip_store_delete
>         gossipd/gossip_store.c:665
> 0x55babf14de49 routing_add_node_announcement
>         gossipd/routing.c:1730
> 0x55babf14e18b handle_node_announcement
>         gossipd/routing.c:1851
> 0x55babf1454b9 handle_node_announce
>         gossipd/gossipd.c:281
> 0x55babf146ba9 handle_recv_gossip
>         gossipd/gossipd.c:507
> 0x55babf146c96 connectd_req
>         gossipd/gossipd.c:583
> 0x55babf153e25 handle_read
>         common/daemon_conn.c:31
> 0x55babf1851ae next_plan
>         ccan/ccan/io/io.c:59
> 0x55babf185635 do_plan
>         ccan/ccan/io/io.c:407
> 0x55babf1856ce io_ready
>         ccan/ccan/io/io.c:417
> 0x55babf186fbd io_loop
>         ccan/ccan/io/poll.c:453
> 0x55babf146e8b main
>         gossipd/gossipd.c:1130
> 0x7fc009147d09 __libc_start_main
>         ../csu/libc-start.c:308
> 0x55babf141e49 ???
>         ???:0
> 0xffffffffffffffff ???
>         ???:0
> lightning_gossipd: FATAL SIGNAL (version v0.11.0.1-189-g87a66c1)
> 0x55babf153cea send_backtrace
>         common/daemon.c:33
> 0x55babf15a74f status_failed
>         common/status.c:221
> 0x55babf15a847 status_backtrace_exit
>         common/subdaemon.c:18
> 0x55babf153d78 crashdump
>         common/daemon.c:49
> 0x7fc00915cd5f ???
>         ./signal/../sysdeps/unix/sysv/linux/x86_64/sigaction.c:0
> 0x7fc00915cce1 __GI_raise
>         ../sysdeps/unix/sysv/linux/raise.c:51
> 0x7fc009146536 __GI_abort
>         ./stdlib/abort.c:79
> 0x7fc00914640e __assert_fail_base
>         ./assert/assert.c:92
> 0x7fc009155661 __GI___assert_fail
>         ./assert/assert.c:101
> 0x55babf147852 delete_by_index
>         gossipd/gossip_store.c:644
> 0x55babf14834c gossip_store_delete
>         gossipd/gossip_store.c:665
> 0x55babf14de49 routing_add_node_announcement
>         gossipd/routing.c:1730
> 0x55babf14e18b handle_node_announcement
>         gossipd/routing.c:1851
> 0x55babf1454b9 handle_node_announce
>         gossipd/gossipd.c:281
> 0x55babf146ba9 handle_recv_gossip
>         gossipd/gossipd.c:507
> 0x55babf146c96 connectd_req
>         gossipd/gossipd.c:583
> 0x55babf153e25 handle_read
>         common/daemon_conn.c:31
> 0x55babf1851ae next_plan
>         ccan/ccan/io/io.c:59
> 0x55babf185635 do_plan
>         ccan/ccan/io/io.c:407
> 0x55babf1856ce io_ready
>         ccan/ccan/io/io.c:417
> 0x55babf186fbd io_loop
>         ccan/ccan/io/poll.c:453
> 0x55babf146e8b main
>         gossipd/gossipd.c:1130
> 0x7fc009147d09 __libc_start_main
>         ../csu/libc-start.c:308
> 0x55babf141e49 ???
>         ???:0
> 0xffffffffffffffff ???
>         ???:0
> lightningd: gossipd failed (exit status 242), exiting.
> Lost connection to the RPC socket.Lost connection to the RPC socket.Lost connection to the RPC socket.Lost connection to the RPC socket.
>
>
>
> Lost connection to the RPC socket.Lost connection to the RPC socket.
> --
> c-lightning mailing list
> c-lightning at lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/c-lightning


More information about the c-lightning mailing list