Bug #4459
closed
Tzdata is too old (needs to be updated for Russia)
0%
Description
Time difference is 1h for Russia.
Updated by Taras Savchuk almost 10 years ago
More info:
I have correct time on the dashboard:
Sun Feb 22 22:45:03 MSK 2015
In console i have incorrect timezone (+1h):
[2.2-RELEASE][admin@]/: date
Sun Feb 22 23:44:07 MSK 2015
Same (incorrect) in system/general log:
Feb 22 23:43:06 check_reload_status: Reloading filter
Updated by Dmitriy K almost 10 years ago
I confirm: Incorrect time offset (+1h) everywhere except for dashboard;
Updated by Eugene Parfenov almost 10 years ago
I confirm too: +1h offset in console (dashboard show correct time).
Sun Mar 22 14:45:37 YAKT 2015
Updated by Eugene Parfenov almost 10 years ago
Eugene Parfenov wrote:
I confirm too: +1h offset in console (dashboard show correct time).
[...]
dashboard: Sun Mar 22 13:49:36 YAKT 2015
How to fix it?
There is no make to build latest zoneinfo from iana.
Updated by Chris Buechler over 9 years ago
- Category changed from OpenVPN to Operating System
is the tzdata in FreeBSD 10.1 not correct? We use stock FreeBSD tzdata.
Updated by Dmitriy K over 9 years ago
Chris Buechler wrote:
is the tzdata in FreeBSD 10.1 not correct? We use stock FreeBSD tzdata.
Nope, still only dashboard as correct time. Logs has incorrect time (+1h).
pfsense 2.2.3.
Updated by Chris Buechler over 9 years ago
I mean in stock FreeBSD 10.1, have you checked it?
Updated by Victor Danilkin over 9 years ago
Chris Buechler wrote:
I mean in stock FreeBSD 10.1, have you checked it?
Updated by Chris Buechler over 9 years ago
- Status changed from New to Feedback
- Target version set to 2.2.3
- Affected Version changed from 2.2 to All
zoneinfo has been updated with latest from FreeBSD, should be fine in 2.2.3.
Updated by Dmitriy K over 9 years ago
Looks like the issue has been successfully fixed, thanks Chris