[JIRA] (JENKINS-54008) Loading library fails - Error fetching remote repo 'origin'

17 views
Skip to first unread message

emtrout33@yahoo.se (JIRA)

unread,
Oct 11, 2018, 6:43:03 AM10/11/18
to jenkinsc...@googlegroups.com
m f updated an issue
 
Jenkins / Bug JENKINS-54008
Loading library fails - Error fetching remote repo 'origin'
Change By: m f
Summary: Loading Loading library fails -  Error fetching remote repo 'origin'
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

emtrout33@yahoo.se (JIRA)

unread,
Oct 11, 2018, 6:44:02 AM10/11/18
to jenkinsc...@googlegroups.com
m f updated an issue
Loading shared library via Jenkinsfile. And it It works for a while, but then the error "ERROR: Error fetching remote repo 'origin'" is generated. The only way to remove the fault is to *clear the workspace for the job.* 

 

*Jenkinsfile:*

library identifier: 'myshared@master', retriever: modernSCM([$class: 'GitSCMSource',
remote: 'https://xxxxxxxx/pipeline-shared/jenkins-pipeline-shared',
credentialsId: 'MY_CREDENTIALS',
branch: 'master',
excludes: '',
includes: '*',
rawRefSpecs: 'refs/heads/master'
]) _

 

*Error log:*

Loading library myshared@master
Attempting to resolve master from remote references...
 > git --version # timeout=10
using GIT_ASKPASS to set credentials CREDENTIALS  > git ls-remote [ https://xxxxxxxx/pipeline-shared/jenkins-pipeline-shared# ] timeout=10
Found match: refs/heads/master revision 9b1346587485736e0d09c107464b73efdd3088ac
 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url [ https://xxxxxxxx/pipeline-shared/jenkins-pipeline-shared ] # timeout=10
Fetching without tags
Fetching upstream changes from [ https://xxxxxxxx/pipeline-shared/jenkins-pipeline-shared ]
 > git --version # timeout=10
using GIT_ASKPASS to set credentials CREDENTIALS
 > git fetch --no-tags --progress [ https://xxxxxxxx/pipeline-shared/jenkins-pipeline-shared ] +refs/heads/*:refs/remotes/origin/*
ERROR: Error fetching remote repo 'origin'
hudson.plugins.git.GitException: Failed to fetch from [ https://xxxxxxxx/pipeline-shared/jenkins-pipeline-shared ]
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:888)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1155)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1186)
at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120)
at org.jenkinsci.plugins.workflow.libs.SCMSourceRetriever.doRetrieve(SCMSourceRetriever.java:116)
at org.jenkinsci.plugins.workflow.libs.SCMSourceRetriever.retrieve(SCMSourceRetriever.java:86)
at org.jenkinsci.plugins.workflow.libs.LibraryAdder.retrieve(LibraryAdder.java:157)
at org.jenkinsci.plugins.workflow.libs.LibraryStep$Execution.run(LibraryStep.java:207)
at org.jenkinsci.plugins.workflow.libs.LibraryStep$Execution.run(LibraryStep.java:156)
at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47)
at hudson.security.ACL.impersonate(ACL.java:290)
at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: hudson.plugins.git.GitException: Command "git fetch --no-tags --progress [ https://xxxxxxxx/pipeline-shared/jenkins-pipeline-shared ] +refs/heads/*:refs/remotes/origin/*" returned status code 255:
stdout: 
stderr: error: cannot open .git/FETCH_HEAD: Invalid argument
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2016)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1735)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:72)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:420)
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:886)
... 16 more
ERROR: Error fetching remote repo 'origin'

 

 

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

unread,
Oct 11, 2018, 9:07:02 AM10/11/18
to jenkinsc...@googlegroups.com
Mark Waite commented on Bug JENKINS-54008
 
Re: Loading library fails - Error fetching remote repo 'origin'

The stack trace indicates that command line git failed and reported the error:

error: cannot open .git/FETCH_HEAD: Invalid argument

The command line git source code didn't show any obvious cases of a direct display of 'Invalid argument'. I assume that message is the result of a call to `perror` for an errno return value of `EINVAL`. Unfortunately, the command line git message doesn't give enough information to easily find the failure case.

The `FETCH_HEAD` file is where command line git stores the SHA-1 that was most recently fetched into the repository. The message 'Invalid argument' hints to me that the '.git/FETCH_HEAD' file may be inaccessible. Some of the possible reasons it might have become inaccessible include:

  • Permission change on the file system (user performing the fetch unable to write to the file - command line git 2.7.4 reports 'permission denied' in this case, not 'Invalid argument')
  • File type changed on the file system (what was a plain file previously might have been deleted and replaced with a directory - command line git 2.7.4 reports 'Is a directory' in this case, not 'Invalid argument')
  • File system related error (seems unlikely, but if the file system is reporting errors it might be worth investigating)
  • File system unavailable (if the repository is stored on a network file system, that might explain both the 'Invalid argument' message and its intermittent nature)

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

