More often than not, after AP is rebooted, local dnsmasq is not working until killed and respawned. Interesting thing is that I have 7 APs, a mix of old UAPs and new UAP-AC and UAP-Ac-Lites and it does not happen all the time on all of them, but it is getting worse, now its one out of 10 reboots it comes up OK without restarting dnsmasq.
example: alex@staff:~$ ssh firstname.lastname@example.org reboot (2 mins wait until it reboots) alex@staff:~$ dig google.com @192.168.2.186 ; <<>> DiG 9.10.3-P4-Debian <<>> google.com @192.168.2.186 ;; global options: +cmd ;; connection timed out; no servers could be reached alex@staff:~$ ssh email@example.com BusyBox v1.25.1 () built-in shell (ash) ___ ___ .__________.__ | | |____ |__\_ ____/__| | | / \| || __) | | (c) 2010-2019 | | | | \ || \ | | Ubiquiti Networks, Inc. |______|___| /__||__/ |__| |_/ https://www.ui.com/ Welcome to UniFi UAP-AC-Lite! FirstFloor2-BZ.v4.0.42# pkill dnsmasq FirstFloor2-BZ.v4.0.42# Connection to 192.168.2.186 closed. alex@staff:~$ dig google.com @192.168.2.186 +short 126.96.36.199
As mentioned I have 7 APs, all are on the latest firmware (v188.8.131.5233) , except one of them is on 184.108.40.20636 and that one is always OK. I have rebooted so many times to try to pinpoint the pattern, but I can't find any.
Any suggestions on how to debug this further are appreciated
How is it doing on 4.0.21?
USG-XG-8 • USG-4-PRO • USG
US-XG-16 • US-48-500W • US-24-POE-250W 2x • US-16-POE-150W 3x • US-24 • US-8-150W • US-8
UAP XG • UAP-SHD • UAP-HD • UAP-NanoHD 2x • UAP-AC-PRO 2x • UAP-AC-LITE • UAP-AC-IW • UAP-AC-M • UAP-AC-M-PRO 2x
UAS-XG • UCK-G2-PLUS • UCK-G2 • UCK
There's a solution for this in testing - it's a now known issue (this was discovered thanks to feedback from 4.042 public release).