existing object shows as unconfigured object in wizard

[nagiosadmin42]

Yes, those checks are for the correct placeholder type host. There are over 300 of them, so list did get cut-off in the screenshot.

-Jason

[Box293]

OK I understand what your issue is.

When this problem occurs, do the services appear when viewing in the Nagos Core interface?

Open a webpage to http://nagiosserverip/nagios
NOTE the URL points to /nagios
Provide nagiosadmin username and password
In the left pane, under Quick Search, search for proxy-server
Do the services appear?

I'm just trying to make sure that the back end (core) is correctly functioning. This may just be an XI visualisation issue.

[nagiosadmin42]

Thanks for the quick replies.

I get one item, which is for the host 'proxy-server', but no services for that host show up.

I've attached a screen shot.

[Box293]

Thanks for the quick replies.

I get one item, which is for the host 'proxy-server', but no services for that host show up.

I've attached a screen shot.

OK this actually points us in the direction of Nagios Core being the issue.

The tech support guys can weigh in on this, but I think that if you empty the /usr/local/nagios/nagiosxi/var/corelog.newobjects file, the checks should disappear from the unconfigured objects display. I could be wrong, so make a copy if you try this.

As pointed out, XI sees unconfigured objects by looking at the file /usr/local/nagios/nagiosxi/var/corelog.newobjects

This file gets populated by a backend process. This process watches /usr/local/nagios/var/nagios.log for any entries like this:

Code: Select all

[1416634449] Warning:  Passive check result was received for service 'xxx Service Name xxx' on host 'yyy Host Name yyy', but the service could not be found!

Soooo what this tells me about your problem is that the existing known passive services are no longer "known" to the nagios core.

The best way to diagnose this moving forward is to turn on debugging:

Try setting the debug level on and then restart Nagios.

Code: Select all

sed -i 's/.*debug_level=.*/debug_level=-1/g' /usr/local/nagios/etc/nagios.cfg
service nagios restart

This generates the file /usr/local/nagios/var/nagios.debug

So when the problem next occurs, we can look in nagios.debug for the entries I described above. We can then look backwards at the debug log to see what is happening before hand and hopefully identify what is causing this.

When you are finished this turns debugging off:

Code: Select all

sed -i 's/.*debug_level=.*/debug_level=0/g' /usr/local/nagios/etc/nagios.cfg
service nagios restart

[nagiosadmin42]

Thanks,

I'll give that a shot.

I'm limited on / so I'll run this tomorrow.

Thanks.

[lmiltchev]

I'll give that a shot.

I'm limited on / so I'll run this tomorrow.

Let us know how it went.

[nagiosadmin42]

Hello,

I cleared the Unconfigured objects, configured Nagios to log debug, and restarted a few hours ago.

The debug log is being populated now. As soon as I get a hit on Unconfigured Objects, I'll update this post.

Thanks,

-Jason

[abrist]

No problem - we are all ears

[nagiosadmin42]

Ok. Couple of things.

1. Got the Unconfigured Obj. notification at 1:08 PM PST.
2. Turned debug on at about 11:45 am
3. Debug log time stamp is in epoc (PITA), but converts to 1:34 PM PST.
4. There are two Nagios debug logs, nagios.debug and nagios.debug.old. Both with A times of 1:34. I figured the first one rolled over, no issue there, however
looking at both log files there are no entries for 'PROXY-SERVER'.

I thought I'd take a look at the nagios.log file and found a bunch these (SANITIZED == removed customer name):

[1425970801] Error: Got check result for service 'Timed out txn count for All Apps - Web2.0 SANITIZED' on host 'PROXY-SERVER'. Unable to find service
[1425970801] Error: Got check result for service 'User count for All Apps - Web2.0 SANITIZED' on host 'PROXY-SERVER'. Unable to find service
[1425970801] Error: Got check result for service 'User count for SANITIZED - Web2.0 SANITIZED' on host 'PROXY-SERVER'. Unable to find service
[1425970801] Error: Got check result for service 'Transaction count for SANITIZED - Web2.0 SANITIZED' on host 'PROXY-SERVER'. Unable to find service
[1425970801] Error: Got check result for service 'Transaction count for All Apps - Web2.0 SANITIZED' on host 'PROXY-SERVER'. Unable to find service
[1425970801] Error: Got check result for service 'Timed out txn count for All Apps - Web2.0 SANITIZED' on host 'PROXY-SERVER'. Unable to find service
[1425970801] Error: Got check result for service 'User count for All Apps - Web2.0 SANITIZED' on host 'PROXY-SERVER'. Unable to find service
[1425970801] Error: Got check result for service 'User count for SANITIZED - Web2.0 SANITIZED' on host 'PROXY-SERVER'. Unable to find service
[1425970801] Error: Got check result for service 'User count for SANITIZED - Web2.0 SANITIZED' on host 'PROXY-SERVER'. Unable to find service
[1425970801] Error: Got check result for service 'Transaction count for Error 2004 - Web2.0 SANITIZED' on host 'PROXY-SERVER'. Unable to find service

I'm not sure why 'PROXY-SERVER' is not in the debug log, and shouldn't the debug log time stamp be when I restarted Nagios to enable debug?

-Jason

[Box293]

So far we have determined that Nagios is not seeing these services that already exist.

With the debug log, please confirm that -1 is the level (thats negative 1).
Then:

Code: Select all

service nagios stop
rm -f /usr/local/nagios/var/nagios.debu*
service nagios start

Starting with a fresh debug log will remove any confusion

I would like to see the debug log in full, please PM me the log.

How are these check results being received? SNMP? NRDP? NSCA?