Failed to connect to the host via ssh: OpenSSH_7.4p1, OpenSSL 1.0.2k-fips 26 Jan 2017

Archives Ansible Project
1

Hi Team,

i was trying to create ssh connection through tower for one server 162.xx.xx.xx
but got below error

when i try to do it manually ssh connection , it is successful
without any error.

fatal: [server.xx.org]: FAILED! => {
“ansible_facts”: {},
“changed”: false,
“failed_modules”: {
“setup”: {
“failed”: true,
“module_stderr”: “OpenSSH_7.4p1, OpenSSL 1.0.2k-fips 26 Jan 2017\r\ndebug1: auto-mux: Trying existing master\r\ndebug2: fd 3 setting O_NONBLOCK\r\ndebug2: mux_client_hello_exchange: master version 4\r\ndebug3: mux_client_forwards: request forwardings: 0 local, 0 remote\r\ndebug3: mux_client_request_session: entering\r\ndebug3: mux_client_request_alive: entering\r\ndebug3: mux_client_request_alive: done pid = 35\r\ndebug3: mux_client_request_session: session request sent\r\ndebug1: mux_client_request_session: master session id: 2\r\ndebug3: mux_client_read_packet: read header failed: Broken pipe\r\ndebug2: Received exit status from master 1\r\nShared connection to 162.xx.xx.xx closed.\r\n”,
“module_stdout”: “\r\n”,
“msg”: “MODULE FAILURE\nSee stdout/stderr for the exact error”,
“rc”: 1
}
},
“msg”: “The following modules failed to execute: setup\n”
}

<162.xx.xx.xx> Failed to connect to the host via ssh: OpenSSH_7.4p1, OpenSSL 1.0.2k-fips 26 Jan 2017

66
debug1: auto-mux: Trying existing master

67
debug2: fd 3 setting O_NONBLOCK

68
debug2: mux_client_hello_exchange: master version 4

69
debug3: mux_client_forwards: request forwardings: 0 local, 0 remote

70
debug3: mux_client_request_session: entering

71
debug3: mux_client_request_alive: entering

72
debug3: mux_client_request_alive: done pid = 35

73
debug3: mux_client_request_session: session request sent

74
debug1: mux_client_request_session: master session id: 2

75
debug3: mux_client_read_packet: read header failed: Broken pipe

76
debug2: Received exit status from master 1

77
Shared connection to 162.xx.xx.xx closed.

2

Hi Team,

I’m also facing same issue which was reported by javed khan Siddque in the previous mail.

Can some one help me on this to get resolve from Tower.

Regards,
Prakash A

3

HI,

SSH failures can be for so many different reasons and for that reason is not easy to say from your output as SSH does not want to give away the the reasons for failure to a potential intruder, I would log on to your target and check your logs in /var/log/ likely messages or secure would tell you why it could not log in, or at least give you an indication as to why. Run a tail -f on the logs while you try your adhoc command or playbook.

Regards

4

Hi Stephen,

Thanks for your reply.

Sure, i’ll share those details or logs soon from “/var/log/ likely messages or secure” as suggested.

Regards,
Prakash.A

5

I noticed that issue got auto resolved after few days.
only changes is those messages still appears but as a WARNING not as a FATAL ERROR.