Can't Discover Linux Server because it doesn't find credentials...Even though I provided them

Fares1 · ‎01-09-2019

Hi!

My problem is in the title of the topic, I've provided SSH Credentials to my Kingston ServiceNow instance and I've validated them by testing them, but whenever I try to discover the linux server, Discovery logs tell me that they couldn't find any credentials associated with them (even though, as I said, I've provided them) and can't finish classifying the CI.

I have already successfully discovered this CI with my other London instance, without any issues and I didn't need to provide extra information in that instance.

Any suggestions to what to do next?

Thanks in advance,

Fares

tim_broberg · ‎01-09-2019

Richard hits a lot of great points.

A few other things to look at that may help you debug:

The ecc_queue input for SSHCommand's that fail to authenticate will have a credential debug section that indicates what credentials were tried and such.
One difference between credential test and SSHCommand is that Credential Test tries only one credential. Sometimes, the ssh server loses patience when we try a large number of credentials.
If all else fails, once you switch to sncssh, you can add a debug = true parameter to your probe (or enable ssh debug for the mid) and see everything that's going on with the ssh connection. It's a lot of information to filter through, but the truth is in there.

- Tim.

View solution in original post

richardbrounste · ‎01-09-2019

In the Credential, check that it applies to "All MID servers" or at least the specific MID Server that is being chosen for the IP Address for this Discovery. Make sure the Credential "Active" is checked on.

On the MID Server, make sure the IP Ranges include this IP Address. Make sure the Applications include All or at least Discovery. Make sure the Capabilities include SSH or ALL.

Fares1 · ‎01-09-2019

Thanks for the answer Richard.

I've used both choices for MID Servers in the Credentials area.

I've made sure to check IP Ranges, Applications and Capabilities and those are all well configured.

Still denies that there aren't any credentials associated with the Linux Server.

richardbrounste · ‎01-09-2019

I recommend that you open a HI ticket. Someone needs to analyze what is going on with this Discovery. There are so many small settings that can mess things up.

robertgeen · ‎01-09-2019

Just a quick check does all your mid servers have the Discovery capability? I've never seen it give you a credential error like that when it doesn't but it could be misleading.