Morten,
Adding TIME_ZONE in nav.conf fixed the problem. Thank you very much for your help
Regards, Adrian
On Wed, 04 Jan 2012 09:18:36 -0600 Adrian Bucuricabucurica@iit.edu wrote:
We've just started to test NAV and I have a strange problem with the timezone reported in NAV. It seems that NAV reports all operations using timezone GMT+1 (Western Europe) but on localhost we have configured a different timezone:
diff -s /etc/localtime /usr/share/zoneinfo/`cat /etc/timezone` Files /etc/localtime and /usr/share/zoneinfo/America/Chicago are identical
You're quite right. This was once an issue we "fixed" and forgot about. Wherever NAV uses Django to create timestamps, it is subject to Django's TIME_ZONE setting, which in NAV defaults to 'Europe/Oslo'.
I've looked into it now, and NAV's Django settings will set TIME_ZONE from the corresponding value in nav.conf; the problem is that nav.conf has never been updated from our side to reflect that TIME_ZONE is an available option.
I suggest you try to add a TIME_ZONE option in your nav.conf, then restart NAV and Apache.
I will add some comments about TIME_ZONE to the nav.conf distributed with NAV. I think maybe a future improvement would also be for NAV to look at /etc/timezone if it exists.