[
https://issues.jenkins-ci.org/browse/JENKINS-11576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Seth Goings closed JENKINS-11576.
---------------------------------
Assignee: Seth Goings
Resolution: Won't Fix
This is not an issue with Jenkins - in my corporate environment we have jobs
that are using Git and Jenkins in two ways:
* Using the git plugin (https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin)
* Using a bash based deployment tool that can checkout code from Git for you
and build/deploy code.
We've recently had jobs of both implementation styles fail, and have done some
investigation and found that the MaxStartups value (defaults to 10) in
sshd_config on our git server needed to be increased. See "MaxStartups" here:
http://www.linuxmanpages.com/man5/sshd_config.5.php
After increasing the MaxStartups value, we haven't seen the issue again. In any
case, this issue is not a Jenkins bug.
> Getting "returned status code 128: ssh_exchange_identification" error
> sometimes
> -------------------------------------------------------------------------------
>
> Key: JENKINS-11576
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11576
> Project: Jenkins
> Issue Type: Bug
> Components: git
> Affects Versions: current
> Environment: Windows Server 2003, IIS
> Reporter: Murali Srinivasan
> Assignee: Seth Goings
> Priority: Blocker
> Labels: exception, git, jenkins, ssh_exchange_identification
> Fix For: current
>
>
> I have Jenkins setup in Windows Server machine and the job will trigger the
> build at specified time. Sometimes the job fails with the below exception and
> when I manually trigger it again it will work fine. I read somewhere that
> moving id_rsa.* file to GIT installation folder will fix the issue, but it
> didn't improve in my case. It would be great if there is a way to fix this
> issue.
> ERROR: Problem fetching from origin / origin - could be unavailable.
> Continuing anyway
> ERROR: (Underlying report) : Error performing command: E:\git\bin\git.exe
> fetch -t gitosis@****.****.com:ServiceApp +refs/heads/*:refs/remotes/origin/*
> Command "E:\git\bin\git.exe fetch -t gitosis@****.****.com:ServiceApp
> +refs/heads/*:refs/remotes/origin/*" returned status code 128:
> ssh_exchange_identification: Connection closed by remote host
> fatal: The remote end hung up unexpectedly
> ERROR: Could not fetch from any repository
> FATAL: Could not fetch from any repository
> hudson.plugins.git.GitException: Could not fetch from any repository
> at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1008)
> at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:968)
> at hudson.FilePath.act(FilePath.java:785)
> at hudson.FilePath.act(FilePath.java:767)
> at hudson.plugins.git.GitSCM.checkout(GitSCM.java:968)
> at hudson.model.AbstractProject.checkout(AbstractProject.java:1193)
> at
> hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:567)
> at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:455)
> at hudson.model.Run.run(Run.java:1404)
> at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
> at hudson.model.ResourceController.execute(ResourceController.java:88)
> at hudson.model.Executor.run(Executor.java:230)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
