Prepare crash - spontaneous reboot - B5 Lite


#1

Our main link has suffered a couple of apparent reboots. Had been very stable until now.
Any clues as to what is happening? Extract from logs copied below
Thanks

2017-03-05 21:38:39 (UTC +0000) root: MIMO_EVENT Prepare died, restarting …
2017-03-05 21:38:39 (UTC +0000) root: MIMO_EVENT Prepare crash:
2017-03-05 21:39:39 (UTC +0000) root: MIMO_EVENT Prepare died, restarting …
2017-03-05 21:39:39 (UTC +0000) root: MIMO_EVENT Prepare crash:
2017-03-05 21:40:39 (UTC +0000) root: MIMO_EVENT Prepare died, restarting …
2017-03-05 21:40:40 (UTC +0000) root: MIMO_EVENT Prepare crash:
2017-03-05 21:41:40 (UTC +0000) root: MIMO_EVENT Prepare died, restarting …
2017-03-05 21:41:40 (UTC +0000) root: MIMO_EVENT Prepare crash:
2017-03-05 21:42:40 (UTC +0000) root: MIMO_EVENT Prepare died, restarting …
2017-03-05 21:42:40 (UTC +0000) root: MIMO_EVENT Prepare crash:
2017-03-05 21:43:40 (UTC +0000) root: MIMO_EVENT Prepare died, restarting …
2017-03-05 21:43:40 (UTC +0000) root: MIMO_EVENT Prepare crash:
2017-03-05 21:44:41 (UTC +0000) root: MIMO_EVENT Prepare died, restarting …
2017-03-05 21:44:41 (UTC +0000) root: MIMO_EVENT Prepare crash:
2017-03-05 21:45:41 (UTC +0000) root: MIMO_EVENT Prepare died, restarting …
2017-03-05 21:45:41 (UTC +0000) root: MIMO_EVENT Prepare crash:
2017-03-05 21:46:41 (UTC +0000) root: MIMO_EVENT Prepare died, restarting …
2017-03-05 21:46:41 (UTC +0000) root: MIMO_EVENT Prepare crash:
2017-03-05 21:47:41 (UTC +0000) root: MIMO_EVENT Prepare died, restarting …
2017-03-05 21:47:41 (UTC +0000) root: MIMO_EVENT Prepare crash:
2017-03-05 21:48:41 (UTC +0000) root: MIMO_EVENT Prepare died, restarting …
2017-03-05 21:48:42 (UTC +0000) root: MIMO_EVENT Prepare crash:
2017-03-05 21:49:42 (UTC +0000) root: MIMO_EVENT Prepare died, restarting …
2017-03-05 21:49:42 (UTC +0000) root: MIMO_EVENT Prepare crash:
2017-03-05 21:50:42 (UTC +0000) root: MIMO_EVENT Prepare died, restarting …
2017-03-05 21:50:42 (UTC +0000) root: MIMO_EVENT Prepare crash:
2017-03-05 21:51:42 (UTC +0000) root: MIMO_EVENT Prepare died, restarting …
2017-03-05 21:51:43 (UTC +0000) root: MIMO_EVENT Prepare crash:
2017-03-05 21:52:43 (UTC +0000) root: MIMO_EVENT Prepare died, restarting …
2017-03-05 21:52:43 (UTC +0000) root: MIMO_EVENT Prepare crash:
2017-03-05 21:53:43 (UTC +0000) root: MIMO_EVENT Prepare died, restarting …
2017-03-05 21:53:43 (UTC +0000) root: MIMO_EVENT Prepare crash:
2016-01-01 00:00:20 (UTC +0000) root: MIMO_EVENT CAC_START:Channel:140:Time:60s
2016-01-01 00:00:25 (UTC +0000) root: MIMO_EVENT CAC_STOP:Channel:140
2016-01-01 00:00:25 (UTC +0000) root: MIMO_EVENT CAC_START:Channel:140:Time:60s
2016-01-01 00:00:26 (UTC +0000) root: MIMO_EVENT CAC_STOP:Channel:140
2016-01-01 00:00:35 (UTC +0000) root: MIMO_EVENT ethernet link is not ready
2016-01-01 00:00:38 (UTC +0000) root: MIMO_EVENT System time changed… phystats re-sync
2016-01-01 00:00:39 (UTC +0000) root: MIMO_EVENT binaryversion=90afb59714e83b80041e9bf58c3ba9765029cc29 build_time=2016-07-20 16:38:40 (UTC +0000) bamboo_build_time_stamp=2016-07-20T16:28:33.779Z bamboo_build_number=3 project=FW-B5164 branch=release/1.4.1
2016-01-01 00:00:46 (UTC +0000) root: MIMO_EVENT ethernet link up (1000/Full)
2016-01-01 00:00:46 (UTC +0000) root: MIMO_EVENT ethernet link becomes ready
2016-01-01 00:00:46 (UTC +0000) root: MIMO_EVENT ethernet vendor id: 0x221622.
2016-01-01 00:00:46 (UTC +0000) root: MIMO_EVENT Shutdown reason: Reboot by a SW User Process - prepare cannot be rescued
2016-01-01 00:00:47 (UTC +0000) root: MIMO_EVENT Startup reason: Reboot by a SW User Process - prepare cannot be rescued
2016-01-01 00:01:26 (UTC +0000) root: MIMO_EVENT CAC_END:Channel:140
2016-01-01 00:01:31 (UTC +0000) root: MIMO_EVENT Wireless associated
2017-03-05 21:56:13 (UTC +0000) root: MIMO_EVENT System time changed… phystats re-sync
2017-03-05 21:56:15 (UTC +0000) root: MIMO_EVENT System time changed… phystats re-sync


#2

Hi Chris,

We fixed a null pointer error in firmware 1.4.4 that can lead this symptom in firmware 1.4.1. Please install the latest version, and then let Mimosa Support know if you continue to see this error - either through Chat (fastest) or email. They will ask for the full support logs (.tar files) which contain additional details about the crash including the stack trace.


#3

Thanks Chris.
Firmware upgraded. Hopefully that will fix it.
Chris