Graphite

Current time of displayed graph incorrect

Asked by auxbuss

I'm in the UK. I have a VM in the US (in NYC) on which I run graphite/carbon/whisper. The server timezone is set to Europe/London. Locale data is all GB. Everything works fine with respect to dates and times on other services, e.g. jenkins, munin, mysql, file timestamps, etc.

However, graphite displays a time 6 hours behind my local time. So, at 18:00 it displays 12:00.

In an attempt to fix this, I changed TIME_ZONE = 'Europe/London' in /opt/graphite/webapp/graphite/local_settings.py, but this had no effect.

Is there a way to configure graphite so that it displays the correct time?

Thanks.

Question information

Language:
English Edit question
Status:
Solved
For:
Graphite Edit question
Assignee:
No assignee Edit question
Solved by:
auxbuss
Solved:
Last query:
Last reply:
Revision history for this message
Gabriel Filion (gabriel-filion) said : 		#1

hello,

I saw the same thing yesterday. I also changed TIME_ZONE, but did so in settings.py instead of local_settings.py

I don't know if it's the right solution but it worked for me. hth

Oh, and also, when I switched the config, the graphs started showing time freegames: the time was randomly going back to the old time zone, and went back to the right one.. but the time flickering went away when data that was entered in the other time zone got out of the graph.

Revision history for this message
auxbuss (launchpad-auxbuss) said : 		#2

I think this was mea culpa!

My restart script for gunicorn was silently failing. So, presuming a gunicorn restart is required after a webapp config change, this was the solution.

@gabriel: settings.py should not be changed, according to the script's comments. The right place for local changes is in local_settings.py. I agree that it's certainly worth a test, though. After all, it was while trying your suggestion that I restarted gunicorn properly!

Please consider this closed.