Reply
Emerging Member
Posts: 73
Registered: ‎05-19-2017
Kudos: 2

USG disconnected from UniFi controller

[ Edited ]

Suddenly the USG is disconnected from the controller. Seems fine in SSH.

 

I rebooted controller and USG, but nothing changes.

 

I cant log into USG via browsing the IP. Or yes i can, but it says "The Gateway status is currently unknown".

The problem now is that i have no clue how to troubleshoot this? What is happening? It seems to be a USG vs. controller issue.

 

 

 Maybe someone could help troubleshoot on this:

Oct 26 00:41:11 USG rsyslogd: set SCM_CREDENTIALS failed on '/dev/log': Protocol not available
Oct 26 00:41:11 USG kernel: Linux version 3.10.20-UBNT (usg-builder@slc-build-usg) (gcc version 4.7.0 (Cavium Inc. Version: SDK_3_1_0_p2 build 34) ) #1 SMP Fri Jun 23 08:47:03 MDT 2017
Oct 26 00:41:11 USG kernel: CVMSEG size: 2 cache lines (256 bytes)
Oct 26 00:41:11 USG kernel: Checking for the multiply/shift bug... no.
Oct 26 00:41:11 USG kernel: Checking for the daddiu bug... no.
Oct 26 00:41:11 USG kernel: Zone ranges:
Oct 26 00:41:11 USG kernel:  DMA32    [mem 0x00400000-0xefffffff]
Oct 26 00:41:11 USG kernel:  Normal   empty
Oct 26 00:41:11 USG kernel: Movable zone start for each node
Oct 26 00:41:11 USG kernel: Early memory node ranges
Oct 26 00:41:11 USG kernel:  node   0: [mem 0x00400000-0x00a2ffff]
Oct 26 00:41:11 USG kernel:  node   0: [mem 0x00c00000-0x0effffff]
Oct 26 00:41:11 USG kernel:  node   0: [mem 0x0f200000-0x0fdfffff]
Oct 26 00:41:11 USG kernel:  node   0: [mem 0x20000000-0x8f7fffff]
Oct 26 00:41:11 USG kernel: Primary instruction cache 37kB, virtually tagged, 37 way, 8 sets, linesize 128 bytes.
Oct 26 00:41:11 USG kernel: Primary data cache 32kB, 32-way, 8 sets, linesize 128 bytes.
Oct 26 00:41:11 USG kernel: Secondary unified cache 1024kB, 16-way, 512 sets, linesize 128 bytes.
Oct 26 00:41:11 USG kernel: Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 512622
Oct 26 00:41:11 USG kernel: Kernel command line:  root=/dev/mmcblk0p2 rootdelay=10 rw rootsqimg=squashfs.img rootsqwdir=w mtdparts=phys_mapped_flash:640k(boot0),640k(boot1),64k(eeprom) console=ttyS0,115200
Oct 26 00:41:11 USG kernel: Checking for the daddi bug... no.
Oct 26 00:41:11 USG kernel: octeon_pci_console: Console not created.
Oct 26 00:41:11 USG kernel: /proc/octeon_perf: Octeon performance counter interface loaded
Oct 26 00:41:11 USG kernel: Bootbus flash: Setting flash for 8MB flash at 0x1f400000
Oct 26 00:41:11 USG kernel: phys_mapped_flash: Swapping erase regions for top-boot CFI table.
Oct 26 00:41:11 USG kernel: number of CFI chips: 1
Oct 26 00:41:11 USG kernel: 3 cmdlinepart partitions found on MTD device phys_mapped_flash
Oct 26 00:41:11 USG kernel: Creating 3 MTD partitions on "phys_mapped_flash":
Oct 26 00:41:11 USG kernel: 0x000000000000-0x0000000a0000 : "boot0"
Oct 26 00:41:11 USG kernel: 0x0000000a0000-0x000000140000 : "boot1"
Oct 26 00:41:11 USG kernel: 0x000000140000-0x000000150000 : "eeprom"
Oct 26 00:41:11 USG kernel: Algorithmics/MIPS FPU Emulator v1.5
Oct 26 00:41:11 USG kernel: ubnt_platform: module license 'Proprietary' taints kernel.
Oct 26 00:41:11 USG kernel: Disabling lock debugging due to kernel taint
Oct 26 00:41:11 USG kernel: octeon-ethernet 2.0
Oct 26 00:41:11 USG kernel: Interface 0 has 4 ports (SGMII)
Oct 26 00:41:11 USG kernel: Interface 1 has 4 ports (SGMII)
Oct 26 00:41:11 USG kernel: Interface 2 has 4 ports (NPI)
Oct 26 00:41:11 USG kernel: Interface 3 has 4 ports (LOOP)
Oct 26 00:41:14 USG kernel: ip_set: protocol 6
Oct 26 00:41:17 USG zebra[636]: Zebra 0.99.20.1 starting: vty@0
Oct 26 00:41:19 USG rl-system.init: Checking/creating SSH host keys.
Oct 26 00:41:23 USG rsyslogd: set SCM_CREDENTIALS failed on '/dev/log': Protocol not available
Oct 26 00:41:23 USG rsyslogd: set SCM_CREDENTIALS failed on '/dev/log': Protocol not available
Oct 26 00:41:37 USG zebra[636]: interface eth0 index 2 changed <UP,BROADCAST,RUNNING,MULTICAST>.
Oct 26 00:41:37 USG zebra[636]: interface eth0 index 2 changed <UP,BROADCAST,MULTICAST>.
Oct 26 00:41:38 USG zebra[636]: interface eth1 index 3 changed <UP,BROADCAST,RUNNING,MULTICAST>.
Oct 26 00:41:38 USG zebra[636]: interface eth1 index 3 changed <UP,BROADCAST,MULTICAST>.
Oct 26 00:41:40 USG zebra[636]: interface eth3 index 5 changed <UP,BROADCAST,RUNNING,MULTICAST>.
Oct 26 00:41:40 USG zebra[636]: interface eth3 index 5 changed <UP,BROADCAST,MULTICAST>.
Oct 26 00:41:40 USG zebra[636]: interface eth3 index 5 changed <BROADCAST,MULTICAST>.
Oct 26 00:41:40 USG zebra[636]: interface eth1 index 3 changed <UP,BROADCAST,RUNNING,MULTICAST>.
Oct 26 00:41:40 USG kernel: eth1: 100 Mbps Full duplex, port 1
Oct 26 00:41:41 USG zebra[636]: interface eth0 index 2 changed <UP,BROADCAST,RUNNING,MULTICAST>.
Oct 26 00:41:41 USG kernel: eth0: 1000 Mbps Full duplex, port 0
Oct 26 00:41:41 USG zebra[636]: interface eth2 index 4 changed <UP,BROADCAST,RUNNING,MULTICAST>.
Oct 26 00:41:41 USG zebra[636]: interface eth2 index 4 changed <UP,BROADCAST,MULTICAST>.
Oct 26 00:41:43 USG ntpd[1954]: ntpd 4.2.6p2@1.2194-o Wed Jun 14 06:09:32 UTC 2017 (1)
Oct 26 00:41:43 USG ntpd[1955]: proto: precision = 25.210 usec
Oct 26 00:41:44 USG rsyslogd: set SCM_CREDENTIALS failed on '/dev/log': Protocol not available
Oct 26 00:41:45 USG ntpd[1955]: ntpd exiting on signal 15
Oct 26 00:41:45 USG zebra[636]: interface eth2 index 4 changed <UP,BROADCAST,RUNNING,MULTICAST>.
Oct 26 00:41:45 USG kernel: eth2: 1000 Mbps Full duplex, port 2
Oct 26 00:41:47 USG ntpd[2071]: ntpd 4.2.6p2@1.2194-o Wed Jun 14 06:09:32 UTC 2017 (1)
Oct 26 00:41:47 USG ntpd[2072]: proto: precision = 25.186 usec
Oct 26 00:41:47 USG ntpd[2072]: ntpd exiting on signal 15
Oct 26 00:41:49 USG ntpd[2130]: ntpd 4.2.6p2@1.2194-o Wed Jun 14 06:09:32 UTC 2017 (1)
Oct 26 00:41:49 USG ntpd[2131]: proto: precision = 25.176 usec
Oct 26 00:41:49 USG ubnt-service-ssh: waiting for netplugd to be started...
Oct 26 00:41:55 USG dhcpd: WARNING: Host declarations are global.  They are not limited to the scope you declared them in.
Oct 26 00:41:56 USG dhcpd:
Oct 26 00:41:56 USG dhcpd: No subnet declaration for eth2 (112.111.23.129).
Oct 26 00:41:56 USG dhcpd: ** Ignoring requests on eth2.  If this is not what
Oct 26 00:41:56 USG dhcpd:    you want, please write a subnet declaration
Oct 26 00:41:56 USG dhcpd:    in your dhcpd.conf file for the network segment
Oct 26 00:41:56 USG dhcpd:    to which interface eth2 is attached. **
Oct 26 00:41:56 USG dhcpd:
Oct 26 00:43:06 USG netplugd: Starting network plug daemon: netplugd.
Oct 26 00:43:08 USG dpi_wlan_fw_rules.pl: dpi_wlan_fw_rules.pl started
Oct 26 00:43:10 USG perl_wrapper: perl_wrapper.pl started
Oct 26 00:43:12 USG system: Process has crashed, creating coredump : core=/var/core/core-mcad-2460-1508971392.gz free-space=1180MB used-space=24%
Oct 26 00:43:13 USG ubnt-service-ssh: starting the SSH service (see messages from sshd).
Oct 26 00:43:18 USG mca-monitor: mca-client.service(): Failed sending request to '/tmp/.mcad' - 'No such file or directory'
Oct 26 00:43:49  mca-monitor: last message repeated 3 times
Oct 26 00:44:49  mca-monitor: last message repeated 6 times
Oct 26 00:45:49  mca-monitor: last message repeated 6 times
Oct 26 00:46:39  mca-monitor: last message repeated 5 times
Oct 26 00:46:39 USG syswrapper: kill-mcad. reason: mcad not responding
Oct 26 00:46:43 USG system: Process has crashed, creating coredump : core=/var/core/core-mcad-3195-1508971603.gz free-space=1179MB used-space=24%
Oct 26 00:46:51 USG mca-monitor: mca-client.service(): Failed sending request to '/tmp/.mcad' - 'No such file or directory'
Oct 26 00:48:01  mca-monitor: last message repeated 7 times
Oct 26 00:49:11  mca-monitor: last message repeated 7 times
Oct 26 00:50:11  mca-monitor: last message repeated 6 times
Oct 26 00:50:11 USG syswrapper: kill-mcad. reason: mcad not responding
Oct 26 00:50:15 USG system: Process has crashed, creating coredump : core=/var/core/core-mcad-3521-1508971815.gz free-space=1179MB used-space=24%
Oct 26 00:50:23 USG mca-monitor: mca-client.service(): Failed sending request to '/tmp/.mcad' - 'No such file or directory'
Oct 26 00:51:33  mca-monitor: last message repeated 7 times
Oct 26 00:52:43  mca-monitor: last message repeated 7 times
Oct 26 00:53:43  mca-monitor: last message repeated 6 times
Oct 26 00:53:43 USG syswrapper: kill-mcad. reason: mcad not responding
Oct 26 00:53:47 USG system: Process has crashed, creating coredump : core=/var/core/core-mcad-4186-1508972027.gz free-space=1179MB used-space=24%
Oct 26 00:53:55 USG mca-monitor: mca-client.service(): Failed sending request to '/tmp/.mcad' - 'No such file or directory'
Oct 26 00:55:05  mca-monitor: last message repeated 7 times
Oct 26 00:56:15  mca-monitor: last message repeated 7 times
Oct 26 00:57:16  mca-monitor: last message repeated 6 times
Oct 26 00:57:16 USG syswrapper: kill-mcad. reason: mcad not responding
Oct 26 00:57:20 USG system: Process has crashed, creating coredump : core=/var/core/core-mcad-4797-1508972240.gz free-space=1179MB used-space=24%
Oct 26 00:57:28 USG mca-monitor: mca-client.service(): Failed sending request to '/tmp/.mcad' - 'No such file or directory'
Oct 26 00:58:38  mca-monitor: last message repeated 7 times
Oct 26 00:59:48  mca-monitor: last message repeated 7 times
Oct 26 01:00:48  mca-monitor: last message repeated 6 times
Oct 26 01:00:48 USG syswrapper: kill-mcad. reason: mcad not responding
Oct 26 01:00:52 USG system: Process has crashed, creating coredump : core=/var/core/core-mcad-5258-1508972452.gz free-space=1179MB used-space=24%
Oct 26 01:01:00 USG mca-monitor: mca-client.service(): Failed sending request to '/tmp/.mcad' - 'No such file or directory'
Oct 26 01:02:10  mca-monitor: last message repeated 7 times
Oct 26 01:03:20  mca-monitor: last message repeated 7 times
Oct 26 01:04:20  mca-monitor: last message repeated 6 times
Oct 26 01:04:20 USG syswrapper: kill-mcad. reason: mcad not responding
Oct 26 01:04:24 USG system: Process has crashed, creating coredump : core=/var/core/core-mcad-5768-1508972664.gz free-space=1178MB used-space=24%
Oct 26 01:04:32 USG mca-monitor: mca-client.service(): Failed sending request to '/tmp/.mcad' - 'No such file or directory'
Oct 26 01:05:42  mca-monitor: last message repeated 7 times

 

