This morning I issued a “halt” command in a MetaRouter console, and the console responded that the metarouter had halted. However, my Winbox session also then died.
When I logged back into the Mikrotik RB console it said
mar/04/2015 10:33:13 system,error,critical router was rebooted without proper shutdown by watchdog timer
mar/04/2015 10:34:55 system,error,critical router was rebooted without proper shutdown by watchdog timer
(yes, I halted the metarouter twice just to make sure that it was repeatable). I’m running v6.27 on a RB-951G
I recommend that you read all posts from earlier threads; some of the initial posts claimed it only happens if you shutdown the guest, not reboot it, and only if you issue the “halt” command inside the guest instead of issuing a “/metarouter shut-down” command. But it has since been demonstrated that the problem can occur regardless of whether you halt or reboot the guest, and regardless of whether you do this from within the guest or from outside of the guest (by having the host signal the guest to take that action). Sometimes it will happen, and sometimes it will not; it is seemingly random.
I’m having the same problem with MetaRouter. Using an openwrt image, when I do a “reboot” it sometimes causes the entire router to reboot itself due to the watchdog timer. This is on a RB951Ui-2HnD.
Is this something Mikrotik is aware of and working on?
Yes. I have a ticket open with them, and I hear from them every once in a while about it, but it apparently is not an easy problem to solve (like pretty much every other MetaROUTER bug…grrr).
root@OpenWrt:/# poweroff
root@OpenWrt:/# br-lan: port 1(eth0) entering disabled state
device eth0 left promiscuous mode
br-lan: port 1(eth0) entering disabled state
System halted.
Write failed: Broken pipe
???