darkfid rpc stops listening after some time ("Error: Connection failed")

[shrugs]

i'm able to sync testnet successfully, validate transactions, etc, but the rpc exposed by darkfid stops listening after some time (or some event). after the circuits have been created, the RPC server is started, and in that moment the various commands like ./drk ping work, but after some time (the daemon seems to be busy handling outbound connections) the rpc server stops listening. if I get a ./drk scan off while the rpc is listening, that command seems to have no trouble continuing to scan the entire chain, even after subsequent ./drk pings return "Error: Connection failed".

there are no other logs related to the rpc, beyond the "16:43:47 [INFO] rpc::server: JSON-RPC server accepted connection from tcp://127.0.0.1:51300" triggered upon ./drk invocation.

full output: https://gist.github.com/shrugs/01f351680d6f5eac137fd916ac65657c

[aggstam]

Hello @shrugs !

From the logs I can safely asume you are using MacOs (correct me if I'm wrong), where this issue has been reported by other users of in the past, not as a ticket tho, and seems to exist only on that operating system.

I would suggest checking if the daemon has changed its listenning port, forced by some os rule.

We are not oficially supporting that os, and we don't plan to investigate this os specific issue. We would of course appreciate any contributions on further investigating this issue, and verify whether or not this is just an os specific issue, or a code related issue.

Sanity assumption: you are on tag v0.4.1

KR

[shrugs]

i am on 0.4.1, sorry for not including that 😅

understood, thanks! will do some soft debugging in my free time