MikroTik

My newly-deployed ax2 is doing this and I get cuts in traffic which is quite annoying while working remotely and in meetings.

jun/06/2023 12:15:30 system,critical,info cloud change time Jun/06/2023 07:37:42 => Jun/06/2023 12:15:30
jun/06/2023 12:15:31 system,error,critical router rebooted without proper shutdown, probably power outage
jun/06/2023 16:20:09 system,critical,info cloud change time Jun/06/2023 12:16:00 => Jun/06/2023 16:20:09
jun/06/2023 16:20:09 system,error,critical router rebooted without proper shutdown, probably power outage
jun/06/2023 18:10:54 system,critical,info cloud change time Jun/06/2023 16:20:39 => Jun/06/2023 18:10:54
jun/06/2023 23:05:34 system,error,critical login failure for user admin from 192.x.x.x via web
jun/06/2023 18:10:55 system,error,critical router rebooted without proper shutdown, probably power outage
jun/06/2023 21:11:48 system,critical,info cloud change time Jun/06/2023 18:11:24 => Jun/06/2023 21:11:48

Anyone know what is going on?

Disable cloud as time source and configure NTP client.

And check your power source, router should not be rebooting just like that.

The power source is likely more of a problem then the time source

Indeed. But time source is often reason for the log message, used as title of this thread.

It was the first line of my post that I wrote initially. And only added the second line after having a better look at the log excerpt.

Well, maybe read more carefully before reply... he also says "I get cuts in traffic which is quite annoying while working remotely and in meetings".
So it is likely not his power failing, but the ax2 crashing for some reason.

What RouterOS version is it running? has that been updated after purchase?

Doesn't traffic get disrupted on your devices when power is cut ?
How odd ...



If it crashes, it would provide a message about kernel panic or so, I think ? And there should also be autosupout files ?
If it is because of unexpected power loss, it's what is being shown.

But the comment on itself is worthwhile to get more clarification.
Do the traffic cuts correlate with the power loss loggings ?
Or not ?

Doesn't traffic get disrupted on your devices when power is cut ?
How odd ...

When the power gets cut, I notice it for other reasons. So I would first fix that before posting on a forum that my new device has a problem.

Well, maybe read more carefully before reply... he also says "I get cuts in traffic which is quite annoying while working remotely and in meetings".
So it is likely not his power failing, but the ax2 crashing for some reason.

What RouterOS version is it running? has that been updated after purchase?

Its 7.7, not upgraded since purchase. Does any later version fix the NordVPN cert chain issue?

If it was a power issue, wouldn't that also result in traffic cuts? I would experience the same.. Actually I mostly suspected it was simply the power in this "not super-modern" hotel that is probably the cause of that. But really I posted the first line because I'm curious why the time change log after power cut.

Because the device does not have a battery powered clock like most PC/Laptops have.
So it starts again with the last known time it can find (somewhere in the filesystem date of last file, I suppose).
And then, using IP cloud or NTP client, it will correct that time to what it needs to be.

What is actually the problem ?
Traffic cuts because of power problems ? Fix that first.
Again: no power = no traffic unless you have some sort of battery backup setup available.

Or the time changes being reported after those power cuts ? Nothing you can do about that and it will not affect the device functioning after time has been corrected.

Doesn't traffic get disrupted on your devices when power is cut ?
How odd ...

When the power gets cut, I notice it for other reasons. So I would first fix that before posting on a forum that my new device has a problem.

I didn't say there was a fault in the device, I asked if the time change log had a good reason. I said the device was new to indicate that I'm not fully familiar with it yet.
Logically, the crash logs correlate with traffic cuts. I was thinking they were micro-blips in traffic handling but now that I see the log it's clear the system is rebooting. I don't blame the router at all, I'm sure it's the flaky electrical supply. But my question is [primarily] about the time adjustments.

I'll switch to NTP and see if that corrects the corrections heh.

Because the device does not have a battery powered clock like most PC/Laptops have.
So it starts again with the last known time it can find (somewhere in the filesystem date of last file, I suppose).
And then, using IP cloud or NTP client, it will correct that time to what it needs to be.

Yes that's clear. I would understand a change of a few mins. A 5hr shift seems surprising though.. I'm never offline for that long. I will try NTP and see if it's more clear.

Yes that's clear. I would understand a change of a few mins. A 5hr shift seems surprising though.. I'm never offline for that long. I will try NTP and see if it's more clear.

I've seen jumps from 1970 to present (on older devices, not anymore) ... until time is synchronised, no further effort needs to be put in investigating that.
IP Cloud or NTP client will not solve your problem. Just a more accurate timestamp (within milliseconds more accurate, as if you would notice it ...)

Indeed even if time source is NTP, there will also be jumps in time after reboot and log will have entries about those.

But really I posted the first line because I'm curious why the time change log after power cut.

The reason for that is the router does not have a realtime clock chip. Its clock only runs when the device is powered on and running.
At intervals of several hours it writes in a file, and the timestamp of that file is used as the starting point of the clock after a reboot, until the time is synced to an external source.
So this behavior is normal.

Yes that's clear. I would understand a change of a few mins. A 5hr shift seems surprising though.. I'm never offline for that long. I will try NTP and see if it's more clear.

I've seen jumps from 1970 to present (on older devices, not anymore) ... until time is synchronised, no further effort needs to be put in investigating that.
IP Cloud or NTP client will not solve your problem. Just a more accurate timestamp (within milliseconds more accurate, as if you would notice it ...)

Not so old, by default the device, brand new ax2, is set to 1970, I suppose that makes sense initially. Until the time is synchronised the first time, naturally.
Of course this brings up an interesting validation: if you do a 'full reset' and it doens't reset the time to 1970, then it wasn't a full reset heh.

But really I posted the first line because I'm curious why the time change log after power cut.

The reason for that is the router does not have a realtime clock chip. Its clock only runs when the device is powered on and running.
At intervals of several hours it writes in a file, and the timestamp of that file is used as the starting point of the clock after a reboot, until the time is synced to an external source.
So this behavior is normal.

Yeah makes sense. Ok so nothing unusual, just need to find more stable power, heh. THanks