unread,
Oct 11, 2018, 9:08:02 AM10/11/18
to jenkinsc...@googlegroups.com
Mark Waite assigned an issue to Unassigned
 
Change By: Mark Waite
Assignee: Mark Waite

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

unread,
Oct 11, 2018, 9:09:01 AM10/11/18
to jenkinsc...@googlegroups.com
 
Re: Loading library fails - Error fetching remote repo 'origin'

In case I decided to investigate further in the command line git source code, what version of command line git is running on the machine that has the problem?

If you add JGit to the "Global Tools Configuration" as one of the git implementations and then configure a copy of the problem job to use JGit, does the same problem appear?

tian.wang@zazzle.com (JIRA)

unread,
Nov 8, 2018, 11:02:03 PM11/8/18
to jenkinsc...@googlegroups.com
Tian Wang edited a comment on Bug JENKINS-54008
Hi Mark,

Thank you for looking into this.

 I also run into the exact same error.

 Currently, I just made a simple workaround with a few git command myself.  

  

* I also want to report that the error only happens for * multibranch * pipeline. *    Scripted * pipeline is completely fine. *

  ** 
checkout(scm: [$class: 'GitSCM', branches: [[name: "*/master"]], browser: [$class: 'Stash', repoUrl: "https://companygit/projects/libs/repos/library/browse"],\
doGenerateSubmoduleConfigurations: false, extensions: [], submoduleCfg: [], userRemoteConfigs: [[credentialsId: 'f46cf06a-2a80-4adb-b4dc-e94a5a77a17c', url: "ssh://git@companygit:7999/libs/library.git"]]]);
 
 
error log:
 
Cloning the remote Git repository*19:49:23* ERROR: Error cloning remote repo 'origin'*19:49:23* hudson.plugins.git.GitException: java.io.IOException: Remote call on Channel to /10.10.82.93 failed*19:49:23*  at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:169)*19:49:23*  at sun.reflect.GeneratedMethodAccessor818.invoke(Unknown Source)*19:49:23*  at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)*19:49:23*  at java.lang.reflect.Method.invoke(Unknown Source)*19:49:23*  at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:132)*19:49:23*  at com.sun.proxy.$Proxy98.execute(Unknown Source)*19:49:23*  at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1146)*19:49:23*  at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1186)*19:49:23*  at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120)*19:49:23*  at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:90)*19:49:23*  at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:77)*19:49:23*  at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:50)*19:49:23*  at hudson.security.ACL.impersonate(ACL.java:290)*19:49:23*  at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:47)*19:49:23*  at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)*19:49:23*  at java.util.concurrent.FutureTask.run(Unknown Source)*19:49:23*  at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)*19:49:23*  at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)*19:49:23*  at java.lang.Thread.run(Unknown Source)*19:49:23* Caused by: java.io.IOException: Remote call on Channel to /10.10.82.93 failed*19:49:23*  at hudson.remoting.Channel.call(Channel.java:961)*19:49:23*  at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:146)*19:49:23*  ... 18 more*19:49:23* Caused by: java.lang.NoSuchFieldError: executor*19:49:23*  at org.jenkinsci.remoting.util.AnonymousClassWarnings.check(AnonymousClassWarnings.java:65)*19:49:23*  at org.jenkinsci.remoting.util.AnonymousClassWarnings$1.annotateClass(AnonymousClassWarnings.java:119)*19:49:23*  at java.io.ObjectOutputStream.writeNonProxyDesc(Unknown Source)*19:49:23*  at java.io.ObjectOutputStream.writeClassDesc(Unknown Source)*19:49:23*  at java.io.ObjectOutputStream.writeOrdinaryObject(Unknown Source)*19:49:23*  at java.io.ObjectOutputStream.writeObject0(Unknown Source)*19:49:23*  at java.io.ObjectOutputStream.writeObject(Unknown Source)*19:49:23*  at hudson.console.ConsoleNote.encodeToBytes(ConsoleNote.java:185)*19:49:23*  at hudson.console.ConsoleNote.encode(ConsoleNote.java:211)*19:49:23*  at hudson.plugins.timestamper.TimestampNotesOutputStream.eol(TimestampNotesOutputStream.java:70)*19:49:23*  at hudson.console.LineTransformationOutputStream.eol(LineTransformationOutputStream.java:60)*19:49:23*  at hudson.console.LineTransformationOutputStream.write(LineTransformationOutputStream.java:56)*19:49:23*  at hudson.console.LineTransformationOutputStream.write(LineTransformationOutputStream.java:74)*19:49:23*  at java.io.PrintStream.write(Unknown Source)*19:49:23*  at sun.nio.cs.StreamEncoder.writeBytes(Unknown Source)*19:49:23*  at sun.nio.cs.StreamEncoder.implFlushBuffer(Unknown Source)*19:49:23*  at sun.nio.cs.StreamEncoder.flushBuffer(Unknown Source)*19:49:23*  at java.io.OutputStreamWriter.flushBuffer(Unknown Source)*19:49:23*  at java.io.PrintStream.newLine(Unknown Source)*19:49:23*  at java.io.PrintStream.println(Unknown Source)*19:49:23*  at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:567)*19:49:23*  at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153)*19:49:23*  at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146)*19:49:23*  at hudson.remoting.UserRequest.perform(UserRequest.java:118)*19:49:23*  at hudson.remoting.UserRequest.perform(UserRequest.java:48)*19:49:23*  at hudson.remoting.Request$2.run(Request.java:328)*19:49:23*  at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)*19:49:23*  at java.util.concurrent.FutureTask.run(Unknown Source)*19:49:23*  at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)*19:49:23*  at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)*19:49:23*  at hudson.remoting.Engine$1$1.run(Engine.java:63)*19:49:23*  ... 1 more*19:49:23*  Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to Channel to /10.10.82.93*19:49:23*   at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741)*19:49:23*   at hudson.remoting.UserResponse.retrieve(UserRequest.java:389)*19:49:23*   at hudson.remoting.Channel.call(Channel.java:955)*19:49:23*   at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:146)*19:49:23*   at sun.reflect.GeneratedMethodAccessor818.invoke(Unknown Source)*19:49:23*   at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)*19:49:23*   at java.lang.reflect.Method.invoke(Unknown Source)*19:49:23*   at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:132)*19:49:23*   at com.sun.proxy.$Proxy98.execute(Unknown Source)*19:49:23*   at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1146)*19:49:23*   at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1186)*19:49:23*   at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120)*19:49:23*   at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:90)*19:49:23*   at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:77)*19:49:23*   at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:50)*19:49:23*   at hudson.security.ACL.impersonate(ACL.java:290)*19:49:23*   at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:47)*19:49:23*   at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)*19:49:23*   at java.util.concurrent.FutureTask.run(Unknown Source)*19:49:23*   at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)*19:49:23*   at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)*19:49:23*   ... 1 more

