topic Re: HELP! New R500 unleashed AP frequent reboots with the reboot reason [watchdog timeout] and [application reboot] in Community and Online Support Services

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

ian_tsang — Sun, 07 Aug 2016 14:42:58 GMT

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

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

michael_brado — Mon, 08 Aug 2016 17:01:40 GMT

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?

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

ian_tsang — Tue, 09 Aug 2016 07:56:43 GMT

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

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

ian_tsang — Tue, 09 Aug 2016 16:39:13 GMT

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

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

michael_brado — Tue, 09 Aug 2016 17:20:19 GMT

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.

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

ian_tsang — Tue, 09 Aug 2016 17:27:28 GMT

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.

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

ian_tsang — Tue, 09 Aug 2016 17:32:19 GMT

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

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

michael_brado — Wed, 10 Aug 2016 18:24:38 GMT

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.

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

marco_eichstet1 — Tue, 04 Oct 2016 14:59:58 GMT

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

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

michael_brado — Tue, 04 Oct 2016 20:06:09 GMT

Announcing: Ruckus Unleashed 200.2.9.13.186 is now Live

https://forums.ruckuswireless.com/ruckuswireless/topics/announcement-ruckus-unleashed-200-2-ga-is-no...

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

jakob_peterh_ns — Mon, 05 Mar 2018 20:57:55 GMT

I have just seen this issue on Unleashed 200.5.10.0.291
And I only have one AP at hope for testing from my employer - any reason for this?

Just saw it two times within 20 min.

Unleashed App says: AP Restart: Application Reboot.
What's happening, and how can I retain debug logs during reboots?

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

saurabh1991 — Mon, 28 Aug 2023 11:18:02 GMT

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).