openoms

Switch to a US English environment to solve this.

@rootzoll [d52f15c](https://github.com/raspiblitz/raspiblitz/pull/4533/commits/d52f15cdac012a6e076018c5ec97bd04684c5e63) and [68b478d](https://github.com/raspiblitz/raspiblitz/pull/4533/commits/68b478d9f74ecae49d24f668a6a1984deac1a770) are catching errors which affect the run of the scripts already. Making these changes allows us to use shellcheck more rigorously so there are no new...

Disabled checking the lines which are working correctly, but causing shellcheck errors. The rest are actual bugs.

@rootzoll should we include [d52f15c](https://github.com/raspiblitz/raspiblitz/pull/4533/commits/d52f15cdac012a6e076018c5ec97bd04684c5e63) separately?

Happens to me from time to time as well, seems to do with filling up a temp folder. Will look into the specifics next time it happens.

Thanks, will update.

I would go as high as avoiding outputs less than 20k sats (the minimum LN channel size) then later a dynamically chosen amount makes sense with `peerswap-strict-amount=false` as described above.

Tried with `peerswap-bitcoin-rpchost=127.0.0.1` and with the line removed, but the output remains the same: ``` DEBUG plugin-peerswap-plugin: connecting with RPC_USER, RPC_PASSWORD to :0 INFO plugin-peerswap-plugin: Killing plugin: exited during normal...

IPv6 was not used on any related interface, but in any case disabled everywhere and also restarted, but no change,

ok, can confirm this. The rpc connection settings were not set as running with the same user lightningd can read them from the bitcoin.conf. Working CLN config: ``` # lightningd...