Established Member
Posts: 1,483
Registered: ‎04-08-2014
Kudos: 473
Solutions: 75

Re: USG disconnected from UniFi controller

When you ssh into the USG, run "info". What does it report?
Controller: 5.9.26 | Sites: 12 | Devices: 55 | Clients: ~250
USGs (4.4.28): XG8 (x1) | Pro4 (x4) | USG3 (x4)
UAPs (3.9.50): AC-Pro (x17) | AC-LR (x3) | Mesh-Pro (x2) | Mesh (x1) | Outdoor+ (x2)
USWs (3.9.50): US-16XG (x2) | US-40-500w (x3) | US-24-250w (x2)| US-8-150w (x3) | US-8-60w (x3) | US-8 (x2)
Emerging Member
Posts: 73
Registered: ‎05-19-2017
Kudos: 2

Re: USG disconnected from UniFi controller

When i run "info" it gives me nothing in return.

 

When i run "show dhcp leases", it does give me the dhcp table.

New Member
Posts: 3
Registered: ‎01-20-2015
Kudos: 5

Re: USG disconnected from UniFi controller

Hi. I have had the same problem on a USG. After an upgrade of the controller, it startet to connect again, but disconnected after some time. After a lot of search on forums, none of the suggested solutions worked, but when I started to look into number of clients and DHCP scope, I wondered if the scope was full and could cause this problem. I change the mask fram /24 to /22, and when the USG picked up the config after two days, it has been stable since.

Hope this can be a solution for others,

 

Eyvind

 

New Member
Posts: 1
Registered: Thursday

Re: USG disconnected from UniFi controller


@Quaid0808 wrote:

Hi. I have had the same problem on a USG. After an upgrade of the controller, it startet to connect again, but disconnected after some time. After a lot of search on forums, none of the suggested solutions worked, but when I started to look into number of clients and DHCP scope, I wondered if the scope was full and could cause this problem. I change the mask fram /24 to /22, and when the USG picked up the config after two days, it has been stable since.

Hope this can be a solution for others,

 

Eyvind

 


Late reply, but I had this exact same issue today and changing the DHCP scope size worked for me as well. Oddly enough, although it was a small scope, it still had plenty of unused addresses available. Perhaps just updating this value in general fixes this bug? ::shrug::

Reply