Possible NTP corruption
AmigaDude:
Has anyone experienced strange time entries? Unfortunately I rebooted to straighted it out before I saved anything.
CurrentLocalTime was gibberish, like 1/2031/34938 or some such. The last Call History entry was similar. After the reboot, the CurrentLocalTime is corrected but I still have:
Call History:
Code:
Call 8 02/07/2036 02:21:31
Terminal ID GoogleVoice2 PHONE1
Peer Name +15194328922
Peer Number 15194328922
Direction Inbound Inbound
OBi-Guru:
Seen this in the past, likely due to NTP server not responding in time to the OBi request.
Please upgrade the OBi the latest firmware (1892) - think this problem has been fixed.
AmigaDude:
ThankX,
But I was already running 1892 when I noticed the problem. If it reoccurs I'll make sure that I save as much info as possible. Not a big deal, just a little strange when you see it.
Now that I think about it, I did have my Internet router down for 5-10 minutes. When I brought up the Obi page (just to make sure my Lan was still up) I noticed that SP1/SP2 Service Status was in a DNS NOT Responding state, or something like that. It is possible that a NTP update was trying to occur and got corrupted around the same time.
plugger2:
I was getting the nonsensical date problem under build 1892. It seems it was due to a firewall problem, possibly blocking port 123. In any case, things started becoming more reliable in this regard once I placed the OBi 110 in the DMZ.
There still appears to be a bug with the Local Timezone calculation however... to get my correct local time, which is GMT+10 (Sydney, Australia), I have to enter GMT+9 (Tokyo, Japan). And it's not a DST calculation error, either... this occurs consistently with DST enabled or not. Oh well. Not a biggie for a workaround as far as these things go, but ti would nice to get it fixed at some stage. Don't know if the bug applies to all timezones, or only some.
OBi-Guru:
We confirmed the Time Zone problem for Sydney, and will make the correction on the next firmware update, adding Adelaide as well.
However, for your current setting, given that it is now DST in Sydney, the correct selection for you should be GMT+10 (Sydney) with DST disabled to compensate for 1 hour difference (uncheck the default DST-enable parameter).
Navigation
[0] Message Index
[#] Next page