Can't find any PR related to this particular flake but let's figure it out. It appears to be an address in use error, so probably this is about either cln-grpc binding to a port we used twice or perhaps cln-grpc is forwarding an error along.
lightningd-2 2026-06-10T18:33:42.537Z DEBUG lightningd: Increasing file descriptor limit to 65524 (0 channels, max is 65524)
lightningd-2 2026-06-10T18:33:42.567Z DEBUG gossipd: pid 44503, msgfd 68
lightningd-2 2026-06-10T18:33:45.042Z DEBUG gossipd: gossip_store: 0 live records, 0 deleted
lightningd-2 2026-06-10T18:33:45.048Z DEBUG gossipd: seeker: state = STARTING_UP New seeker
lightningd-2 2026-06-10T18:33:45.048Z DEBUG gossipd: REPLY WIRE_GOSSIPD_INIT_REPLY with 0 fds
lightningd-2 2026-06-10T18:33:45.057Z DEBUG lightningd: io_break: gossipd_init_done
lightningd-2 2026-06-10T18:33:45.057Z DEBUG lightningd: io_loop: gossip_init
lightningd-1 2026-06-10T18:33:45.193Z DEBUG connectd: pid 44592, msgfd 70
lightningd-1 2026-06-10T18:33:45.237Z DEBUG hsmd: preinit: dev_fail_preapprove = 0, dev_no_preapprove_check = 0, dev_warn_on_overgrind = 0
lightningd-1 2026-06-10T18:33:45.238Z DEBUG hsmd: Client: Received message 27 from client
lightningd-1 2026-06-10T18:33:45.238Z DEBUG hsmd: Client: Received message 27 from client
lightningd-1 2026-06-10T18:33:45.238Z DEBUG hsmd: Client: Received message 27 from client
lightningd-1 2026-06-10T18:33:45.238Z DEBUG hsmd: new_client: 0
lightningd-2 2026-06-10T18:33:45.297Z DEBUG plugin-cln-lsps-client: Killing plugin: disabled itself at init: `experimental-lsps-client` not enabled
lightningd-2 2026-06-10T18:33:45.330Z DEBUG plugin-wss-proxy: Killing plugin: disabled itself at init: `wss-bind-addr` option is not configured
lightningd-2 2026-06-10T18:33:45.337Z DEBUG plugin-clnrest: Killing plugin: disabled itself at init: `clnrest-port` option is not configured
lightningd-2 2026-06-10T18:33:45.369Z DEBUG plugin-cln-lsps-service: Killing plugin: disabled itself at init: `experimental-lsps2-service` not enabled
lightningd-2 2026-06-10T18:33:45.402Z UNUSUAL plugin-cln-grpc: Error running grpc interface: Err(serving requests
lightningd-2 2026-06-10T18:33:45.405Z UNUSUAL plugin-cln-grpc:
lightningd-2 2026-06-10T18:33:45.406Z UNUSUAL plugin-cln-grpc: Caused by:
lightningd-2 2026-06-10T18:33:45.406Z UNUSUAL plugin-cln-grpc: 0: transport error
lightningd-2 2026-06-10T18:33:45.407Z UNUSUAL plugin-cln-grpc: 1: Address already in use (os error 98))
lightningd-2 2026-06-10T18:33:45.421Z INFO plugin-cln-grpc: Killing plugin: exited during normal operation
lightningd-2 2026-06-10T18:33:45.422Z **BROKEN** plugin-cln-grpc: Plugin marked as important, shutting down lightningd!
(CI log)
Can't find any PR related to this particular flake but let's figure it out. It appears to be an address in use error, so probably this is about either
cln-grpcbinding to a port we used twice or perhapscln-grpcis forwarding an error along.