BrightBox Log Gaining 1 Hour per Day

I had previously noticed, and it had been discussed here, that the times in the BrightBox log were randomly gaining an hour cumulatively.

I had assumed that this 1 hour gain occurred every time it resynced with exchange. However, I had been continuously connected for days on end and it still happened.

Upon further examination, I discovered that each 1 hour gain occurred on the daily "anniversary" of the time that it was last rebooted, e.g. I rebooted router at 16:00 on 2 May and at 16:00 on 3 May the times in the log increased by 1 hour, including the log event of the original resync yesterday.

Maybe it has something to do with falsely correcting for Daylight Saving Time every day, but I'm sure I've seen it in the winter. Let you know next Oct!

Note that is not just the times in the log subsequent to the increase event that are increased, but all the times in the log are increased by 1 hour every day at the same time as the BrightBox was originally rebooted.

However the "Time Connected: " in the top Status page is not increased and is always correct.

Hi Xray,

Thanks for raising, I'll have it checked out.

From previous mentions it appears to be that the hour is gained everytime the router resyncs, suggesting there is a bug in the BST and NTP time sync handling.

In reply to a post by MrSaffron:

From previous mentions it appears to be that the hour is gained everytime the router resyncs

That was only mooted by me only previously here and if you read my OP you now see that is not the case. Stop laying red herrings about something you have no personal experience and have only read about on the Net.

Myself and others drew attention to this in the autumn of 2012; as the jumps then were significantly larger.

I think you got involved then; and it was apparently corrected.

However, I have noticed a series of similar but smaller increments in the past two weeks - very rarely look at the SYSTEM Log, hence it possibly has been going on for longer.

I continue to be amazed and disappointed that such a seemingly simple function as keeping track of the correct time is apparently so difficult in this day and age.

Perhaps you should try to get the programmers etc to provide an explanation for publication on this forum?

Hello,

I thought it sounded familiar and it is on the defect list for the next firmware upgrade, and no, I don't have a date.

Overall the last last firmware contained quite a few items that this community requested, so any further thoughts I am quite happy to assess.

Cheers

Yes we have known for ages that this was happening but until now we never knew exactly in what circumstances.

You can even see it happening in realtime by refreshing the log at the same time as you last rebooted.

Does the log show ntp synch events?

Funnily enough, none at last reboot or since.

But have seen them before, probably at re-syncs w/out hard reboot, none of which occurred in this session.

In reply to a post by UKDoc:

Hello,

I thought it sounded familiar and it is on the defect list for the next firmware upgrade, and no, I don't have a date.

Overall the last last firmware contained quite a few items that this community requested, so any further thoughts I am quite happy to assess.

Cheers

The ability to use free DDNS providers like routers on dd-wrt or openwrt firmware would be great.

I hope it can be soon. The bug doesn't just affect the times shown in the system log. It also renders all the scheduling rules in the firewall somewhat useless! As scheduling is a significant and potentially useful feature in the Brightbox for many users, is there any chance that the bug's impact on this feature that would make it a higher priority firmware bug-fix item?