Discovery error-No results returned from probe

[salu]

Hello all,

Can someone please help me to understand this error?

[tim_broberg]

It's not an error. It's a warning. :^)

It simply indicates that the probe has no output, which just happens for some probes on some devices.

I'm afraid discovery log can be on the chatty side sometimes.
    - Tim.

[Bogdan Moldove5]

Hi Salu,

1. Your target IP has the HTTP port enabled and active from SN perspective (hence the message Active...)

2. This triggers the Classifier probe "HTTP - Classify" which returns an empty result (</results) (hence the error "No results returned from the probe). This may happen if the port is not bound to a known Web service the ServiceNow probe is quering for. Network Appliances that run custom OS tend to do that.

3. Lastly the entire classification fails because the only scanned port that returned active (HTTP) could not be classified (hence ...couldn;t classify, now finished) 

4. Because Credential based discovery has now failed and Credentialless Discovery is enabled (strongly recommend to disable it ) the Credentialless Discovery is triggered but it's probably misconfigured hence you see the message (Failed Exploring CI Patterb, Pattern Name : Credentialless Discovery....)

Let me know if this helped.

Bogdan 

[Anuraag]

Hello Bogdan,

I am facing a similar issue when scanning for ESX servers but it is failing at HTTPClassyProbe "No results returned from probe"

can you please suggest a solution for this error?

here's the screenshot of discovery log and ECC queue

[Bogdan Moldove5]

Hi Anuraag,

The ESX servers are not discoverable directly but via their associated vCenter server. Once you discovered the vCenter all the ESX hosts, virtual machines, datastores, everything will be populated in CMDB.

Hope this helps,

Bogdan