tian.wang@zazzle.com (JIRA)

unread,
Nov 8, 2018, 11:02:03 PM11/8/18
to jenkinsc...@googlegroups.com

Hi I also run into the exact same error.

 

I also want to report that the error only happens for multibranch pipeline.   Scripted pipeline is completely fine.

 
checkout(scm: [$class: 'GitSCM', branches: [[name: "*/master"]], browser: [$class: 'Stash', repoUrl: "https://companygit/projects/libs/repos/library/browse"],\
doGenerateSubmoduleConfigurations: false, extensions: [], submoduleCfg: [], userRemoteConfigs: [[credentialsId: 'f46cf06a-2a80-4adb-b4dc-e94a5a77a17c', url: "ssh://git@companygit:7999/libs/library.git"]]]);
 
 
error log:
 

Cloning the remote Git repository*19:49:23* ERROR: Error cloning remote repo 'origin'19:49:23 hudson.plugins.git.GitException: java.io.IOException: Remote call on Channel to /10.10.82.93 failed*19:49:23* at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:169)19:49:23 at sun.reflect.GeneratedMethodAccessor818.invoke(Unknown Source)19:49:23 at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)19:49:23 at java.lang.reflect.Method.invoke(Unknown Source)19:49:23 at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:132)19:49:23 at com.sun.proxy.$Proxy98.execute(Unknown Source)19:49:23 at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1146)19:49:23 at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1186)19:49:23 at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120)19:49:23 at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:90)19:49:23 at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:77)19:49:23 at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:50)19:49:23 at hudson.security.ACL.impersonate(ACL.java:290)19:49:23 at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:47)19:49:23 at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)19:49:23 at java.util.concurrent.FutureTask.run(Unknown Source)19:49:23 at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)19:49:23 at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)19:49:23 at java.lang.Thread.run(Unknown Source)19:49:23 Caused by: java.io.IOException: Remote call on Channel to /10.10.82.93 failed*19:49:23* at hudson.remoting.Channel.call(Channel.java:961)19:49:23 at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:146)19:49:23 ... 18 more*19:49:23* Caused by: java.lang.NoSuchFieldError: executor*19:49:23* at org.jenkinsci.remoting.util.AnonymousClassWarnings.check(AnonymousClassWarnings.java:65)19:49:23 at org.jenkinsci.remoting.util.AnonymousClassWarnings$1.annotateClass(AnonymousClassWarnings.java:119)19:49:23 at java.io.ObjectOutputStream.writeNonProxyDesc(Unknown Source)19:49:23 at java.io.ObjectOutputStream.writeClassDesc(Unknown Source)19:49:23 at java.io.ObjectOutputStream.writeOrdinaryObject(Unknown Source)19:49:23 at java.io.ObjectOutputStream.writeObject0(Unknown Source)19:49:23 at java.io.ObjectOutputStream.writeObject(Unknown Source)19:49:23 at hudson.console.ConsoleNote.encodeToBytes(ConsoleNote.java:185)19:49:23 at hudson.console.ConsoleNote.encode(ConsoleNote.java:211)19:49:23 at hudson.plugins.timestamper.TimestampNotesOutputStream.eol(TimestampNotesOutputStream.java:70)19:49:23 at hudson.console.LineTransformationOutputStream.eol(LineTransformationOutputStream.java:60)19:49:23 at hudson.console.LineTransformationOutputStream.write(LineTransformationOutputStream.java:56)19:49:23 at hudson.console.LineTransformationOutputStream.write(LineTransformationOutputStream.java:74)19:49:23 at java.io.PrintStream.write(Unknown Source)19:49:23 at sun.nio.cs.StreamEncoder.writeBytes(Unknown Source)19:49:23 at sun.nio.cs.StreamEncoder.implFlushBuffer(Unknown Source)19:49:23 at sun.nio.cs.StreamEncoder.flushBuffer(Unknown Source)19:49:23 at java.io.OutputStreamWriter.flushBuffer(Unknown Source)19:49:23 at java.io.PrintStream.newLine(Unknown Source)19:49:23 at java.io.PrintStream.println(Unknown Source)19:49:23 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:567)19:49:23 at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153)19:49:23 at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146)19:49:23 at hudson.remoting.UserRequest.perform(UserRequest.java:118)19:49:23 at hudson.remoting.UserRequest.perform(UserRequest.java:48)19:49:23 at hudson.remoting.Request$2.run(Request.java:328)19:49:23 at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)19:49:23 at java.util.concurrent.FutureTask.run(Unknown Source)19:49:23 at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)19:49:23 at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)19:49:23 at hudson.remoting.Engine$1$1.run(Engine.java:63)19:49:23 ... 1 more*19:49:23* Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to Channel to /10.10.82.93*19:49:23* at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741)19:49:23 at hudson.remoting.UserResponse.retrieve(UserRequest.java:389)19:49:23 at hudson.remoting.Channel.call(Channel.java:955)19:49:23 at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:146)19:49:23 at sun.reflect.GeneratedMethodAccessor818.invoke(Unknown Source)19:49:23 at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)19:49:23 at java.lang.reflect.Method.invoke(Unknown Source)19:49:23 at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:132)19:49:23 at com.sun.proxy.$Proxy98.execute(Unknown Source)19:49:23 at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1146)19:49:23 at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1186)19:49:23 at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120)19:49:23 at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:90)19:49:23 at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:77)19:49:23 at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:50)19:49:23 at hudson.security.ACL.impersonate(ACL.java:290)19:49:23 at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:47)19:49:23 at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)19:49:23 at java.util.concurrent.FutureTask.run(Unknown Source)19:49:23 at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)19:49:23 at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)19:49:23 ... 1 more

