problem with my routerboard 5009_no save graph after rebooot

Hello all .
I have a problem with my routerboard 5009.

As a special setting has been added for it to restart every day at 4 am.

After the reboot has been set, the graph does not save the data that was present before the reboot and is zeroed.
It only saves data from the moment it restarts and starts recording normally
Until it restarts again the next day. Deletes the previous day and starts recording from the same moment, and so on

There are other types of Mikrotik that do not do this same thing, such as the Routerboard 1100 and CCR.
It also has a restart command, but it saves the previous day’s graph and adds on top of it normally.

I have a suspicion that the problem is in software version 7. But the Routerboard 5009 does not allow you to downgrade the software to version 7.

These pictures illustrate the topic:
Picture No. 1 is the settings for rebooting every day at 4 am.
https://www10.0zz0.com/2023/11/11/06/505845526.png

Picture No. 2 is the graph
The red line shows the location of loss of data that is not saved after adding the settings.
The green line shows what the situation was like before the adjustment.
https://www10.0zz0.com/2023/11/11/06/448142540.png




Are there any suggestions?
What to do?

It could be 5009 specific (i.e. a bug), but anyway: check how frequently graphing data gets stored to flash, it’s under Tools->Graphing->Interface Rules->Graphing Settings … it seems that default is 24 hours, try setting it to shorter interval. This probably won’t make the bug disappear, but you’ll loose less of graphing data due to reboot.

And file bug report with support@mikrotik.com (supout.rif file included), they generally don’t react on forum posts.

apart from that … why on earth are you rebooting daily anyway…

Special settings?
No special setting, it’s _fullshift_™ reboot everyday for no reason.

(Not to mention the gem of the “y” at the end of the script…)

Thank you for your answer ..

I tried this before, but it didn’t work.
It’s a good idea to talk to support. I didn’t know that they don’t usually interact with forums. I’ll write to them.
Thanks again

The idea here is to restart. Sometimes, after long hours of operation, something happens that the routerboard does not respond to some things. I think it is due to the recent release of the Stable system.
Usually in long-term versions we do not need to reboot
It is stable and works well no matter the duration.

But here is the problem: there is no (version 7) Long-term yet

My friend, yes, it is a complete reboot

The letter “y” at the end was one of my attempts to solve the problem. Before I start posting about it here

I have 2 Rb5009 running. Apart from reboot because of upgrade or power loss, they never get rebooted.
Never.