Random AP R510 reboots - [application reboot]

[harry_incs]

Ruckus R510 AP reboots randomly.

I have 6 AP's in the network and only this one reboots. 
I have checked the switch that it is connected to and there are no problems with connectivity. There are also 2 PoE cameras connected to it and they do not drop any video or reboot. Network is all cabled with CAT6e and exhibits very low latency.

Below i posted some logs and the only clue might be a conflict with the Master AP. I have manually set the Preferred Master to be one of the R610's. I have also searched the forums for other clues but nothing comes up for [application reboot] errors that offers any clues. Documentation is also lacking with explanation. 

--------------------------------------------------------------



May 28 04:51:01 Incs-Ruckus-Unleashed syslog: eventd_to_syslog():AP[Shed-R510@60:d0:2c:29:ce:90] joins with uptime [75] s and last disconnected reason [AP Restart : application reboot] 
May 28 04:51:01 Incs-Ruckus-Unleashed stamgr: stamgr_update_reboot_info():AP[60:d0:2c:29:ce:90] reboot detail:/usr/sbin/election  election: The unleashed network have another master and the priority is less than it, reboot.  
May 28 04:51:01 Incs-Ruckus-Unleashed syslog: eventd_to_syslog():AP[Shed-R510@60:d0:2c:29:ce:90] warm boot successfully,last reboot reason [application reboot]. 
May 28 04:52:04 Incs-Ruckus-Unleashed syslog: eventd_to_syslog():Radio [2.4G] of AP[Shed-R510@60:d0:2c:29:ce:90] is ON 
May 28 04:52:04 Incs-Ruckus-Unleashed syslog: eventd_to_syslog():Radio [5G] of AP[Shed-R510@60:d0:2c:29:ce:90] is ON 
May 28 10:33:30 Incs-Ruckus-Unleashed syslog: eventd_to_syslog():AP[Shed-R510@60:d0:2c:29:ce:90] joins with uptime [80] s and last disconnected reason [AP Restart : application reboot] 
May 28 10:33:31 Incs-Ruckus-Unleashed stamgr: stamgr_update_reboot_info():AP[60:d0:2c:29:ce:90] reboot detail:/usr/sbin/election  election: The unleashed network have another master and the priority is less than it, reboot.  
May 28 10:33:31 Incs-Ruckus-Unleashed syslog: eventd_to_syslog():AP[Shed-R510@60:d0:2c:29:ce:90] warm boot successfully,last reboot reason [application reboot]. 
May 28 10:34:33 Incs-Ruckus-Unleashed syslog: eventd_to_syslog():Radio [2.4G] of AP[Shed-R510@60:d0:2c:29:ce:90] is ON 
May 28 10:34:33 Incs-Ruckus-Unleashed syslog: eventd_to_syslog():Radio [5G] of AP[Shed-R510@60:d0:2c:29:ce:90] is ON 
May 28 11:22:27 Incs-Ruckus-Unleashed syslog: eventd_to_syslog():AP[Shed-R510@60:d0:2c:29:ce:90] joins with uptime [76] s and last disconnected reason [AP Restart : application reboot] 
May 28 11:22:29 Incs-Ruckus-Unleashed stamgr: stamgr_update_reboot_info():AP[60:d0:2c:29:ce:90] reboot detail:/usr/sbin/election  election: The unleashed network have another master and the priority is less than it, reboot.  
May 28 11:22:29 Incs-Ruckus-Unleashed syslog: eventd_to_syslog():AP[Shed-R510@60:d0:2c:29:ce:90] warm boot successfully,last reboot reason [application reboot]. 
May 28 11:23:31 Incs-Ruckus-Unleashed syslog: eventd_to_syslog():Radio [2.4G] of AP[Shed-R510@60:d0:2c:29:ce:90] is ON 
May 28 11:23:31 Incs-Ruckus-Unleashed syslog: eventd_to_syslog():Radio [5G] of AP[Shed-R510@60:d0:2c:29:ce:90] is ON 

---------------------------------------
---------------------------------------

2020/05/28  11:23:31
High
Radio [5G] of AP[Shed-R510@60:d0:2c:29:ce:90] is ON
2020/05/28  11:23:31
High
Radio [2.4G] of AP[Shed-R510@60:d0:2c:29:ce:90] is ON
2020/05/28  11:22:29
High
AP[Shed-R510@60:d0:2c:29:ce:90] warm boot successfully,last reboot reason [application reboot].
2020/05/28  11:22:27
High
AP[Shed-R510@60:d0:2c:29:ce:90] joins with uptime [76] s and last disconnected reason [AP Restart : application reboot]
2020/05/28  10:34:33
High
Radio [5G] of AP[Shed-R510@60:d0:2c:29:ce:90] is ON
2020/05/28  10:34:33
High
Radio [2.4G] of AP[Shed-R510@60:d0:2c:29:ce:90] is ON
2020/05/28  10:33:31
High
AP[Shed-R510@60:d0:2c:29:ce:90] warm boot successfully,last reboot reason [application reboot].
2020/05/28  10:33:30
High
AP[Shed-R510@60:d0:2c:29:ce:90] joins with uptime [80] s and last disconnected reason [AP Restart : application reboot]
2020/05/28  04:52:04
High
Radio [5G] of AP[Shed-R510@60:d0:2c:29:ce:90] is ON
2020/05/28  04:52:04
High
Radio [2.4G] of AP[Shed-R510@60:d0:2c:29:ce:90] is ON

---------------------------------------
---------------------------------------

2020/05/28  11:23:31
High
Radio [5G] of AP[Shed-R510@60:d0:2c:29:ce:90] is ON
2020/05/28  11:23:31
High
Radio [2.4G] of AP[Shed-R510@60:d0:2c:29:ce:90] is ON
2020/05/28  11:22:27
High
AP[Shed-R510@60:d0:2c:29:ce:90] joins with uptime [76] s and last disconnected reason [AP Restart : application reboot]
2020/05/28  10:33:30
High
AP[Shed-R510@60:d0:2c:29:ce:90] joins with uptime [80] s and last disconnected reason [AP Restart : application reboot]
2020/05/28  04:51:00
High
AP[Shed-R510@60:d0:2c:29:ce:90] joins with uptime [75] s and last disconnected reason [AP Restart : application reboot]
2020/05/27  21:37:28
High
AP[Shed-R510@60:d0:2c:29:ce:90] joins with uptime [79] s and last disconnected reason [AP Restart : application reboot]
2020/05/27  16:40:08
High
AP[Shed-R510@60:d0:2c:29:ce:90] joins with uptime [177] s and last disconnected reason [Heartbeat Loss]

[steve_parsons]

I have this issue as well with an R510....

[jimjob77]

I have the same issue as well -- only affects the single  H510 i have ion the network running the latest unleashed firmware, all other R500s have no issue. 

[sanjay_kumar]

Hi @jimjob77 
It is best to open the support case and provide us the AP support file so that we can see the reboot history and signature.
AP support log right after the AP reboot will help us a lot.