tian.wang@zazzle.com (JIRA)

unread,
Nov 8, 2018, 11:03:03 PM11/8/18
to jenkinsc...@googlegroups.com
Tian Wang edited a comment on Bug JENKINS-54008
Hi Mark,

Thank you for looking into this.

I also run into the exact same error.

Currently, I just made a simple workaround with a few git command myself. 

 

*I also want to report that the error only happens for* multibranch *pipeline.*   Scripted *pipeline with the exact same checkout(scm) command is completely fine.*

 ** 

checkout(scm: [$class: 'GitSCM', branches: [[name: "*/master"]], browser: [$class: 'Stash', repoUrl: "https://companygit/projects/libs/repos/library/browse"],\
doGenerateSubmoduleConfigurations: false, extensions: [], submoduleCfg: [], userRemoteConfigs: [[credentialsId: 'f46cf06a-2a80-4adb-b4dc-e94a5a77a17c', url: "ssh://git@companygit:7999/libs/library.git"]]]);
 
 
error log:
 
Cloning the remote Git repository*19:49:23* ERROR: Error cloning remote repo 'origin'*19:49:23* hudson.plugins.git.GitException: java.io.IOException: Remote call on Channel to /10.10.82.93 failed*19:49:23* at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:169)*19:49:23* at sun.reflect.GeneratedMethodAccessor818.invoke(Unknown Source)*19:49:23* at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)*19:49:23* at java.lang.reflect.Method.invoke(Unknown Source)*19:49:23* at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:132)*19:49:23* at com.sun.proxy.$Proxy98.execute(Unknown Source)*19:49:23* at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1146)*19:49:23* at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1186)*19:49:23* at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120)*19:49:23* at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:90)*19:49:23* at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:77)*19:49:23* at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:50)*19:49:23* at hudson.security.ACL.impersonate(ACL.java:290)*19:49:23* at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:47)*19:49:23* at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)*19:49:23* at java.util.concurrent.FutureTask.run(Unknown Source)*19:49:23* at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)*19:49:23* at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)*19:49:23* at java.lang.Thread.run(Unknown Source)*19:49:23* Caused by: java.io.IOException: Remote call on Channel to /10.10.82.93 failed*19:49:23* at hudson.remoting.Channel.call(Channel.java:961)*19:49:23* at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:146)*19:49:23* ... 18 more*19:49:23* Caused by: java.lang.NoSuchFieldError: executor*19:49:23* at org.jenkinsci.remoting.util.AnonymousClassWarnings.check(AnonymousClassWarnings.java:65)*19:49:23* at org.jenkinsci.remoting.util.AnonymousClassWarnings$1.annotateClass(AnonymousClassWarnings.java:119)*19:49:23* at java.io.ObjectOutputStream.writeNonProxyDesc(Unknown Source)*19:49:23* at java.io.ObjectOutputStream.writeClassDesc(Unknown Source)*19:49:23* at java.io.ObjectOutputStream.writeOrdinaryObject(Unknown Source)*19:49:23* at java.io.ObjectOutputStream.writeObject0(Unknown Source)*19:49:23* at java.io.ObjectOutputStream.writeObject(Unknown Source)*19:49:23* at hudson.console.ConsoleNote.encodeToBytes(ConsoleNote.java:185)*19:49:23* at hudson.console.ConsoleNote.encode(ConsoleNote.java:211)*19:49:23* at hudson.plugins.timestamper.TimestampNotesOutputStream.eol(TimestampNotesOutputStream.java:70)*19:49:23* at hudson.console.LineTransformationOutputStream.eol(LineTransformationOutputStream.java:60)*19:49:23* at hudson.console.LineTransformationOutputStream.write(LineTransformationOutputStream.java:56)*19:49:23* at hudson.console.LineTransformationOutputStream.write(LineTransformationOutputStream.java:74)*19:49:23* at java.io.PrintStream.write(Unknown Source)*19:49:23* at sun.nio.cs.StreamEncoder.writeBytes(Unknown Source)*19:49:23* at sun.nio.cs.StreamEncoder.implFlushBuffer(Unknown Source)*19:49:23* at sun.nio.cs.StreamEncoder.flushBuffer(Unknown Source)*19:49:23* at java.io.OutputStreamWriter.flushBuffer(Unknown Source)*19:49:23* at java.io.PrintStream.newLine(Unknown Source)*19:49:23* at java.io.PrintStream.println(Unknown Source)*19:49:23* at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:567)*19:49:23* at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153)*19:49:23* at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146)*19:49:23* at hudson.remoting.UserRequest.perform(UserRequest.java:118)*19:49:23* at hudson.remoting.UserRequest.perform(UserRequest.java:48)*19:49:23* at hudson.remoting.Request$2.run(Request.java:328)*19:49:23* at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)*19:49:23* at java.util.concurrent.FutureTask.run(Unknown Source)*19:49:23* at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)*19:49:23* at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)*19:49:23* at hudson.remoting.Engine$1$1.run(Engine.java:63)*19:49:23* ... 1 more*19:49:23* Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to Channel to /10.10.82.93*19:49:23* at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741)*19:49:23* at hudson.remoting.UserResponse.retrieve(UserRequest.java:389)*19:49:23* at hudson.remoting.Channel.call(Channel.java:955)*19:49:23* at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:146)*19:49:23* at sun.reflect.GeneratedMethodAccessor818.invoke(Unknown Source)*19:49:23* at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)*19:49:23* at java.lang.reflect.Method.invoke(Unknown Source)*19:49:23* at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:132)*19:49:23* at com.sun.proxy.$Proxy98.execute(Unknown Source)*19:49:23* at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1146)*19:49:23* at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1186)*19:49:23* at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120)*19:49:23* at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:90)*19:49:23* at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:77)*19:49:23* at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:50)*19:49:23* at hudson.security.ACL.impersonate(ACL.java:290)*19:49:23* at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:47)*19:49:23* at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)*19:49:23* at java.util.concurrent.FutureTask.run(Unknown Source)*19:49:23* at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)*19:49:23* at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)*19:49:23* ... 1 more

