Page 1 of 1

Graphs off by 5 hours after v2.1 upgrade ** solved

Posted: Wed Mar 12, 2008 5:00 am
by cbhiii
Hi,

I upgraded to v2.1 and now all of my graphs readings are plotting ahead 5 hours.

For instance the 2pm (1400) data is showing up at 7pm (1900) on all of my graphs.

How do I fix this?

http://weather.huffman.info/ Image

Re:Graphs off by 5 hours after v2.1 upgrade

Posted: Wed Mar 12, 2008 11:30 am
by skyewright
cbhiii wrote: I upgraded to v2.1 and now all of my graphs readings are plotting ahead 5 hours.
Do graphs with recent time ranges look right?

If so, did you need to reset your timezone after the upgrade? I did.

If so, could there have been a time frame during which meteohub thought it was 5 hours away (e.g. in Europe?).

Just a thought...

Re:Graphs off by 5 hours after v2.1 upgrade

Posted: Wed Mar 12, 2008 2:12 pm
by cbhiii
After the upgrade I had to reset everything. My timezone, timeservers, clock, etc.

The upgrade only took me an hour or so but all of yesterday's data was off by 5 hours and not just the data during the upgrade.

I will watch it more closely today.

Re:Graphs off by 5 hours after v2.1 upgrade

Posted: Wed Mar 12, 2008 3:43 pm
by cbhiii
It appears that my data after the upgrade is being collected and displaying correctly, but all data before the upgrade is now wrong and useless.

Re:Graphs off by 5 hours after v2.1 upgrade

Posted: Wed Mar 12, 2008 8:29 pm
by admin
not sure what really happens here.

1. Please try to press \"save\" on the settings page (this makes sure that the \"use local timezone\" switch is stored into the config files).

2. Then press \"recompute\" on the maintenance page and wait about 20 min until finished.

Is the problem then still there?

Re:Graphs off by 5 hours after v2.1 upgrade

Posted: Thu Mar 13, 2008 3:32 pm
by cbhiii
No change. It seems to be only that day's data so I will just ignore it. Current data is being displayed correctly.

Re:Graphs off by 5 hours after v2.1 upgrade

Posted: Sat Mar 15, 2008 4:07 am
by cbhiii
I found out what happened (I think). After the upgrade my Meteohub did a NTP update with the timezone wrong and it changed my clock by 18005 seconds. That moved my data I believe.

My current timezone and clock update are set properly so this shouldn't happen again (until v2.2 :laugh:)