When router loses power, the time stays incorrect until I go into settings and click on the time zone again and hit save. I found this out because it set the peak quotas out by a few hours. It happened a few times so its pretty repeatable too - not sure if the degree of error in the displayed time is relative to the time the router remains off or a problem with time zones.
Cheers,
Pen
Incorrect time reported after power failure
Moderator: Moderators
Re: Incorrect time reported after power failure
Happened again today. Router had time of 8:00am then lost power so reconnected and it had time of 4:00am. Had to go into settings and resave the timezone.
-
braveheartleo
- Posts: 47
- Joined: Sun Dec 13, 2009 9:50 am
Re: Incorrect time reported after power failure
This happens in my setup too. I'm using 1.3.3 and I found out that when this problem occurs, ntpclient, which is responsible for correcting the time isn't running.
The time backup restores the date when it last saved so the time is at least somewhere near the current time, depending on how long the router remained offline it might be off by a few minutes or more, when the router powers up and if inet connection is unavailable.
The problem is that ntpclient sometimes starts, then sometimes it doesn't. I notice that when inet connection is unavailable, ex. it can't resolve the timeservers, it doesn't start. But when it is available upon boot then it starts fine, although sometimes after rebooting even while inet is up ntpclient may choose _not_ to start.
If inet is unvailable upon boot because the gateway is down, then goes back up again, without restarting the router, if inet connection does become available ntpclient won't get started. I have to restart it manually at the console, because saving in webif is has some undersirable consequences due to a bug that has been fixed.
Anybody else having this problem?
The time backup restores the date when it last saved so the time is at least somewhere near the current time, depending on how long the router remained offline it might be off by a few minutes or more, when the router powers up and if inet connection is unavailable.
The problem is that ntpclient sometimes starts, then sometimes it doesn't. I notice that when inet connection is unavailable, ex. it can't resolve the timeservers, it doesn't start. But when it is available upon boot then it starts fine, although sometimes after rebooting even while inet is up ntpclient may choose _not_ to start.
If inet is unvailable upon boot because the gateway is down, then goes back up again, without restarting the router, if inet connection does become available ntpclient won't get started. I have to restart it manually at the console, because saving in webif is has some undersirable consequences due to a bug that has been fixed.
Anybody else having this problem?
Re: Incorrect time reported after power failure
Makes sense.
I guess when I restore power to the Modem and Router at same time then the Modem hasn't had a chance to reconnect hence ntpclient cannot resolve timeserver & so ntpclient doesn't start (until i go to settings=> reset the timezone).
I guess when I restore power to the Modem and Router at same time then the Modem hasn't had a chance to reconnect hence ntpclient cannot resolve timeserver & so ntpclient doesn't start (until i go to settings=> reset the timezone).