Reply
Emerging Member
mcornstubble
Posts: 59
Registered: ‎10-20-2011
Posts: 59
Kudos: 5
Registered: 10-20-2011

Unifi AP Adoption Issues

All -

I have been having some issues adpoting UniFi Access Points to my Unifi Controller.

My Picostation M2 with Unifi Firmware adopted fine, and is working great on my controller.

However, when I add the Unifi AP's, they get stuck in the "adopting" process.

I have approved them, and have made sure to "adopt" them, however, they stay orange, and only say adopting.

Can anyone offer some insight as to why this is happening? It would be greatly appreciated
Veteran Member
urmom
Posts: 4,607
Registered: ‎02-19-2010
Posts: 4607
Kudos: 1862
Solutions: 29
Registered: 02-19-2010

Re: Unifi AP Adoption Issues

All -

I have been having some issues adpoting UniFi Access Points to my Unifi Controller.

My Picostation M2 with Unifi Firmware adopted fine, and is working great on my controller.

However, when I add the Unifi AP's, they get stuck in the "adopting" process.

I have approved them, and have made sure to "adopt" them, however, they stay orange, and only say adopting.

Can anyone offer some insight as to why this is happening? It would be greatly appreciated


what version of the software are you using?
Not getting the answers you wanted? Check out this link --> http://www.catb.org/~esr/faqs/smart-questions.html -- I need a thumbs down button!
Emerging Member
mcornstubble
Posts: 59
Registered: ‎10-20-2011
Posts: 59
Kudos: 5
Registered: 10-20-2011

Re: Unifi AP Adoption Issues

Unifi or on the AP itself?

The Unifi version is what I pulled from Aptitude which is 1.3.2
Veteran Member
urmom
Posts: 4,607
Registered: ‎02-19-2010
Posts: 4607
Kudos: 1862
Solutions: 29
Registered: 02-19-2010

Re: Unifi AP Adoption Issues

try using the latest version of the controller software. it should update the unifis to the latest version, also.
Not getting the answers you wanted? Check out this link --> http://www.catb.org/~esr/faqs/smart-questions.html -- I need a thumbs down button!
New Member
novasystems
Posts: 12
Registered: ‎03-31-2011
Posts: 12
Registered: 03-31-2011

Stuck in Adopting

Win7 64 bit, read all the previous hot tips, still can't get AP's to adopt.
L2 switch network, no problems
AP's take a DHCP address no problem from router
Tried re-settting AP's to default, no go
Tried re-installing software, no go
Tried adopting by connecting to my laptop, no go

This is really an enormous waste of time and money. Installed an 8 AP system in a far more complicated job last month....40 devices constant on and off the network, streaming work, etc, Runs like a good watch. No problems adopting or anything!

This one is supposed to be 8 APs, buy after connecting 3 and none of them adopting, I'm stumped. HELP please....:icon_cry:
Regular Member
test1
Posts: 669
Registered: ‎10-07-2011
Posts: 669
Kudos: 143
Registered: 10-07-2011

Re: Unifi AP Adoption Issues

Is the Windows firewall disabled?
Is the controller version greater than or equal to the AP firmware version?
Is the controller running?
This is really an enormous waste of time and money.

While I understand your frustration with it not working, we know that it does indeed work. You claim to have proved as much with a previous installation.
Emerging Member
mcornstubble
Posts: 59
Registered: ‎10-20-2011
Posts: 59
Kudos: 5
Registered: 10-20-2011

Re: Unifi AP Adoption Issues

Ive tried the same process as NovaSystems, and I'm also stuck in the same boat but on a unix based system.
Ill try upgrading all my packages in apt to make sure that I have the latest software
Emerging Member
mcornstubble
Posts: 59
Registered: ‎10-20-2011
Posts: 59
Kudos: 5
Registered: 10-20-2011

Re: Unifi AP Adoption Issues

Upgraded via apt, as the Unifi deb has been added to my sources list. However, it claimed that all of my packages were current

