Hi, for the first time I got this error, the router didn’t restart itself to try to correct the problem, as result it was reachable but no t functional (WiFi not working, cause Capsman non configured).
The problem abbeared during daily restart, panned at 6:00, as ou see it appeared after few minutes.
WHat can it be? Maybe NVram failing? Should I be careful for the future? Thanks
RB941-2nD, about 1,5 years old
It appears that this message suggests that you contact MikroTik. Did you do that?
I have not seen this particular message before, but I have noticed that things can fail when you rename the wireless interface(s) to something else.
So, do not change the wlan1 or wlan2 name. It does not seem to matter for virtual wireless interfaces, so I name those like wlan1-xxxxx when wlan1 is the parent.
no it just happened, no changes before, the router rebooted by schedule this morning, I’ve noticed no wifi then this in the log, I’ve rebooted without changes and it worked. Shoudl I be afraid for the future? Why watchdog didn’t restart the board?
It appears that this message suggests that you contact MikroTik. Did you do that?
No I haven’t, should I? It appears really generic, how they can help me?
Why reboot?
I have core routers running for years, rebooted just for upgrade the RouterOS (6.44.6 → 6.46.8 → 6.47.10 → 6.48.6)
If you have some needs that requere reboot, probably you do that on wrong way… for sure…
About the specific problem,
what script your device run on start?
The RB941-2nD (hAP lite) probably is the worst routerboard ever created, the file space is full???
I reboot on shedule every day, to avoid any posible problem, but if it’s risky I’ll do it once a week
The platform mayb the worst one, but worked ok tilllast update to 6.49.4, two days ago..
Export script config and netinstall long-term 6.48.6 with only the strict package needed, not the single full package
Do not export and reimport .backup
I have no idea what a script is for Mikrotik, it’s the first time I hear about that. On the file I have the following, and I’ve only created the backup one
You have autosupout.rif file … likely created when ROS state was weird. So you can open support ticket and send them the file for analysis. They might find something out.
thanks, if it will happen again I’ll send them this file