Device reboot in strange way

Hi, have encountered a strage reboot from the device. It seems that ETH port goes up and down… and the system seems to restart

the logs are here down…


0000-01-01 00:00:08 (UTC +0000) root: 2016-06-16 16:13:10 (UTC +0000) root: 0000-01-01 00:00:08 (UTC +0000) root: 2016-06-16 16:11:55 (UTC +0000) watchcat[2706]: MIMO_EVENT Shutdown reason: Too many retries to restart a daemon - Cannot rescue hostapd
2015-01-01 00:00:02 (UTC +0000) root: MIMO_EVENT no GPS signal for 3 seconds
2016-06-21 10:27:21 (UTC +0000) root: MIMO_EVENT GPS signal recovered
2016-06-21 10:27:39 (UTC +0000) root: MIMO_EVENT System time changed… phystats re-sync
2016-06-21 10:27:44 (UTC +0000) root: 0000-01-01 00:00:08 (UTC +0000) root: 2016-06-16 16:13:10 (UTC +0000) root: 0000-01-01 00:00:08 (UTC +0000) root: 2016-06-16 16:11:55 (UTC +0000) watchcat[2706]: MIMO_EVENT Shutdown reason: Too many retries to restart a daemon -
2016-06-21 10:27:59 (UTC +0000) root: MIMO_EVENT ethernet link is not ready
2016-06-21 10:27:59 (UTC +0000) root: MIMO_EVENT Startup reason: Power On Reset
2016-06-21 10:28:00 (UTC +0000) syslog: MIMO_EVENT Station, exiting TDWR exclusion
2016-06-21 10:28:00 (UTC +0000) root: MIMO_EVENT Wireless associated


Hi Thesok,

Please go to Diagnostics > Logs > Support Info > click the blue Support Files button to download a .tar file from each radio to your local computer, and then email the files to support@mimosa.co.

This message means that a process stopped, the system could not restart it, and the radio rebooted to recover itself: “MIMO_EVENT Shutdown reason: Too many retries to restart a daemon - Cannot rescue hostapd.”

The detailed logs will tell us why, and depending on the reason and firmware version, we may have already solved it. Please send the logs and we will let you know.

1 Like

What was the fix? I’m having TDWR problems as well. This radio is 66 miles from the closest Doppler and is facing a different direction.

Hi Alan,

After receiving the support logs, we traced the problem above ("…Cannot rescue hostapd") to a firmware bug that was fixed in the version 1.4.1 release. The TDWR line in the file above is displayed on every bootup before association. It is normal to see that (not an error), and it is completely unrelated.

Please email your support logs (.tar files) to support and they will diagnose the problem for you.

1 Like

Hello, I have the same problem i think, I don’t know how to fix it.
Can anyone help me? I have 1.5.0 version
Thank you

2017-01-01 00:00:01 (UTC +0000) root: MIMO_EVENT no GPS signal for 3 seconds
2019-01-21 05:37:22 (UTC +0000) root: MIMO_EVENT GPS signal recovered
2019-01-21 05:37:49 (UTC +0000) root: MIMO_EVENT Wireless associated
2019-01-21 05:37:51 (UTC +0000) root: MIMO_EVENT Startup reason: Non-Responsive System
2019-01-21 05:38:00 (UTC +0000) root: MIMO_EVENT ethernet link is not ready
2019-01-21 05:38:05 (UTC +0000) root: MIMO_EVENT ethernet link up (1000/Full)
2019-01-21 05:38:08 (UTC +0000) root: MIMO_EVENT binaryversion=90afb59714e83b80041e9bf58c3ba9765029cc29 build_time=2018-04-18 17:53:23 (UTC +0000) bamboo_build_time_stamp=2018-04-18T17:52:39.645Z bamboo_build_number=3 project=FWREL-REL4 branch=release/1.5.0
2019-01-21 05:38:15 (UTC +0000) root: MIMO_EVENT ethernet vendor id: 0x221622.
2019-01-21 05:38:17 (UTC +0000) root: MIMO_EVENT Startup reason: Non-Responsive Systemstrong text

Hi @Jota

This thread is very old and would be better if you created a new one. Regardless of that, I might have a fix for you. Give me some time and I’ll see what I can do.

1 Like

It will be great. Thank you.

Hey have you figured this problem out, we seem to encounter it and looking for a fix.

Thanks , we can be reached at yhbb.yhgov.net

Firmware - 2.5.2

This thread is old, I am closing it. If you are experiencing similar issues please start a new thread and link to this one.