Problem with the gRPC on Debian 11.7 VMs in a proxmox cluster.

[2Fast2BCn]

ref. lncapital/torq#4

Someone is trying to use Torq but somehow is getting a strange response from CLN.
I suspect the error is originating in CLN (v23.08.1) itself so I'm wondering what the next steps would be to resolve/investigate this situation.

rpc error: code = Internal desc = No such file or directory (os error 2)

[cdecker]

That sounds like it's the cln-grpc crate attempting to talk to the JSON-RPC socket, but being unable to connect to it. Do you somehow configure the RPC socket file to be in a custom location (not ${lightning-dir}/lightning-rpc)? If yes, we may have to teach cln-grpc how to read that from the configuration.

[martinbehrens]

Thanks Christian! It's set in the config file with rpc-file=/home/$HOME/.lightning/lightning-rpc while $HOME is the user running CLN of course. That should equal the default location and the RPC socket exists in that very location.

[martinbehrens]

The initial issue refers to CLN v23.08.1-modded and unfortunately persists with CLN v23.08.1-3-g2a870eb-modded (v23.11 - bump version?) and Torq v1.4.3 (commit: c910f01):

{"level":"warn","protocol":"grpc","grpc.component":"client","grpc.service":"cln.Node","grpc.method":"Getinfo","grpc.method_type":"unary","grpc.start_time":"2023-12-13T01:03:46Z","grpc.request.deadline":"2023-12-13T01:05:46Z","grpc.code":"Internal","grpc.error":"rpc error: code = Internal desc = No such file or directory (os error 2)","grpc.time_ms":"11.66","message":"finished call"} {"level":"error","error":"Get info from CLN Node: Obtaining information from CLN: rpc error: code = Internal desc = No such file or directory (os error 2)","time":"2023-12-13T01:03:46Z"}

@cdecker Is there anything that can be done to debug/fix this? Log level is set to log-level=debug already but there's nothing in the CLN log pertaining this issue I can spot.