Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-63621

Node: SSH authentication succeeded, but still cannot connect to agent machine

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Critical
    • Resolution: Unresolved
    • Component/s: _unsorted
    • Labels:
      None
    • Environment:
      jenkins.war
    • Similar Issues:

      Description

       

      Windows child nodes are set up on the MAC machine

       

      SSHLauncher{host='192.168.0.140', port=22, credentialsId='8aa1cda1-c3b2-4608-b6ab-156eb5ac7b18', jvmOptions='', javaPath='', prefixStartSlaveCmd='', suffixStartSlaveCmd='', launchTimeoutSeconds=60, maxNumRetries=10, retryWaitTime=15, sshHostKeyVerificationStrategy=hudson.plugins.sshslaves.verifiers.NonVerifyingKeyVerificationStrategy, tcpNoDelay=true, trackCredentials=true}
      [09/08/20 14:21:56] [SSH] Opening SSH connection to 192.168.0.140:22.
      [09/08/20 14:21:56] [SSH] WARNING: SSH Host Keys are not being verified. Man-in-the-middle attacks may be possible against this connection.
      [09/08/20 14:21:57] [SSH] Authentication success
      SSH connection reports a garbage before a command execution.
      Check your .bashrc, .profile, and so on to make sure it is quiet.
      The received junk text is as follows:
      Active code page: 65001

      null
      [09/08/20 14:21:57] Launch failed - cleaning up connection

        Attachments

          Activity

          ven ven wang created issue -
          ven ven wang made changes -
          Field Original Value New Value
          Description SSHLauncher\{host='192.168.0.140', port=22, credentialsId='8aa1cda1-c3b2-4608-b6ab-156eb5ac7b18', jvmOptions='', javaPath='', prefixStartSlaveCmd='', suffixStartSlaveCmd='', launchTimeoutSeconds=60, maxNumRetries=10, retryWaitTime=15, sshHostKeyVerificationStrategy=hudson.plugins.sshslaves.verifiers.NonVerifyingKeyVerificationStrategy, tcpNoDelay=true, trackCredentials=true}
          [09/08/20 14:21:56] [SSH] Opening SSH connection to 192.168.0.140:22.
          [09/08/20 14:21:56] [SSH] WARNING: SSH Host Keys are not being verified. Man-in-the-middle attacks may be possible against this connection.
          [09/08/20 14:21:57] [SSH] Authentication success
          SSH connection reports a garbage before a command execution.
          Check your .bashrc, .profile, and so on to make sure it is quiet.
          The received junk text is as follows:
          Active code page: 65001

          null
          [09/08/20 14:21:57] Launch failed - cleaning up connection
           

          Windows child nodes are set up on the MAC machine

           

          SSHLauncher\{host='192.168.0.140', port=22, credentialsId='8aa1cda1-c3b2-4608-b6ab-156eb5ac7b18', jvmOptions='', javaPath='', prefixStartSlaveCmd='', suffixStartSlaveCmd='', launchTimeoutSeconds=60, maxNumRetries=10, retryWaitTime=15, sshHostKeyVerificationStrategy=hudson.plugins.sshslaves.verifiers.NonVerifyingKeyVerificationStrategy, tcpNoDelay=true, trackCredentials=true}
           [09/08/20 14:21:56] [SSH] Opening SSH connection to 192.168.0.140:22.
           [09/08/20 14:21:56] [SSH] WARNING: SSH Host Keys are not being verified. Man-in-the-middle attacks may be possible against this connection.
           [09/08/20 14:21:57] [SSH] Authentication success
           SSH connection reports a garbage before a command execution.
           Check your .bashrc, .profile, and so on to make sure it is quiet.
           The received junk text is as follows:
           Active code page: 65001

          null
           [09/08/20 14:21:57] Launch failed - cleaning up connection
          ianw Ian Williams made changes -
          Issue Type Task [ 3 ] Bug [ 1 ]
          slide_o_mix Alex Earl made changes -
          Summary Node: SSH authentication succeeded, but still cannot connect to slave machine Node: SSH authentication succeeded, but still cannot connect to agent machine
          Hide
          slide_o_mix Alex Earl added a comment -

          This usually happens because Powershell or your selected shell is outputing something during loading it's profile. Can you SSH into the machine with the same user account and see if something like that is happening?

          Show
          slide_o_mix Alex Earl added a comment - This usually happens because Powershell or your selected shell is outputing something during loading it's profile. Can you SSH into the machine with the same user account and see if something like that is happening?

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            ven ven wang
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated: