This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Accept
Reject
RUCKUS Self Help |   ASK the Pack
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

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

ian_tsang
New Contributor II

‎08-07-2016 07:42 AM

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 
11 REPLIES 11

michael_brado
Esteemed Contributor II

‎08-08-2016 10:01 AM

That looks like Unleashed (Master) in the msgs, but I have not seen those before.
Please contact Tech Support for further more in depth troubleshooting assistance.

https://support.ruckuswireless.com/contact-us

You might try factory defaulting this AP too, to see if it might clear things up?
0 Kudos

ian_tsang
New Contributor II

‎08-09-2016 12:56 AM

Rebooted again

Aug  9 12:52:17 ruckus syslog: eventd_to_syslog():AP[PPSH-AP03@e0:10:7f:17:ae:60] joins with uptime [191] s and last disconnected reason [AP Restart : application reboot] Aug  9 12:52:18 ruckus syslog: eventd_to_syslog():AP[PPSH-AP04@d4:68:4d:05:ae:10] joins with uptime [194] s and last disconnected reason [AP Restart : application reboot] 
Aug  9 12:52:20 ruckus syslog: eventd_to_syslog():AP[PPSH-AP01@e0:10:7f:17:ee:10] joins with uptime [196] s and last disconnected reason [AP Restart : application reboot] 
Aug  9 12:52:21 ruckus stamgr: stamgr_update_reboot_info():AP[e0:10:7f:17:ae:60] reboot detail:election: rcv the reboot package send by master.   
Aug  9 12:52:21 ruckus syslog: eventd_to_syslog():AP[PPSH-AP03@e0:10:7f:17:ae:60] warm boot successfully,last reboot reason [application reboot]. 
Aug  9 12:52:22 ruckus stamgr: stamgr_update_reboot_info():AP[d4:68:4d:05:ae:10] reboot detail:election: rcv the reboot package send by master.   
Aug  9 12:52:22 ruckus syslog: eventd_to_syslog():AP[PPSH-AP04@d4:68:4d:05:ae:10] warm boot successfully,last reboot reason [application reboot]. 
Aug  9 12:52:25 ruckus stamgr: stamgr_update_reboot_info():AP[e0:10:7f:17:ee:10] reboot detail:election: rcv the reboot package send by master.   
Aug  9 12:52:25 ruckus syslog: eventd_to_syslog():AP[PPSH-AP01@e0:10:7f:17:ee:10] warm boot successfully,last reboot reason [application reboot]. 
Aug  9 12:52:36 ruckus syslog: eventd_to_syslog():AP[PPSH-AP02@e0:10:7f:17:80:10] joins with uptime [215] s and last disconnected reason [AP Restart : watchdog timeout ] 
Aug  9 12:52:42 ruckus syslog: eventd_to_syslog():AP[PPSH-AP02@e0:10:7f:17:80:10] warm boot successfully,last reboot reason [watchdog timeout ]. 
Aug  9 12:53:22 ruckus syslog: eventd_to_syslog():AP[e0:10:7f:17:ae:60] Radio ON 
Aug  9 12:53:22 ruckus syslog: eventd_to_syslog():AP[e0:10:7f:17:ae:60] Radio ON 
Aug  9 12:53:24 ruckus syslog: eventd_to_syslog():AP[d4:68:4d:05:ae:10] Radio ON 
Aug  9 12:53:24 ruckus syslog: eventd_to_syslog():AP[d4:68:4d:05:ae:10] Radio ON 
Aug  9 12:53:26 ruckus syslog: eventd_to_syslog():AP[e0:10:7f:17:ee:10] Radio ON 
Aug  9 12:53:26 ruckus syslog: eventd_to_syslog():AP[e0:10:7f:17:ee:10] Radio ON 
Aug  9 12:53:44 ruckus syslog: eventd_to_syslog():AP[e0:10:7f:17:80:10] Radio ON 
Aug  9 12:53:44 ruckus syslog: eventd_to_syslog():AP[e0:10:7f:17:80:10] Radio ON 
Aug  9 15:52:45 ruckus syslog: eventd_to_syslog():AP[PPSH-AP03@e0:10:7f:17:ae:60] joins with uptime [55] s and last disconnected reason [AP Restart : watchdog timeout ] 
Aug  9 15:52:49 ruckus syslog: eventd_to_syslog():AP[PPSH-AP03@e0:10:7f:17:ae:60] warm boot successfully,last reboot reason [watchdog timeout ]. 
Aug  9 15:53:50 ruckus syslog: eventd_to_syslog():AP[e0:10:7f:17:ae:60] Radio ON 
Aug  9 15:53:50 ruckus syslog: eventd_to_syslog():AP[e0:10:7f:17:ae:60] Radio ON 
0 Kudos

ian_tsang
New Contributor II

‎08-09-2016 09:39 AM

Anyone can tell me what is [application reboot] & [watchdog timeout ]??
0 Kudos

michael_brado
Esteemed Contributor II
In response to ian_tsang

‎08-09-2016 10:20 AM

The Application Reboot says it was due to election issue with the Master AP.

Aug  9 12:52:22 ruckus stamgr:
stamgr_update_reboot_info():AP[d4:68:4d:05:ae:10] reboot
detail:election: rcv the reboot package send by master.   
Aug  9
12:52:22 ruckus syslog:
eventd_to_syslog():AP[PPSH-AP04@d4:68:4d:05:ae:10] warm boot
successfully,last reboot reason [application reboot].

Have you tried Ruckus Tech Support?

I cannot find any existing bugs, they will want your Support Info file for review.
0 Kudos
Copyright © 2024 Khoros, LLC