B5-lite rebooting with "watchdog reset" in logs but I'm not using Watchdog


#1

Starting today, a B5Lite that has been in service for over a year is randomly rebooting. I have trouble shot it back to the client end radio of a link. Both the client and the AP are running 1.4.6. Both are being powered by a Netonix switch.

When the client radio reboots, it is down for almost exactly 1 minute and the log file shows this:

2018-02-11 16:02:26 (UTC +0000) root: MIMO_EVENT ethernet link up (1000/Full)
2018-02-11 16:02:26 (UTC +0000) root: MIMO_EVENT System time changed… phystats re-sync
2018-02-11 16:02:26 (UTC +0000) syslog: MIMO_EVENT Station, exiting TDWR exclusion
2018-02-11 16:02:26 (UTC +0000) root: MIMO_EVENT ethernet link becomes ready
2018-02-11 16:02:28 (UTC +0000) root: MIMO_EVENT ethernet link up (1000/Full)
2018-02-11 16:02:28 (UTC +0000) root: MIMO_EVENT System time changed… phystats re-sync
2018-02-11 16:02:33 (UTC +0000) root: MIMO_EVENT ethernet vendor id: 0x221622.
2018-02-11 16:02:34 (UTC +0000) root: MIMO_EVENT Shutdown reason: Watchdog Reset
2018-02-11 16:02:36 (UTC +0000) root: MIMO_EVENT Startup reason: Watchdog Reset

I do not have watchdog turned on in either the radio or the switch. I don’t know why I am seeing Watchdog Reset in the logs… The reboots are random. I’ll get 4 or 5 in a 30 minute window and then quiet for a few hours and then another. No traffic spikes, no voltage changes, everything is running on battery systems…

Any insight as to what is causing this reboot?


#2

In regard to sort of similar ‘watchdog’ reboots on a A5 I have been told that the radio has a watchdog functionality build-in that cannot be switched off. It is triggered by lack of memory or cpu issues. How and when exactly I am not aware. In my case it was probably something to do with interference from airplanes approach radar. I swapped frequency and the issue was gone together with the many clients disconnects…


#3

Chadwick,

The watchdog you are referring to is an internal system process that monitors all the other system processes.

It not the same as the Watchdog feature which allows one have the radio reboot if does not get ping response from an IP address configured by the user.

I notice that you did reach out to us, and thanks for the log data you provided. We will analyze this data and let you know our findings.


#4

Looks like we may be having the same problem - pair of B5 Lites put up yesterday.

This is an extract from the log on the AP:

2018-03-17 12:27:47 (UTC +0000) root: MIMO_EVENT System time changed… phystats re-sync
2018-03-17 12:27:58 (UTC +0000) root: MIMO_EVENT CAC_END:Channel:110
2018-03-17 12:28:08 (UTC +0000) root: MIMO_EVENT Wireless associated
2016-01-01 00:00:20 (UTC +0000) root: MIMO_EVENT CAC_START:Channel:110:Time:60s
2016-01-01 00:00:33 (UTC +0000) root: MIMO_EVENT CAC_STOP:Channel:110
2016-01-01 00:00:34 (UTC +0000) root: MIMO_EVENT CAC_START:Channel:110:Time:60s
2016-01-01 00:00:35 (UTC +0000) root: MIMO_EVENT CAC_STOP:Channel:110
2016-01-01 00:00:43 (UTC +0000) root: MIMO_EVENT ethernet link is not ready
2016-01-01 00:00:46 (UTC +0000) root: MIMO_EVENT ethernet link up (1000/Full)
2016-01-01 00:00:47 (UTC +0000) root: MIMO_EVENT ethernet link becomes ready
2016-01-01 00:00:47 (UTC +0000) root: MIMO_EVENT System time changed… phystats re-sync
2016-01-01 00:00:49 (UTC +0000) root: MIMO_EVENT binaryversion=90afb59714e83b80041e9bf58c3ba9765029cc29 build_time=2017-07-04 05:52:41 (UTC +0000) bamboo_build_time_stamp=2017-07-04T05:51:22.004Z bamboo_build_number=9 project=FW-B5207 branch=release/1.4.6
2016-01-01 00:00:49 (UTC +0000) root: MIMO_EVENT ethernet link up (1000/Full)
2016-01-01 00:00:54 (UTC +0000) root: MIMO_EVENT ethernet vendor id: 0x221622.
2016-01-01 00:00:54 (UTC +0000) root: MIMO_EVENT Shutdown reason: Watchdog Reset
2016-01-01 00:00:56 (UTC +0000) root: MIMO_EVENT Startup reason: Watchdog Reset
2018-03-17 16:23:01 (UTC +0000) root: MIMO_EVENT System time changed… phystats re-sync
2018-03-17 16:23:35 (UTC +0000) root: MIMO_EVENT CAC_END:Channel:110
2018-03-17 16:23:47 (UTC +0000) root: MIMO_EVENT Wireless associated

