Incorrect date/time in system log

[Nicklas]

Hi,

On both of my routers RT-AC87U and RT-AC3200, the date and time in the system log is incorrect. I've tried different ntp servers. But alwas after a while or after rebooting new log events appears in the log with incorrect date/time stamp. Seems like many of the services is logging incorrect date/time. Then other events (clients logging in and such, dchcp lease to clients etc.) is getting the correct time.

See attached image. Incorrect date/ime Aug 1. Correct time Jun 6.

 

[martinr]

Have you searched the forum for similar posts? Have a look here, for example (I ran a Google seach rather than using the forum's search tool):

https://www.snbforums.com/threads/rt-ac5300-wrong-time-and-date-when-rebooted.33731/#post-320423

 

[Nicklas]

Have you searched the forum for similar posts? Have a look here, for example (I ran a Google seach rather than using the forum's search tool):

https://www.snbforums.com/threads/rt-ac5300-wrong-time-and-date-when-rebooted.33731/#post-320423

Hi,

Thanks!

That's obviously the reason behind the incorrect timestamps during reboot. It seems like the ntp server is working ok, so during reboot, the router is loosing the correct date/time and without the help of an internal RTC, the services is not able to log a correct date/time after reboot, but before the ntp service has got the correct date/time.

Regards

Nicklas

 

[martinr]

Yes, at the start of reboot, understandably, there's an incorrect time/date, but you wrote, "But always after a while or after rebooting..". I took "always after a while" to mean that for no obvious reason, and after working perfectly, the time/date drifts to some incorrect setting. Is that not the case?

 

[Nicklas]

It's hard to really know when certain evens occur, when the date/time is incorrect. But now I think that the incorrect timestamps originates from events just after reboot, but before ntp service is able to set correct date/time.

At first I thought that some of the events occured without reboot, but know I am pretty sure that they occur just after a reboot.

I think it's quite shirtty hardware on many consumer routers, despite that they cost 220$ or more. Now, with more facts on hand, I would have spent a little more many and built something with a pfsense box, a switch and one or two (wired) wireless access points.

 

[thelonelycoder]

It's hard to really know when certain evens occur, when the date/time is incorrect. But now I think that the incorrect timestamps originates from events just after reboot, but before ntp service is able to set correct date/time.

At first I thought that some of the events occured without reboot, but know I am pretty sure that they occur just after a reboot.

I think it's quite shirtty hardware on many consumer routers, despite that they cost 220$ or more. Now, with more facts on hand, I would have spent a little more many and built something with a pfsense box, a switch and one or two (wired) wireless access points.

What does it matter, it's justbthe first few minutes if at all, then as soon as the WAN is up, the time is syncronized and all is well from then on.
Many of the mandatory internet connected devices have no hardware clock built in. It's a cost factor and needs a replacable battery to work.

 

[Nicklas]

What does it matter, it's justbthe first few minutes if at all, then as soon as the WAN is up, the time is syncronized and all is well from then on.
Many of the mandatory internet connected devices have no hardware clock built in. It's a cost factor and needs a replacable battery to work.

Yes, I know. But 256mb RAM, jffs area about 60mb or less. Very small nvram, for ex. unable to hold larger certificates. As the first release of Raspberry PI at best. It seems that the juice is mostly focused on the wifi and ethernet controllers and MIMO or <x>-band technology, power consumtion, noice-level etc.

And then I am sorry to say, we have these EU regulation shirt, indirectly crippling the wireless performance. Seems like most routers in my area is fighting for the few channels available on the 5ghz band. Some of them with a more permissive setting of the tx power, than Asus now have on their latest routers and firmware. US and many others seems to accept much more channels.

 

[thelonelycoder]

Yes, I know. But 256mb RAM, jffs area about 60mb or less. Very small nvram, for ex. unable to hold larger certificates. As the first release of Raspberry PI at best. It seems that the juice is mostly focused on the wifi and ethernet controllers and MIMO or <x>-band technology, power consumtion, noice-level etc.

And then I am sorry to say, we have these EU regulation shirt, indirectly crippling the wireless performance. Seems like most routers in my area is fighting for the few channels available on the 5ghz band. Some of them with a more permissive setting of the tx power, than Asus now have on their latest routers and firmware. US and many others seems to accept much more channels.

The EU has nothing to do with your problem, it's how things are here, so don't bring it up.
The Asus consumer grade routers have no HW clock. Buy professional grade then if you're not happy.
As a consumer level user, I'm very happy with what I've got.

 

[sfx2000]

On both of my routers RT-AC87U and RT-AC3200, the date and time in the system log is incorrect. I've tried different ntp servers. But alwas after a while or after rebooting new log events appears in the log with incorrect date/time stamp.

There's no real-time clock in the RT's - so on startup (or reboot), it'll default to a data/time stamp in the code until NTP is up and running...

Known issue, and not much to worry about - in some ways, it does make debug a bit easier when the router goes back to the future