[dev.icinga.com #1902] instance status cronk - status age is calculated wrong with utc (minus 2 hours) #498

Closed
icinga-migration opened this Issue Sep 15, 2011 · 10 comments

Projects

None yet

1 participant

@icinga-migration
Member

This issue has been migrated from Redmine: https://dev.icinga.com/issues/1902

Created by mfriedrich on 2011-09-15 14:18:12 +00:00

Assignee: mhein
Status: Resolved (closed on 2011-11-22 10:18:43 +00:00)
Target Version: 1.6
Last Update: 2011-12-03 11:30:15 +00:00 (in Redmine)


using icinga-web 1.5.2 r1.5 git, 7990db3

time now is 16:15, server time in icinga-web shows 14:15

the instance status cronk now calculates that wrong, and says ~ minus 2 hours old. so my instance status is in the future?

icinga_web_1.5.2_instance_status_data.png

i do think that the query is somehow wrong, in combination with the default timesettings - i'm not using any changes in icinga-web configs nor do i set the default timezone in php.ini as i always test fresh unmodified installs.

Attachments

@icinga-migration
Member

Updated by mhein on 2011-09-27 12:00:17 +00:00

  • Status changed from New to Feedback
  • Depending on oracle issues #1954
@icinga-migration
Member

Updated by mhein on 2011-10-05 05:55:12 +00:00

  • Status changed from Feedback to Assigned
  • Assigned to set to mhein
@icinga-migration
Member

Updated by mhein on 2011-10-05 05:59:14 +00:00

  • Status changed from Assigned to Feedback

Are there any news for this?

@icinga-migration
Member

Updated by mfriedrich on 2011-11-16 17:50:33 +00:00

  • File added icinga_web_utc_oracle_timeproblems02.png
  • File added icinga_web_utc_oracle_timeproblems01.png

servertime now thinks of 17:35, while localtime is 18:35

icinga_web_utc_oracle_timeproblems02.png

changing translation.xml to according timezone,

                          Deutsch
                        
                        
                          English

this adds another difference of 1 hour.

icinga_web_utc_oracle_timeproblems01.png

hm....

@icinga-migration
Member

Updated by jmosshammer on 2011-11-17 11:15:43 +00:00

Which timezone is defined in your oracle-db?

@icinga-migration
Member

Updated by Wolfgang on 2011-11-17 18:33:42 +00:00

That sounds as if servertime is set to UTC. MESZ is two hours ahead, MEZ
only one.

Am 16.11.2011 18:50, schrieb development@icinga.org:

this reduces the difference to 1 hour.

icinga_web_utc_oracle_timeproblems01.png

hm....

@icinga-migration
Member

Updated by mhein on 2011-11-21 11:19:11 +00:00

  • Status changed from Feedback to Assigned
  • Estimated Hours set to 0.0
@icinga-migration
Member

Updated by mhein on 2011-11-21 14:03:55 +00:00

  • Status changed from Assigned to Feedback

Hi.

For oracle this error comes from the agent_version. "1.6.0-dev" is longer that 8 chars. Thanks thomas dressler to give that hint:

= SCHNIPP =

Gibt es evt. andere Oracle Fehler im Log (z.B. ist Versionsstring zu gross
und deshalb kommt das hello gar nicht so weit)? Das kommt von der
Erweiterung auf " 1.6.0-dev"
Dann z.b. mit "alter table conninfo modify (agent_version varchar2(10));"
das Schema ändern.

= SCHNAPP =

Can some one agree with that?

Kind regards,
Marius.

@icinga-migration
Member

Updated by mhein on 2011-11-21 15:20:54 +00:00

  • Done % changed from 0 to 100
@icinga-migration
Member

Updated by mhein on 2011-11-22 10:18:43 +00:00

  • Status changed from Feedback to Resolved

I'll close that bug. If there are any further problems / hints, please reopen at will.

Kind regards,
Marius.

@icinga-migration icinga-migration added this to the 1.6 milestone Jan 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment