What's new

RT-N66U -380.69_2 (legacy) - Time keeps going out

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Bill Venables

New Around Here
After installing this version, at midnight the date changes to August 1st. I have set the router to reboot at 3.00 am and this sorts out the problem until midnight the following day. Any ideas what is causing this? Not sure when the next release is due but maybe this will sort it?
 
Are you sure it's changing at midnight? It sounds more like your reboot at 03:00 is causing it. The reboot will cause the date to reset until the router has had a chance to re-sync with the NTP servers.
 
Thanks for the helpful advice. I hadn't appreciated that when the router reboots, the time is lost. So midnight was probably three.
 
Systemlog entries are always in chronological order so even if you notice a timestamp issue, you know that it was issued between its surrounding correctly timed commands.

If the large descrepency bothers you then on a scheduled reboot this could close the gap significantly

1)to save the time into a file
2)soft reboot
3) zero the time with the time in the file instead of instead of epoch time
4) delete the file immediately after so the time doesn't backdate on any unexpected power cycle

(It will still be offset for however long the reboot takes to complete until next ntp update)

--

OR

Check system log after bootup for ntp descrepency notifications.

Rewrite system log updating all epoch times according to discrepancy found so they are all correct.
 
Similar threads
Thread starter Title Forum Replies Date
M Missing ethctl on 380.70 Asuswrt-Merlin 3

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top