SSH authentication to nodes fails - "Failed: ConnectionFailure: Connection timed out: connect"

[Andrii Kalytiuk]

Hi,

Is there any kind of detailed log in Rundeck to track down reasons of problems of SSH authentication to nodes? I need help to configure Rundeck for SSH authentication to nodes.

At the moment at attempt to run command on node - I get error:

"Failed: ConnectionFailure: Connection timed out: connect"

Rundeck server runs on Windows Server 2012 machine.
As a node Windows 7 32-bit machine is used.

KymM Telnet/SSH server runs on node machine (Windows 7 32-bit).
I can log in to node using Putty via SSH with public/private key authentication (generated keys with PuTTYGen - .ppk file stores private key).

I have converted .ppk file of private key to OpenSSH format with PuTTYGen and saved it as file in Rundeck project directory.

In project.properties file I have:

project.ssh-authentication=privateKey
project.ssh-keypath=C\:\\Rundeck\\projects\\... - path to private key file in OpenSSH format

Still when I navigate to 'Nodes' in Rundeck and run a command on remote Windows 7 32-bit node - I get 'Connection timed out' error.

In framework.properties file I have default setting for infinite SSH timeout:

framework.ssh.timeout = 0

So I don't have a clue what can be reason of error and what tools I can use to debug for the source of an error. Look for any kind of hint.

Thanks.
Regards.
Andrii Kalytiuk

[Andrii Kalytiuk]

I get 'Connection timed out' error in ~20 seconds after starting command on remote node.
In logs of SSH server on remote node there is no entries even about log-in attempt.

[Andrii Kalytiuk]

Update of resource file with full domain name have enabled successful public-key authentication to remote node.
Full domain name - host-name.domain-name.com - was specified in resources file of project. After fix of resources file - public key authentication worked successfully (according to logs of KTS server) for private key in both .ppk and OpenSSH format.

Nevertheless - execution of any command on node results into following output:

Remote command failed with exit status -1

Failed: NonZeroResultCode: Remote command failed with exit status -1

[Andrii Kalytiuk]

Another strange thing - is output '0J' that is always shown before following error is displayed after nearly 5 minutes:

Remote command failed with exit status -1

Failed: NonZeroResultCode: Remote command failed with exit status -1