SSH authentication or connection failure

pavanyuvi · ‎04-27-2018

Hi All,

When we are trying to run Quick Discovery . i am facing the below issue on classify phase. I think credentials part we do not have any issue because few Linux devices are discovered through discovery.

<results probe_time="27067" result_code="0">
<result id="6f10ed420a0a0b7e49052d83a32b586f" name="sh ${file:esx.sh}" order="1" topic="SSHCommand">
<results error="SSH authentication or connection failure" probe_time="18002" result_code="900000">
<result error="SSH authentication or connection failure">
<output/>
</result>
<parameters>
<parameter name="discover" value="CIs"/>
<parameter name="agent" value="mid.server.usavispsnsapp01"/>
<parameter name="use_class" value="discovery_classy_unix"/>
<parameter name="source" value="10.143.39.114"/>
<parameter name="priority" value="0"/>
<parameter name="probe" value="10e0eebd0a0a0b4f61f46a5027df7fb6"/>
<parameter name="command_to_run" value="sh ${file:esx.sh}"/>
<parameter name="port_probe" value="97ff2abd0a0a070300b7f37daa11a241"/>
<parameter name="port" value="22"/>
<parameter name="cidata" value="<CIData><data><fld name="ip_address">10.143.39.114</fld></data></CIData>"/>
<parameter name="used_by_discovery" value="true"/>
<parameter name="name" value="sh ${file:esx.sh}"/>
<parameter name="topic" value="SSHCommand"/>
<parameter name="esx.sh" value="#!/bin/sh # This command is rarely installed, so a Bourne shell script is used to squelch the exit status and sensor warning when not found. # tcsh doesn't squelch exist status codes within backticked statements echo `vmware -v 2>&1`"/>
</parameters>
</results>
</result>
<result id="e5e075a2a9fe1561018f2a9636d5ec39" name="uname -a" order="1" topic="SSHCommand">
<results error="SSH authentication or connection failure" probe_time="4306" result_code="900000">
<result error="SSH authentication or connection failure">
<output/>
</result>
<parameters>
<parameter name="discover" value="CIs"/>
<parameter name="agent" value="mid.server.usavispsnsapp01"/>
<parameter name="use_class" value="discovery_classy_unix"/>
<parameter name="source" value="10.143.39.114"/>
<parameter name="priority" value="0"/>
<parameter name="probe" value="10e0eebd0a0a0b4f61f46a5027df7fb6"/>
<parameter name="command_to_run" value="uname -a"/>
<parameter name="port_probe" value="97ff2abd0a0a070300b7f37daa11a241"/>
<parameter name="port" value="22"/>
<parameter name="cidata" value="<CIData><data><fld name="ip_address">10.143.39.114</fld></data></CIData>"/>
<parameter name="used_by_discovery" value="true"/>
<parameter name="name" value="uname -a"/>
<parameter name="topic" value="SSHCommand"/>
</parameters>
</results>
</result>
<result id="ab613cdf9f5312003cb191aec32e7044" name="sh ${file:f5.sh}" order="1" topic="SSHCommand">
<results error="SSH authentication or connection failure" probe_time="4306" result_code="900000">
<result error="SSH authentication or connection failure">
<output/>
</result>
<parameters>
<parameter name="discover" value="CIs"/>
<parameter name="agent" value="mid.server.usavispsnsapp01"/>
<parameter name="f5.sh" value="#!/bin/sh echo `tmsh show sys version 2>&1`"/>
<parameter name="use_class" value="discovery_classy_unix"/>
<parameter name="source" value="10.143.39.114"/>
<parameter name="priority" value="0"/>
<parameter name="probe" value="10e0eebd0a0a0b4f61f46a5027df7fb6"/>
<parameter name="command_to_run" value="sh ${file:f5.sh}"/>
<parameter name="port_probe" value="97ff2abd0a0a070300b7f37daa11a241"/>
<parameter name="port" value="22"/>
<parameter name="cidata" value="<CIData><data><fld name="ip_address">10.143.39.114</fld></data></CIData>"/>
<parameter name="used_by_discovery" value="true"/>
<parameter name="name" value="sh ${file:f5.sh}"/>
<parameter name="topic" value="SSHCommand"/>
</parameters>
</results>
</result>
<parameters>
<parameter name="agent" value="mid.server.usavispsnsapp01"/>
<parameter name="use_class" value="discovery_classy_unix"/>
<parameter name="source" value="10.143.39.114"/>
<parameter name="port_probe" value="97ff2abd0a0a070300b7f37daa11a241"/>
<parameter name="sys_id" value="7d4cafd86f355700ddfb8ebf2c3ee496"/>
<parameter name="sys_created_on" value="2018-04-27 10:05:40"/>
<parameter name="used_by_discovery" value="true"/>
<parameter name="state" value="ready"/>
<parameter name="discover" value="CIs"/>
<parameter name="response_to" value="094c6b5c6f355700ddfb8ebf2c3ee406"/>
<parameter name="priority" value="0"/>
<parameter name="agent_correlator" value="353cab986f355700ddfb8ebf2c3ee4cd"/>
<parameter name="probe" value="10e0eebd0a0a0b4f61f46a5027df7fb6"/>
<parameter name="sequence" value="1630690c1300000001"/>
<parameter name="port" value="22"/>
<parameter name="cidata" value="<CIData><data><fld name="ip_address">10.143.39.114</fld></data></CIData>"/>
<parameter name="name" value="UNIX - Classify"/>
<parameter name="topic" value="MultiProbe"/>
<parameter name="queue" value="output"/>
<parameter name="ecc_queue" value="7d4cafd86f355700ddfb8ebf2c3ee496"/>
</parameters>
</results>
 
Thanks,
Pavan

hannu · ‎04-28-2018

It is possible that the using the same credential some ip get discovered and some will show credential issue.

Did you try to test credential for this particular ip ??

karmeng · ‎04-30-2018

Hi,

From MID server box, have you try SSH to the target server and check if SSH can be established?

I suspect there might be some issues on the target server. One of the reason outline in below KB:

https://hi.service-now.com/kb_view.do?sysparm_article=KB0622607

Regards,

Kar Meng

manjusha · ‎05-01-2018

Hi ,

Please check the username you provided in credentials is root previledged user if not you have to

create a user with some root privileges not all.

please follow below document

https://www.liquidweb.com/kb/how-to-add-a-user-and-grant-root-privileges-on-ubuntu-14-04/

https://www.shellhacks.com/how-to-grant-root-access-user-root-privileges-linux/

Please mark if it is helpful

Regards,

Manjusha