I have upgraded my hotspot (411AR) from 4.12 to 5.5.
Now I am having spontaneous reboots.
It looks lilke they occure, when a download is started, via BT for instance.
So it might be connected with a sudden peak in download traffic. Until now I have no limitations on traffic implemented, no queues.
Any hint, what to do/how to do, to chase down the reason for the reboots ?
/log print entries show reason for reboot.
Actually, I used remote logging. No info about reason of spontaneous boot, which might be understandable.
So, which logging (error, critical ?) to set to “disk”, to get reason of spontaneous boot later on ? I assume, “memory” will not be good enough.
I’m pretty pragmatic this way, but I’d just hook up a computer to the serial port, and use a terminal program that allows you to log sessions to file. That’ll catch everything happening at the time, including the boot process.
Might not be possible depending on the install location, of course.
I’m pretty sure ‘critical’ should cover it, though. That’s what I get console messages for after reboot for ‘improper shutdowns’ when I just pull the plug on lab equipment.
Got one reboot. And what does log print say ?
“01:00:20 system,error,critical router was rebooted without proper shutdown (cause 1)”
Is that good enough for you to have an idea about the real cause ?
Sorry, I do not understand, what you mean. Will not show more than the log file, or am I wrong ?
During my good times as a real time programmer, writing multithreaded device drivers for exotic HW or comms protocols, in Assembler, we already had an OS-module doing a (real) core-dump to disk in case of crash. Which might be because of illegal adrs in kernel mode, or also unexpected power-failure. And after restart a smart utility to interpret system lists etc., to show all active processes, current process at time of crash, open files etc.
Such a tool would be the right one to track such problems down.
Not something similar available for RoS ?
(The OS I was using could handle 2MB main memory max.)
reinerotto, generate support output file from your router and send it to support (support@mikrotik.com),
http://wiki.mikrotik.com/wiki/Support_Output_File
“01:00:20 system,error,critical router was rebooted without proper shutdown (cause 1)”
power outage. this doesn’t look like a software issue. to be sure, you can email the supout.rif file to support and we will see if there were any crashes before this.
It’ll show the boot process, for one thing. As well as anything the OS was unable to write to disk for some reason.
However, like normis said, that looks like a power failure to me.
I have been facing the same problem for sometime in one ap
solution?
it is power issue so, decrease the tx power of the wireless by 2 dbm and see
suggestion?
replace the package of wireless nv2 to wireless only