0

UniFi cli fail to activate

In the latest Unifi OS beta build 1.9.0-12 at https://community.ui.com/releases/UniFi-Dream-Machine-Firmware-1-9-0-12/43915f9b-3bae-4958-93cb-fc0a8687d70b nextdns cli on my unifi dream machine error like this

 

  ___ ___      .__________.__
 |   |   |____ |__\_  ____/__|
 |   |   /    \|  ||  __) |  |   (c) 2010-2021
 |   |  |   |  \  ||  \   |  |   Ubiquiti Inc.
 |______|___|  /__||__/   |__|
            |_/                  http://www.ui.com

      Welcome to UniFi Dream Machine!
# uname -a
Linux UDM 4.1.37-v1.9.0-12.3406-c12d863 #1 SMP Fri Feb 19 06:02:12 UTC 2021 aarch64 GNU/Linux
# nextdns version
nextdns version 1.10.1
# nextdns status
running
# nextdns activate
Error: setup resolv.conf: rename /etc/resolv.conf /etc/resolv.conf.nextdns-bak: device or resource busy
Error: non zero exit code: 1: OCI runtime error
#

5 replies

null
    • Rohit
    • 3 yrs ago
    • Reported - view

    try sudo nextdns activate

    • Poomrat_Boonyawong
    • 2 yrs ago
    • Reported - view

    I’m already login as root and no it doesn’t change anything in latest firmware.

    In fact even the log shows similar error.

    # nextdns log
    Apr 02 00:09:48 ubnt systemd[1]: Starting NextDNS DNS53 to DoH proxy....
    Apr 02 00:09:48 ubnt nextdns[857]: Starting NextDNS 1.10.1/linux on localhost:5553
    Apr 02 00:09:48 ubnt nextdns[857]: Starting mDNS discovery
    Apr 02 00:09:48 ubnt nextdns[857]: Listening on TCP/127.0.0.1:5553
    Apr 02 00:09:48 ubnt nextdns[857]: Listening on UDP/127.0.0.1:5553
    Apr 02 00:09:49 ubnt ssh[858]: Warning: Permanently added '127.0.0.1' (RSA) to the list of known hosts.
    Apr 02 00:09:49 ubnt ssh[858]: Welcome to UbiOS
    Apr 02 00:09:49 ubnt ssh[858]: By logging in, accessing, or using the Ubiquiti product, you
    Apr 02 00:09:49 ubnt ssh[858]: acknowledge that you have read and understood the Ubiquiti
    Apr 02 00:09:49 ubnt ssh[858]: License Agreement and agree to be bound by its terms.
    Apr 02 00:09:49 ubnt systemd[1]: Started NextDNS DNS53 to DoH proxy..
    Apr 02 00:10:16 ubnt nextdns[857]: Setting up router
    Apr 02 00:10:17 ubnt nextdns[857]: Activating
    Apr 02 00:10:17 ubnt nextdns[857]: Activate: setup resolv.conf: rename /etc/resolv.conf /etc/resolv.conf.nextdns-bak: device or resource busy
    Apr 02 00:10:18 ubnt nextdns[857]: Connected 45.90.28.0:443 (con=28ms tls=222ms, TLS13)
    Apr 02 00:10:18 ubnt nextdns[857]: Connected 116.204.183.61:443 (con=6ms tls=10ms, TLS13)
    Apr 02 00:10:18 ubnt nextdns[857]: Switching endpoint: https://dns.nextdns.io.#43.229.79.19,116.204.183.61
    Apr 02 00:12:55 ubnt nextdns[857]: Control client connected: &{{0x4000206e80}}
    Apr 02 00:12:55 ubnt nextdns[857]: Control client sent event: &{{0x4000206e80}}: cache-stats(<nil>)
    Apr 02 00:12:55 ubnt nextdns[857]: Control client disconnected: &{{0x4000206e80}}
    Apr 02 00:14:45 ubnt nextdns[857]: Connected 116.204.183.61:443 (con=6ms tls=12ms, TLS13)
    Apr 02 00:15:25 ubnt nextdns[857]: Connected 43.229.79.19:443 (con=5ms tls=10ms, TLS13)
    Apr 02 00:17:37 ubnt nextdns[857]: Connected 116.204.183.61:443 (con=6ms tls=10ms, TLS13)
    #
    
    
    • Aspi
    • 2 yrs ago
    • Reported - view

    Same issue here with UDM Pro running 1.9.2.3432

    • Rick_Ross
    • 2 yrs ago
    • Reported - view

    Same problem here with UDM Pro running 1.10.0-8

    • S_Lassen
    • 2 yrs ago
    • Reported - view

    Did you manage to fix this?

Content aside

  • 2 yrs agoLast active
  • 5Replies
  • 254Views
  • 5 Following