NextDNS CLI stopped on ASUS router (why?)
Today my MacBook Pro was totally unresponsive. Investigation revealed that the NextDNS CLI client had stopped on my router (so all DNS lookups failed). I have noticed the client being in "stopped" state, without me asking it to stop, a couple of times recently.
How can I (help you) debug what's going on?
- Router: ASUS RT-AC86U
- Firwmare: ASUSWRT-Merlin RT-AC86U 386.1_beta2
- NextDNS CLI client: nextdns version 1.9.4
-
Please check the logs with “nextdns log” command.
-
That log is empty...
In /opt/var/log/nextdns.log the last entry is from 01:24 this morning. No errors.
-
It just stopped again.
"nextdns log" is still empty; last entry in /opt/var/log/nextdns.log is still 01:24 this morning.
-
And a third time today!
This is getting very annoying...
-
Has not reproduced during Christmas.
Hope it keeps working now!
-
Was fine the entire holiday, but the first day of work(ing at home; COVID-19 measures) the issue hit me hard again...
How to debug/fix?
"Relevant" log:
Jan 4 01:23:26 ac86u nextdns[20703]: Connected <IP>:443 (con=14ms tls=43ms, TLS13) Jan 4 09:13:21 ac86u nextdns.init: Stopped Jan 4 09:13:26 ac86u nextdns.init: Not running(so no entries when it broke?)
-
Rob do you see OOM messages in logs or something that could explain why the process get killed?
-
Olivier Poitrey Is OOM a literal string I should search for?
Or is it an abbreviation for something, like "Out Of Memory"?
(I see neither BTW)
-
-
Happened two more times today.
Is there a way to generate (more/debug) logging?
-
Rob you can enable query logging, but I'm not sure it will be helpful. The daemon is not supposed to quite silently like that. If there is a crash, it should spit out a stack trace or something.
-
