[JIRA] (JENKINS-47660) ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException

2 views
Skip to first unread message

gjphilp@gmail.com (JIRA)

unread,
Jan 8, 2019, 2:25:02 PM1/8/19
to jenkinsc...@googlegroups.com
Gregor Philp commented on Bug JENKINS-47660
 
Re: ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException

ERROR we get after upgrading these plugins and trying to checkout in a pipeline job

 

17:52:07 Cloning the remote Git repository
17:52:07 ERROR: Error cloning remote repo 'origin'
17:52:07 hudson.plugins.git.GitException: java.io.IOException: Remote call on JNLP4-connect connection from ip-10-192-23-154.us-west-2.compute.internal/10.192.23.154:23354 failed
17:52:07 at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:169)
17:52:07 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
17:52:07 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
17:52:07 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
17:52:07 at java.lang.reflect.Method.invoke(Method.java:498)
17:52:07 at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:132)
17:52:07 at com.sun.proxy.$Proxy140.execute(Unknown Source)
17:52:07 at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1146)
17:52:07 at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1186)
17:52:07 at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120)
17:52:07 at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:90)
17:52:07 at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:77)
17:52:07 at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:51)
17:52:07 at hudson.security.ACL.impersonate(ACL.java:290)
17:52:07 at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:48)
17:52:07 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
17:52:07 at java.util.concurrent.FutureTask.run(FutureTask.java:266)
17:52:07 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
17:52:07 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
17:52:07 at java.lang.Thread.run(Thread.java:748)
17:52:07 Caused by: java.io.IOException: Remote call on JNLP4-connect connection from ip-10-192-23-154.us-west-2.compute.internal/10.192.23.154:23354 failed
17:52:07 at hudson.remoting.Channel.call(Channel.java:961)
17:52:07 at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:146)
17:52:07 ... 19 more
17:52:07 Caused by: java.lang.IllegalAccessError: tried to access field hudson.remoting.Channel.executor from class org.jenkinsci.remoting.util.AnonymousClassWarnings
17:52:07 at org.jenkinsci.remoting.util.AnonymousClassWarnings.check(AnonymousClassWarnings.java:65)
17:52:07 at org.jenkinsci.remoting.util.AnonymousClassWarnings$1.annotateClass(AnonymousClassWarnings.java:121)
17:52:07 at java.io.ObjectOutputStream.writeNonProxyDesc(ObjectOutputStream.java:1290)
17:52:07 at java.io.ObjectOutputStream.writeClassDesc(ObjectOutputStream.java:1231)
17:52:07 at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1427)
17:52:07 at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
17:52:07 at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:348)
17:52:07 at hudson.console.ConsoleNote.encodeToBytes(ConsoleNote.java:185)
17:52:07 at hudson.console.ConsoleNote.encode(ConsoleNote.java:211)
17:52:07 at hudson.plugins.timestamper.TimestampNotesOutputStream.eol(TimestampNotesOutputStream.java:70)
17:52:07 at hudson.console.LineTransformationOutputStream.eol(LineTransformationOutputStream.java:60)
17:52:07 at hudson.console.LineTransformationOutputStream.write(LineTransformationOutputStream.java:56)
17:52:07 at hudson.console.LineTransformationOutputStream.write(LineTransformationOutputStream.java:74)
17:52:07 at java.io.PrintStream.write(PrintStream.java:480)
17:52:07 at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)
17:52:07 at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:291)
17:52:07 at sun.nio.cs.StreamEncoder.flushBuffer(StreamEncoder.java:104)
17:52:07 at java.io.OutputStreamWriter.flushBuffer(OutputStreamWriter.java:185)
17:52:07 at java.io.PrintStream.newLine(PrintStream.java:546)
17:52:07 at java.io.PrintStream.println(PrintStream.java:807)
17:52:07 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:589)
17:52:07 at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153)
17:52:07 at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146)
17:52:07 at hudson.remoting.UserRequest.perform(UserRequest.java:207)
17:52:07 at hudson.remoting.UserRequest.perform(UserRequest.java:53)
17:52:07 at hudson.remoting.Request$2.run(Request.java:358)
17:52:07 at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
17:52:07 at java.util.concurrent.FutureTask.run(FutureTask.java:266)
17:52:07 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
17:52:07 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
17:52:07 at hudson.remoting.Engine$1$1.run(Engine.java:98)
17:52:07 ... 1 more
17:52:07 Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from ip-10-192-23-154.us-west-2.compute.internal/10.192.23.154:23354
17:52:07 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741)
17:52:07 at hudson.remoting.UserResponse.retrieve(UserRequest.java:389)
17:52:07 at hudson.remoting.Channel.call(Channel.java:955)
17:52:07 at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:146)
17:52:07 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
17:52:07 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
17:52:07 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
17:52:07 at java.lang.reflect.Method.invoke(Method.java:498)
17:52:07 at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:132)
17:52:07 at com.sun.proxy.$Proxy140.execute(Unknown Source)
17:52:07 at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1146)
17:52:07 at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1186)
17:52:07 at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120)
17:52:07 at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:90)
17:52:07 at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:77)
17:52:07 at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:51)
17:52:07 at hudson.security.ACL.impersonate(ACL.java:290)
17:52:07 at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:48)
17:52:07 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
17:52:07 at java.util.concurrent.FutureTask.run(FutureTask.java:266)
17:52:07 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
17:52:07 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
17:52:07 ... 1 more
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // node
[Pipeline] }
[Pipeline] // timestamps
[Pipeline] End of Pipeline
ERROR: Error cloning remote repo 'origin'
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

