-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
darkfid rpc stops listening after some time ("Error: Connection failed") #181
Comments
Hello @shrugs ! From the logs I can safely asume you are using I would suggest checking if the daemon has changed its listenning port, forced by some We are not oficially supporting that os, and we don't plan to investigate this os specific issue. Sanity assumption: you are on tag v0.4.1 KR |
i am on 0.4.1, sorry for not including that 😅 understood, thanks! will do some soft debugging in my free time |
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 ping
s 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
The text was updated successfully, but these errors were encountered: