Please help, UAP Outdoor+ rebooting every 5 mins in busy wifi environment - "too much inter

[marc3k]

I just give a try but it's worse than the 3.3.12 firmware ...

AP reboot each 3 minutes.

[UBNT-BenBuckley]

@andris

---

When you say the last binary you provided: uap-odplus-busy-env3.bin is "based on 3.7.9" can you clarify how that differs from the uap-odplus-busy-env2.bin binary....was that also based on 3.7.9 or was that based on a different version?

---

It's no different than uap-odplus-busy-env2.bin.  They are both based on 3.7.9.  I was clarifying because the same solution will be rolled out in the forthcoming newest Alpha.  So I was confirming that this should be identical to 3.7.9, except that this has the update.

---

I think if i understand correctly - uap-odplus-busy-env3.bin contains the more robust / permanent solutions you mentioned in earlier posts, where the earlier debug builds were quick/debug implementations and tests of the solutions?

---

Correct.  The latest firmware has the same robust solution that is being rolled into the newest Alpha.

[UBNT-BenBuckley]

@marc3k In what way is this "worse?"  Are the reboots more frequent?

Can you log into a running AP and see what the output of 'cat /var/log/messages' is?

If necessary, can you provide me with SSH access and/or set up remote logging in order to catch the crashes?  I can give you commands to log directly to our remote log server if that interests you.  

Also, I still have it in queu to help you upgrade your PicostationM2's, but I have a few other things on my plate that very important.  Sorry for the delay on that

[marc3k]

@UBNT-BenBuckley lets go for both solution. I will provide you the link to ssh into the ap and the controller.

[Amaravati]

@UBNT-BenBuckley

The custom firmware worked normal as long as it was operational. It did reboot itself after 14 hours. Below is Log file around reboot time for custom firmware:

2016-08-29	21:46:01	Information	("U2O,24a43ca2ad33,feature-busy-env-bjb.2")	daemon	dnsmasq	read /etc/hosts - 1 addresses
2016-08-29	21:46:01	Information	("U2O,24a43ca2ad33,feature-busy-env-bjb.2")	daemon	dnsmasq	using nameserver 192.168.0.250#53
2016-08-29	21:46:01	Information	("U2O,24a43ca2ad33,feature-busy-env-bjb.2")	daemon	dnsmasq	reading /etc/resolv.conf
2016-08-29	21:44:53	Information	("U2O,24a43ca2ad33,feature-busy-env-bjb.2")	daemon	hostapd	ath3: STA cc:55:ad:fc:f9:94 IEEE 802.11: associated
2016-08-29	21:44:53	Warning	("U2O,24a43ca2ad33,feature-busy-env-bjb.2")	user	kernel	[53719.182000] 13 16 19
2016-08-29	21:44:53	Warning	("U2O,24a43ca2ad33,feature-busy-env-bjb.2")	user	kernel	[53719.182000] valid pRc->validRateIndex :
2016-08-29	21:44:53	Warning	("U2O,24a43ca2ad33,feature-busy-env-bjb.2")	user	kernel	[53719.181000] vap: 46:a4:3c:a3:ad:33
2016-08-29	21:43:44	Information	("U2O,24a43ca2ad33,feature-busy-env-bjb.2")	user	libubnt	wevent.ubnt_custom_event(): EVENT_STA_LEAVE ath4: 28:ef:01:1d:72:d8 / 0
2016-08-29	21:43:44	Information	("U2O,24a43ca2ad33,feature-busy-env-bjb.2")	daemon	hostapd	ath4: STA 28:ef:01:1d:72:d8 IEEE 802.11: disassociated
2016-08-29	21:43:44	Information	("U2O,24a43ca2ad33,feature-busy-env-bjb.2")	daemon	hostapd	ath4: STA 28:ef:01:1d:72:d8 IEEE 802.11: sta_stats
2016-08-29	21:41:01	Error	("U2O,24a43ca2ad33,feature-busy-env-bjb.2")	cron	crond	USER admin pid 20014 cmd syswrapper.sh schedule-action
2016-08-29	21:38:49	Information	("U2O,24a43ca2ad33,feature-busy-env-bjb.2")	user	libubnt	wevent.ubnt_custom_event(): EVENT_STA_LEAVE ath2: 38:aa:3c:f3:11:8a / 0
2016-08-29	21:38:49	Information	("U2O,24a43ca2ad33,feature-busy-env-bjb.2")	daemon	hostapd	ath2: STA 38:aa:3c:f3:11:8a IEEE 802.11: disassociated
2016-08-29	21:38:49	Information	("U2O,24a43ca2ad33,feature-busy-env-bjb.2")	daemon	hostapd	ath2: STA 38:aa:3c:f3:11:8a IEEE 802.11: sta_stats
2016-08-29	21:36:01	Error	("U2O,24a43ca2ad33,feature-busy-env-bjb.2")	cron	crond	USER admin pid 18675 cmd syswrapper.sh schedule-action
2016-08-29	21:31:01	Error	("U2O,24a43ca2ad33,feature-busy-env-bjb.2")	cron	crond	USER admin pid 17260 cmd syswrapper.sh schedule-action
2016-08-29	21:26:01	Error	("U2O,24a43ca2ad33,feature-busy-env-bjb.2")	cron	crond	USER admin pid 15923 cmd syswrapper.sh schedule-action
2016-08-29	21:21:01	Error	("U2O,24a43ca2ad33,feature-busy-env-bjb.2")	cron	crond	USER admin pid 14582 cmd syswrapper.sh schedule-action
2016-08-29	21:16:01	Error	("U2O,24a43ca2ad33,feature-busy-env-bjb.2")	cron	crond	USER admin pid 13167 cmd syswrapper.sh schedule-action
2016-08-29	21:11:01	Error	("U2O,24a43ca2ad33,feature-busy-env-bjb.2")	cron	crond	USER admin pid 11830 cmd syswrapper.sh schedule-action
2016-08-29	21:06:01	Error	("U2O,24a43ca2ad33,feature-busy-env-bjb.2")	cron	crond	USER admin pid 10419 cmd syswrapper.sh schedule-action
2016-08-29	21:01:01	Error	("U2O,24a43ca2ad33,feature-busy-env-bjb.2")	cron	crond	USER admin pid 9072 cmd syswrapper.sh schedule-action
2016-08-29	20:56:01	Error	("U2O,24a43ca2ad33,feature-busy-env-bjb.2")	cron	crond	USER admin pid 7733 cmd syswrapper.sh schedule-action
2016-08-29	20:51:01	Error	("U2O,24a43ca2ad33,feature-busy-env-bjb.2")	cron	crond	USER admin pid 6320 cmd syswrapper.sh schedule-action

This 3.7.10.5096 AP Outdoor also started reboot within 10 minutes of the above for not particular reason I could understand.

2016-08-29	21:50:53	Warning	("U2O,24a43ca293e6,v3.7.10.5096")	user	kernel	[ 59.296000] Set bcast rate 6000
2016-08-29	21:50:53	Warning	("U2O,24a43ca293e6,v3.7.10.5096")	user	kernel	[ 59.296000] Set mcast rate : 6000
2016-08-29	21:50:53	Warning	("U2O,24a43ca293e6,v3.7.10.5096")	user	kernel	[ 59.296000] vap->iv_mgt_rate 6000
2016-08-29	21:49:42	Warning	("U2O,24a43ca293e6,v3.7.10.5096")	user	kernel	[190030.162000] 13 16 19
2016-08-29	21:49:42	Warning	("U2O,24a43ca293e6,v3.7.10.5096")	user	kernel	[190030.162000] valid pRc->validRateIndex :
2016-08-29	21:49:42	Warning	("U2O,24a43ca293e6,v3.7.10.5096")	user	kernel	[190030.162000] vap: 46:a4:3c:a3:93:e6
2016-08-29	21:49:42	Information	("U2O,24a43ca293e6,v3.7.10.5096")	daemon	hostapd	ath3: STA cc:55:ad:fc:f9:94 IEEE 802.11: associated
2016-08-29	21:46:01	Error	("U2O,24a43ca293e6,v3.7.10.5096")	cron	crond	USER admin pid 24046 cmd syswrapper.sh schedule-action
2016-08-29	21:43:04	Information	("U2O,24a43ca293e6,v3.7.10.5096")	user	libubnt	wevent.ubnt_custom_event(): EVENT_STA_LEAVE ath3: cc:55:ad:fc:f9:94 / 0
2016-08-29	21:43:04	Information	("U2O,24a43ca293e6,v3.7.10.5096")	daemon	hostapd	ath3: STA cc:55:ad:fc:f9:94 IEEE 802.11: disassociated
2016-08-29	21:43:04	Information	("U2O,24a43ca293e6,v3.7.10.5096")	daemon	hostapd	ath3: STA cc:55:ad:fc:f9:94 IEEE 802.11: sta_stats
2016-08-29	21:41:01	Error	("U2O,24a43ca293e6,v3.7.10.5096")	cron	crond	USER admin pid 22709 cmd syswrapper.sh schedule-action

[UBNT-BenBuckley]

@Amaravati are these logs from before the reboot?  Did you get them from SSH session, or do you have a remote log server set-up?

[Amaravati]

@UBNT-BenBuckley

The above was before and after reboot (so reboot happened somehwer in the middle). Also, we have a syslog on a Synology box. Do you want me to do ssh? (if so...what command pulls the logs?)

Both of the AP went again on reboot just before 10pm. Does that has to do with our timer setting for our guest network? (that should go off at 10pm).

2016-08-30	21:49:57	Warning	("U2O,24a43ca2ad33,feature-busy-env-bjb.2")	user	kernel	[ 83.987000] 13 14 15 16 17 18 19
2016-08-30	21:49:57	Warning	("U2O,24a43ca2ad33,feature-busy-env-bjb.2")	user	kernel	[ 83.986000] valid pRc->validRateIndex :
2016-08-30	21:49:57	Warning	("U2O,24a43ca2ad33,feature-busy-env-bjb.2")	user	kernel	[ 83.986000] vap: 56:a4:3c:a3:ad:33
2016-08-30	21:49:48	Information	("U2O,24a43ca2ad33,feature-busy-env-bjb.2")	daemon	hostapd	ath3: STA cc:55:ad:fc:f9:94 IEEE 802.11: deauthenticated due to local deauth request
2016-08-30	21:49:44	Information	("U2O,24a43ca2ad33,feature-busy-env-bjb.2")	user	libubnt	wevent.ubnt_custom_event(): EVENT_STA_LEAVE ath3: cc:55:ad:fc:f9:94 / 0
2016-08-30	21:49:44	Information	("U2O,24a43ca2ad33,feature-busy-env-bjb.2")	user	libubnt	wevent.ubnt_custom_event(): EVENT_STA_JOIN ath3: cc:55:ad:fc:f9:94 / 1
2016-08-30	21:49:44	Notice	("U2O,24a43ca2ad33,feature-busy-env-bjb.2")	user	syswrapper	[busy] skipping: reload
2016-08-30	21:49:42	Information	("U2O,24a43ca2ad33,feature-busy-env-bjb.2")	daemon	hostapd	ath3: STA cc:55:ad:fc:f9:94 IEEE 802.11: associated
2016-08-30	21:49:42	Warning	("U2O,24a43ca2ad33,feature-busy-env-bjb.2")	user	kernel	[ 69.598000] 13 16 19
2016-08-30	21:49:42	Warning	("U2O,24a43ca2ad33,feature-busy-env-bjb.2")	user	kernel	[ 69.598000] valid pRc->validRateIndex :
2016-08-30	21:49:42	Warning	("U2O,24a43ca2ad33,feature-busy-env-bjb.2")	user	kernel	[ 69.597000] vap: 46:a4:3c:a3:ad:33
2016-08-30	21:49:40	Information	("U2O,24a43ca2ad33,feature-busy-env-bjb.2")	user	syslog	ace_reporter.reporter_set_managed(): [STATE] enter MANAGED
2016-08-30	21:49:40	Notice	("U2O,24a43ca2ad33,feature-busy-env-bjb.2")	user	syswrapper	[state is locked] skipping reload
2016-08-30	21:49:40	Notice	("U2O,24a43ca2ad33,feature-busy-env-bjb.2")	user	syswrapper	[state is locked] skipping reload

[UBNT-BenBuckley]

@Amaravati it's possible that your reboots have to do with your timer.  Will you configure one of your AP's for remote logging per the instructions here:

http://community.ubnt.com/t5/UniFi-Wireless/UniFi-Debug-Methods-for-capturing-useful-debug-informati...

[andris]

Just reporting back now that i've upgraded about 60% of my 50 Unifi to the latest Outdoo+ firmware @UBNT-BenBuckley provided above.  

Looking good so far!  Not seeing the reboots or the "unable to open sock" errors any more.

I'll continue to update this thread as i get to 100% units upgraded.

Thanks again for the support on this @UBNT-BenBuckley

[andris]

@UBNT-Brandon @UBNT-BenBuckley  please see my post here http://community.ubnt.com/t5/UniFi-Wireless-Beta/Questions-on-1st-Gen-Firmware-revert-to-3-7-8-and-n... regarding the 3.7.8 firmware rollback.

Trying to determine how the regression that required the revert to 3.7.8 relates to the "unable to open sock" and "too much interference" issues from this thread.  Since the fixes for that were based on 3.7.9...I think I'll lose them if i revert to 3.7.8....is that correct?