HELP! New R500 unleashed AP frequent reboots with the reboot reason [watchdog timeout] and [application reboot]

[ian_tsang]

New R500 unleashed AP frequent reboots with the reboot reason [watchdog timeout] and [application reboot].

The APs included member and master AP frequent reboots 3-4 times daily. The WiFi channel will be resumed 5-10 minutes everytime. The below is the updated AP's log. Please help!

Aug  5 16:07:10 ruckus syslog: eventd_to_syslog():AP[PPSH-AP01@e0:10:7f:17:ee:10] joins with uptime [195] s and last disconnected reason [AP Restart : watchdog timeout ] Aug  5 16:07:10 ruckus syslog: eventd_to_syslog():AP[PPSH-AP02@e0:10:7f:17:80:10] joins with uptime [199] s and last disconnected reason [AP Restart : watchdog timeout ] 
Aug  5 16:07:15 ruckus syslog: eventd_to_syslog():AP[PPSH-AP01@e0:10:7f:17:ee:10] warm boot successfully,last reboot reason [watchdog timeout ]. 
Aug  5 16:07:15 ruckus syslog: eventd_to_syslog():AP[PPSH-AP02@e0:10:7f:17:80:10] warm boot successfully,last reboot reason [watchdog timeout ]. 
Aug  5 16:08:18 ruckus syslog: eventd_to_syslog():AP[e0:10:7f:17:80:10] Radio ON 
Aug  5 16:08:18 ruckus syslog: eventd_to_syslog():AP[e0:10:7f:17:80:10] Radio ON 
Aug  5 16:08:33 ruckus syslog: eventd_to_syslog():AP[PPSH-AP04@d4:68:4d:05:ae:10] joins with uptime [55] s and last disconnected reason [AP Restart : application reboot] 
Aug  5 16:08:35 ruckus syslog: eventd_to_syslog():AP[PPSH-AP03@e0:10:7f:17:ae:60] joins with uptime [57] s and last disconnected reason [AP Restart : application reboot] 
Aug  5 16:08:37 ruckus stamgr: stamgr_update_reboot_info():AP[d4:68:4d:05:ae:10] reboot detail:election: rcv the reboot package send by master.   
Aug  5 16:08:37 ruckus syslog: eventd_to_syslog():AP[PPSH-AP04@d4:68:4d:05:ae:10] warm boot successfully,last reboot reason [application reboot]. 
Aug  5 16:08:40 ruckus stamgr: stamgr_update_reboot_info():AP[e0:10:7f:17:ae:60] reboot detail:election: rcv the reboot package send by master.   
Aug  5 16:08:40 ruckus syslog: eventd_to_syslog():AP[PPSH-AP03@e0:10:7f:17:ae:60] warm boot successfully,last reboot reason [application reboot]. 
Aug  5 16:08:55 ruckus syslog: eventd_to_syslog():AP[PPSH-AP01@e0:10:7f:17:ee:10] joins with uptime [60] s and last disconnected reason [AP Restart : application reboot] 
Aug  5 16:08:59 ruckus stamgr: stamgr_update_reboot_info():AP[e0:10:7f:17:ee:10] reboot detail:election: The unleashed network have another master and the priority is less than it, so reboot.   
Aug  5 16:08:59 ruckus syslog: eventd_to_syslog():AP[PPSH-AP01@e0:10:7f:17:ee:10] warm boot successfully,last reboot reason [application reboot]. 
Aug  5 16:09:39 ruckus syslog: eventd_to_syslog():AP[d4:68:4d:05:ae:10] Radio ON 
Aug  5 16:09:39 ruckus syslog: eventd_to_syslog():AP[d4:68:4d:05:ae:10] Radio ON 
Aug  5 16:09:43 ruckus syslog: eventd_to_syslog():AP[e0:10:7f:17:ae:60] Radio ON 
Aug  5 16:09:43 ruckus syslog: eventd_to_syslog():AP[e0:10:7f:17:ae:60] Radio ON 
Aug  5 16:10:02 ruckus syslog: eventd_to_syslog():AP[e0:10:7f:17:ee:10] Radio ON 
Aug  5 16:10:02 ruckus syslog: eventd_to_syslog():AP[e0:10:7f:17:ee:10] Radio ON 

[ian_tsang]

Yes, I have report to Ruckus Support more 10 days ago. But they didn't reply any resolution or suggestion. Their response time is too low as well.

[ian_tsang]

I attached AP's log file for them to investigate.

[michael_brado]

Advice is to upgrade to current Unleashed 200.1.9.12.62, from Admin&Services, Administer, Upgrade page, click upgrade button, when it shows 200.1.9.12.62 click OK.

[saurabh1991]

Watchdog Timeout: system is too busy and causes the rebooting. (Could be a high cpu or memory utilization on AP can cause AP watchdog timeout)

Application Reboot: AP’s daemons reboots the AP. (Internal reason ;  such as AP upgrade ,  receive rebootcommand from ZD, Heartbeat lost, fail to join controller and reboots).

[marco_eichstet1]

Hi Ian,

i have a similar issue with my T300 APs.
Did you get this working in the meanwhile?
I am using Firmware 200.1.9.12.62.

Thanks.
Kind Regards
Marco