I think the strangest thing is that it works great with my Pico M2 that has been upgraded to Unifi firmware, however, a Unifi AP does not want to adopt successfully
New Member
lamy
Posts: 24
Registered: ‎04-26-2011
Posts: 24
Kudos: 13
Registered: 04-26-2011

Re: Unifi AP Adoption Issues

You've probably already tried this, but I'm going to say it anyway.


  • Login to UnFi and click on each AP that is stuck in the adopting stage.
  • Click "Configuration" and forget the AP.
  • Figure out what the IP's of the problematic AP's are, and ssh into the each AP (username: ubnt password: ubnt).
  • Then, run the following command:

    syswrapper.sh restore-default




    Hope it helps.
  • Ubiquiti Employee
    UBNT-Jerry
    Posts: 978
    Registered: ‎05-04-2009
    Posts: 978
    Kudos: 462
    Solutions: 6
    Contributions: 1
    Registered: 05-04-2009

    Re: Unifi AP Adoption Issues

    To be a little more analytical, try the following:

  • from the UI, make sure AP does obtain the IP from DHCP, note the IP
  • from Controller PC, SSH into the AP (using the IP, default username/password is ubnt/ubnt)
  • tail -f /var/log/messages

    AP sent out beacon every 5 seconds when it's in factory default. When controller sees the beacon, it will SSH into the AP and ask the AP to inform back. You should be able to see it from the logs. And if anything goes wrong, you'll see it, too.
  • Emerging Member
    mcornstubble
    Posts: 59
    Registered: ‎10-20-2011
    Posts: 59
    Kudos: 5
    Registered: 10-20-2011

    Re: Unifi AP Adoption Issues

    heres a shot of what Im seeing from the logs of the AP. I think its looking for the wrong URL for the Unifi controller. It keeps looking for unifi:8080/

    Jan 1 00:03:48 UBNT authpriv.info dropbear: Child connection from 192.168.88.254:38745
    Jan 1 00:03:49 UBNT user.debug syslog: infctld.send_packet(): Send MULTICAST: OK
    Jan 1 00:03:49 UBNT authpriv.notice dropbear: password auth succeeded for 'ubnt' from 192.168.88.254:38745
    Jan 1 00:03:49 UBNT authpriv.info dropbear: exit after auth (ubnt): Disconnect received
    Jan 1 00:03:49 UBNT user.debug syslog: mca-ctrl.operation_run(): Sending connect request to '/tmp/.mcad.0'
    Jan 1 00:03:49 UBNT user.debug syslog: mcad-ctrl.cl_read(): received packet of 109 bytes from '/tmp/.mca-iUhZfZ' (fromlen: 19)
    Jan 1 00:03:49 UBNT user.debug syslog: mcad-ctrl.cl_read(): Processing connect request...
    Jan 1 00:03:49 UBNT user.debug syslog: ace_reporter.reporter_prepare_inform_payload(): dumping athstat for wifi0
    Jan 1 00:03:49 UBNT user.err syslog: libubnt.get_athstat(): Unable to get athstat for wifi0
    Jan 1 00:03:49 UBNT user.debug syslog: ace_reporter.reporter_inform(): connect(127.0.0.1:8080/inform) in progress...
    Jan 1 00:03:49 UBNT user.debug syslog: mcad-ctrl.cl_read(): sending back the response (type: 254)..
    Jan 1 00:03:49 UBNT user.err syslog: ace_reporter.reporter_connected(): connect(127.0.0.1:8080/inform) failed with errors: 0 146 - Connection refused
    Jan 1 00:03:49 UBNT user.err syslog: ace_reporter.reporter_fail(): server unreachable
    Jan 1 00:03:49 UBNT user.err syslog: ace_reporter.reporter_fail(): initial contact failed #52, url=http://127.0.0.1:8080/inform, rc=2
    Jan 1 00:03:49 UBNT user.info syslog: ace_reporter.reporter_next_inform_url(): next inform url=http://unifi:8080/inform
    Jan 1 00:03:49 UBNT user.debug syslog: mca-ctrl.operation_run(): Waiting for response...
    Jan 1 00:03:54 UBNT user.debug syslog: ace_reporter.reporter_prepare_inform_payload(): dumping athstat for wifi0
    Jan 1 00:03:54 UBNT user.err syslog: libubnt.get_athstat(): Unable to get athstat for wifi0
    Jan 1 00:03:54 UBNT user.err syslog: ace_reporter.reporter_inform(): Failed resolving URL 'http://unifi:8080/inform'
    Jan 1 00:03:54 UBNT user.err syslog: ace_reporter.reporter_fail(): server unreachable
    Jan 1 00:03:54 UBNT user.err syslog: ace_reporter.reporter_fail(): initial contact failed #53, url=http://unifi:8080/inform, rc=1
    Jan 1 00:03:54 UBNT user.info syslog: ace_reporter.reporter_next_inform_url(): next inform url=http://unifi:8080/inform
    Jan 1 00:03:58 UBNT user.debug syslog: infctld.fill_response_data(): verison=1.2.3.360
    Jan 1 00:03:58 UBNT user.debug syslog: infctld.mcast_beacon(): send_beacon(): src=00:27:22:50:53:eb, seq=21, len=119
    Jan 1 00:03:58 UBNT user.debug syslog: infctld.send_packet(): Iface br0 sin_family is: 2
    Jan 1 00:03:58 UBNT user.debug syslog: infctld.send_packet(): Send BROADCAST: OK
    Jan 1 00:03:58 UBNT authpriv.info dropbear: Child connection from 192.168.88.254:38747
    Jan 1 00:03:59 UBNT user.debug syslog: infctld.send_packet(): Send MULTICAST: OK
    Jan 1 00:03:59 UBNT authpriv.notice dropbear: password auth succeeded for 'ubnt' from 192.168.88.254:38747
    Jan 1 00:03:59 UBNT authpriv.info dropbear: exit after auth (ubnt): Disconnect received
    Jan 1 00:03:59 UBNT user.debug syslog: mca-ctrl.operation_run(): Sending connect request to '/tmp/.mcad.0'
    Jan 1 00:03:59 UBNT user.debug syslog: mcad-ctrl.cl_read(): received packet of 109 bytes from '/tmp/.mca-x3TmhH' (fromlen: 19)
    Jan 1 00:03:59 UBNT user.debug syslog: mcad-ctrl.cl_read(): Processing connect request...
    Jan 1 00:03:59 UBNT user.debug syslog: ace_reporter.reporter_prepare_inform_payload(): dumping athstat for wifi0
    Jan 1 00:03:59 UBNT user.err syslog: libubnt.get_athstat(): Unable to get athstat for wifi0
    Jan 1 00:03:59 UBNT user.debug syslog: ace_reporter.reporter_inform(): connect(127.0.0.1:8080/inform) in progress...
    Jan 1 00:03:59 UBNT user.debug syslog: mcad-ctrl.cl_read(): sending back the response (type: 254)..
    Jan 1 00:03:59 UBNT user.err syslog: ace_reporter.reporter_connected(): connect(127.0.0.1:8080/inform) failed with errors: 0 146 - Connection refused
    Jan 1 00:03:59 UBNT user.err syslog: ace_reporter.reporter_fail(): server unreachable
    Jan 1 00:03:59 UBNT user.err syslog: ace_reporter.reporter_fail(): initial contact failed #54, url=http://127.0.0.1:8080/inform, rc=2
    Jan 1 00:03:59 UBNT user.info syslog: ace_reporter.reporter_next_inform_url(): next inform url=http://unifi:8080/inform
    Jan 1 00:03:59 UBNT user.debug syslog: mca-ctrl.operation_run(): Waiting for response...
    Jan 1 00:04:04 UBNT user.debug syslog: ace_reporter.reporter_prepare_inform_payload(): dumping athstat for wifi0
    Jan 1 00:04:04 UBNT user.err syslog: libubnt.get_athstat(): Unable to get athstat for wifi0
    Jan 1 00:04:04 UBNT user.err syslog: ace_reporter.reporter_inform(): Failed resolving URL 'http://unifi:8080/inform'
    Jan 1 00:04:04 UBNT user.err syslog: ace_reporter.reporter_fail(): server unreachable
    Jan 1 00:04:04 UBNT user.err syslog: ace_reporter.reporter_fail(): initial contact failed #55, url=http://unifi:8080/inform, rc=1
    Jan 1 00:04:04 UBNT user.info syslog: ace_reporter.reporter_next_inform_url(): next inform url=http://unifi:8080/inform
    Jan 1 00:04:08 UBNT user.debug syslog: infctld.fill_response_data(): verison=1.2.3.360
    Jan 1 00:04:08 UBNT user.debug syslog: infctld.mcast_beacon(): send_beacon(): src=00:27:22:50:53:eb, seq=22, len=119
    Jan 1 00:04:08 UBNT user.debug syslog: infctld.send_packet(): Iface br0 sin_family is: 2
    Jan 1 00:04:08 UBNT user.debug syslog: infctld.send_packet(): Send BROADCAST: OK
    Jan 1 00:04:08 UBNT authpriv.info dropbear: Child connection from 192.168.88.254:38749
    Jan 1 00:04:08 UBNT user.debug syslog: mca-ctrl.operation_run(): Sending status request to '/tmp/.mcad.0'
    Jan 1 00:04:08 UBNT user.debug syslog: mcad-ctrl.cl_read(): received packet of 22 bytes from '/tmp/.mca-1i4Npz' (fromlen: 19)
    Jan 1 00:04:08 UBNT user.debug syslog: mcad-ctrl.cl_read(): Processing status request...
    Jan 1 00:04:08 UBNT user.debug syslog: mcad-ctrl.cl_read(): sending back the response (type: 0)..
    Jan 1 00:04:08 UBNT user.debug syslog: mca-ctrl.operation_run(): Waiting for response...
    Jan 1 00:04:09 UBNT user.debug syslog: infctld.send_packet(): Send MULTICAST: OK
    Jan 1 00:04:09 UBNT authpriv.notice dropbear: password auth succeeded for 'ubnt' from 192.168.88.254:38749
    Jan 1 00:04:09 UBNT authpriv.info dropbear: exit after auth (ubnt): Disconnect received
    Jan 1 00:04:09 UBNT user.debug syslog: ace_reporter.reporter_prepare_inform_payload(): dumping athstat for wifi0
    Jan 1 00:04:09 UBNT user.err syslog: libubnt.get_athstat(): Unable to get athstat for wifi0
    Jan 1 00:04:09 UBNT user.err syslog: ace_reporter.reporter_inform(): Failed resolving URL 'http://unifi:8080/inform'
    Jan 1 00:04:09 UBNT user.err syslog: ace_reporter.reporter_fail(): server unreachable
    Jan 1 00:04:09 UBNT user.err syslog: ace_reporter.reporter_fail(): initial contact failed #56, url=http://unifi:8080/inform, rc=1
    Jan 1 00:04:09 UBNT user.info syslog: ace_reporter.reporter_next_inform_url(): next inform url=http://unifi:8080/inform
    Jan 1 00:04:09 UBNT user.debug syslog: mca-ctrl.operation_run(): Sending connect request to '/tmp/.mcad.0'
    Jan 1 00:04:09 UBNT user.debug syslog: mcad-ctrl.cl_read(): received packet of 109 bytes from '/tmp/.mca-gfu2ul' (fromlen: 19)
    Jan 1 00:04:09 UBNT user.debug syslog: mcad-ctrl.cl_read(): Processing connect request...
    Jan 1 00:04:09 UBNT user.debug syslog: ace_reporter.reporter_prepare_inform_payload(): dumping athstat for wifi0
    Jan 1 00:04:09 UBNT user.err syslog: libubnt.get_athstat(): Unable to get athstat for wifi0
    Jan 1 00:04:09 UBNT user.debug syslog: ace_reporter.reporter_inform(): connect(127.0.0.1:8080/inform) in progress...
    Jan 1 00:04:09 UBNT user.debug syslog: mcad-ctrl.cl_read(): sending back the response (type: 254)..
    Jan 1 00:04:09 UBNT user.err syslog: ace_reporter.reporter_connected(): connect(127.0.0.1:8080/inform) failed with errors: 0 146 - Connection refused
    Jan 1 00:04:09 UBNT user.err syslog: ace_reporter.reporter_fail(): server unreachable
    Jan 1 00:04:09 UBNT user.err syslog: ace_reporter.reporter_fail(): initial contact failed #57, url=http://127.0.0.1:8080/inform, rc=2
    Jan 1 00:04:09 UBNT user.info syslog: ace_reporter.reporter_next_inform_url(): next inform url=http://unifi:8080/inform
    Jan 1 00:04:09 UBNT user.debug syslog: mca-ctrl.operation_run(): Waiting for response...
    Jan 1 00:04:14 UBNT user.debug syslog: ace_reporter.reporter_prepare_inform_payload(): dumping athstat for wifi0
    Jan 1 00:04:14 UBNT user.err syslog: libubnt.get_athstat(): Unable to get athstat for wifi0
    Jan 1 00:04:14 UBNT user.err syslog: ace_reporter.reporter_inform(): Failed resolving URL 'http://unifi:8080/inform'
    Jan 1 00:04:14 UBNT user.err syslog: ace_reporter.reporter_fail(): server unreachable
    Jan 1 00:04:14 UBNT user.err syslog: ace_reporter.reporter_fail(): initial contact failed #58, url=http://unifi:8080/inform, rc=1


    Sorry for the long cut of log, but I wanted to make sure I provided enough information.

    After trying the proposed solutions, as well as the solution posted in the FAQ, Unifi's are still stuck in adopting. My Pico M2 is still working great lol

    Thanks to all for taking a look at my issues!
    Ubiquiti Employee
    UBNT-Jerry
    Posts: 978
    Registered: ‎05-04-2009
    Posts: 978
    Kudos: 462
    Solutions: 6
    Contributions: 1
    Registered: 05-04-2009

    Re: Unifi AP Adoption Issues


    After trying the proposed solutions, as well as the solution posted in the FAQ, Unifi's are still stuck in adopting. My Pico M2 is still working great lol

    For this specific one, restart your UniFi controller.
    controller can SSH into the AP but tells AP the wrong URL (127.0.0.1:8080/inform) to call back. The coming release should address this.
    Emerging Member
    mcornstubble
    Posts: 59
    Registered: ‎10-20-2011
    Posts: 59
    Kudos: 5
    Registered: 10-20-2011

    Re: Unifi AP Adoption Issues

    Restart the controller with or without the AP's connected?
    I've restarted the controller only, which yielded no change.
    ETA to next release? :manhappy:
    Emerging Member
    mcornstubble
    Posts: 59
    Registered: ‎10-20-2011
    Posts: 59
    Kudos: 5
    Registered: 10-20-2011

    Re: Unifi AP Adoption Issues

    Well I did have everything running great. However, after a power cycle of the PoE switch that the AP's are connected to, all Access Points are still stuck in the adopting process again. I attempted to remove them, and factory reset the AP's, and then tried adopting the AP's all over, but no avail. Im still stuck in the "adopting" process.

    Im also having this issue with both my Unifi's and Pico M2's

    Heres a shot of /var/log/messages from one of my AP's.



    Jan 1 00:01:47 (none) user.info syslog: ace_reporter.reporter_next_inform_url():
    next inform url=http://unifi:8080/inform
    Jan 1 00:01:48 (none) user.debug syslog: uplink-monitor.update(): prev observatio
    n is eth, seq 5
    Jan 1 00:01:49 (none) user.debug syslog: uplink-monitor.update(): belief is eth
    Jan 1 00:01:49 (none) user.debug syslog: uplink-monitor.update(): uplink is eth0
    Jan 1 00:01:50 (none) authpriv.info dropbear: Child connection from 192.168.
    1.1:43104
    Jan 1 00:01:52 (none) user.debug syslog: infctld.fill_response_data(): verison=2.
    2.0.996
    Jan 1 00:01:52 (none) user.debug syslog: infctld.mcast_beacon(): send_beacon(): s
    rc=00:27:22:50:53:a8, seq=8, len=145
    Jan 1 00:01:52 (none) user.debug syslog: libubnt.url_resolve(): url: unifi
    :8080/inform
    Jan 1 00:01:52 (none) user.debug syslog: ace_reporter.reporter_inform(): connect(
    unifi:8080/inform) in progress...
    Jan 1 00:01:53 (none) authpriv.notice dropbear: password auth succeeded for
    'ubnt' from 192.168.1.1:43104
    Jan 1 00:02:02 (none) user.debug syslog: infctld.fill_response_data(): verison=2.
    2.0.996
    Jan 1 00:02:02 (none) user.debug syslog: infctld.mcast_beacon(): send_beacon(): s
    rc=00:27:22:50:53:a8, seq=9, len=145
    Jan 1 00:02:04 (none) user.debug syslog: uplink-monitor.update(): prev observatio
    n is eth, seq 6
    Jan 1 00:02:05 (none) user.debug syslog: uplink-monitor.update(): belief is eth
    Jan 1 00:02:05 (none) user.debug syslog: uplink-monitor.update(): uplink is eth0
    Jan 1 00:02:07 (none) user.debug syslog: ace_reporter.reporter_timedout(): Connect(unifi:8080/inform) h
    as timed out
    Jan 1 00:02:07 (none) user.err syslog: ace_reporter.reporter_fail(): server unreachable
    Jan 1 00:02:07 (none) user.err syslog: ace_reporter.reporter_fail(): initial contact failed #12, url=http://un
    ifi:8080/inform, rc=3
    Jan 1 00:02:07 (none) user.info syslog: ace_reporter.reporter_next_inform_url(): next inform url=http://uni
    fi:8080/inform
    Jan 1 00:02:12 (none) user.debug syslog: infctld.fill_response_data(): verison=2.2.0.996
    Jan 1 00:02:12 (none) user.debug syslog: infctld.mcast_beacon(): send_beacon(): src=00:27:22:50:53:a8, seq=10,
    len=145
    Jan 1 00:02:12 (none) user.debug syslog: mca-client.service(): Sending request to '/tmp/.mcad'
    Jan 1 00:02:12 (none) user.debug syslog: mcad-ctrl.cl_read(): received packet of 22 bytes from '/tmp/.mca-oE9
    dVT' (fromlen: 19)
    Jan 1 00:02:12 (none) user.debug syslog: mcad-ctrl.cl_read(): Processing status request...
    Jan 1 00:02:12 (none) user.debug syslog: mcad-ctrl.cl_read(): sending back the response (type: 0)..
    Jan 1 00:02:12 (none) user.debug syslog: mca-client.service(): Waiting for response...
    Jan 1 00:02:12 (none) user.debug syslog: libubnt.url_resolve(): url: unifi:8080/inform
    Jan 1 00:02:12 (none) user.debug syslog: ace_reporter.reporter_inform(): connect(unifi:8080/inform) in
    progress...
    Jan 1 00:02:20 (none) user.debug syslog: uplink-monitor.update(): prev observation is eth, seq 7
    Jan 1 00:02:21 (none) user.debug syslog: uplink-monitor.update(): belief is eth
    Jan 1 00:02:21 (none) user.debug syslog: uplink-monitor.update(): uplink is eth0
    Jan 1 00:02:22 (none) user.debug syslog: infctld.fill_response_data(): verison=2.2.0.996
    Jan 1 00:02:22 (none) user.debug syslog: infctld.mcast_beacon(): send_beacon(): src=00:27:22:50:53:a8, seq=11,
    len=145
    Jan 1 00:02:27 (none) user.debug syslog: ace_reporter.reporter_timedout(): Connect(unifi:8080/inform) h
    as timed out
    Jan 1 00:02:27 (none) user.err syslog: ace_reporter.reporter_fail(): server unreachable
    Jan 1 00:02:27 (none) user.err syslog: ace_reporter.reporter_fail(): initial contact failed #13, url=http://un
    ifi:8080/inform, rc=3
    Jan 1 00:02:27 (none) user.info syslog: ace_reporter.reporter_next_inform_url(): next inform url=http://uni
    fi:8080/inform
    Jan 1 00:02:32 (none) user.debug syslog: infctld.fill_response_data(): verison=2.2.0.996
    Jan 1 00:02:32 (none) user.debug syslog: infctld.mcast_beacon(): send_beacon(): src=00:27:22:50:53:a8, seq=12,
    len=145
    Jan 1 00:02:32 (none) user.debug syslog: libubnt.url_resolve(): url: unifi:8080/inform
    Jan 1 00:02:32 (none) user.debug syslog: ace_reporter.reporter_inform(): connect(unifi:8080/inform) in
    progress...
    Jan 1 00:02:36 (none) user.debug syslog: uplink-monitor.update(): prev observation is eth, seq 8
    Jan 1 00:02:37 (none) user.debug syslog: uplink-monitor.update(): belief is eth
    Jan 1 00:02:37 (none) user.debug syslog: uplink-monitor.update(): uplink is eth0
    Jan 1 00:02:42 (none) user.debug syslog: infctld.fill_response_data(): verison=2.2.0.996
    Jan 1 00:02:42 (none) user.debug syslog: infctld.mcast_beacon(): send_beacon(): src=00:27:22:50:53:a8, seq=13,
    len=145
    Jan 1 00:02:42 (none) user.debug syslog: mca-client.service(): Sending request to '/tmp/.mcad'
    Jan 1 00:02:42 (none) user.debug syslog: mcad-ctrl.cl_read(): received packet of 22 bytes from '/tmp/.mca-geD
    LoP' (fromlen: 19)
    Jan 1 00:02:42 (none) user.debug syslog: mcad-ctrl.cl_read(): Processing status request...
    Jan 1 00:02:42 (none) user.debug syslog: mcad-ctrl.cl_read(): sending back the response (type: 0)..
    Jan 1 00:02:42 (none) user.debug syslog: mca-client.service(): Waiting for response...
    Jan 1 00:02:47 (none) user.debug syslog: ace_reporter.reporter_timedout(): Connect(unifi:8080/inform) h
    as timed out
    Jan 1 00:02:47 (none) user.err syslog: ace_reporter.reporter_fail(): server unreachable
    Jan 1 00:02:47 (none) user.err syslog: ace_reporter.reporter_fail(): initial contact failed #14, url=http://un
    ifi:8080/inform, rc=3
    Jan 1 00:02:47 (none) user.info syslog: ace_reporter.reporter_next_inform_url(): next inform url=http://uni
    fi:8080/inform
    Jan 1 00:02:52 (none) user.debug syslog: infctld.fill_response_data(): verison=2.2.0.996
    Jan 1 00:02:52 (none) user.debug syslog: infctld.mcast_beacon(): send_beacon(): src=00:27:22:50:53:a8, seq=14,
    len=145
    Jan 1 00:02:52 (none) user.debug syslog: libubnt.url_resolve(): url: unifi:8080/inform
    Jan 1 00:02:52 (none) user.debug syslog: ace_reporter.reporter_inform(): connect(unifi:8080/inform) in
    progress...
    Jan 1 00:02:53 (none) user.debug syslog: uplink-monitor.update(): prev observation is eth, seq 9
    Jan 1 00:02:54 (none) user.debug syslog: uplink-monitor.update(): belief is eth
    Jan 1 00:02:54 (none) user.debug syslog: uplink-monitor.update(): uplink is eth0


    Any help? :manhappy:
    Ubiquiti Employee
    UBNT-Jerry
    Posts: 978
    Registered: ‎05-04-2009
    Posts: 978
    Kudos: 462
    Solutions: 6
    Contributions: 1
    Registered: 05-04-2009

    Re: Unifi AP Adoption Issues


    Heres a shot of /var/log/messages from one of my AP's.

    Your controller never tries to adopt the AP. For L3, make sure you do Inform twice.
    Emerging Member
    mcornstubble
    Posts: 59
    Registered: ‎10-20-2011
    Posts: 59
    Kudos: 5
    Registered: 10-20-2011

    Re: Unifi AP Adoption Issues

    Inform twice? Where is this variable located?

    Also, more specifically, it looks like the controller is stuck "readopting" the AP.

    I am seeing "automatic readoption" in the alerts tab

    Thanks again for all your help.
    Emerging Member
    mcornstubble
    Posts: 59
    Registered: ‎10-20-2011
    Posts: 59
    Kudos: 5
    Registered: 10-20-2011

    Re: Unifi AP Adoption Issues

    Ah my bad all. It was a DNS issue all the way.

    Originally the AP's were looking for unifi:8080 where unifi was the hostname of my controller.

    I changed the hostname to the IP Address of the controller, effectively 192.168.1.6, so the AP's then looked for 192.168.1.6:8080, which allowed the AP's to adopt successfully with no issues.

    Looks like I need to fix DNS on my home network :manhappy:

    Thanks Jerry!
    Longtime Visitor
    tganet
    Posts: 9
    Registered: ‎07-05-2008
    Posts: 9
    Registered: 07-05-2008

    Unifi AP Adoption Issues

    Hello, I'm having almost the same problem, trying to inform PicoStatiomM2 is unifi:8080/inform to the server, but when I conetcat PicoStation in M2 follow the procedures via SSH and enter the commands:
    MCA-cli

    set-inform IP_OF_MY_UNIFI:8080/inform

    but when you enter the command:

    info

    I see that he continues to seek the url unifi:8080/inform

    What to do?

    Since the re-recorded three times fimware
    Already made to restore factory
    I followed all the procedures and can not change the url of the set-inform.


    Sandro
    Novo! Clique nas palavras acima para ver tr
    New Member
    ABrese
    Posts: 10
    Registered: ‎09-08-2011
    Posts: 10
    Registered: 09-08-2011

    Re: Unifi AP Adoption Issues

    I had similar issue on an AP this week. it turned out to be a name resolution issue. Even though the AP was on the same subnet as the Unifi Controller it would not adopt. I used ssh to get into the device to check the error logs (tail -100 /var/log/messages) and saw the errors. I tried the advice to run syswrapper.sh restore-default without success.
    To resolve I manually edited the /etc/hosts file to include the unifi entry with the ip address of the Unifi controller. The AP immediately saw the controller and downloaded the current firmware form the controller then rebooted.
    Once the device rebooted I manually entered the unifi entry on the hosts file again. The device rebooted a second time and began operating as expected from that point on.
    -- Adam Breese
    Lead Architect
    Kinross Gold Corporation
    New Visitor
    Dominic
    Posts: 1
    Registered: ‎04-02-2013
    Posts: 1
    Registered: 04-02-2013

    Re: Unifi AP Adoption Issues

    It is same my problem.

    Did you find any solution to solve problem?

    Could you tell me about the solution?

    I hope have best solution to help me.

    Thank you so much.

     

    Reply