I upgraded to the latest 2.9.39 Mikrotik software and discovered that I can not back up the configuration anymore.
The CPU load of the device will go to 100% and eventually the box will fall off the network (most times the hardware watchdog will reboot it, but not always) as soon as I issue:
export file=backup
If to look into the partial backup file the there are some signs of distress:
what do you mean? if there is a bug, everyone can send it to support. if you are talking about the 30 days limitation, well that is only for configuration assistance or that kind of help. a specific bug report is welcome by anyone.
No. It’s clearly stated in several places and has been stated by Normunds & Co several times here:
This is a user-to-user forum. To get (“guaranteed”) support from MikroTik, you have to write an e-mail to support@mikrotik.com.
Even the 2.9.41 has this issue. I have no much hope for the 2.9.42, but I’ll try it out.
Edit: The 2.9.42 is the same.
What does make this issue so hard to fix?
Or does the MikroTik intend not to fix this at all?
Btw: The “backup” functionality is not a replacement for the “export” as it is not human readable.
If the “backup” can be made human readable then I’ll be happy to drop the use of “export” command.
On 2.9.42 (x86 only) and a full export I see the following weirdness:
/ system console
set FIXME term=“linux” disabled=no
set FIXME term=“linux” disabled=no
set FIXME term=“linux” disabled=no
set FIXME term=“linux” disabled=no
set FIXME term=“linux” disabled=no
set FIXME term=“linux” disabled=no
set FIXME term=“linux” disabled=no
set FIXME term=“linux” disabled=no
The rest looks okay to me… maybe there is something corrupted in the config and it can’t handle it? Or is this only ap roblem on routerboards?
If there is something broken in the configuration then the MikroTik is free to say it and I’ll try to fix it. I can even grant them a permission to access these devices from outside world so they can do all the “magic” by themselves.
Or is this only ap roblem on routerboards?
I see this problem only on RB112. RB153 and RB532 do not have this issue.