Project

General

Profile

Actions
Copy link

Bug #5768

closed

Document how to configure your timezone in rudder webapp

Added by Matthieu CERDA about 10 years ago. Updated almost 3 years ago.

Status:
Resolved
Priority:
3
Assignee:
-
Category:
Documentation
Target version:
Ideas (not version specific)
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Small
Priority:
0
Name check:
Fix check:
Regression:

Description

On some JRE's (seen with at least the standard Oracle one, installed using the Linux x86_64 RPM on SLES11 SP1), Java uses a default timezone which is America/Los Angeles if no TZ variable is defined.

It completely f*cks up the "Last seen" date shown on the node details pane (they are shown relative the the JRE timezone)

From webapp logs:

[2014-11-12 17:13:48] INFO  application - registered property: user.country="US" 
[2014-11-12 17:13:48] INFO  application - registered property: user.language="en" 
[2014-11-12 17:13:48] INFO  application - registered property: user.timezone="America/Los Angeles"

I suspect that system OpenJDK packages on other system set the default TZ without anything to do.

We should make sure that the timezone Java uses is the same as the system one, and change it accordingly.

I am not yet sure if it should be done on the packaging side (init scripts) or directly Rudder webapp side...

FAR, any advice ?

WORKAROUND

Edit /etc/default/rudder-jetty and add:

JAVA_OPTIONS="-Duser.timezone=Europe/Paris"

Related issues 2 (0 open — 2 closed)

Related to Rudder - User story #4708: Display time of reports in the web interface in the server timezoneResolvedActions
Related to Rudder - Bug #5653: rudder-jetty init script may fail on successReleasedBenoît PECCATTE2014-10-17Actions
Actions
Copy link

Also available in: Atom PDF