Custom probe/sensor classifies but doesn't identify

[scott111]

Writing custom probe for HP Enclosure device. My custom probe allows unsupported shells and does "show enclosure info" ssh command and gets back plenty of info to classify. Discovery output using custom probe says it classifies based on ssh output but then it goes ahead and tries SNMP to classify and fails. I've read that any sensor failure marks the whole discovery as a failure. Discovery output:

SNMP Classify                   SNMP probe timed out. Target is either unreachable or there are no valid credentials for it.

SNMP Classify                   Active, couldn't classify, now finished

UNIX Classify                   Unsupported shell, '$0', and probe parameter 'allow_unsupported_shells' is set to 'false'. Supported shells are [ksh, sh, bash, tcsh, csh]

UNIX Classify                   Active, couldn't classify, now finished

UNIX Classify                   Active, couldn't classify, now finished

UNIX Classify                   Classified, now Identifying

Shazzam                                   Active, now Classifying

ShazzamLaunch         MID midhost.com discovering 10.xx.xx.xx

Discovery                             Discovery started

Debug "gs.log" statements print from my classifier and from custom sensor but not from my identifier.

[venkatiyer1]

Hi Scott,

In the screenshot you have attached above for UNIX classification i dont see a trigger probe attached to it. Do you have one attached to it during classification phase? May be this wiki article will aid you.

Horizontal discovery process flow

[scott111]

I looked at that link on "horizontal discovery" and it applies to Istanbul. I have Fuji. But i did get me thinking:   must my classifier trigger an "identifier probe"?

[rajeevlochan82]

Can you check your ECC queue to see if you getting name contains bladesystem in your ecc

[scott111]

Did not see "name contains bladesystem" in ECC queue but I assume my classifier worked. This would suggest it found correct class for target:

Look at "correct answer" in this thread. It looks very much like the same issue but his back-ticks solution did not work for me.

https://community.servicenow.com/thread/154583?q=Custom%20probe/sensor%20classifies%20but%20doesn%27...

[rajeevlochan82]

check the 6 ECC queue entries....