Linux Discovery fails identification, error in Linux server pattern.

[Mark Todorov]

Dear Community, 

After scanning 3 UNIX devices, 2 of them are successfully discovered and one fails the identification phase. 

Discovery log spits error with exploring the Linux server pattern.

Providing the error message, I couldn't find any similar error here or online, so any advice would be helpful. 

Step 3.2.83 is failing but I cannot find any connection why the whole Discovery fails. 

Credentials are good as usual. validated. Any idea what might be the cause of this?

Thanks in advance.

Mark

[SiD2]

Hi @Mark Todorov 

I suggest verifying if your Linux pattern or the shared library pattern where this step resides is OOB and not customized.

If it's OOB and you still see this, it could be something specific to your env or a particular host. The above step has an EVAL script, and possibly due to some reason, the values are not populated for some variables, causing such errors.

I suggest debugging prior steps to know why some data is not fetched, which it has to ideally, leading to such an exception.

Usually, the whole discovery fails in such exceptions, which is expected behavior.

[Mark Todorov]

Hello, 

Sorry for the late reply. 

This step is the only one shown as also causing issues to the pattern. I tested a lot of other steps with debugging but cannot orient myself what might be the general issue.  Do you know by any chance which other steps might be connected with this? The error is observed for let's say 1/4 of the scanned IPs. Any specific configuration that might be causing this? 

I got the same result for a CI that is successfully updated, but the route interface step is successful. Seems that I am receiving an empty value for some devices and others are good.

--> device with no issues

[SiD2 · Accepted solution]

Hi @Mark Todorov 

The pattern might have been customized else we wouldn't get such syntax errors per your screenshot, or else there could be some valid scenario where the commands are not working on specific hosts.

I suggest checking if the pattern and corresponding shared library where this step exists are not customized. If not customized better, raise a support ticket so someone can check directly from your instance and provide any assistance.

[Mark Todorov]

Thank you for the reply !