[dev.icinga.com #3417] HostStatus cronk does not update Status column with warning/critical state count #951
Comments
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: 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. Icinga version: 1.6.1 on icinga server(Ubuntu 12.04.1 LTS): dpkg -l | grep -i postgres on postgres server(CentOS release 5.8 (Final)): |
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? |
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. |
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. |
Updated by mfriedrich on 2012-12-08 15:10:36 +00:00 sorry for trying to help ... |
Updated by jcasale on 2012-12-08 17:13:08 +00:00 Michael, 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... |
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. |
Updated by mfrosch on 2013-02-11 17:53:18 +00:00
Should be fixed with 1.8.2 |
Updated by mfrosch on 2013-02-11 19:18:22 +00:00
|
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)
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.
The text was updated successfully, but these errors were encountered: