acknowledge and disabled

[equick]

Sure, this one is (starting from the top):

Code: Select all

define service {
  name                            check_mk_default
  register                        0
  active_checks_enabled           1
  passive_checks_enabled          1
  parallelize_check               1
  obsess_over_service             1
  check_freshness                 0
  notifications_enabled           1
  event_handler_enabled           0
  flap_detection_enabled          1
  failure_prediction_enabled      1
  process_perf_data               0
  retain_status_information       1
  retain_nonstatus_information    1
  notification_interval           0
  is_volatile                     0
  normal_check_interval           1
  retry_check_interval            1
  max_check_attempts              1
  notification_options            u,c,w,r,f,s
  notification_period             24X7
  check_period                    24X7
}

Code: Select all

define service {
  name                            check_mk_passive
  use                             check_mk_default
  register                        0
  active_checks_enabled           0
}

Code: Select all

define service {
  use                           check_mk_passive
  host_name                     host000000775
  service_description           Permissions: /home/duttaujj
  check_interval                1
  service_groups                Directories permissions
  notifications_enabled         0
  notification_period           24x7_sans_reboots
  normal_check_interval         5
  max_check_attempts            3
  check_command                 check_mk-directories_permissions
}

And now I realise that message about disabling checks is coming from this:

Code: Select all

define command {
  command_name                  check_mk-directories_permissions
  command_line                  echo "ERROR - you did an active check on this service - please disable active checks" && exit 1
}

[equick]

Hi, does the configuration help explain things any better?

[sreinhardt]

So here's what I am seeing.

Your configs are just fine, in fact they look reasonably nice! This is not a bug but a design decision as far as the disabled goes. As troy mentioned, this is only stating that you do not have active checks on one or more hosts\services within your groupings. If you like, you can largely think of it as a passive check counter. I do realize that it's a bit misleading and could make a person worry that it's not being checked, but it really isn't, as it's waiting for that device to send nagios the check.

You were getting active results and nagios thinking it was an active check, because you enabled active checks per troys suggestion. I'm sure the message with "ERROR an active check was performed..." is what the active check command on your host\service is set to, as its under the status output portion of your page.

I hope that helps some, but the disabled is fully expected and without core code changes, will not be possible to remove unless you make checks active. Everything you are seeing so far seems to be exactly as you have configured it, just more of wrapping your head around what is going on with all the parts. Let us know you have further questions, or if that doesn't help clarify things.