NRDS Checks removed and deleted - still showing up

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
Locked
jbennett
Posts: 522
Joined: Mon Apr 16, 2012 3:00 pm

NRDS Checks removed and deleted - still showing up

Post by jbennett »

I removed the NRDS checks from the NRDS config on the Nagios server. I then selected and deleted those same checks from services.

The check results from 7-9 are still showig up - Last Check: 2013-07-09 09:44:54

I'm not sure where else I'm supposed to delete the items from in order to prevent them from showing up?
abrist
Red Shirt
Posts: 8334
Joined: Thu Nov 15, 2012 1:20 pm

Re: NRDS Checks removed and deleted - still showing up

Post by abrist »

Write, and then verify your configs through the CMM --> write config files option. Afterwards, check the services directory for any old config files:

Code: Select all

ls -lat /usr/local/nagios/etc/services
You are looking for any files that have an older date (probably the 9th).
Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
jbennett
Posts: 522
Joined: Mon Apr 16, 2012 3:00 pm

Re: NRDS Checks removed and deleted - still showing up

Post by jbennett »

I did as suggested and I don't see any configs that are titled the same as the ones that keep showing up.
User avatar
lmiltchev
Bugs find me
Posts: 13589
Joined: Mon May 23, 2011 12:15 pm

Re: NRDS Checks removed and deleted - still showing up

Post by lmiltchev »

I'm not sure where else I'm supposed to delete the items from in order to prevent them from showing up?
Where are they showing up? Do you see them in the Unconfigured Objects? Did you remove the entries on the remote boxes (in the crontab for linux machines and Task Scheduler for Windows machines)?
Be sure to check out our Knowledgebase for helpful articles and solutions!
jbennett
Posts: 522
Joined: Mon Apr 16, 2012 3:00 pm

Re: NRDS Checks removed and deleted - still showing up

Post by jbennett »

They are showing up under the ops Center screen as alerting. When I search Nagios for the Service name, I get all of them. That's where I can see the last checked date/time.

If I go to Tactical Overview, only one of the 3 that show up under the Ops Center show up. When I click on it and check the data, I see the following:

Code: Select all

Service State:	Critical
Duration:	7d 3h 36m 8s
Service Stability:	Unchanging (stable)
Last Check:	2013-07-09 09:47:24
Next Check:	1969-12-31 17:00:00
These checks do not show up in unconfigured objects.

I cannot remove the crontab from the remote machines as I still have other NRDS checks that are being sent. I HAVE removed the check from the NRDS config on the Nagios box and saved the config. If I check the current config being used in /usr/local/nrdp/clients/nrds/nrds.cfg, the specific check that I am seeing results for is no longer listed which goes along with the fact that the checks haven't had any recent results.
User avatar
lmiltchev
Bugs find me
Posts: 13589
Joined: Mon May 23, 2011 12:15 pm

Re: NRDS Checks removed and deleted - still showing up

Post by lmiltchev »

Did you make sure the times are synced among these servers?
Last Check: 2013-07-09 09:47:24
Next Check: 1969-12-31 17:00:00
Be sure to check out our Knowledgebase for helpful articles and solutions!
jbennett
Posts: 522
Joined: Mon Apr 16, 2012 3:00 pm

Re: NRDS Checks removed and deleted - still showing up

Post by jbennett »

Time is as follows on the two boxes in question -

Client:

Code: Select all

 # date
Tue Jul 16 14:43:28 CDT 2013
Nagios Server:

Code: Select all

]# date
Tue Jul 16 14:43:01 CDT 2013
I have noticed that Nagios shows 1969 whenever there isn't another check scheduled. For instance, when a host has been de-activated but the host is still assigned to a host group that is active.
jbennett
Posts: 522
Joined: Mon Apr 16, 2012 3:00 pm

Re: NRDS Checks removed and deleted - still showing up

Post by jbennett »

For some reason, after updating PHP, this issue seems to have been resolved.

*confused but ok*
Locked