Relation to tbl_host, entry - deletion not possible

[pouda]

Ok found > Go to Configure and you'll find the new option

Concerning my feed back about Bulk modification :

maybe you should increase the size of the list box see pictures attached to this reply.

I can't see the complete name of the services listed

Screenshot - 19_04_2012 , 09_28_18.jpg

Bye

[TenTimes]

The bulk modification is found under the option tools in the CCM beta (which is found under configuration)

I also found a bug in the CCM beta bulk modification.
I used this to deactive active checks for about 500 services for testing purposes and that worked, but now I want to reactivate active checks on them, and it won't activate the active checks the services.

This means I have to activate active checks on about 500 checks manually

[jbennett]

Turns out, it didn't catch everything apparently.

Code: Select all

Error: Contact 'xxx' specified in service 'Ping' for host 'yyy' is not defined anywhere!
Error: Contact 'xxx' specified in service 'Generator Check' for host 'zzz' is not defined anywhere!
	Checked 4380 services.
Checking hosts...
Error: Contact 'xxx' specified in host 'aaa' is not defined anywhere!
Error: Contact 'xxx' specified in host 'bbb' is not defined anywhere!
Error: Contact 'xxx' specified in host 'ccc' is not defined anywhere!
Error: Contact 'xxx' specified in host 'ddd' is not defined anywhere!
Warning: Host 'zzz' has no default contacts or contactgroups defined!

The contact is no where to be found in the contact list, nor attached to any of the hosts or services. Also, host aaa,bbb,ccc,ddd, and zzz don't exist in the system any more.

Any thoughts?

[mguthrie]

@pouda

maybe you should increase the size of the list box see pictures attached to this reply.
I can't see the complete name of the services listed

Good call. That's definitely something I'll tweak for the next revision.


@TenTimes

I used this to deactive active checks for about 500 services for testing purposes and that worked, but now I want to reactivate active checks on them, and it won't activate the active checks the services.
This means I have to activate active checks on about 500 checks manually

Doh! Ok, I'll put that on my bug list and see what's going on. Sorry you had to discover that bug with such a large list ; )


@jbennet

The contact is no where to be found in the contact list, nor attached to any of the hosts or services. Also, host aaa,bbb,ccc,ddd, and zzz don't exist in the system any more.

Can you check to see if the configuration files for thoses hosts and services are still in /usr/local/nagios/etc/hosts & /usr/local/nagios/etc/services. It's possible that they did not delete properly from the file system.

[mguthrie]

@TenTimes. Bug confirmed. I repeated your steps on a smaller scale, and it worked to disable active checks, but not to re-enable them.

[jbennett]

@jbennet

The contact is no where to be found in the contact list, nor attached to any of the hosts or services. Also, host aaa,bbb,ccc,ddd, and zzz don't exist in the system any more.

Can you check to see if the configuration files for thoses hosts and services are still in /usr/local/nagios/etc/hosts & /usr/local/nagios/etc/services. It's possible that they did not delete properly from the file system.

I found them in the /hosts folder and deleted them (backed them up to my computer first). I've tried to run the configuration again and I'm getting almost the exact same output...which doesn't make any sense!!

EDIT: Refreshed the folder and lo-and-behold, they're back. Something is creating them. Where would I check to find out what is telling the system to create the .cfg file again even after it's deleted?

[mguthrie]

@jbennet

OH, I know what's going on here. When Nagios XI tries to Apply a bad configuration, it rolls back to the last known good configuration. So even though you may have deleted those files, if it's trying to apply a bad config, XI is rolling the configuration files back to keep the monitoring engine running. Lets go about this a different way.

Use the Core Config Manager->Tools->Write Config Tool to manually write out new configurations, if the verification stage fails, fix the config issue and delete any of those ghost configs that got put in place. Repeat the Write Configs->Verify process until the verification complete and you're able to restart Nagios. That should get things back to normal.

[jbennett]

@jbennet

OH, I know what's going on here. When Nagios XI tries to Apply a bad configuration, it rolls back to the last known good configuration. So even though you may have deleted those files, if it's trying to apply a bad config, XI is rolling the configuration files back to keep the monitoring engine running. Lets go about this a different way.

Use the Core Config Manager->Tools->Write Config Tool to manually write out new configurations, if the verification stage fails, fix the config issue and delete any of those ghost configs that got put in place. Repeat the Write Configs->Verify process until the verification complete and you're able to restart Nagios. That should get things back to normal.

Thanks for the quick response!

Found that if I use the beta CCM that you provided, it is exactly what you wrote. Going through this now and restarting Nagios. Crossing my fingers along the way!

[jbennett]

IT WORKED!

Thanks for the assistance! Now I just need to figure out what happened to email notifications....thats the last thing on the list before integrating with OTRS...maybe.

[mguthrie]

Good deal, glad it's working for you! Go ahead and open another thread if you have trouble resolving the notification issue.