tian.wang@zazzle.com (JIRA)

unread,
Nov 8, 2018, 11:10:11 PM11/8/18
to jenkinsc...@googlegroups.com
Tian Wang updated an issue
 
Change By: Tian Wang
Attachment: currentpluginversion.txt

tian.wang@zazzle.com (JIRA)

unread,
Nov 8, 2018, 11:11:01 PM11/8/18
to jenkinsc...@googlegroups.com
Tian Wang commented on Bug JENKINS-54008
 
Re: Loading library fails - Error fetching remote repo 'origin'

I also want to mention that this only happened after we auto upgraded jenkins plugins last Friday 02/11/2018.

the plugin versions and their downgrade last version are posted  currentpluginversion.txt  

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

unread,
Nov 8, 2018, 11:12:02 PM11/8/18
to jenkinsc...@googlegroups.com

Tian Wang the stack trace you reported is not the same as the stack trace in this bug report. The stack trace in this bug report includes the stderr output:

error: cannot open .git/FETCH_HEAD: Invalid argument

Your stack trace does not include that message.

Your stack trace (hard to read because it is being wrapped instead of being inserted into a `noformat` tagged area) includes the message:

Caused by: java.lang.NoSuchFieldError: executor

I have not seen that before, but it is a different condition and most likely a different root cause than the message reported in this bug report. Please submit a separate bug report for that message, since it is quite different from the message in this bug report.

tian.wang@zazzle.com (JIRA)

unread,
Nov 8, 2018, 11:12:02 PM11/8/18
to jenkinsc...@googlegroups.com
Tian Wang edited a comment on Bug JENKINS-54008
Hi Mark,

Thank you for looking into this.

I also run into the exact same error.

Currently, I just made a simple workaround with a few git command myself. 

 

*I also want to report that the error only happens for* multibranch *pipeline.*    Scripted single  *pipeline job with the exact same checkout(scm) command is completely fine.*

tian.wang@zazzle.com (JIRA)

unread,
Nov 8, 2018, 11:13:01 PM11/8/18
to jenkinsc...@googlegroups.com

you are right my bad.

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

unread,
Nov 8, 2018, 11:14:02 PM11/8/18
to jenkinsc...@googlegroups.com
Mark Waite edited a comment on Bug JENKINS-54008
[~zazzletian] the stack trace you reported is *not* the same as the stack trace in this bug report.  The stack trace in this bug report includes the stderr output:

{ { noformat}
error: cannot open .git/FETCH_HEAD: Invalid argument

{noformat } }

Your stack trace does not include that message.

Your stack trace (hard to read because it is being wrapped instead of being inserted into a `noformat` tagged area) includes the message:

{ { noformat}
 Caused by: java.lang.NoSuchFieldError: executor
{noformat } }

I have not seen that before, but it is a different condition and most likely a different root cause than the message reported in this bug report.  Please submit a separate bug report for that message, since it is quite different from the message in this bug report.


You may want to confirm that the agent which is executing that job is using a current version of the `agent.jar` file.  I had unexpected failures a few weeks ago when I discovered that I was running very old agent.jar versions with a current Jenkins.

tian.wang@zazzle.com (JIRA)

unread,
Nov 8, 2018, 11:14:03 PM11/8/18
to jenkinsc...@googlegroups.com
Tian Wang updated an issue
Change By: Tian Wang
Comment:
Hi Mark,

Thank you for looking into this.

I also run into the exact same error.

Currently, I just made a simple workaround with a few git command myself. 

 

*I also want to report that the error only happens for* multibranch *pipeline.*   single *pipeline job with the exact same checkout(scm) command is completely fine.*

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

unread,
Nov 8, 2018, 11:17:03 PM11/8/18
to jenkinsc...@googlegroups.com
Mark Waite updated Bug JENKINS-54008
 

Since m f has not responded in a month, I'm closing this as "cannot reproduce". If steps can be provided which duplicate the problem, we can reopen the report.
Change By: Mark Waite
Status: Open Fixed but Unreleased
Resolution: Cannot Reproduce

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

unread,
Nov 8, 2018, 11:17:03 PM11/8/18
to jenkinsc...@googlegroups.com
Change By: Mark Waite
Status: Fixed but Unreleased Resolved

ilatypov@yahoo.ca (JIRA)

unread,
Jun 10, 2019, 12:17:02 PM6/10/19
to jenkinsc...@googlegroups.com
Ilguiz Latypov commented on Bug JENKINS-54008
 
Re: Loading library fails - Error fetching remote repo 'origin'

