Jenkins pipeline fails with hudson.plugins.git.gitexception returned status code 128 stderr: ssh_exchange_identification: read: Connection reset by peer

Using Jenkins
1

Hi Team,

I’m having issues all of a sudden with my Jenkins cannot execute any jobs. all my jobs are pipeline structured and run on agent machines. when I try to run the job I get the below error couldn’t get enough info online to fix or root cause of this.

Error:`Started by user mmmm
Running as mmmm
hudson.plugins.git.GitException: Command “git fetch --tags --force --progress --prune – origin +refs/heads/controller:refs/remotes/origin/controller” returned status code 128:
stdout:
stderr: ssh_exchange_identification: read: Connection reset by peer
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2842)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:2185)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:635)
at jenkins.plugins.git.GitSCMFileSystem$BuilderImpl.build(GitSCMFileSystem.java:406)
at jenkins.scm.api.SCMFileSystem.of(SCMFileSystem.java:219)
at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:118)
at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:70)
at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:312)
at hudson.model.ResourceController.execute(ResourceController.java:101)
at hudson.model.Executor.run(Executor.java:442)

[withMaven] downstreamPipelineTriggerRunListener - Failure to introspect build steps: java.io.IOException: CI-CD Job #2631 did not yet start
[withMaven] downstreamPipelineTriggerRunListener - Failure to introspect build steps: java.io.IOException: CI-CD Job #2631 did not yet start
Finished: FAILURE`

Jenkins setup:
Jenkins version: 2.401.3
Gitlab version: 1.7.15

2

The stack overflow article on that message contains several alternatives you can explore on the ssh server. Since it is a recent problem seen on all agents, it seems more likely that there was a change on the server than a change on all the agents.