SSH credential fails in discovery but passes credential test

[User166533]

We have an SSH credential that works to login from command line to target host. It also passes the 'test credential' test from the instance to the same target host. It works to discovery several thousand other hosts. But it fails in actual discovery job.

The ECC queue shows: SSH authentication or connection failure and the system is not classified

[bernyalvarado]

Hi Sean,

What type of device are you trying to discover?

If it's a network type of device such like a load balancer, router, etc... then make sure you also include the IPs of the MID Servers to the ACLs within the Network devices.

Thanks,

Berny

[User166533]

The device is a LINUX server. The credential works fine using ssh from another LINUX server and it also passes the 'test credential' in the credentials form in ServiceNow.

[Dave Smith1]

Can you try an SSH connection from the MID just to see if there's nothing blocking further access?

It does sound strange if it passes the credential check but then not get any further.

[User166533]

Yes, this does work also from PuTTY client on a MID server, but not discovery from the midserver:

FROM PUTTY:
login as: sacmlinux

Authenticating with public key "sacmlinux" from agent

Welcome to Ubuntu 16.04.2 LTS (GNU/Linux 4.4.0-79-generic x86_64)

* Documentation:   https://help.ubuntu.com

* Management:         https://landscape.canonical.com

* Support:               https://ubuntu.com/advantage

Welcome to Alibaba Cloud Elastic Compute Service !

Last login: Fri Oct 13 23:08:31 2017 from <MID SERVER IP>

sacmlinux@cnhszhdcs1vup16:~$

MID SERVER AGENT LOG:

10/16/17 13:35:30 (738) Worker-Interactive:MultiProbe Worker starting: MultiProbe source: 10.65.192.75

10/16/17 13:35:30 (738) Worker-Interactive:MultiProbe Worker starting: SSHCommand source: 10.65.192.75

10/16/17 13:35:30 (738) Worker-Interactive:MultiProbe Creating cache entry: SSH://10.65.192.75:22

10/16/17 13:35:30 (738) Worker-Interactive:MultiProbe Waiting for connection semaphore

10/16/17 13:35:30 (738) Worker-Interactive:MultiProbe Obtained connection semaphore

10/16/17 13:35:30 (738) Worker-Interactive:MultiProbe Connection taken from pool

10/16/17 13:35:33 (489) Worker-Interactive:MultiProbe Waiting for connection semaphore

10/16/17 13:35:33 (489) Worker-Interactive:MultiProbe Obtained connection semaphore

10/16/17 13:35:33 (489) Worker-Interactive:MultiProbe Connection taken from pool

10/16/17 13:35:34 (207) Worker-Interactive:MultiProbe Worker completed: SSHCommand source: 10.65.192.75 time: 0:00:03.469

10/16/17 13:35:34 (207) Worker-Interactive:MultiProbe Worker starting: SSHCommand source: 10.65.192.75

10/16/17 13:35:34 (207) Worker-Interactive:MultiProbe Waiting for connection semaphore

10/16/17 13:35:34 (207) Worker-Interactive:MultiProbe Obtained connection semaphore

10/16/17 13:35:34 (207) Worker-Interactive:MultiProbe Connection taken from pool

10/16/17 13:35:36 (754) ConnectionCacheTickler Monitoring active connections

10/16/17 13:35:36 (942) Worker-Interactive:MultiProbe Creating cache entry: SSH://10.65.192.75:22

10/16/17 13:35:36 (942) Worker-Interactive:MultiProbe Waiting for connection semaphore

10/16/17 13:35:36 (942) Worker-Interactive:MultiProbe Obtained connection semaphore

10/16/17 13:35:36 (942) Worker-Interactive:MultiProbe Connection taken from pool

10/16/17 13:35:37 (660) Worker-Interactive:MultiProbe Worker completed: SSHCommand source: 10.65.192.75 time: 0:00:03.453

10/16/17 13:35:37 (660) Worker-Interactive:MultiProbe Worker starting: SSHCommand source: 10.65.192.75

10/16/17 13:35:37 (660) Worker-Interactive:MultiProbe Waiting for connection semaphore

10/16/17 13:35:37 (660) Worker-Interactive:MultiProbe Obtained connection semaphore

10/16/17 13:35:37 (660) Worker-Interactive:MultiProbe Connection taken from pool

10/16/17 13:35:40 (410) Worker-Interactive:MultiProbe Waiting for connection semaphore

10/16/17 13:35:40 (410) Worker-Interactive:MultiProbe Obtained connection semaphore

10/16/17 13:35:40 (410) Worker-Interactive:MultiProbe Connection taken from pool

10/16/17 13:35:41 (129) Worker-Interactive:MultiProbe Worker completed: SSHCommand source: 10.65.192.75 time: 0:00:03.469

10/16/17 13:35:41 (145) Worker-Interactive:MultiProbe Enqueuing: D:\ServiceNow\PRD\work\monitors\ECCSender\output_0\ecc_queue.cc068252db3dc38031fa766eaf961948.xml

10/16/17 13:35:41 (145) Worker-Interactive:MultiProbe Worker completed: MultiProbe source: 10.65.192.75 time: 0:00:10.391

In the ECC input from UNIX discovery:
<result id="e5e075a2a9fe1561018f2a9636d5ec39" name="uname -a" order="1" topic="SSHCommand">
  <results error="SSH authentication or connection failure: The connection did not complete" probe_time="3453" result_code="900000">
      <result error="SSH authentication or connection failure: The connection did not complete">
<output/>
</result>

Same MID server and target