I recognize the community spirit of the project and lack of hobby time for its maintainers, but closing an issue just because its submitters did not respond seems evil. The git plugin seems an utmost importance component of Jenkins. Closing issues or suggesting that reporters re-submit part of them as separate bugs always throws me off as if maintainers are not really to own the code.

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

unread,
Jun 10, 2019, 2:37:02 PM6/10/19
to jenkinsc...@googlegroups.com

Ilguiz Latypov , thanks for your comments. You said:

I recognize the community spirit of the project and lack of hobby time for its maintainers, but closing an issue just because its submitters did not respond seems evil.

I don't want to be evil. I don't want to do things that are evil. However, I don't understand what you envision should happen as an alternative to what happened with this ticket. With this ticket:

  1. m f reported a problem and provided a stack trace which showed the problem
  2. I investigated the problem, was unable to reproduce the problem, and provided several ideas of conditions that might cause that type of problem
  3. I asked some further clarifying questions but received no responses to those clarifying questions
  4. Tian Wang reported a different problem which included a different error message inside a stack trace
  5. I asked Tian Wangto submit a different bug report so that independent issues have distinct bug reports,
  6. Tian Wang agreed that it was a separate bug report
  7. A month after receiving no answers from m f on the original questions, I closed the bug because I could not reproduce it

The Jenkins project Jira has "Cannot reproduce" as an allowed resolution of an issue. It is used by core and many different plugins. It allows those who attempt to verify a bug to explain to the submitter that they were unable to duplicate the bug. Resolving an issue as "Cannot reproduce" does not hide the issue. It does not prevent the issue from being reopened. It does not prevent someone from reopening it and assigning it to themselves to resolve.

If I don't close an issue I cannot reproduce, then as a maintainer I must regularly filter the issues that I cannot reproduce by some other means. If I don't close an issue that I cannot reproduce, then I need to use another way of communicating to others that I could not reproduce the bug.

Can you explain further what you think should have happened in this case and how those different steps would have been better?

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

unread,
Jun 10, 2019, 5:33:03 PM6/10/19
to jenkinsc...@googlegroups.com
Mark Waite edited a comment on Bug JENKINS-54008
[~ilatypov] , thanks for your comments.  You said:

bq. I recognize the community spirit of the project and lack of hobby time for its maintainers, but closing an issue just because its submitters did not respond seems evil.


I don't want to be evil.  I don't want to do things that are evil.  However, I don't understand what you envision should happen as an alternative to what happened with this ticket.  With this ticket:

# [~emchi] reported a problem and provided a stack trace which showed the problem
# I investigated the problem, was unable to reproduce the problem, and provided several ideas of conditions that might cause that type of problem
# I asked some further clarifying questions but received no responses to those clarifying questions
# [~zazzletian] reported a different problem which included a different error message inside a stack trace
# I asked [~zazzletian]to submit a different bug report so that independent issues have distinct bug reports,
#  [~zazzletian] agreed that it was a separate bug report
# A month after receiving no answers from [~emchi] on the original questions, I closed the bug because I could not reproduce it


The Jenkins project Jira has "Cannot reproduce" as an allowed resolution of an issue.  It is used by core and many different plugins.  It allows those who attempt to verify a bug to explain to the submitter that they were unable to duplicate the bug.  Resolving an issue as "Cannot reproduce" does not hide the issue.  It does not prevent the issue from being reopened.  It does not prevent someone from reopening it and assigning it to themselves to resolve.

If I don't close an issue I cannot reproduce, then as a maintainer I must regularly filter the issues that I cannot reproduce by some other means.  If I don't close an issue that I cannot reproduce, then I need to use another way of communicating to others that I could not reproduce the bug.

Can you explain further what you think should have happened in this case and how those different steps would have been better?

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

unread,
Jun 10, 2019, 5:46:02 PM6/10/19
to jenkinsc...@googlegroups.com
Mark Waite edited a comment on Bug JENKINS-54008
[~ilatypov] , thanks for your comments.  You said:

bq. I recognize the community spirit of the project and lack of hobby time for its maintainers, but closing an issue just because its submitters did not respond seems evil.

I don't want to be evil.  I don't want to do things that are evil.  However, I don't understand what you envision should happen as an alternative to what happened with this ticket.  With this ticket:

# [~emchi] reported a problem and provided a stack trace which showed the problem
# I investigated the problem, was unable to reproduce the problem, and provided several ideas of conditions that might cause that type of problem
# I asked some further clarifying questions but received no responses to those clarifying questions or to my original investigation
# [~zazzletian] reported a different problem which included a different error message inside a stack trace
# I asked [~zazzletian] to submit a different bug report so that independent issues have distinct bug reports,
#  [~zazzletian] agreed that it was a separate bug report
# A month after receiving no answers from [~emchi] on the original questions, I closed the bug because I could not reproduce it

