peerswap can fail to start if lightningd startup is too slow

[wtogami]

2025-01-28T18:01:44.190Z INFO    plugin-peerswap: Killing plugin: exited before replying to init

peerswap can fail to start if lightningd startup is too slow.

Version: peerswap 3eadb6b

[grubles]

How long did it take to start?

[YusukeShimizu]

c-lightning has a 60-second timeout for both “getmanifest” and “init.”
https://docs.corelightning.org/docs/a-day-in-the-life-of-a-plugin#timeouts

Any plugin that fails to respond within this timeframe is forcibly terminated. It is highly likely that the peerswap plugin is exceeding this timeout during its startup process and thus terminates before responding to “init.”

The current startup process involves establishing a Unix domain socket connection with CLN, which is taking too long. Making this process asynchronous could potentially resolve the issue, but the full scope of the impact is not yet fully understood.

[grubles]

This CLN commit that bumps the timeout to 120 seconds might help: ElementsProject/lightning@ee3133f

[YusukeShimizu]

There is also the approach mentioned at #346 (comment), but how about we consider this issue resolved once v25.02, which includes those changes, is released and the startup is confirmed stable?

[grubles]

@YusukeShimizu yes once we can confirm peerswap can start using v25.02 we can close this.

[grubles]

@wtogami have you given CLN v25.02.x a try?