MikroTik

I have a two month old RB433AH operating as a hotspot controller. It is running on an UPS so power stability is not in question. Twice now, the routerboard system (running MT v3.1.5) has "halted" and quit processing data. When this happened, WinBox was not able to access the RB433AH from either the WAN side or the Hotspot side.

Power failing and restarting the router brought back normal operation in both cases. The log is erased by the reboot and offers no history. Are others having this problem? Is there a way to generate a history log to view what might be going on here? As of now, it is not possible for me to even guess if it is the software or the new hardware. I do have v3.1.5 running fine on a PC but of course the PC router OS is different from the routerboard version OS.

Suggestions welcome.

Thanks.

Does anyone have an answer?

Should I get an exchange on the hardware?

Is anyone else having the OS on a RB433AH just "stop running" intermittantly?

Thanks!

Set you logging to log to disk vice memory.
Aug

Thanks.. I did find in the log setup the place to save CRITICAL and ERRORS, etc to disk. I set to save critical and errors to disk.

Now.. My routerboard does not actually HAVE a disk so I assume that the logs of critical and error warnings go to flash. Is that right? Do these then appear in the LOG entries following a system failure or somewhere else?

I appreciate the help.

Hah I really need to know this as well. Where to find the log 'on disk' after the reboot? I looked in files and its not there.

You are so right. The unit crashed again this week and I too could not find where the log was stored. I did make a supout file after the reboot (no access was possible following the crash), and sent it to MT. They recommended I update to 3.18 (now 3.19) which I have done. We are all hoping that will fix the problem..

If you set a log entry to save to 'disk' it will save it in flash memory as surmised. Then just open the log normally right after a reboot to see the log entry.

R/

Thom

Now it's working. I set just the warning and error topics to log to disk, and ROS is v3.19 on the RB now and I can see logs before reboot. Nice.