The Jenkins project Jira has "Cannot reproduce" as an allowed resolution of an issue.  It is used by core and many different plugins.  It allows those who attempt to verify a bug to explain to the submitter that they were unable to duplicate the bug.  Resolving an issue as "Cannot reproduce" does not hide the issue.  It does not prevent the issue from being reopened.  It does not prevent someone from reopening it and assigning it to themselves to resolve.

If I don't close an issue I cannot reproduce, then as a maintainer I must regularly filter the issues that I cannot reproduce by some other means.  If I don't close an issue that I cannot reproduce, then I need to use another way of communicating to others that I could not reproduce the bug.

Can you explain further what you think should have happened in this case and how those different steps would have been better?

ilatypov@yahoo.ca (JIRA)

unread,
Jun 11, 2019, 8:37:02 AM6/11/19
to jenkinsc...@googlegroups.com

Ah sorry I targeted a wrong bug. I thought it was related to my frustration with the git plugin showing a "fatal: Could not read from remote repository" error. I think if the git plugin could add this trace message before invoking git,

echo "Checking out branch ${branch} with credentials ${credentialsId} from ${url} ..."

dozens of devops would be happier.

ilatypov@yahoo.ca (JIRA)

unread,
Jun 11, 2019, 8:37:03 AM6/11/19
to jenkinsc...@googlegroups.com
Ilguiz Latypov edited a comment on Bug JENKINS-54008
Ah sorry I targeted a wrong bug.  I thought it was related to my frustration with the git plugin showing a "fatal: Could not read from remote repository" error.  I think if the git plugin could add this trace message before invoking git,

{noformat}

echo "Checking out branch ${branch} with credentials ${credentialsId} from ${url} ..."
{noformat}


dozens of devops would be happier.

Mu problem resolved when I saw that I was using a wrong credential, which did not agree with the error message.

ilatypov@yahoo.ca (JIRA)

unread,
Jun 11, 2019, 9:22:02 AM6/11/19
to jenkinsc...@googlegroups.com
Ilguiz Latypov edited a comment on Bug JENKINS-54008
Ah sorry I targeted a wrong bug.  I thought it was related to my frustration with the git plugin showing a " an error implying connectivity issues,

{noformat}
fatal: Could not read from remote repository " error.

{noformat}

  I think if the git plugin could add this trace message before invoking git,

{noformat}
echo "Checking out branch ${branch} with credentials ${credentialsId} from ${url} ..."
{noformat}

dozens of devops would be happier.
Mu My problem resolved when I saw that I was using a wrong credential, which did not agree with the error message.

ilatypov@yahoo.ca (JIRA)

unread,
Jun 11, 2019, 9:24:03 AM6/11/19
to jenkinsc...@googlegroups.com
Ilguiz Latypov edited a comment on Bug JENKINS-54008
Ah sorry I targeted a wrong bug.  I thought it was related to my frustration with the git plugin showing an error implying connectivity issues,
{noformat}
fatal: Could not read from remote repository
{noformat}

 I think if the git plugin could add this trace message before invoking git,
{noformat}
echo "Checking out branch ${branch} with credentials ${credentialsId} from ${url} ..."
{noformat}
dozens of devops would be happier.

My problem resolved when I saw that I was using a wrong credential, which did not agree with the error message.   Oh and whoever suggested to try a bare {{git@git../repo.git}} URL on StackOverflow: this ignored the port number after the host name (we use a TCP port 2222 for reasons unknown).  The proper {{ssh://HOST:PORT/REPO.git}} URL worked.

ilatypov@yahoo.ca (JIRA)

unread,
Jun 12, 2019, 9:51:03 AM6/12/19
to jenkinsc...@googlegroups.com
Ilguiz Latypov edited a comment on Bug JENKINS-54008
Ah sorry I targeted a wrong bug. I thought it was related to my frustration with the git plugin showing an error implying connectivity issues,
{noformat}
fatal: Could not read from remote repository
{noformat}
I think if the git plugin could add this trace message before invoking git,
{noformat}
echo "Checking out branch ${branch} with credentials ${credentialsId} from ${url} ..."
{noformat}
dozens of devops would be happier.

My problem resolved when I saw that I was using a wrong credential, which did not agree with the error message.  Oh and whoever suggested to try a bare {{git@git../repo.git}} URL on StackOverflow: this ignored the port number after the host name (we use a TCP port 2222 for reasons unknown).  The " proper " {{ssh:// git@ HOST:PORT/REPO.git}} URL worked.

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

unread,
Oct 22, 2019, 9:34:10 PM10/22/19
to jenkinsc...@googlegroups.com
Mark Waite closed an issue as Cannot Reproduce
 
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