Test Probe Works - Discovery with that probe Does Not: How come?

[steveshiflett]

Simple probe tests okay with the "Test Probe" facility. When I run a discovery using that probe - no results are returned. (This is for Redhat Linux)

Here's the probe:

#!/bin/sh
#
# hostname.sh: Gets the hostname.
#
# Output as:
# hostname: example = hostname:mdc2vr3037
#
uname -a | awk '{print $2}' | cut -d '.' -f 1| awk '{print "hostname:" $1}'
uname -n | cut -d "." -f1 | awk '{print $1}' | nslookup |grep Name:| cut -d "." -f2- | awk '{ print "domain_name:" $1}' | cut -d "d" -f 1-


1) I assume that *even* if my sensor has issues, I should still see something from the probe in the "Output" section of the XML Payload input queue when I launch a discovery. (I do not.)
2) There are similar issues with other probes that do not return output... and when I login to the box that is targeted for discovery... as the user configured for the discovery - I can get data back - but not when I do the discovery. i.e. the "df -kP" probe that is one of our OOB probes. When I use the "Test Probe" - it works - but not in the discovery.
3) It appears the "Test Probe" and the "Discovery" behave differently. What's different? How can I figure out why the probe failed in the discovery? I examined the /var/log/secure file to see if there were any sudoer problems - but did not see anything.

[doug_schulze]

First thought is have you included the probe in a Classifier? If you can PM me your instance I can take a look, it all works the same!

[steveshiflett]

Doug - I think you are right that the CI is not setup properly - and my guess is that the reason it works for some probes is that the Linux CI is included in the Unix CI. The confusion I have is in the development process of the probe - then running the discovery. Looks like if the probe is not assigned to the proper CI, I won't get the expected results...

[tony_fugere]

Hey Steve, I got the email you sent yesterday regarding this and everything appears to be functioning as expected. Let's chat over email and/or phone as soon as possible if you need more assistance here.

[steveshiflett]

Helpful suggestions to set up logging for probes on my CI:

Setting up logging for Unix
0. Go to Probes
1. select UNIX - Classify probe
2. For each Probe: ESX - OS and UNIX - OS add parameters: debug and debug ssh (see http://wiki.service-now.com/index.php?title=Discovery_Probes_and_Sensors)


ParameterDescription
debug Enables debug logging.
debug_ssh Enable J2SSH debug logging (into ssh.log, which can get very large).

3. Truncate log files
4. Restart mid server