Monitor Isilon with Nagios XI

[jolson]

In addition to what jdalrymple has stated (check your CCM for any duplicate configurations) -

I have some experience regarding this plugin, and unfortunately it's one of the more difficult ones to get set up - I spent a good hour in a remote session with a client and we had to modify several parts of the plugin on the Isilon end. The good news is that after some work, this plugin *does* work and you won't have to think about it after it's good to go.

Let's take a look at where your duplicate configuration error might be coming from:

Code: Select all

grep -R rtpisilon-1 /usr/local/nagios/etc/

Code: Select all

cat /usr/local/nagios/etc/static/*

This plugin is a very special case - most plugins are much, much easier to get implemented and working properly. Unfortunately this one is old and a bit of a pain - we're happy to help you through any hurdles you may encounter along the way. For now, report the above back to us and we can go from there. Thanks.

[SilvesterDU]

It sounds though like you already have the host defined in CCM. You will have to remove it from CCM in order to define it in the static directory. Nagios balks when you have a host defined in 2 places.

Please find the screenshots of CCM and my /usr/local/nagios/etc/static/isilon-services.cfg file attached. As a newbie to Nagios maybe I has some problem in configuring the isilon-services.config, but I'm sure I haven't used CCM.


thanks
Silvester

[jdalrymple]

Sorry, I misread your earlier post. I read it as the exact opposite as what you actually indicated. This config looks valid. Are there any other files in that static directory? What about the import directory?

I can understand why you'd be frustrated right now with the static configuration writing, it really isn't bad at all though, you just have some sort of strange entry lying about that is tripping up validation. Your syntax looks OK.

[SilvesterDU]

In addition to what jdalrymple has stated (check your CCM for any duplicate configurations) -

I have some experience regarding this plugin, and unfortunately it's one of the more difficult ones to get set up - I spent a good hour in a remote session with a client and we had to modify several parts of the plugin on the Isilon end. The good news is that after some work, this plugin *does* work and you won't have to think about it after it's good to go.

Let's take a look at where your duplicate configuration error might be coming from:

Code: Select all

grep -R rtpisilon-1 /usr/local/nagios/etc/

Code: Select all

cat /usr/local/nagios/etc/static/*

This plugin is a very special case - most plugins are much, much easier to get implemented and working properly. Unfortunately this one is old and a bit of a pain - we're happy to help you through any hurdles you may encounter along the way. For now, report the above back to us and we can go from there. Thanks.

Please find the output from these 2 commands attached.

thanks.
Silvester

[jdalrymple]

Please find the output from these 2 commands attached.

No attachment. Make sure that after you Browse the file you "Add the file"

[SilvesterDU]

Ah... sorry I wasn't realizing the extension was blocked.

Here you are.

Silvester

[SilvesterDU]

Also, here are the 2 configurations files exported from Isilon.

Global Nagios Configuration-Configuration file for Nagios -applicable to all Isilon clusters
Cluster Nagios Configuration-Configuration file for Nagios applicable to this cluster (rtpisilon)

Although they may or may not be imported to nagios directly, hope it helps you to understand my system.

Thanks

Silvester

[jdalrymple]

I'm a bit baffled. I copied/pasted your isilon config directly into my 4.0.8 lab box and it validated no problem. I did have to add the isilon-clusters hostgroup, but that is to be expected.

Just for fun (because it's more fun than digging into cfg directives in the main file anyway) let's try to change host_name from "rtpisilon-1" to something like "foobar" and see if you get similar results when trying to apply config.

[SilvesterDU]

I'm a bit baffled. I copied/pasted your isilon config directly into my 4.0.8 lab box and it validated no problem. I did have to add the isilon-clusters hostgroup, but that is to be expected.

Just for fun (because it's more fun than digging into cfg directives in the main file anyway) let's try to change host_name from "rtpisilon-1" to something like "foobar" and see if you get similar results when trying to apply config.

yes, when I changed to foobar, it reported the same error with "foorbar".

BTW, besides the /usr/local/nagios/etc/static/isilon-services.cfg , I also updated /usr/local/nagios/etc/nagios.config (by adding "cfg_file=/usr/local/nagios/etc/static/isilon-services.cfg" in the front)
according to https://sites.google.com/a/verypowerful ... ith-nagios

Here I attached both config files again.

Thanks
Silvester

[jdalrymple]

BTW, besides the /usr/local/nagios/etc/static/isilon-services.cfg , I also updated /usr/local/nagios/etc/nagios.config (by adding "cfg_file=/usr/local/nagios/etc/static/isilon-services.cfg" in the front)according to https://sites.google.com/a/verypowerful ... ith-nagios

Did you do this before or after you first tried applying config with this file in your static directory?

Either way, remove it and try again. I'm not sure what Nagios will do if you explicitly define a file twice, it's just nothing I've ran into before. However that is what you've done here, let's remove that line and try again:

Code: Select all

cfg_file=/usr/local/nagios/etc/static/isilon-services.cfg