And this is from the Station:

2016-01-01 00:02:16 (UTC +0000) root: MIMO_EVENT Wireless associated
2018-03-17 12:28:43 (UTC +0000) root: MIMO_EVENT System time changed… phystats re-sync
2016-01-01 00:00:23 (UTC +0000) root: MIMO_EVENT Wireless associated
2016-01-01 00:00:36 (UTC +0000) root: MIMO_EVENT ethernet link is not ready
2016-01-01 00:00:39 (UTC +0000) root: MIMO_EVENT ethernet link up (1000/Full)
2016-01-01 00:00:39 (UTC +0000) root: MIMO_EVENT ethernet link becomes ready
2016-01-01 00:00:41 (UTC +0000) root: MIMO_EVENT System time changed… phystats re-sync
2016-01-01 00:00:42 (UTC +0000) root: MIMO_EVENT ethernet link down
2016-01-01 00:00:42 (UTC +0000) root: MIMO_EVENT binaryversion=90afb59714e83b80041e9bf58c3ba9765029cc29 build_time=2017-07-04 05:52:41 (UTC +0000) bamboo_build_time_stamp=2017-07-04T05:51:22.004Z bamboo_build_number=9 project=FW-B5207 branch=release/1.4.6
2016-01-01 00:00:42 (UTC +0000) root: MIMO_EVENT ethernet link up (1000/Full)
2016-01-01 00:00:49 (UTC +0000) root: MIMO_EVENT ethernet vendor id: 0x221622.
2016-01-01 00:00:50 (UTC +0000) root: MIMO_EVENT Shutdown reason: Watchdog Reset
2016-01-01 00:00:40 (UTC +0000) root: MIMO_EVENT ethernet link is not ready
2016-01-01 00:00:43 (UTC +0000) root: MIMO_EVENT ethernet link up (1000/Full)
2016-01-01 00:00:44 (UTC +0000) root: MIMO_EVENT ethernet link becomes ready
2016-01-01 00:00:45 (UTC +0000) root: MIMO_EVENT System time changed… phystats re-sync
2016-01-01 00:00:47 (UTC +0000) root: MIMO_EVENT binaryversion=90afb59714e83b80041e9bf58c3ba9765029cc29 build_time=2017-07-04 05:52:41 (UTC +0000) bamboo_build_time_stamp=2017-07-04T05:51:22.004Z bamboo_build_number=9 project=FW-B5207 branch=release/1.4.6
2016-01-01 00:00:47 (UTC +0000) root: MIMO_EVENT ethernet link down
2016-01-01 00:00:47 (UTC +0000) root: MIMO_EVENT ethernet link up (1000/Full)
2016-01-01 00:00:51 (UTC +0000) root: MIMO_EVENT ethernet vendor id: 0x221622.
2016-01-01 00:00:51 (UTC +0000) root: MIMO_EVENT Shutdown reason: Watchdog Reset
2016-01-01 00:00:52 (UTC +0000) root: MIMO_EVENT Startup reason: Watchdog Reset
2016-01-01 00:02:07 (UTC +0000) root: MIMO_EVENT Wireless associated
2018-03-17 16:24:30 (UTC +0000) root: MIMO_EVENT System time changed… phystats re-sync

The Ping W/dog is turned off.
Both running firmware 1.4.6
Auto-everything is off. 20MHz channel. 10dB Tx Power

Thanks


#5

I have very little experience with setting up my newly purchased B5 Lite system.
My problem is that I have unlocked both units, however when I log on to my access point B5 Lite, using my passwork, it kicks me out after aboutn 10 seconds and I have to re-enter my password to re-access it. What do I have to do where I don’t get sent back to my orange screen where I have to enter my password… also, sometimes it doesn’t recognize my password.
thx
Eddie.


#6

@E11
You probably should start a new thread or contact Mimosa Support. (I would recommend the latter, they will get you all sorted out)


#7

If you haven’t already, please open a support chat as William has recommended! Closing this topic.


#8