Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-34138

jenkins jobs are failing at maven installation

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      we started seeing issue with maven installation failed which resulted job fail. Until we re-launch the slave we are not able to execute the job.

      Please find exception details...
      [EnvInject] - Loading node environment variables.
      Building remotely on STPSlave305 in workspace <path>/workspace/SamyakTest
      java.io.IOException: Failed to install https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.0.3/apache-maven-3.0.3-bin.zip to <path>/tools/hudson.tasks.Maven_MavenInstallation/MavenMaster1QDC
      at hudson.FilePath.installIfNecessaryFrom(FilePath.java:822)
      at hudson.tools.DownloadFromUrlInstaller.performInstallation(DownloadFromUrlInstaller.java:70)
      at hudson.tools.InstallerTranslator.getToolHome(InstallerTranslator.java:68)
      at hudson.tools.ToolLocationNodeProperty.getToolHome(ToolLocationNodeProperty.java:107)
      at hudson.tools.ToolInstallation.translateFor(ToolInstallation.java:205)
      at hudson.tasks.Maven$MavenInstallation.forNode(Maven.java:609)
      at hudson.maven.MavenModuleSetBuild.getEnvironment(MavenModuleSetBuild.java:182)
      at hudson.plugins.git.GitSCM.checkout(GitSCM.java:965)
      at hudson.scm.SCM.checkout(SCM.java:488)
      at hudson.model.AbstractProject.checkout(AbstractProject.java:1253)
      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:1745)
      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: java.io.IOException: remote file operation failed: <path>/tools/hudson.tasks.Maven_MavenInstallation/MavenMaster1QDC at hudson.remoting.Channel@6dd0796f:STPSlave305: java.nio.file.FileSystemException: <path>/tools/hudson.tasks.Maven_MavenInstallation/MavenMaster1QDC/lib/.nfs00000000104d564e0000015a: Device or resource busy
      at hudson.FilePath.act(FilePath.java:976)
      at hudson.FilePath.act(FilePath.java:958)
      at hudson.FilePath.deleteContents(FilePath.java:1173)
      at hudson.FilePath.installIfNecessaryFrom(FilePath.java:786)
      ... 16 more
      Caused by: java.nio.file.FileSystemException: <path>/tools/hudson.tasks.Maven_MavenInstallation/MavenMaster1QDC/lib/.nfs00000000104d564e0000015a: Device or resource busy
      at sun.nio.fs.UnixException.translateToIOException(UnixException.java:91)
      at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
      at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)
      at sun.nio.fs.UnixFileSystemProvider.implDelete(UnixFileSystemProvider.java:243)
      at sun.nio.fs.AbstractFileSystemProvider.delete(AbstractFileSystemProvider.java:103)
      at java.nio.file.Files.delete(Files.java:1071)
      at sun.reflect.GeneratedMethodAccessor2701.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
      at java.lang.reflect.Method.invoke(Method.java:601)
      at hudson.Util.deleteFile(Util.java:247)
      at hudson.FilePath.deleteRecursive(FilePath.java:1193)
      at hudson.FilePath.deleteContentsRecursive(FilePath.java:1202)
      at hudson.FilePath.deleteRecursive(FilePath.java:1184)
      at hudson.FilePath.deleteContentsRecursive(FilePath.java:1202)
      at hudson.FilePath.access$1100(FilePath.java:190)
      at hudson.FilePath$15.invoke(FilePath.java:1176)
      at hudson.FilePath$15.invoke(FilePath.java:1173)
      at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2577)
      at hudson.remoting.UserRequest.perform(UserRequest.java:121)
      at hudson.remoting.UserRequest.perform(UserRequest.java:49)
      at hudson.remoting.Request$2.run(Request.java:324)
      at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
      at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
      at java.util.concurrent.FutureTask.run(FutureTask.java:166)
      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
      at java.lang.Thread.run(Thread.java:722)
      at ......remote call to STPSlave305(Native Method)
      at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356)
      at hudson.remoting.UserResponse.retrieve(UserRequest.java:221)
      at hudson.remoting.Channel.call(Channel.java:752)
      at hudson.FilePath.act(FilePath.java:969)
      ... 19 more

        Attachments

          Activity

          Hide
          jgrant216 Jeff G added a comment -

          We also just recently started seeing this issue within the last couple of weeks I believe.

          In my configuration, I am loading all 5 executors with the same job via remote triggering using a curl statement without any delay. This job spawning configuration has not been changed in several months. Recently, however, I have noticed this defect's error turn up and all jobs fail.

          I am thinking there is contention against the destination maven installation folder.

          Environment details...
          Ubuntu Jenkins LTS 1.642.2 (will be 1.642.3 this weekend)
          Windows 2008 Slave
          5 Executors
          Maven 3.0.4
          JDK 8

          While my scenario is around concurrently executing a single maven project, I expect any combination of multiple Maven projects could result in this condition. This is unless Jenkins has some built in throttle mechanism which is not being respected while using a single project concurrently.

          Unfortunately, the Windows slave in my case is effectively dead to Maven projects after this and I need to kill the Java process on the system before it will serve Maven projects again.

          I agree with the Critical status of this Defect.

          Show
          jgrant216 Jeff G added a comment - We also just recently started seeing this issue within the last couple of weeks I believe. In my configuration, I am loading all 5 executors with the same job via remote triggering using a curl statement without any delay. This job spawning configuration has not been changed in several months. Recently, however, I have noticed this defect's error turn up and all jobs fail. I am thinking there is contention against the destination maven installation folder. Environment details... Ubuntu Jenkins LTS 1.642.2 (will be 1.642.3 this weekend) Windows 2008 Slave 5 Executors Maven 3.0.4 JDK 8 While my scenario is around concurrently executing a single maven project, I expect any combination of multiple Maven projects could result in this condition. This is unless Jenkins has some built in throttle mechanism which is not being respected while using a single project concurrently. Unfortunately, the Windows slave in my case is effectively dead to Maven projects after this and I need to kill the Java process on the system before it will serve Maven projects again. I agree with the Critical status of this Defect.
          Hide
          scm_issue_link SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: t-hall
          Path:
          core/src/main/java/hudson/tasks/Maven.java
          test/src/test/java/hudson/tasks/MavenTest.java
          http://jenkins-ci.org/commit/jenkins/d688c154907d17e75ea31067c8fc2525aa679584
          Log:
          JENKINS-34138 Fix maven installs from stepping on each other (#3042)

          • JENKINS-34138 Adding equals/hashCode methods so that installs don't step on each other
          Show
          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: t-hall Path: core/src/main/java/hudson/tasks/Maven.java test/src/test/java/hudson/tasks/MavenTest.java http://jenkins-ci.org/commit/jenkins/d688c154907d17e75ea31067c8fc2525aa679584 Log: JENKINS-34138 Fix maven installs from stepping on each other (#3042) JENKINS-34138 Adding equals/hashCode methods so that installs don't step on each other JENKINS-34138 Added issue reference to unit tests JENKINS-34138 - changed the order of equals / hashcode
          Hide
          oleg_nenashev Oleg Nenashev added a comment -

          The fix has been integrated towards 2.91. I will mark it as lts-candidate

          Show
          oleg_nenashev Oleg Nenashev added a comment - The fix has been integrated towards 2.91. I will mark it as lts-candidate
          Hide
          scm_issue_link SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: t-hall
          Path:
          core/src/main/java/hudson/tasks/Maven.java
          test/src/test/java/hudson/tasks/MavenTest.java
          http://jenkins-ci.org/commit/jenkins/065b874a4784c5d0bcfd9731c0ad4139c5e61c78
          Log:
          JENKINS-34138 Fix maven installs from stepping on each other (#3042)

          • JENKINS-34138 Adding equals/hashCode methods so that installs don't step on each other

          (cherry picked from commit d688c154907d17e75ea31067c8fc2525aa679584)

          Show
          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: t-hall Path: core/src/main/java/hudson/tasks/Maven.java test/src/test/java/hudson/tasks/MavenTest.java http://jenkins-ci.org/commit/jenkins/065b874a4784c5d0bcfd9731c0ad4139c5e61c78 Log: JENKINS-34138 Fix maven installs from stepping on each other (#3042) JENKINS-34138 Adding equals/hashCode methods so that installs don't step on each other JENKINS-34138 Added issue reference to unit tests JENKINS-34138 - changed the order of equals / hashcode (cherry picked from commit d688c154907d17e75ea31067c8fc2525aa679584)

            People

            • Assignee:
              Unassigned
              Reporter:
              grayudu Gangadhar Rayudu
            • Votes:
              3 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: