Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Time Error on Web Console

Description

With 64-bit CentOS 5 as OpenNMS Server, settings from OpenNMS System Configurations page are:

  • OpenNMS Version: 1.8.14

  • Server Time: Mon Oct 31 08:39:08 PKT 2011

  • Client Time: Mon Oct 31 2011 09:45:02 GMT+0500 (PKT)

  • Java Version: 1.6.0_27 Sun Microsystems Inc.

  • Java Virtual Machine: 20.2-b06 Sun Microsystems Inc.

  • Operating System: Linux 2.6.18-194.el5 (amd64)

  • Servlet Container: jetty/6.1.24 (Servlet Spec 2.5)

  • User Agent: Mozilla/5.0 (X11; Linux i686; rv:7.0.1) Gecko/20100101 Firefox/7.0.1

The Problem:

As shown above, there is a difference of one hour in System time (both server and client - it is same as actual time) and OpenNMS web console time. It seems that openNMS is using Daylight saving time whereas actually it is not in practice and OS too is not using that. I have seen another post regarding this but the issue looks unresolved.
http://opennms.530661.n2.nabble.com/OpenNMS-has-moved-to-standard-time-operating-system-has-not-td1396026.html

I have update zoneinfo few days back without any effect. Also created the following link as advised elsewhere:
sudo ln -s /usr/share/zoneinfo/Asia/Karachi /etc/localtime
But there is no effect even after restarting OpenNMS (and a reboot too didn't help)

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Arshad Parvez November 17, 2011 at 2:22 AM

That means the issue doesn't actually belong here! Ok. Despite that, will you suggest some ad hoc measures (like changing system time etc.) to get things going until we either shift to some other platform or find a solution?

Seth Leger November 3, 2011 at 12:56 PM

This is a Linux or Java platform-level issue. Any Java program that executes on the same server should experience the same problem. You could write a simple Java program to verify this and maybe help with debugging the problem.

Also, check the timestamps of the events in your database and see if they match the JVM. If there is a skew between the database values and time in the JVM, you may get bad behavior in OpenNMS (missing events and collected data).

Configuration

Details

Assignee

Reporter

Labels

Components

Affects versions

Priority

PagerDuty

Created October 31, 2011 at 1:13 AM
Updated November 17, 2011 at 2:22 AM
Resolved November 3, 2011 at 12:56 PM
Loading...