Wednesday, May 22nd 2013, 10:54am UTC+2

You are not logged in.

  • Login
  • Register

Removed services remain in "unknown" state

Dear visitor, welcome to Monitoring-Portal.
Although this is a german monitoring forum, please don't hesitate to post in English. Nearly everybody here understands you and will answer in English as well.
If this is your first visit here, please read the Help. It explains how this page works. You must be registered before you can use all the page's features. Please use the registration form to register here or read more information about the registration process. If you are already registered, please login here.

aswen

Beginner

Posts: 3

Birthday: Dec 23rd 1976 (36)

Gender: male

Location: Groenlo

Occupation: sys admin

Number of monitoring servers: 4

Nagios Version: 2x 3.0.6, 1x 3.2.3

Icinga Version: 1.6.1 (plus ido/web)

Distributed monitoring: Nein

Redundant monitoring: Ja

Number of hosts: 2x 84 + 35 + 84

Number of services: 2x 2485 + 330 +2485

OS: Debian

Plugin Version: several

IDO-Version: 1.6.1

Other Addons: icinga-web

1

Tuesday, February 7th 2012, 9:24am

Removed services remain in "unknown" state

hi,

we use icinga 1.6.1-2 (Debian packages from backports), plus ido utils (1.6.1-2 as well), on top of that we run icinga-web 1.6.1 which has been compiled from source since there is no packaged version.
Ido utils and web each have their own mysql db on our mysql server.

We are in the process of a migration from nagios (3.0.3) to icinga and now run into a strange effect that very likely is there because we don't understand something not enough:

while adding some old windows servers we added checks for four disks on them while the newer ones only have one disk. so, later we removed the group "windows-servers" and added those two old servers to the services that check disks d/f/g.
however, the old drive space checks still remain as unknown (since they never succeeded) in our status overview.

Please help us by giving instructions on how to sanitize our icinga server.

thanks in advance!

Alex

julian

Intermediate

Posts: 240

Number of monitoring servers: 3

Nagios Version: 3.2.3

Icinga Version: 1.6.1

Distributed monitoring: Nein

Redundant monitoring: Nein

Number of hosts: 40,230,150

Number of services: 350,500,200

OS: Debian Squeeze, SLES11, Win2k8R2

Plugin Version: 1.4.15

IDO-Version: 1.6

Other Addons: nrpe, pnp4nagios, check_mk

2

Tuesday, February 7th 2012, 7:40pm

Welcome,

you removed the hostgroup?
The servers themselves and the services probably still remain in your config.

You should give us some more information.


Regards
julian

aswen

Beginner

Posts: 3

Birthday: Dec 23rd 1976 (36)

Gender: male

Location: Groenlo

Occupation: sys admin

Number of monitoring servers: 4

Nagios Version: 2x 3.0.6, 1x 3.2.3

Icinga Version: 1.6.1 (plus ido/web)

Distributed monitoring: Nein

Redundant monitoring: Ja

Number of hosts: 2x 84 + 35 + 84

Number of services: 2x 2485 + 330 +2485

OS: Debian

Plugin Version: several

IDO-Version: 1.6.1

Other Addons: icinga-web

3

Wednesday, February 8th 2012, 3:20pm

hi Julian,

(while typing this message I realized what I did wrong... leave my explanation here for learning purpose...and you can have a laugh ;-)

Thanks for taking the effort to reply.
here's what I did:
added some windows boxes with checks on four disks (cdfg).
then saw that some of them don't have so many disks. so removed those windows nodes from the services. however, icinga still "thinks" they need to be tested and therefor keeps them in an unknown state.

so this was my cfg before removal:

Source code

 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24

define service {
  use windows-service (template to set proper servicegroups)
  check_command	check_nt!USEDDISKSPACE!-l c -w 90 -c 95
hostgroup_name windows-servers
  service_description  C:\ Drive Space
}
define service {
  use windows-service
  check_command	check_nt!USEDDISKSPACE!-l d -w 90 -c 95
hostgroup_name windows-servers
  service_description D:\ Drive Space
}
define service {
use windows-service
check_command	check_nt!USEDDISKSPACE!-l f -w 90 -c 95
hostgroup_name windows-servers
service_description F:\ Drive Space
}
define service {
use windows-service
check_command	check_nt!USEDDISKSPACE!-l g -w 90 -c 95
hostgroup_name windows-servers
service_description G:\ Drive Space
}

then I altered it this way:

Source code

 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24

define service {
  use windows-service (template to set proper servicegroups)
  check_command	check_nt!USEDDISKSPACE!-l c -w 90 -c 95
hostgroup_name windows-servers
  service_description  C:\ Drive Space
}
define service {
  use windows-service
  check_command	check_nt!USEDDISKSPACE!-l d -w 90 -c 95
hostgroup_name windows-servers
  service_description D:\ Drive Space
}
define service {
use windows-service
check_command	check_nt!USEDDISKSPACE!-l f -w 90 -c 95
host_name servera,serverb
service_description F:\ Drive Space
}
define service {
use windows-service
check_command	check_nt!USEDDISKSPACE!-l g -w 90 -c 95
host_name servera,serverb
service_description G:\ Drive Space
}


then of course I reloaded icinga. however, those F and G drives still show up in my unknown services view.
This is both on icinga ("old") and icinga-web.

Reason I suspected My IDO is because I have thoroughly checked all my cfg files and there are no other check_nt|USEDDISK commands.

And, I wanted to do it again but then noticed my "use window-service" template also added a "hostgroup_name windows-servers" to the service....
so. I think I found the solution! my stupidity...

Similar threads