Open brodyhoskins opened 5 years ago
Are you saying that stubby exits after the very first TLS session is closed (or is it more random than that)? If so that sounds like the underlying problem, not how stubby is being run. Do you have the logs for this (run with -l for full logging)?
I don't think it is related but also be aware of: https://github.com/getdnsapi/stubby/issues/124
Hi, have you solved this? I have the same problem and I can't find a solution.
I unfortunately did not. I ended up switching to unbound.
On Mar 30, 2019, at 7:19 PM, Acris Liu notifications@github.com wrote:
Hi, do you solve it? I have the same problem and I can't find a solution.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.
Problem still persist with Stubby 0.2.6.
Solved by starting it with nohup stubby -g
.
I'm running stubby on an ASUS router (with asuswrt-merlin installed) and while I've installed stubby via Entware, stubby exits when an ssh session is terminated while running as a daemon with the -g flag. I've attempted using
nohup
as a workaround but stubby still exits when the ssh session is terminated.Is there another option to run stubby as a "true" daemon?