RB4011 random reboots

RouterOS General
1

Hi.

I have an RB4011 with routeros v6.46.5. I’m using a 57V power supply and I have a Rapsberry Pi with a POE hat plugged into the eth10. The power supply is connected to a UPS. Everything works as expected, but from time to time the router reboots! The only thing in the logs is “router rebooted without proper shutdown”, there is no support file generated. Initially, I had a 48V power supply, I thought maybe I need more power, but nothing changed. I’ve been monitoring the temperature and it’s at 48C constantly. I’m monitoring it with SNMP every few seconds.

Does anybody has the same problem? Any ideas why this could happen?

Regards

2

Try upgrading the units firmware.
System>routerboard>upgrade.

What voltage is it reporting under system>health?

3

The routerboard firware is upgraded. And I also was monitoring the voltage with SNMP, it is always about 52.7V.

But now I reverted everything back. I powered Raspberry with it's own power supply and Mikrotik is powered with it's factory 24V power supply. I hope that it will work in this configuration. It is so frustrating.

4

A blind shot, a couple of people here on the forum are pretty sure that running the “real” NTP package (i.e. not the SNTP client which is part of the basic bundle, but the ntp package which needs to be installed separately) causes random reboots of hAP ac², which has the same CPU architecture. Do you happen to have it installed?

5

I have an RB450Gx4 (same CPU as in hAP ac²) with “real” NTP package. And I don’t have any random router reboots.

6

Woow, that is a really strange bug. Unfortunately, I don’t have NTP package installed.

7

I have the same issue.
Every xx day the router reboot out of the blue, without any reason.
The log start with “router rebooted without proper shutdown” and there is no support file generated.
As workaround I have disabled the 5GHz and that looks to help.

8

Hm. I’ve seen another two topics, and in one of them the same situation happens with a wireless version.

http://forum.mikrotik.com/t/rb4011-wireless-version-setting-reboot-automatically/126322/1

http://forum.mikrotik.com/t/spontaneous-reboots/137765/1

Regards

9

I can see this on the changelog of the latest release (6.46.6):

wireless - improved 5GHz interface stability on RB4011iGS+5HacQ2HnD and Audience;

10

End users can not detect the cause of the reboot unless they get lucky and manage to make a workaround by guessing what to change in the configuration. Always, if you have a router that is rebooting - contact support@mikrotik.com.

11

I’ve opened a support ticket throuhg the support portal. I’ve been told (twice) to send a supout.rif generated after a reboot but the router does not generate the supout file. I just rebooted it twice, once from console with /system reboot and once through winbox. I have checked in /system watchdog that Automatic Supout is enabled, but the file is not being generated. I’ve updated to 6.46.6, and also no success. I’m so frustrated with mikrotik, I love the ideas and the theorical part, but i hate it when it comes to the reality. I already assumed that it does not perform well enough for relatively big enterprice, I thought, ok, I’ts really cool for home/small office…but I think that I was wrong.

12

If the supout file is not generated automatically, generate it manually ASAP after the reboot and send to support that one. Or you may even schedule a script in the scheduler, start-time=startup, to create the supout file as one of the first things to happen after the reboot:

/system scheduler
add name=supout on-event=“{/system sup-output}” start-time=startup

13

Will that be ok? I’ve been told that the file should be generated by system not by user.

14

There is no way how you could force the system to generate the autosupout.rif, so if it hasn’t generated it a single time, it means that it didn’t notice any event causing the reboot. So this “semi-automated” supout.rif is the maximum you can provide. It’s up to Mikrotik staff to deal with the fact that autosupout.rif is not generated.

I’ve edited my previous post with a tested script.

15

Thanks for your help. I’m waiting for their reply. But firs time I explained them the situation and they basically repeated their message: do a /system reboot and send us the automatically generated file.

They insist that the file should be generated without any human interaction. I guess, there will be some differences.

16

Sure there will be differences. The autosupout.rif one should contain the information related to the crash, but if it is not generated, what can you do.

What does /system watchdog print show?

17

Here is the output:

[admin@GloryHole] > /system watchdog print 
          watch-address: none
         watchdog-timer: yes
  ping-start-after-boot: 5m
           ping-timeout: 1m
       automatic-supout: yes
       auto-send-supout: no
18

OK, that’s the maximum that can be done. If, with this setting, the autosupout.rif is not generated, it means that the reboot was not triggered by the watchdog. I don’t know any other place where to enable/disable autosupout.rif generation.

19

Well the random reboot was not definitely generated by a reboot, but the question is why it was not generated when I manually rebooted it? Very strange. But anyway, thank you very much for your help.

20

I have never seen an autosupout.rif to be generated at every reboot; even if I abruptly disconnect power (and there is a complaint in the log that the device has been rebooted without a proper shutdown after it comes up again), the autosupout.rif is not generated. So I do not understand the requirement of the support team. To me, the fact that autosupout.rif is not generated is an information on its own, saying that the reason of the reboot was not a watchdog bite. So if I were a support team member and had got this information, I would replicate your configuration from the manually created supout.rif on another 4011 of the exact same model, try to generate the same traffic patterns, and see what happens.