gjphilp@gmail.com (JIRA)

unread,
Jan 8, 2019, 2:41:01 PM1/8/19
to jenkinsc...@googlegroups.com

This is not to do with a large repository or timeout.  The repo is extremely small I am testing with and the job fails in just over 20 seconds.  I remove that plugin and the job works fine.

timestamps {
node ('ECS-CO7-LATEST') {
stage ('Checkout')

{ checkout([$class: 'GitSCM', branches: [[name: '*/master']], doGenerateSubmoduleConfigurations: false, extensions: [], submoduleCfg: [], userRemoteConfigs: [[credentialsId: '*******, url: 'g...@github.move.com:IT-Operations/aws-certificates.git']]]) }

stage ('sleep')

{ sh ''' sleep 20 ''' }

stage ('Clean')

{ cleanWs() }

}
}

mark.earl.waite@gmail.com (JIRA)

unread,
Jan 8, 2019, 2:57:04 PM1/8/19
to jenkinsc...@googlegroups.com

Gregor Philp the original bug report is related to a large repository and a timeout. The stack trace you're reporting is significantly different from the stack trace in the description of this bug report. The differences are evident because your stack trace does not include the message:

ERROR: Timeout after 10 minutes

I suspect you'll be better served by first asking for help on one of the chat locations, or on the Jenkins users mailing list. They will tend to ask you questions that will help you identify the problem and will help you decide if a bug report is needed. Some of the questions that they will probably ask in those places will include things like:

  • What versions of Jenkins and plugins were you running when it worked?
  • What versions of Jenkins and plugins were you running after it stopped working?
  • What operating system is running Jenkins?
  • What operating system is running the agent where the failure happens?
  • Is the agent connected to the master with ssh, JNLP, or some other way?
  • Does the failure happen on multiple agents?

The chat and the mailing list have many more readers than individual bug reports, especially individual bug reports that are already resolved.

If you don't find an answer through chat and the mailing list, you'll need to open a new bug report. If you open a new bug report, please be sure to include answers to those questions and the other items identified in "How to report an issue".

gjphilp@gmail.com (JIRA)

unread,
Jan 8, 2019, 6:38:02 PM1/8/19
to jenkinsc...@googlegroups.com

ok I will try that.  This was a new bug I filed this morning so I don't know how it got merged onto this one.

I created a new issue.  It is breaking or production stack with over 700 jobs and over 400 users

gjphilp@gmail.com (JIRA)

unread,
Jan 8, 2019, 7:01:09 PM1/8/19
to jenkinsc...@googlegroups.com

Mark Waite

ok this is not easy.

I've tried contacting both the users and dev email addresses on the  Jenkins users mailing list and both just get returned emails saying the group does not exist.

What is the jenkins support mailing list?

mark.earl.waite@gmail.com (JIRA)

unread,
Jan 8, 2019, 7:10:02 PM1/8/19
to jenkinsc...@googlegroups.com

Send an e-mail message to jenkins...@googlegroups.com . Due to spam, your first posting to the mailing list will be held until it is approved.

If that doesn't work, then connect to Gitter

mark.earl.waite@gmail.com (JIRA)

unread,
Jan 8, 2019, 7:11:02 PM1/8/19
to jenkinsc...@googlegroups.com
Mark Waite edited a comment on Bug JENKINS-47660
Send an e-mail message to [jenkins...@googlegroups.com|mailto:jenkins...@googlegroups.com] .  Due to spam, your first posting to the mailing list will be held until it is approved.

If that doesn't work, then connect to [Gitter|https://gitter.im/jenkinsci/jenkins]

The users mailing list is where users support each other.  Internet Relay Chat is also used so that users can support each other.

CloudBees also sells support contracts for Jenkins for those that need the power of a commercial support team.

gjphilp@gmail.com (JIRA)

unread,
Jan 8, 2019, 7:27:03 PM1/8/19
to jenkinsc...@googlegroups.com

yeah thats the one I sent to and also tried to subscribe like it mentioned.  Both failed telling me the group does not exist.

Now I guess I have to try gitter

mark.earl.waite@gmail.com (JIRA)

unread,
Jan 8, 2019, 8:41:02 PM1/8/19
to jenkinsc...@googlegroups.com

If neither of those work, then please open a bug report with the answers to my questions. I don't know if I will have time to help you, but that's probably better than nothing.

mark.earl.waite@gmail.com (JIRA)

unread,
Oct 22, 2019, 9:30:48 PM10/22/19
to jenkinsc...@googlegroups.com
Mark Waite closed an issue as Not A Defect
 
Jenkins / Bug JENKINS-47660
Change By: Mark Waite
Status: Resolved Closed
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages