All my contact and contactgroup options reset to standard!

[WillemDH]

Hello,

I jsut discovered all my contact and contact group options have been reset from '+' to standard! This is kind of a big problem, as all hosts and services considered critical are inheriting their contacts from templates with these high prio notification contacts configured...

I'm not sure what migh have caused this situation. It could be the update to R1.3, the problem could exist for a longer time and it could be the update to R1.2.

Hostgroup and service group options seem still ok.

As resetting all these contact option would take a very long time, i have no idea how to quickly correct this situation. Please advice / help.

Grtz

Willem

[WillemDH]

Ok, after some more research, it seems the cfg files on the nagios server still seem to have the + option configured. The gui however is showing the standard option. I did some with one such a service and the contact defined in the template does get the notification. So it seems to be some kind of display bug in the gui.

An example:

The service DRV_C for server 'server1' had in the gui, see uploaded screenshot the '+' option defined for the last year. As said since an undefined time (1 day - 3 weeks max), in the gui, it now shows the 'standard' contact option. In CLI the '/usr/local/nagios/etc/services/server1.cfg file looks like this:

Code: Select all

define service {
        host_name                       server1
        service_description             DRV_C
        use                             dig-nrpe-svc-win-drv-c-prio1
        servicegroups                   +all_svc_dummy_servicegroup
        check_period                    xi_timeperiod_24x7
        notification_period             xi_timeperiod_24x7
        contacts                        +nagiosadmin
        contact_groups                  +xi_dig_dummy_contact_group
        register                        1
        }

So in CLI, it does have the + options defined!

Please advice on what to do, so the gui and cfg files are
1) consistent
2) all have the + option defined

When I try to set the + option again on a service where it already should be set, after applying configuration, the option is reset to standard......

Thanks.

Willem

[sreinhardt]

Having a dev take a look at this now. There has and will be again with the next release or so, been a LOT of CCM changes. This sounds like a regression from past similar issues, so hopefully it is already fixed for the next CCM release, which will be shortly, or is in the works.

Edit: Jake proved me wrong, as I misread your post. The config files are correct, just the display in CCM that is not after reopening the object. He requested that I submit a bug for this, and he will take a look.

[WillemDH]

Hey Spenser,

So I'm not the only one with this problem?

Grtz

Willem

[sreinhardt]

Just posted an edit above: No this is not something specific to you, we do consider it a bug with CCM that it is not properly displaying your config settings in that regard. However we are not 100% if this was ever the case, so while we do want to correct it, it may not actually be "new" per say.

[WillemDH]

Well i'm 99 % sure the '+' option was shown correctly end of juli. As I regularily need to edit host and service config I would definitely have seen it. Let me know if you find anything or if I can do anything to help.

Thanks.

[sreinhardt]

Oh I was able to recreate the issue and send the bug off, just also not sure when this would have happened. I agree I thought this was all resolved long ago.

[WillemDH]

I hope there will be a fix soon for this. In the end it seems to be working as expected, but it's getting a bit fishy cloning hosts, that seem to have no '+' option configured, but actually has.

[lmiltchev]

I've seen similar CCM bugs in the past, where the config has been modified but the change is NOT shown in the CCM.

[WillemDH]

It seems this issue has been solved in CCM 2.2.0. Thanks for the quick fix!

Willem