Scheduled maintenance: Community will be offline Monday June 17th, 1:00 AM - 6:00 AM (PT)
Reply
New Member
Posts: 9
Registered: ‎01-25-2016
Kudos: 1
Solutions: 1
Accepted Solution

Cannot adopt AP-AC-LR, initial contact failed, url=http://unifi:8080/inform, rc=6

[ Edited ]

I have a working setup with 6 AP-AC-PRO's and one, new, AP-AC-LR. The latter cannot seem to be adopted.

It can ping the controller, the controller can ping it. SSH working etc. Numerous attempts using set-inform (with and without restore-defaults)  yielded nothing but the same error. tcpdump on the controller shows the request arriving. The server.log on the controller shows no errors. When I wget from the AP it throws the 'content to short' error in the server.log, so I am positive the AP can reach the controller.

 

Below the full log from the AP. Controller is 5.4.10 ( 5.4.9 failed same way) running on Debian Jessie latest, OpenJDK 1.8.111 in an OpenVZ virtual. Firmware on all AP's including the AC-LR is 3.7.37.6065

 

I am clueless on how to proceed. What does a return code of 6 imply? Can I increase the debug level on the controller side to see what is going wrong there?

 

Info

Model:       UAP-AC-LR
Version:     3.7.37.6065
MAC Address: 80:2a:a8:xx:xx:xx
IP Address:  192.168.XX.YYY
Hostname:    UBNT
Uptime:      135 seconds

Status:      Not Adopted (http://unifi:8080/inform)

 AP Log

 

Jan  1 00:00:12 UBNT syslog.info syslogd started: BusyBox v1.19.4
Jan  1 00:00:12 UBNT daemon.info init: starting pid 1136, tty '/dev/null': '/bin/hostapd /etc/aaa1.cfg'
Jan  1 00:00:12 UBNT daemon.info init: starting pid 1138, tty '/dev/null': '/sbin/ntpclient -i 86400 -n -s -c 0 -l -h 0.ubnt.pool.ntp.org'
Jan  1 00:00:12 UBNT daemon.info init: starting pid 1139, tty '/dev/null': '/bin/dropbear -F -d /var/run/dropbear_dss_host_key -r /var/run/dropbear_rsa_host_key -p
Jan  1 00:00:12 UBNT authpriv.warn dropbear[1139]: Failed loading /var/run/dropbear_dss_host_key
Jan  1 00:00:12 UBNT daemon.info init: starting pid 1140, tty '/dev/null': '/bin/mcad'
Jan  1 00:00:12 UBNT daemon.info init: starting pid 1141, tty '/dev/null': '/bin/mca-monitor'
Jan  1 00:00:12 UBNT daemon.info init: starting pid 1142, tty '/dev/null': '/bin/stamgr -i 1 '
Jan  1 00:00:12 UBNT daemon.info init: starting pid 1143, tty '/dev/null': '/bin/utermd -m 1'
Jan  1 00:00:12 UBNT kern.notice kernel: [    0.550000] Creating 7 MTD partitions on "ath-nor0":
Jan  1 00:00:12 UBNT kern.notice kernel: [    0.550000] 0x000000000000-0x000000060000 : "u-boot"
Jan  1 00:00:12 UBNT kern.notice kernel: [    0.550000] 0x000000060000-0x000000070000 : "u-boot-env"
Jan  1 00:00:12 UBNT kern.notice kernel: [    0.550000] 0x000000070000-0x000000800000 : "kernel0"
Jan  1 00:00:12 UBNT kern.notice kernel: [    0.550000] 0x000000800000-0x000000f90000 : "kernel1"
Jan  1 00:00:12 UBNT kern.notice kernel: [    0.560000] 0x000000f90000-0x000000fb0000 : "bs"
Jan  1 00:00:12 UBNT kern.notice kernel: [    0.560000] 0x000000fb0000-0x000000ff0000 : "cfg"
Jan  1 00:00:12 UBNT kern.notice kernel: [    0.560000] 0x000000ff0000-0x000001000000 : "EEPROM"
Jan  1 00:00:12 UBNT kern.warn kernel: [    0.560000]  ath_flash_init: init ath_flash driver, res=0
Jan  1 00:00:12 UBNT kern.info kernel: [    0.570000] ag71xx_mdio: probed
Jan  1 00:00:12 UBNT kern.info kernel: [    0.570000] eth0: Atheros AG71xx at 0xb9000000, irq 4
Jan  1 00:00:12 UBNT kern.info kernel: [    1.120000] ag71xx ag71xx.0: eth0: connected to PHY at ag71xx-mdio.0:04 [uid=004dd074, driver=Atheros 8033 PHY]
Jan  1 00:00:12 UBNT kern.info kernel: [    1.120000] ALSA device list:
Jan  1 00:00:12 UBNT kern.info kernel: [    1.120000]   No soundcards found.
Jan  1 00:00:12 UBNT kern.info kernel: [    1.120000] u32 classifier
Jan  1 00:00:12 UBNT kern.info kernel: [    1.120000]     Performance counters on
Jan  1 00:00:12 UBNT kern.info kernel: [    1.120000]     input device check on
Jan  1 00:00:12 UBNT kern.info kernel: [    1.120000]     Actions configured
Jan  1 00:00:12 UBNT kern.info kernel: [    1.120000] TCP cubic registered
Jan  1 00:00:12 UBNT kern.info kernel: [    1.120000] NET: Registered protocol family 17
Jan  1 00:00:12 UBNT kern.notice kernel: [    1.120000] Bridge firewalling registered
Jan  1 00:00:12 UBNT kern.info kernel: [    1.120000] 8021q: 802.1Q VLAN Support v1.8
Jan  1 00:00:12 UBNT kern.info kernel: [    1.120000] ### of_selftest(): No testcase data in device tree; not running tests
Jan  1 00:00:12 UBNT kern.info kernel: [    1.250000] Freeing unused kernel memory: 23216k freed
Jan  1 00:00:12 UBNT kern.warn kernel: [    1.290000] ubnthal: module license 'Proprietary' taints kernel.
Jan  1 00:00:12 UBNT kern.warn kernel: [    1.290000] Disabling lock debugging due to kernel taint
Jan  1 00:00:12 UBNT kern.info kernel: [    1.290000] Init caladdr[0]=0xbfff1000 caladdr[1]=0xbfff5000
Jan  1 00:00:12 UBNT kern.info kernel: [    1.290000]
Jan  1 00:00:12 UBNT kern.debug kernel: [    1.290000] flash (0xbfff1000) magic (0x0202) is wrong
Jan  1 00:00:12 UBNT kern.debug kernel: [    1.290000] flash (0xbfff1000) magic (0x0202) is wrong
Jan  1 00:00:12 UBNT kern.debug kernel: [    1.290000] flash (0xbfff1000) magic (0x0202) is wrong
Jan  1 00:00:12 UBNT kern.info kernel: [    1.290000] Init caladdr[0]=0xbfff1000 caladdr[1]=0xbfff5000
Jan  1 00:00:12 UBNT kern.info kernel: [    1.290000]
Jan  1 00:00:12 UBNT kern.debug kernel: [    1.290000] flash (0xbfff5000) magic (0x4408) is wrong
Jan  1 00:00:12 UBNT kern.debug kernel: [    1.290000] flash (0xbfff5000) magic (0x4408) is wrong
Jan  1 00:00:12 UBNT kern.debug kernel: [    1.290000] flash (0xbfff5000) magic (0x4408) is wrong
Jan  1 00:00:12 UBNT kern.info kernel: [    1.300000] ubnthal: Ubiquiti UAP-AC-LR
Jan  1 00:00:12 UBNT kern.info kernel: [    1.300000] ubnthal: Dragonfly: maxPower 24 powerOffset 0 txmask 7 antenna 4 [0] gain 0 caps 0x4024
Jan  1 00:00:12 UBNT kern.info kernel: [    1.300000] ubnthal: Peregrine: maxPower 22 powerOffset 0 txmask 3 antenna 4 [0] gain 0 caps 0x3004014
Jan  1 00:00:12 UBNT kern.debug kernel: [    1.300000] creating procfs for ubnthal
Jan  1 00:00:12 UBNT kern.debug kernel: [    1.300000] creating proc entry for system.info
Jan  1 00:00:12 UBNT kern.debug kernel: [    1.300000] creating proc entry for board
Jan  1 00:00:12 UBNT kern.debug kernel: [    1.300000] creating proc entry for wifi0
Jan  1 00:00:12 UBNT kern.debug kernel: [    1.300000] creating proc entry for wifi1
Jan  1 00:00:12 UBNT kern.debug kernel: [    1.300000] creating procfs for status
Jan  1 00:00:12 UBNT kern.debug kernel: [    1.300000] creating proc entry for IsDefault
Jan  1 00:00:12 UBNT kern.debug kernel: [    1.300000] creating proc entry for IsLocated
Jan  1 00:00:12 UBNT kern.debug kernel: [    1.300000] creating proc entry for IsIsolated
Jan  1 00:00:12 UBNT kern.info kernel: [    1.300000] gpiodev: reset_timeout=3
Jan  1 00:00:12 UBNT kern.debug kernel: [    1.300000] creating /proc/gpio/
Jan  1 00:00:12 UBNT kern.debug kernel: [    1.300000]          /proc/gpio/led_pattern
Jan  1 00:00:12 UBNT kern.debug kernel: [    1.300000]          /proc/gpio/led_tempo
Jan  1 00:00:12 UBNT kern.debug kernel: [    1.300000]          /proc/gpio/poe_passthrough
Jan  1 00:00:12 UBNT kern.debug kernel: [    1.300000]          /proc/gpio/resetbtn
Jan  1 00:00:12 UBNT kern.debug kernel: [    1.300000]          /proc/gpio/resetbtn_age
Jan  1 00:00:12 UBNT kern.info kernel: [    3.240000] NET: Registered protocol family 10
Jan  1 00:00:12 UBNT kern.info kernel: [    3.440000] usbcore: registered new interface driver usbfs
Jan  1 00:00:12 UBNT kern.info kernel: [    3.440000] usbcore: registered new interface driver hub
Jan  1 00:00:12 UBNT kern.info kernel: [    3.440000] usbcore: registered new device driver usb
Jan  1 00:00:12 UBNT kern.info kernel: [    3.680000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jan  1 00:00:12 UBNT kern.info kernel: [    3.680000] ehci-platform ehci-platform.0: Generic Platform EHCI Controller
Jan  1 00:00:12 UBNT kern.info kernel: [    3.680000] ehci-platform ehci-platform.0: new USB bus registered, assigned bus number 1
Jan  1 00:00:12 UBNT kern.info kernel: [    3.710000] ehci-platform ehci-platform.0: irq 48, io mem 0x1b000000
Jan  1 00:00:12 UBNT kern.info kernel: [    3.730000] ehci-platform ehci-platform.0: USB 2.0 started, EHCI 1.00
Jan  1 00:00:12 UBNT kern.info kernel: [    3.730000] hub 1-0:1.0: USB hub found
Jan  1 00:00:12 UBNT kern.info kernel: [    3.730000] hub 1-0:1.0: 1 port detected
Jan  1 00:00:12 UBNT kern.info kernel: [    3.730000] ehci-platform ehci-platform.1: Generic Platform EHCI Controller
Jan  1 00:00:12 UBNT kern.info kernel: [    3.730000] ehci-platform ehci-platform.1: new USB bus registered, assigned bus number 2
Jan  1 00:00:12 UBNT kern.info kernel: [    3.760000] ehci-platform ehci-platform.1: irq 49, io mem 0x1b400000
Jan  1 00:00:12 UBNT kern.info kernel: [    3.780000] ehci-platform ehci-platform.1: USB 2.0 started, EHCI 1.00
Jan  1 00:00:12 UBNT kern.info kernel: [    3.780000] hub 2-0:1.0: USB hub found
Jan  1 00:00:12 UBNT kern.info kernel: [    3.780000] hub 2-0:1.0: 1 port detected
Jan  1 00:00:12 UBNT kern.info kernel: [    3.890000] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jan  1 00:00:12 UBNT kern.debug kernel: [    3.950000] Registered led device: ubnt_gen2:green:usb0
Jan  1 00:00:12 UBNT kern.debug kernel: [    3.950000] Registered led device: ubnt_gen2:green:usb1
Jan  1 00:00:12 UBNT kern.info kernel: [    4.010000] usbcore: registered new interface driver snd-usb-audio
Jan  1 00:00:12 UBNT kern.warn kernel: [    5.820000] ****Address of trace_timer :85e7e360
Jan  1 00:00:12 UBNT kern.info kernel: [    6.140000] ath_hal: 0.9.17.1 (AR5416, AR9380, DEBUG, REGOPS_FUNC, WRITE_EEPROM, TX_DATA_SWAP, RX_DATA_SWAP, 11D)
Jan  1 00:00:12 UBNT kern.info kernel: [    6.430000] ath_rate_atheros: Copyright (c) 2001-2005 Atheros Communications, Inc, All Rights Reserved
Jan  1 00:00:12 UBNT kern.info kernel: [    6.460000] ath_dfs: Version 2.0.0
Jan  1 00:00:12 UBNT kern.info kernel: [    6.460000] Copyright (c) 2005-2006 Atheros Communications, Inc. All Rights Reserved
Jan  1 00:00:12 UBNT kern.info kernel: [    6.490000] ath_spectral: Version 2.0.0
Jan  1 00:00:12 UBNT kern.info kernel: [    6.490000] Copyright (c) 2005-2009 Atheros Communications, Inc. All Rights Reserved
Jan  1 00:00:12 UBNT kern.info kernel: [    6.490000] SPECTRAL module built on Jan 18 2017 09:11:42
Jan  1 00:00:12 UBNT kern.info kernel: [    6.790000] ath_dev: Copyright (c) 2001-2007 Atheros Communications, Inc, All Rights Reserved
Jan  1 00:00:12 UBNT kern.warn kernel: [    7.160000] __ath_attach: Set global_scn[0]
Jan  1 00:00:12 UBNT kern.warn kernel: [    7.160000] *** All the minfree values should be <= ATH_TXBUF-32, otherwise default value will be used instead ***
Jan  1 00:00:12 UBNT kern.warn kernel: [    9.290000] ol_ath_phyerr_attach: called
Jan  1 00:00:12 UBNT kern.warn kernel: [    9.290000] ieee80211_bsteering_attach: Band steering initialized
Jan  1 00:00:12 UBNT kern.warn kernel: [    9.290000] ol_if_spectral_setup
Jan  1 00:00:12 UBNT kern.warn kernel: [    9.290000] SPECTRAL : get_capability not registered
Jan  1 00:00:13 UBNT kern.warn kernel: [    9.290000] HAL_CAP_PHYDIAG : Capable
Jan  1 00:00:13 UBNT kern.warn kernel: [    9.290000] SPECTRAL : Need to fix the capablity check for RADAR (spectral_attach : 231)
Jan  1 00:00:13 UBNT kern.warn kernel: [    9.290000] SPECTRAL : get_capability not registered
Jan  1 00:00:13 UBNT kern.warn kernel: [    9.290000] HAL_CAP_RADAR   : Capable
Jan  1 00:00:13 UBNT kern.warn kernel: [    9.290000] SPECTRAL : Need to fix the capablity check for SPECTRAL
Jan  1 00:00:13 UBNT kern.warn kernel: [    9.290000]  (spectral_attach : 236)
Jan  1 00:00:13 UBNT kern.warn kernel: [    9.300000] SPECTRAL : get_capability not registered
Jan  1 00:00:13 UBNT kern.warn kernel: [    9.300000] HAL_CAP_SPECTRAL_SCAN : Capable
Jan  1 00:00:13 UBNT kern.warn kernel: [    9.300000] SPECTRAL : get_tsf64 not registered
Jan  1 00:00:13 UBNT kern.warn kernel: [    9.300000] spectral_init_netlink 65 NULL SKB
Jan  1 00:00:13 UBNT kern.warn kernel: [    9.300000] ieee80211_mac_nfbypass_globalinit: global ic ref 0x80cc0380
Jan  1 00:00:13 UBNT user.info syslog: uplink-monitor.uplink_monitor_main(): sysid=0xe527, serial: 80:2a:a8:xx:xx:xx
Jan  1 00:00:13 UBNT user.info syslog: uplink-monitor.uplink_monitor_main(): vport ath1: 80:2a:a8:xx:xx:xx
Jan  1 00:00:13 UBNT kern.info kernel: [   13.240000] br0: port 3(ath1) entered forwarding state
Jan  1 00:00:13 UBNT kern.info kernel: [   13.240000] br0: port 3(ath1) entered forwarding state
Jan  1 00:00:13 UBNT kern.info kernel: [   13.240000] ADDRCONF(NETDEV_CHANGE): br0: link becomes ready
Jan  1 00:00:13 UBNT user.err syslog: ace_reporter.reporter_fail(): Waiting for IP (http://unifi:8080/inform)
Jan  1 00:00:13 UBNT user.err syslog: ace_reporter.reporter_fail(): initial contact failed #1, url=http://unifi:8080/inform, rc=2
Jan  1 00:00:13 UBNT kern.warn kernel: [   13.440000] wlan_get_active_vport_chan: ch=0
Jan  1 00:00:13 UBNT kern.info kernel: [   13.440000] br0: port 2(ath0) entered forwarding state
Jan  1 00:00:13 UBNT kern.info kernel: [   13.440000] br0: port 2(ath0) entered forwarding state
Jan  1 00:00:14 UBNT kern.info kernel: [   14.240000] br0: port 3(ath1) entered forwarding state
Jan  1 00:00:14 UBNT kern.info kernel: [   14.440000] br0: port 2(ath0) entered forwarding state
Jan  1 00:00:15 UBNT kern.warn kernel: [   15.810000] ath_rate_find_ieee_rate_w_kbps: Rate not found: 0 kpbs
Jan  1 00:00:17 UBNT kern.info kernel: [   17.200000] eth0: link up (1000Mbps/Full duplex)
Jan  1 00:00:17 UBNT kern.info kernel: [   17.200000] br0: port 1(eth0) entered forwarding state
Jan  1 00:00:17 UBNT kern.info kernel: [   17.200000] br0: port 1(eth0) entered forwarding state
Jan  1 00:00:17 UBNT kern.info kernel: [   17.200000] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Jan  1 00:00:18 UBNT user.notice syswrapper: current time is not set yet
Jan  1 00:00:18 UBNT kern.info kernel: [   18.150000] br0: port 3(ath1) entered disabled state
Jan  1 00:00:18 UBNT kern.info kernel: [   18.200000] br0: port 1(eth0) entered forwarding state
Jan  1 00:00:19 UBNT user.notice syswrapper: ipready.br0 = 192.168.XX.YYY
Jan  1 00:00:19 UBNT daemon.info init: process '/sbin/ntpclient -i 86400 -n -s -c 0 -l -h 0.ubnt.pool.ntp.org' (pid 1138) exited. Scheduling for restart.
Jan  1 00:00:19 UBNT daemon.info init: starting pid 1217, tty '/dev/null': '/sbin/ntpclient -i 86400 -n -s -c 0 -l -h 0.ubnt.pool.ntp.org'
Jan 30 13:06:53 UBNT user.err syslog: ace_reporter.reporter_fail(): Not Adopted (http://unifi:8080/inform)
Jan 30 13:06:53 UBNT user.err syslog: ace_reporter.reporter_fail(): initial contact failed #2, url=http://unifi:8080/inform, rc=6
Jan 30 13:06:57 UBNT kern.debug kernel: [   23.530000] ath0: no IPv6 routers present
Jan 30 13:06:58 UBNT kern.debug kernel: [   23.980000] br0: no IPv6 routers present
Jan 30 13:07:01 UBNT kern.debug kernel: [   27.860000] eth0: no IPv6 routers present
Jan 30 13:08:23 UBNT user.err syslog: ace_reporter.reporter_fail(): Not Adopted (http://unifi:8080/inform)
Jan 30 13:08:23 UBNT user.err syslog: ace_reporter.reporter_fail(): initial contact failed #3, url=http://unifi:8080/inform, rc=6
Jan 30 13:08:23 UBNT user.info syslog: ace_reporter.reporter_next_inform_url(): next inform url[0]=http://unifi:8080/inform
Jan 30 13:08:23 UBNT user.info syslog: ace_reporter.reporter_next_inform_url(): authkey=ba86f2bbe107c7c57eb5f2690775c712

 


Accepted Solutions
New Member
Posts: 9
Registered: ‎01-25-2016
Kudos: 1
Solutions: 1

Re: Cannot adopt AP-AC-LR, initial contact failed, url=http://unifi:8080/inform, rc=6

Reinstalled controller.AP's  *are* being discovered now. No clue wrt cause, but hey, it works.

View solution in original post


All Replies
Senior Member
Posts: 2,811
Registered: ‎04-21-2015
Kudos: 420
Solutions: 112

Re: Cannot adopt AP-AC-LR, initial contact failed, url=http://unifi:8080/inform, rc=6

[ Edited ]

can your AP resolve http://unifi:8080/inform hostname?

Thanks,
Myky
CWSP
--------------------------------------------------------------------------------------------------------------------------------------------------
Don`t blame the device as it`s always doing what you have asked it to do, this is not always the same as what you want.
New Member
Posts: 9
Registered: ‎01-25-2016
Kudos: 1
Solutions: 1

Re: Cannot adopt AP-AC-LR, initial contact failed, url=http://unifi:8080/inform, rc=6


@mlskrypka wrote:
can your AP resolve unifi hostname?
Yep.
BZ.v3.7.37# ping unifi
PING unifi (192.168.XX.YYY): 56 data bytes
64 bytes from 192.168.XX.YYY: seq=0 ttl=64 time=0.185 ms
64 bytes from 192.168.XX.YYY: seq=1 ttl=64 time=0.235 ms
64 bytes from 192.168.XX.YYY: seq=2 ttl=64 time=0.245 ms
^C
--- unifi ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.185/0.221/0.245 ms
BZ.v3.7.37#
Highlighted
Senior Member
Posts: 2,811
Registered: ‎04-21-2015
Kudos: 420
Solutions: 112

Re: Cannot adopt AP-AC-LR, initial contact failed, url=http://unifi:8080/inform, rc=6

Can you post output "info" command  of the already adopted AP. 

Thanks,
Myky
CWSP
--------------------------------------------------------------------------------------------------------------------------------------------------
Don`t blame the device as it`s always doing what you have asked it to do, this is not always the same as what you want.
New Member
Posts: 9
Registered: ‎01-25-2016
Kudos: 1
Solutions: 1

Re: Cannot adopt AP-AC-LR, initial contact failed, url=http://unifi:8080/inform, rc=6

BZ.v3.7.37# info

Model:       UAP-AC-Pro-Gen2
Version:     3.7.37.6065
MAC Address: 44:d9:e7:xx:xx:xx
IP Address:  192.168.XX.YYY
Hostname:    unifi-whatever
Uptime:      354517 seconds

Status:      Connected (http://unifi:8080/inform)
Senior Member
Posts: 2,811
Registered: ‎04-21-2015
Kudos: 420
Solutions: 112

Re: Cannot adopt AP-AC-LR, initial contact failed, url=http://unifi:8080/inform, rc=6

Output of this command pls

# cat /var/etc/persistent/cfg/mgmt
Thanks,
Myky
CWSP
--------------------------------------------------------------------------------------------------------------------------------------------------
Don`t blame the device as it`s always doing what you have asked it to do, this is not always the same as what you want.
Emerging Member
Posts: 45
Registered: ‎08-20-2016
Kudos: 14
Solutions: 2

Re: Cannot adopt AP-AC-LR, initial contact failed, url=http://unifi:8080/inform, rc=6

@peter-v - I can't tell from your post if you tried it yet, but I had similar issues with a AC-LR that I setup over this past weekend.  After multiple set-informs, AP reboots, etc., for some reason it didn't take until I rebooted my controller (running on linux).  After I rebooted my controller, my AC-LR showed up under devices and i adopted it through the GUI.

 

It's difficult to tell if that would work in your situation or if everything I did was a matter of timing.  My controller is a linux VM and my situation was compounded by a host-based firewall I had on my host system.  I had tried multiple times to rebooting the AP, set-infor/set-default via SSH into the controller, pressing the reset button on the AP, hard power-cycling the AP, and multiple reboots of the controller itself.  I was seeing similar messages in the/var/log/messages of the AP and just couldn't get the AP to show up under devices in the controller gui.  If I recall correctly, my last time was to turn off any host-based firewalls, verify no blocking on my USG firewall rules, set-inform via SSH, and then finally just rebooting the controller as a last resort.  Then, for some reason after the final reboot of the controller, it showed up in the GUI.

New Member
Posts: 9
Registered: ‎01-25-2016
Kudos: 1
Solutions: 1

Re: Cannot adopt AP-AC-LR, initial contact failed, url=http://unifi:8080/inform, rc=6


@mlskrypka wrote:
Output of this command pls

# cat /var/etc/persistent/cfg/mgmt

On the non-working AP this file doesn't exist.

On a working AP the content is:

mgmt.is_default=false
mgmt.led_enabled=true
mgmt.cfgversion=a2301305cd693171
mgmt.authkey=51376224AD6C0A8E7DCXXXXXXXXXXXXXX
mgmt.selfrun_guest_mode=pass
mgmt.capability=notif
mgmt.servers.1.url=http://unifi:8080/inform
stun_url=stun://unifi/
mgmt_url=https://unifi:8443/manage/site/default
New Member
Posts: 9
Registered: ‎01-25-2016
Kudos: 1
Solutions: 1

Re: Cannot adopt AP-AC-LR, initial contact failed, url=http://unifi:8080/inform, rc=6

If have no firewalls between the AP's and the controller, neither hardware nor software.
The use of OpenVZ might kill some L2 broadcasts, but that should not influence a L3 discover.
Did restart the controller, the whole host, the AP numerous times. Didn't help at all.
Senior Member
Posts: 2,811
Registered: ‎04-21-2015
Kudos: 420
Solutions: 112

Re: Cannot adopt AP-AC-LR, initial contact failed, url=http://unifi:8080/inform, rc=6

[ Edited ]

Interesting why it doesn't exist as it should contain similar info as above from working one. This is a default file. Do you think you can reinstall firmware using ssh? Not sure if that is possible 

Thanks,
Myky
CWSP
--------------------------------------------------------------------------------------------------------------------------------------------------
Don`t blame the device as it`s always doing what you have asked it to do, this is not always the same as what you want.
New Member
Posts: 9
Registered: ‎01-25-2016
Kudos: 1
Solutions: 1

Re: Cannot adopt AP-AC-LR, initial contact failed, url=http://unifi:8080/inform, rc=6

Found something else in TCPDUMP:

the controller answers 404 Not found in reply to the packet from the AP:

        HTTP/1.1 404 Not Found
        Server: Apache-Coyote/1.1
        Content-Length: 0
        Date: Mon, 30 Jan 2017 15:07:54 GMT
        Connection: close

Weird...

New Member
Posts: 9
Registered: ‎01-25-2016
Kudos: 1
Solutions: 1

Re: Cannot adopt AP-AC-LR, initial contact failed, url=http://unifi:8080/inform, rc=6

Not a problem. I've reinstalled the firmware a couple of times using SSH. Did not fix a thing.
Senior Member
Posts: 2,811
Registered: ‎04-21-2015
Kudos: 420
Solutions: 112

Re: Cannot adopt AP-AC-LR, initial contact failed, url=http://unifi:8080/inform, rc=6

[ Edited ]

So this is a new AP and never worked, right? Just for test can you spin another controller and try to adopt to it? Same time reset AP to its default.

Thanks,
Myky
CWSP
--------------------------------------------------------------------------------------------------------------------------------------------------
Don`t blame the device as it`s always doing what you have asked it to do, this is not always the same as what you want.
Senior Member
Posts: 2,811
Registered: ‎04-21-2015
Kudos: 420
Solutions: 112

Re: Cannot adopt AP-AC-LR, initial contact failed, url=http://unifi:8080/inform, rc=6

For better analysis write tcpdump output to the pcap file:

# tcpdump -r 0001.pcap
Thanks,
Myky
CWSP
--------------------------------------------------------------------------------------------------------------------------------------------------
Don`t blame the device as it`s always doing what you have asked it to do, this is not always the same as what you want.
New Member
Posts: 9
Registered: ‎01-25-2016
Kudos: 1
Solutions: 1

Re: Cannot adopt AP-AC-LR, initial contact failed, url=http://unifi:8080/inform, rc=6

That worked - in a way. Obviously I did not change my DNS for unifi, but it did connect to the 2nd controller after pointing it there using set-inform.So it seems that my controller installation might be the cause here.

I'll re-install the controller and report back.

New Member
Posts: 9
Registered: ‎01-25-2016
Kudos: 1
Solutions: 1

Re: Cannot adopt AP-AC-LR, initial contact failed, url=http://unifi:8080/inform, rc=6

Reinstalled controller.AP's  *are* being discovered now. No clue wrt cause, but hey, it works.

Senior Member
Posts: 2,811
Registered: ‎04-21-2015
Kudos: 420
Solutions: 112

Re: Cannot adopt AP-AC-LR, initial contact failed, url=http://unifi:8080/inform, rc=6

[ Edited ]

Heh nice one! Now i believe you can locate this file:

 

# cat /var/etc/persistent/cfg/mgmt

Thanks,
Myky
CWSP
--------------------------------------------------------------------------------------------------------------------------------------------------
Don`t blame the device as it`s always doing what you have asked it to do, this is not always the same as what you want.
New Member
Posts: 1
Registered: ‎12-01-2016

Re: Cannot adopt AP-AC-LR, initial contact failed, url=http://unifi:8080/inform, rc=6

I am having the same issue.   Reading the thread it seem like if the controller is re-installed the adoption start working.

 

I get this logged  in /var/log/messages :

 UBNT user.err syslog: ace_reporter.reporter_fail(): initial contact failed

 

This is an existing environment and  I believe it has to do with the controller/cloud key having different username and password .  When you re-install the Controller  it defaults to ubnt/ubnt and so it works.  My 2 cents :-)  Will confirm once   I am able to reset the controller and adopt.

New Member
Posts: 14
Registered: ‎04-29-2018
Kudos: 3
Solutions: 1

Re: Cannot adopt AP-AC-LR, initial contact failed, url=http://unifi:8080/inform, rc=6

For people who find this topic: This indeed seems to be related to credentials being configured in the site config.
If you create a new site (and don't change anything to it), then you'll be able to adopt.

New Member
Posts: 13
Registered: ‎08-04-2016
Kudos: 1

Re: Cannot adopt AP-AC-LR, initial contact failed, url=http://unifi:8080/inform, rc=6

I had the same issue after we've upgraded our Cloud Key. We have about 25 APs, all UAP-AC-Pro's, except for 1 device that is a UAP-AP-SHD. The SHD device didn't come online after the Cloud Key upgrade.

 

I've tried all sorts of things, eventually 'forgot' the device, reset the device to factory defaults and did the adoption again. That worked.

 

No clue what was wrong.

 

Reply