[dev.icinga.com #2602] (Pending) service not listed #785
Comments
Updated by jmosshammer on 2012-05-11 12:23:54 +00:00
That's perfectly fine, it's best to open a new bug and reference to the closed one. You never know if it's a regression or a new bug. I can't reproduce this issue, all pending services are shown in my web instance (see attachement). AFAIK you're using mysql, does the service appear when you try querying SELECT s.display_name, ss.service_object_id FROM icinga_servicestatus ss INNER JOIN icinga_services s ON s.service_object_id = ss.service_object_id WHERE has_been_checked = 0 \G in your mysql database. |
Updated by ossmon on 2012-05-11 13:15:48 +00:00 i have done again a simple test:
we have icinga-core 1.6.1. Perhaps we need the new core version ? i will redo the test next week with the official release of core+web. |
Updated by jmosshammer on 2012-05-11 14:06:13 +00:00 hi, I fear that this might be an issue of ido2db not recognizing that the service exists. If doesn't return your service, its the idodb. |
Updated by ossmon on 2012-05-11 14:24:45 +00:00 yes you are right, the service is not found in above select. |
Updated by ossmon on 2012-05-22 09:43:12 +00:00 hi, with the new icinga/icinga-web version 1.7.0, it's the same problem. |
Updated by ossmon on 2012-06-01 07:23:48 +00:00 I have test again and the problem is not resolved in my environment.
|
Updated by ossmon on 2012-06-01 07:25:35 +00:00 can anyone remove the string "(with current git-master)" in the title of the issue because i've tested with the official 1.7 release. |
Updated by mfriedrich on 2012-06-01 07:56:17 +00:00
|
Updated by ossmon on 2012-07-04 05:54:41 +00:00 Can someone reopen this Bug ? Thanks. |
Updated by mfriedrich on 2012-07-04 08:00:49 +00:00 status is still 'new' |
Updated by mfriedrich on 2012-09-24 13:32:07 +00:00
ossmon wrote:
when the core dumps retained states, as well as on new checks, resulting in a status update.
it will remain there, as the status tables won't be cleaned on restarts. a dedicated solution for marking single objects as deleted is not given right now.
in general, there's currently 2 conditions
|
Updated by kustodian on 2012-10-10 09:58:15 +00:00 I hade the same problem when I added new servers to the configuration and then released Icinga, but after a icinga restart everything worked fine. It is version 1.7.2. |
Updated by mfriedrich on 2012-11-20 17:22:11 +00:00 within #2265 there have been fixes implanted into the core - is this fixed within 1.8.x ? |
Updated by talpa on 2013-01-09 13:23:45 +00:00 I don't think so. I tested with core 1.8.3/ web 1.8.1. |
Updated by mfriedrich on 2013-03-11 17:29:57 +00:00
I'm aware of the problem (ido related), but still, i don't have an idea to properly fix it. Just assigning to me to keep it on my todo list. |
Updated by mfriedrich on 2013-03-12 09:10:31 +00:00 partly related to the change in #1741 which revokes all status updates during scheduling queue initialisation. re-enabling this might solve the issue partly, but still it will dump the retained states (retention.dat) duplicated then, which does not make sense at all. |
Updated by mfrosch on 2013-03-13 09:25:40 +00:00
Hey,
Regards |
Updated by mfrosch on 2013-03-13 09:25:56 +00:00
|
Updated by mfrosch on 2013-03-13 11:24:43 +00:00
I've pushed the fixes into next branch. Could you please test this in your environment? We are considering to release the #3843 fix with 1.8.3, which should solve your main problem. |
Updated by ossmon on 2013-03-13 13:39:02 +00:00
Hi Markus, i've tested your git version (your branch with the tag "mfrosch/pendingstates"). i created a new service and it is now displayed after a reload in the icinga-web as a pending service. One problem perhaps: In the "Attempt" column, the name of a variable is displayed (${field.service_...), see screenshot. What is it ? |
Updated by mfrosch on 2013-03-13 17:07:20 +00:00 Hey, Basically: The status row is NULL at this time, and I'm cheating some values to be 0 instead of NULL, so the backend interprets the values as PENDING. I could change all those columns to their respective "default" values, but that would mess up the XMLs quite a bit. -Markus |
Updated by mfrosch on 2013-04-10 21:54:30 +00:00
Considering this done for now! |
This issue has been migrated from Redmine: https://dev.icinga.com/issues/2602
Created by ossmon on 2012-05-11 11:15:11 +00:00
Assignee: mfrosch
Status: Resolved (closed on 2013-04-10 21:54:30 +00:00)
Target Version: 1.9
Last Update: 2013-04-10 21:54:30 +00:00 (in Redmine)
Icinga-Core: 1.6.1
Icinga-Web: git master
In the current git master (a75f1e3;sf), the bug #2472 is not resolved.
New service are shown als pending im classic gui, but are not shown in icinga-web.
Can anyone say me how we have to handle closed issue that are again buggy ? I dont't know if the issue will be handled from the developers when i add a comment although the issue is already closed. For this reason i open a new issue.
Attachments
Changesets
2013-03-13 11:12:54 +00:00 by mfrosch 898005f
Relations:
The text was updated successfully, but these errors were encountered: