Skip to content
This repository has been archived by the owner. It is now read-only.

[dev.icinga.com #3417] HostStatus cronk does not update Status column with warning/critical state count #951

Closed
icinga-migration opened this issue Nov 2, 2012 · 9 comments

Comments

Projects
None yet
1 participant
@icinga-migration
Copy link
Member

commented Nov 2, 2012

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

Created by jcasale on 2012-11-02 02:52:47 +00:00

Assignee: jmosshammer
Status: Resolved (closed on 2013-02-11 17:53:18 +00:00)
Target Version: 1.8.2
Last Update: 2013-02-11 19:18:22 +00:00 (in Redmine)

Icinga Version: 1.8.0
Icinga Web Version: 1.8.0
IDO Version: 1.8.0
OS Version: CentOS x64 6.3
DB Type: PostgreSQL
DB Version: 8.4.13
Browser Version: Chrome 22.0.1229.94 | Internet Explorer 9

The HostStatus cronk Status column remains at "- -" for hosts even with critical/failed services. It does however change from green/up to red/down when the hosts is down.

This manifests on upgraded and new databases.

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Dec 8, 2012

Updated by crysmi on 2012-12-08 05:14:30 +00:00

Same issue but noticed in js for updateHostServiceData, comparison of HOST_OBJECT_ID was between number and string

from /usr/local/icinga-web/app/modules/Cronks/lib/js/Cronk/grid/renderer/AdvancedHostStatusColumnRenderer.js:
LINE 46: if (current.HOST_OBJECT_ID !== elem.getAttribute("host_object_id")) {

I changed this to use toString() on HOST_OBJECT_ID and it seems to work

Checked on http://web.demo.icinga.org/icinga-web/ and this was a string to string comparison. Dont know enough about the application to know why Ive got current.HOST_OBJECT_ID as number.
Version or the fact Im using postgres?

Icinga version: 1.6.1
ido2db version: 1.6.1
Icinga-web version: 1.8.1

on icinga server(Ubuntu 12.04.1 LTS):
dpkg -l | grep -i icinga
ii icinga 1.6.1-2 host and network monitoring system - metapackage
ii icinga-cgi 1.6.1-2 host and network monitoring system - CGI scripts
ii icinga-common 1.6.1-2 host and network monitoring system - support files
ii icinga-core 1.6.1-2 host and network monitoring system - core files
ii icinga-doc 1.6.1-2 host and network monitoring system - documentation
ii icinga-idoutils 1.6.1-2 host and network monitoring system - icinga-dataobjects support

dpkg -l | grep -i postgres
ii libdbd-pgsql 0.8.3-1+s-2.1ubuntu4 PostgreSQL database server driver for libdbi
ii libpq5 9.1.6-0ubuntu12.04.1 PostgreSQL C client library
ii php5-pgsql 5.3.10-1ubuntu3.4 PostgreSQL module for php5
ii postgresql-client 9.1+129ubuntu1 front-end programs for PostgreSQL (supported version)
ii postgresql-client-9.1 9.1.6-0ubuntu12.04.1 front-end programs for PostgreSQL 9.1
ii postgresql-client-common 129ubuntu1 manager for multiple PostgreSQL client versions

on postgres server(CentOS release 5.8 (Final)):
rpm -qa | grep -i postgres
postgresql-libs-8.1.23-6.el5_8
postgresql-8.1.23-6.el5_8
postgresql-server-8.1.23-6.el5_8

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Dec 8, 2012

Updated by mfriedrich on 2012-12-08 08:12:53 +00:00

your client 9.1 talks to a 8.1 server. i have seen lots of strange issues with 8.1 - so upgrade to 8.4 which is available, and also not EOL - which 8.1 is. tried a newer postgresql server version to reproduce the issue?

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Dec 8, 2012

Updated by mfriedrich on 2012-12-08 08:14:22 +00:00

furthermore, you should use the same major versions among core, ido and web, which may also cause irritations here.

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Dec 8, 2012

Updated by jcasale on 2012-12-08 14:35:59 +00:00

These suggestions do not explain the original report where all versions are at 1.8.0. Also, two fresh installs were done with the shipped 8.4 client and server as well as the official PostgreSQL 9.2 repo being used.

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Dec 8, 2012

Updated by mfriedrich on 2012-12-08 15:10:36 +00:00

sorry for trying to help ...

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Dec 8, 2012

Updated by jcasale on 2012-12-08 17:13:08 +00:00

Michael,
I am sorry you feel the need to respond that way.

The original report when unanswered for over a month without even a request to provide anything that might help reach a resolution with little to no effort by devs, in other words I would be happy and still am happy to help in any way. This is all fair, but the only solution offered didn't fit the original case? There was no lack of appreciation mentioned...

http://www.ou.edu/research/electron/internet/use-writ.htm

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Dec 8, 2012

Updated by mfriedrich on 2012-12-08 21:21:57 +00:00

Well i was answering the second question, as this version mismatch was disturbing. Complaining about no response - you might figure that ppl got a busy life, always til the end of the year. If someone gets time they will answer, and be more helpful then.

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Feb 11, 2013

Updated by mfrosch on 2013-02-11 17:53:18 +00:00

  • Status changed from New to Resolved
  • Assigned to set to jmosshammer
  • Target Version set to 1.8.2

Should be fixed with 1.8.2

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Feb 11, 2013

Updated by mfrosch on 2013-02-11 19:18:22 +00:00

  • Done % changed from 0 to 100

@icinga-migration icinga-migration added this to the 1.8.2 milestone Jan 17, 2017

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.