Upcoming Maintenance Alert:

The UBNT Community will be upgraded at 5pm MDT on April 25th. During this time the community forums will be set to read-only status.

Learn more

×
Reply
New Member
Posts: 11
Registered: ‎01-11-2015
Kudos: 1
Accepted Solution

UniFi AP Constantly Restarting and Readopting

Hi All,

 

I've had multiple Ubiquiti networks in our home and offices and friends homes.  Love it.  

 

For some reason I keep running into a problem at our house with the APs readopting 4-6 times a day.  

 

My house is a ranch, so it's pretty spread out with plaster walls.  So we have 3 indoor 1st floor APs about 150 feet apart (Mudroom, Great Room, Bedrooms).  We have 1 in the basement and one outdoor AP outside (but about 100 feet from the Bedroom AP).

 

When it works, I'm seeing awesome speeds (50-75mbps).  The only problem, and it's a biggie, is that for whatever reason the APs disconnect and readopt ALL the time. This cuts out internet and SONOS (which is a huge pain in the ass to hear music skipping all over the house.  

 

My System

  • Comcast Internet
  • Arris Modem 
  • Ubiquiti TS-8-PRO ToughSwitch 8 Port Advanced Power Ethernet Controllers
  • Wired to 4 UniFi AP-LR and 1 UniFi AP-Outdoor+
  • All APs running version 3.2.5.2791

What I've Tried

  • Changing to a mix of radio channels, all HT40.
  • Changing to a mix of TX Power.

 

The issue seems to all happen at once - ALL the APs disconnect and then readopt.  

 

Also include screenshots of the configs.

 

Drives us crazy, and help would be greatly appreciated!!

 

Thanks,

Tom

 

Screen Shot 2017-03-13 at 7.24.03 PM.pngScreen Shot 2017-03-13 at 7.46.53 PM.pngScreen Shot 2017-03-13 at 7.47.01 PM.pngScreen Shot 2017-03-13 at 7.47.13 PM.png


Accepted Solutions
Ubiquiti Employee
Posts: 317
Registered: ‎10-04-2015
Kudos: 388
Solutions: 22
Contributions: 1

Re: UniFi AP Constantly Restarting and Readopting

@tomvranas Thanks for posting- we've made a number of improvements in our firmware that could address this issue. Our most recent release (3.7.47.6194) actually addresses an issue we've seen with Sonos devices. I'd recommend trying to update your device firmware and seeing how the devices function. 

UBNT_Alternate_Logo.png
Ubiquiti Networks Enterprise Support Team

Check out our ever-evolving Help Center for answers to many common questions!

View solution in original post


All Replies
New Member
Posts: 11
Registered: ‎01-11-2015
Kudos: 1

Re: UniFi AP Constantly Restarting and Readopting

...and just so you see what our client side looks like....there's a lot here.  Mostly iPhones, computers, SONOS, AppleTVs and logitech remotes.

 

Again sorry this is so much info, but figured it may help!

 

Screen Shot 2017-03-13 at 8.05.41 PM.pngScreen Shot 2017-03-13 at 8.05.59 PM.png

Regular Member
Posts: 506
Registered: ‎04-22-2016
Kudos: 93
Solutions: 39

Re: UniFi AP Constantly Restarting and Readopting

@tomvranas

 

How many Sonos devices?

How are the Sonos connectet?

Do you use the Sonos Mesh Network?

New Member
Posts: 11
Registered: ‎01-11-2015
Kudos: 1

Re: UniFi AP Constantly Restarting and Readopting

Thanks @cempa!

 

It's the standard SONOS Setup - all speaker communicate directly with WiFi (that's why you see all of the speakers with seperate IPs connecting to the various APs).  This means it is NOT creating a mesh network.

 

Standard_Setup_Diagram.png

 

We have 14 speakers (I know. addiction.) - essentially one in every room.  

 

We used to use the BOOST (which allows you to change the WiFi channel, but we had even more problems with that setup so got rid of it in favor of the STANDARD/direct connection.

 

And another potential interference? We have 10 NetGear VueZone wireless cameras all around the house- these all communicate with a base station by the router.  I couldn't find information on what frequency/technology those use.

 

Phew!

 

Thanks again,

 

Tom

Ubiquiti Employee
Posts: 317
Registered: ‎10-04-2015
Kudos: 388
Solutions: 22
Contributions: 1

Re: UniFi AP Constantly Restarting and Readopting

@tomvranas Thanks for posting- we've made a number of improvements in our firmware that could address this issue. Our most recent release (3.7.47.6194) actually addresses an issue we've seen with Sonos devices. I'd recommend trying to update your device firmware and seeing how the devices function. 

UBNT_Alternate_Logo.png
Ubiquiti Networks Enterprise Support Team

Check out our ever-evolving Help Center for answers to many common questions!

New Member
Posts: 11
Registered: ‎01-11-2015
Kudos: 1

Re: UniFi AP Constantly Restarting and Readopting

@UBNT-APieper I also had to update the controller...it looks EVEN better - I remember the first controllers and these are so slick.

 

It automatically updated the APs but only to version 3.7.37.6065. It's on auto update.

 

Provisioning went well.  I've been stationary the entire time I did the update and saw better speeds.

 

Should I change any of these settings?

  • Transmit Power - all currently set to medium
  • Channels - I'm using 1, 6 and 11. Saw in the new upgrade you can use channels all 1-11.
  • Channel Width - using HT20

Thanks!

 

New Member
Posts: 11
Registered: ‎01-11-2015
Kudos: 1

Re: UniFi AP Constantly Restarting and Readopting

This seems to have worked so far and seems like clients are connecting more appropriately (aka I used to have a client on one side of the house bypass 2 closer APs and connect to a farther one).

 

Will keep fingers crossed and see if this does the trick!  Thanks!!!

Ubiquiti Employee
Posts: 317
Registered: ‎10-04-2015
Kudos: 388
Solutions: 22
Contributions: 1

Re: UniFi AP Constantly Restarting and Readopting

[ Edited ]

@tomvranas Glad you're liking the updated controller Man Happy based on your devices that should be fine. 

Just depends on the environment though- see how it performs and if you note any performance issues we can make adjustments from there. 

UBNT_Alternate_Logo.png
Ubiquiti Networks Enterprise Support Team

Check out our ever-evolving Help Center for answers to many common questions!

New Member
Posts: 11
Registered: ‎01-11-2015
Kudos: 1

Re: UniFi AP Constantly Restarting and Readopting

@UBNT-APieper and @cempa Looks like the problem continues....had a few disconnects + readoptions today.  

 

Grrrr.

 

Thoughts?

 

MUDROOM was automatically readoptedToday6:54 pm
BASEMENT was automatically readoptedToday6:54 pm
GREAT ROOM was automatically readoptedToday6:54 pm
BACK YARD was automatically readoptedToday6:54 pm
BASEMENT was automatically readoptedToday6:34 pm
BACK YARD was automatically readoptedToday6:34 pm
BEDROOMS was automatically readoptedToday11:13 am
BACK YARD was automatically readoptedToday11:13 am
BASEMENT was automatically readoptedToday11:13 am
GREAT ROOM was automatically readoptedToday11:13 am
MUDROOM was automatically readoptedToday11:13 am
MUDROOM was automatically readoptedToday10:25 am
BASEMENT was automatically readoptedToday10:25 am
BACK YARD was automatically readoptedToday10:25 am
BASEMENT was automatically readoptedToday9:50 am
BEDROOMS was automatically readoptedToday9:50 am
BASEMENT was automatically readoptedToday9:49 am
BEDROOMS was automatically readoptedToday9:44 am
GREAT ROOM was automatically readoptedToday9:44 am
MUDROOM was automatically readoptedToday9:44 am
BACK YARD was automatically readoptedToday9:44 am
Regular Member
Posts: 506
Registered: ‎04-22-2016
Kudos: 93
Solutions: 39

Re: UniFi AP Constantly Restarting and Readopting

Hi @tomvranas

 

Make sure the thoughswitch TS8 pro Firmware is up do date and RSTP switched on.

 

First we need to find out if the interrupts are coming from your WAN Internet connection or from inside the LAN.

 

Connect a wired computer / Laptop directly behind the arris modem. Run a constant ping to 8.8.8.8. When the interruptions happen, what about the pinging computer?

 

UniFi controller: Which controller and how is it connected to the UniFi AP?

In the UnFi controller under Site > settings > turn off Uplink Connectivity Monitor if switched on

 

 

 

 

Regular Member
Posts: 654
Registered: ‎03-28-2013
Kudos: 198
Solutions: 22

Re: UniFi AP Constantly Restarting and Readopting

[ Edited ]

tomvranas wrote:

This seems to have worked so far and seems like clients are connecting more appropriately (aka I used to have a client on one side of the house bypass 2 closer APs and connect to a farther one).

 

Will keep fingers crossed and see if this does the trick!  Thanks!!!


 

Make sure you do NOT have any AP set to use HT40. Switch them all to HT20 if any are still on HT40.

 

Turn your power down to LOW on all the APs.

 

Do a walk test with a phone/tablet to check signal levels.

 

Consider hooking as many of the Sonos devices into Ethernet as possible, at minimum, a single centrally located SonosDevice. Remember, the more the better.

Then use the SonosNet, set that to Channel 1, via the Sonos App. This channel will be dedicated to the Sonos network.

 

Then with the other APs, use channel 6 for two APs and channel 11 for the other two APs. Power LOW.

 

Set all the APs to have a reserved IP address. Make sure the controller is either static or has a reserved IP address.

 

Set all the Sonos devices to also have reserved IP addresses.

 

This is simialr to what I do, I never have a Sonos problem.

New Member
Posts: 11
Registered: ‎01-11-2015
Kudos: 1

Re: UniFi AP Constantly Restarting and Readopting

Thanks @JimBob

 

  • Set all APs to HT20.
  • Set all APs power to LOW.
  • I talked with SONOS and they suggested that NOT using the BOOST/Mesh network is better.  With using the new "Standard" setup you can't control channels (since all SONOS is connecting directly to WIFI and not Mesh).  I would only be able to connect 1 speaker or the BOOST to ethernet (long story - super old house, wiring is tough)
  • Changed all the APs to either 6 or 11 trying to space out channels so they aren't near eachother.

 

Went to give AP static IP, but don't know how to find the rest of the info:

 

Screen Shot 2017-03-15 at 10.34.03 AM.png

 

Also, went to give SONOS a static IP and it doesn't allow me to give Clients a fixed IP:

Screen Shot 2017-03-15 at 10.34.58 AM.png

 

++

 

Let me know thoughts about SONOS Mesh vs. Standard.  Also any help with the other configurations.

 

 

Highlighted
New Member
Posts: 1
Registered: ‎09-30-2016

Re: UniFi AP Constantly Restarting and Readopting

Did you ever get a solution?

 

I have the same for some time now.

Without obvious reason , my APs got to 98% sirq and reboot.

And this every one or two hours, as soon as they are in use.

 

Interesting detail in syslog:

Sep 14 12:01:06 10.1.0.26 syslog: mca-client.service(): Failed sending request to '/tmp/.mcad' - 'Resource temporarily unavailable'

....

Sep 14 12:01:41 10.1.0.26 syswrapper: kill-mcad. reason: mcad not responding
Sep 14 12:01:43 10.1.0.26 init: process '/bin/reset-handler' (pid 1970) exited. Scheduling for restart.

 

HELP please.

 

Syslog says:

Sep 14 12:00:28 10.1.0.26 hostapd: ath6: STA 92:2a:a8:4b:b7:99 DRIVER: Sead AUTH addr=58:7f:57:3b:13:db status_code=0
Sep 14 12:00:38 10.1.0.26 syslog: mca-monitor.do_monitor(): mcad.checkin is 148 ago (max=200)
Sep 14 12:00:43 10.1.0.26 libubnt[1972]: wevent.ubnt_custom_event(): EVENT_STA_LEAVE ath1: 58:7f:57:3b:13:db / 0
Sep 14 12:01:06 10.1.0.26 syslog: mca-client.service(): Failed sending request to '/tmp/.mcad' - 'Resource temporarily unavailable'
Sep 14 12:01:06 10.1.0.26 syslog: mca-monitor.do_monitor(): mcad.checkin is 183 ago (max=200)
Sep 14 12:01:06 10.1.0.26 libubnt[1972]: wevent.ubnt_custom_event(): EVENT_STA_LEAVE ath1: 58:7f:57:3b:13:db / 0
Sep 14 12:01:06 10.1.0.26 libubnt[1972]: wevent.ubnt_custom_event(): EVENT_STA_LEAVE ath1: 58:7f:57:3b:13:db / 0
Sep 14 12:01:06 10.1.0.26 libubnt[1972]: wevent.ubnt_custom_event(): EVENT_STA_LEAVE ath1: 58:7f:57:3b:13:db / 0
Sep 14 12:01:06 10.1.0.26 libubnt[1972]: wevent.ubnt_custom_event(): EVENT_STA_LEAVE ath6: 58:7f:57:3b:13:db / 0
Sep 14 12:01:06 10.1.0.26 libubnt[1972]: wevent.ubnt_custom_event(): EVENT_STA_LEAVE ath1: 14:5f:94:34:a1:cf / 0
Sep 14 12:01:06 10.1.0.26 hostapd: ath1: STA 82:2a:a8:4a:b7:99 DRIVER: Sead AUTH addr=14:5f:94:34:a1:cf status_code=0
Sep 14 12:01:06 10.1.0.26 hostapd: ath6: STA 92:2a:a8:4b:b7:99 DRIVER: Sead AUTH addr=14:5f:94:34:a1:cf status_code=0
Sep 14 12:01:06 10.1.0.26 hostapd: ath6: STA 92:2a:a8:4b:b7:99 DRIVER: Sead AUTH addr=14:5f:94:34:a1:cf status_code=0
Sep 14 12:01:06 10.1.0.26 hostapd: ath1: STA 14:5f:94:34:a1:cf IEEE 802.11: associated
Sep 14 12:01:06 10.1.0.26 hostapd: ath1: STA 14:5f:94:34:a1:cf RADIUS: stopped accounting session 00000013-00000003
Sep 14 12:01:06 10.1.0.26 hostapd: ath6: STA 92:2a:a8:4b:b7:99 DRIVER: Sead AUTH addr=78:f8:82:cd:06:6b status_code=0
Sep 14 12:01:06 10.1.0.26 hostapd: ath6: STA 92:2a:a8:4b:b7:99 DRIVER: Sead AUTH addr=14:5f:94:34:a1:cf status_code=0
Sep 14 12:01:06 10.1.0.26 hostapd: ath6: STA 92:2a:a8:4b:b7:99 DRIVER: Sead AUTH addr=14:5f:94:34:a1:cf status_code=0
Sep 14 12:01:06 10.1.0.26 hostapd: ath1: STA 14:5f:94:34:a1:cf RADIUS: starting accounting session 00000013-00000007
Sep 14 12:01:06 10.1.0.26 kernel: [  278.870000]  ieee80211_ioctl_setparam: VLANID32 = 99
Sep 14 12:01:06 10.1.0.26 kernel: [  278.870000] 14:5f:94:34:a1:cf: node vid=99 rsn_authmode=0x00000040, ni_authmode=0x00
Sep 14 12:01:06 10.1.0.26 hostapd: ath6: STA 92:2a:a8:4b:b7:99 DRIVER: Sead AUTH addr=14:5f:94:34:a1:cf status_code=0
Sep 14 12:01:06 10.1.0.26 hostapd: ath6: STA 92:2a:a8:4b:b7:99 DRIVER: Sead AUTH addr=14:5f:94:34:a1:cf status_code=0
Sep 14 12:01:06 10.1.0.26 hostapd: ath6: STA 92:2a:a8:4b:b7:99 DRIVER: Sead AUTH addr=14:5f:94:34:a1:cf status_code=0
Sep 14 12:01:06 10.1.0.26 hostapd: ath6: STA 92:2a:a8:4b:b7:99 DRIVER: Sead AUTH addr=14:5f:94:34:a1:cf status_code=0
Sep 14 12:01:06 10.1.0.26 hostapd: ath1: STA 14:5f:94:34:a1:cf IEEE 802.1X: authenticated - EAP type: 25 (PEAP)
Sep 14 12:01:06 10.1.0.26 hostapd: ath1: STA 58:7f:57:3b:13:db IEEE 802.11: disassociated
Sep 14 12:01:06 10.1.0.26 hostapd: ath1: STA 14:5f:94:34:a1:cf WPA: pairwise key handshake completed (RSN)
Sep 14 12:01:06 10.1.0.26 hostapd: ath6: STA 92:2a:a8:4b:b7:99 DRIVER: Sead AUTH addr=14:5f:94:34:a1:cf status_code=0
Sep 14 12:01:06 10.1.0.26 hostapd: ath6: STA 92:2a:a8:4b:b7:99 DRIVER: Sead AUTH addr=14:5f:94:34:a1:cf status_code=0
Sep 14 12:01:06 10.1.0.26 hostapd: ath6: STA 92:2a:a8:4b:b7:99 DRIVER: Sead AUTH addr=14:5f:94:34:a1:cf status_code=0
Sep 14 12:01:06 10.1.0.26 hostapd: ath6: STA 92:2a:a8:4b:b7:99 DRIVER: Sead AUTH addr=14:5f:94:34:a1:cf status_code=0
Sep 14 12:01:19 10.1.0.26 syslog: mca-client.service(): Failed sending request to '/tmp/.mcad' - 'Resource temporarily unavailable'
Sep 14 12:01:20 10.1.0.26 syslog: mca-monitor.do_monitor(): mcad.checkin is 193 ago (max=200)
Sep 14 12:01:25 10.1.0.26 hostapd: ath1: STA 82:2a:a8:4a:b7:99 DRIVER: Sead AUTH addr=f0:24:75:be:e3:42 status_code=0
Sep 14 12:01:25 10.1.0.26 hostapd: ath1: STA 82:2a:a8:4a:b7:99 DRIVER: Sead AUTH addr=f0:24:75:be:e3:42 status_code=0
Sep 14 12:01:27 10.1.0.26 hostapd: ath1: STA 82:2a:a8:4a:b7:99 DRIVER: Sead AUTH addr=f0:24:75:be:e3:42 status_code=0
Sep 14 12:01:27 10.1.0.26 hostapd: ath1: STA 82:2a:a8:4a:b7:99 DRIVER: Sead AUTH addr=f0:24:75:be:e3:42 status_code=0
Sep 14 12:01:28 10.1.0.26 hostapd: ath1: STA 82:2a:a8:4a:b7:99 DRIVER: Sead AUTH addr=f0:24:75:be:e3:42 status_code=0
Sep 14 12:01:30 10.1.0.26 kernel: [  302.010000] ubnt_calc_airtime_average[1391] tick counter wrapped, time_delta:1175
Sep 14 12:01:31 10.1.0.26 syslog: mca-client.service(): Failed sending request to '/tmp/.mcad' - 'Resource temporarily unavailable'
Sep 14 12:01:34 10.1.0.26 kernel: [  304.470000] ubnt_calc_airtime_average[1391] tick counter wrapped, time_delta:464
Sep 14 12:01:35 10.1.0.26 syslog: mca-monitor.do_monitor(): mcad.checkin is 208 ago (max=200)
Sep 14 12:01:40 10.1.0.26 hostapd: ath1: STA 82:2a:a8:4a:b7:99 DRIVER: Sead AUTH addr=f0:24:75:be:e3:42 status_code=0
Sep 14 12:01:40 10.1.0.26 hostapd: ath1: STA 82:2a:a8:4a:b7:99 DRIVER: Sead AUTH addr=f0:24:75:be:e3:42 status_code=0
Sep 14 12:01:40 10.1.0.26 hostapd: ath1: STA 82:2a:a8:4a:b7:99 DRIVER: Sead AUTH addr=f0:24:75:be:e3:42 status_code=0
Sep 14 12:01:40 10.1.0.26 hostapd: ath1: STA 82:2a:a8:4a:b7:99 DRIVER: Sead AUTH addr=f0:24:75:be:e3:42 status_code=0
Sep 14 12:01:41 10.1.0.26 syswrapper: kill-mcad. reason: mcad not responding
Sep 14 12:01:43 10.1.0.26 init: process '/bin/reset-handler' (pid 1970) exited. Scheduling for restart.
Sep 14 12:01:46 10.1.0.26 init: starting pid 2752, tty '/dev/null': '/bin/reset-handler'
Sep 14 12:01:46 10.1.0.26 hostapd: ath1: STA 82:2a:a8:4a:b7:99 DRIVER: Sead AUTH addr=f0:24:75:be:e3:42 status_code=0
Sep 14 12:01:47 10.1.0.26 hostapd: ath1: STA 82:2a:a8:4a:b7:99 DRIVER: Sead AUTH addr=f0:24:75:be:e3:42 status_code=0
Sep 14 12:01:49 10.1.0.26 init: process '/bin/mca-monitor' (pid 1992) exited. Scheduling for restart.
Sep 14 12:01:50 10.1.0.26 init: process '/bin/reset-handler' (pid 2752) exited. Scheduling for restart.
Sep 14 12:01:51 10.1.0.26 init: starting pid 2755, tty '/dev/null': '/bin/reset-handler'
Sep 14 12:01:56 10.1.0.26 init: starting pid 2756, tty '/dev/null': '/bin/mca-monitor'
Sep 14 12:02:01 10.1.0.26 hostapd: ath1: STA 82:2a:a8:4a:b7:99 DRIVER: Sead AUTH addr=f0:24:75:be:e3:42 status_code=0
Sep 14 12:02:02 10.1.0.26 hostapd: ath1: STA 82:2a:a8:4a:b7:99 DRIVER: Sead AUTH addr=f0:24:75:be:e3:42 status_code=0
Sep 14 12:02:02 10.1.0.26 hostapd: ath1: STA 82:2a:a8:4a:b7:99 DRIVER: Sead AUTH addr=f0:24:75:be:e3:42 status_code=0
Sep 14 12:02:06 10.1.0.26 hostapd: ath1: STA 82:2a:a8:4a:b7:99 DRIVER: Sead AUTH addr=f0:24:75:be:e3:42 status_code=0
Sep 14 12:02:06 10.1.0.26 hostapd: ath1: STA 48:5a:3f:62:6a:bb IEEE 802.11: disassociated
Sep 14 12:02:06 10.1.0.26 hostapd: ath1: STA 82:2a:a8:4a:b7:99 DRIVER: Sead AUTH addr=4c:7c:5f:49:d8:2b status_code=0
Sep 14 12:02:14 10.1.0.26 syslog: mca-client.service(): Failed sending request to '/tmp/.mcad' - 'Resource temporarily unavailable'
Sep 14 12:02:15 10.1.0.26 syslog: mca-monitor.do_monitor(): mcad.checkin is 247 ago (max=200)
Sep 14 12:02:16 10.1.0.26 hostapd: ath1: STA 82:2a:a8:4a:b7:99 DRIVER: Sead AUTH addr=4c:7c:5f:49:d8:2b status_code=0
Sep 14 12:02:16 10.1.0.26 hostapd: ath1: STA 82:2a:a8:4a:b7:99 DRIVER: Sead AUTH addr=4c:7c:5f:49:d8:2b status_code=0
Sep 14 12:02:16 10.1.0.26 hostapd: ath1: STA f0:24:75:be:e3:42 IEEE 802.11: disassociated
Sep 14 12:02:18 10.1.0.26 syswrapper: kill-mcad. reason: mcad not responding
Sep 14 12:02:21 10.1.0.26 hostapd: ath1: STA 82:2a:a8:4a:b7:99 DRIVER: Sead AUTH addr=b8:44:d9:95:36:12 status_code=0
Sep 14 12:02:21 10.1.0.26 hostapd: ath1: STA 82:2a:a8:4a:b7:99 DRIVER: Sead AUTH addr=b8:44:d9:95:36:12 status_code=0
Sep 14 12:02:22 10.1.0.26 init: process '/bin/reset-handler' (pid 2755) exited. Scheduling for restart.
Sep 14 12:02:23 10.1.0.26 kernel: [  307.950000] ubnt_calc_airtime_average[1391] tick counter wrapped, time_delta:6809
Sep 14 12:02:23 10.1.0.26 kernel: [  313.050000] ubnt_calc_airtime_average[1391] tick counter wrapped, time_delta:1963
Sep 14 12:02:23 10.1.0.26 kernel: [  321.350000] ubnt_calc_airtime_average[1391] tick counter wrapped, time_delta:2412
Sep 14 12:02:23 10.1.0.26 kernel: [  324.360000] ubnt_calc_airtime_average[1391] tick counter wrapped, time_delta:11402
Sep 14 12:02:23 10.1.0.26 init: process '/bin/uplink-monitor' (pid 1973) exited. Scheduling for restart.
Sep 14 12:02:24 10.1.0.26 init: starting pid 2761, tty '/dev/null': '/bin/reset-handler'
Sep 14 12:02:25 10.1.0.26 init: starting pid 2762, tty '/dev/null': '/bin/uplink-monitor'
Sep 14 12:02:33 10.1.0.26 init: process '/bin/mca-monitor' (pid 2756) exited. Scheduling for restart.
Sep 14 12:02:33 10.1.0.26 init: process '/bin/reset-handler' (pid 2761) exited. Scheduling for restart.
Sep 14 12:02:34 10.1.0.26 init: process '/bin/uplink-monitor' (pid 2762) exited. Scheduling for restart.
Sep 14 12:02:35 10.1.0.26 init: starting pid 2765, tty '/dev/null': '/bin/reset-handler'
Sep 14 12:02:37 10.1.0.26 kernel: [  369.950000] ubnt_calc_airtime_average[1391] tick counter wrapped, time_delta:26657
Sep 14 12:02:39 10.1.0.26 kernel: [  371.480000] ubnt_calc_airtime_average[1391] tick counter wrapped, time_delta:7546
Sep 14 12:02:40 10.1.0.26 init: starting pid 2766, tty '/dev/null': '/bin/uplink-monitor'
Sep 14 12:02:41 10.1.0.26 init: starting pid 2767, tty '/dev/null': '/bin/mca-monitor'
Sep 14 12:02:47 10.1.0.26 hostapd: ath1: STA 4c:7c:5f:49:d8:2b IEEE 802.11: disassociated
Sep 14 12:02:47 10.1.0.26 syslog: uplink-monitor.uplink_monitor_main(): sysid=0xe537, serial: 80:2a:a8:49:b7:99
Sep 14 12:02:49 10.1.0.26 syslog: uplink-monitor.uplink_monitor_main(): vport ath4: 80:2a:a8:4b:b7:99
Sep 14 12:02:49 10.1.0.26 dropbear[2768]: Child connection from 10.1.99.53:8778

Reply