Reputation: 967
My jenkins build is suddenly not working now.The error is as follows:-
Fetching changes from the remote Git repository
> git config remote.origin.url <url> # timeout=10
ERROR: Error fetching remote repo 'origin'
hudson.plugins.git.GitException: Failed to fetch from <url>
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:735)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:983)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1016)
at hudson.scm.SCM.checkout(SCM.java:484)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1270)
at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:622)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:528)
at hudson.model.Run.execute(Run.java:1759)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:529)
at hudson.model.ResourceController.execute(ResourceController.java:89)
at hudson.model.Executor.run(Executor.java:240)
Caused by: hudson.plugins.git.GitException: Command "git config remote.origin.url <url> returned status code 4:
stdout:
stderr: error: failed to write new configuration file .git/config.lock
I am not able to figure out the root cause. I have checked the permission and ownership for jenkins home folder which is /var/lib/jenkins:- drwxrwxrwx 17 jenkins jenkins 4096 Jun 25 04:30 jenkins
Permission and ownership of .git folder inside workspace folder of jenkins is:- drwxrwxrwx 8 jenkins jenkins 4096 Jun 30 21:51 .git
Please guide me fix the problem.
Upvotes: 67
Views: 154974
Reputation: 1
Below mentioned steps I have performed
Upvotes: -1
Reputation: 1678
In my case, I just renamed the baseDir on the Jenkins Agent where my pipeline script code was being synced in to. So, I effectively deleted the directory. After that, this the job ran completely fine.
So I assume there's a permissions problem, but I don't actually see one when I compare the renamed dir against the one that automatically replaced it.
Upvotes: 1
Reputation: 171
I fixed the issue cleaning every git directory stored on /var/lib/jenkins/caches:
ls
git-18890751adbbb4acf793765536038794 git-4e3aa803edee6bea2129fd817c36f896 git-9f242af77f8053aed6fedce8d0a76e3d git-e41ee04648298b79b4c7743c24ef70bd git-fceab3b3b569be214a737dca642e9276
git-18890751adbbb4acf793765536038794@tmp git-4e3aa803edee6bea2129fd817c36f896@tmp git-9f242af77f8053aed6fedce8d0a76e3d@tmp git-e41ee04648298b79b4c7743c24ef70bd@tmp git-fceab3b3b569be214a737dca642e9276@tmp
git-3733802e4022f95fbc60b4cb18a03217 git-551e81c26de5bcb6a5378e19af1e1be6 git-abf9e4e7e290be76e1f5b71ec660963e git-e707f9321b2bb37b96406ef713030927
git-3733802e4022f95fbc60b4cb18a03217@tmp git-551e81c26de5bcb6a5378e19af1e1be6@tmp git-abf9e4e7e290be76e1f5b71ec660963e@tmp git-e707f9321b2bb37b96406ef713030927@tmp
git-383d5f162d992a4ab05c37bf92f5a6a6 git-778102e2deb4f6ba3addd2a6598b243c git-c0a299dd0e54280fdc284e0f84116c25 git-ee5e64ec787f47fcbc3d1fb72b7f3431
git-383d5f162d992a4ab05c37bf92f5a6a6@tmp git-778102e2deb4f6ba3addd2a6598b243c@tmp git-c0a299dd0e54280fdc284e0f84116c25@tmp git-ee5e64ec787f47fcbc3d1fb72b7f3431@tmp
sh-4.2$ rm -rf git*
Upvotes: 3
Reputation: 11
we deleted the branches from gitlab, but the slaves weren't updated so we saw this error. We deleted the workspace and it looks ok
Upvotes: 1
Reputation: 741
In my case, found that my infrastructure team member changed the ownership of the workspace. After changing folder ownership (in my case it jenkins:apache) its start working.
Thanks & Regards Jaiswar Vipin Kumar R.
Upvotes: 2
Reputation: 6145
In my case, fetching/downloading the remote code was quite slow and was aborted due to a timeout. So I increased the "Timeout (in minutes) for clone and fetch operations" to 20 minutes.
Upvotes: 8
Reputation: 621
I was seeing the same issue, but disk space and VM memory were not the problem. What fixed it for me was making the job re-clone on build:
Upvotes: 51
Reputation: 91
I resolved this error by setting the User Account Control settings to "Never notify" and restarting the machine and reconnecting the node to Jenkins.
Upvotes: 1
Reputation: 1274
Experienced it when Jenkins VM was running out of disk space. Cleaned it up, don't see this problem anymore.
Upvotes: 32