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

Jenkins returns "Error 6 (net::ERR_FILE_NOT_FOUND): The file or directory could not be found" when trying to download artifacts >2GB

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • core
    • None

          • This issues appears to be that artifacts larger than 2GB can not be downloaded from Jenkins server ***

      We have started getting bad links to artifacts from some runs of our package build job.

      • The build completes with out error.
      • The artifacts are sucesfully copied back to the server.
      • The artifacts can be copied and verified ok using SMB drive share.
      • Any artifacts which are larger than 2GB will fail to download from the jenkins server.

      This web page has not been found
      Error 6 (net::ERR_FILE_NOT_FOUND): The file or directory could not be found.

      As a work around we are looking to split up the artifacts into multiple files but this is a less than ideal workflow.

      Thanks
      Richard.

          [JENKINS-13352] Jenkins returns "Error 6 (net::ERR_FILE_NOT_FOUND): The file or directory could not be found" when trying to download artifacts >2GB

          Richard Taylor added a comment -

          Searching jenkins.err.log for show no errors for the a build where the artifact link is broken.

          05-Apr-2012 08:35:38 hudson.model.Run run
          INFO: evo11-PKG #126 branches/evo11dx11 main build action completed: SUCCESS

          Richard Taylor added a comment - Searching jenkins.err.log for show no errors for the a build where the artifact link is broken. 05-Apr-2012 08:35:38 hudson.model.Run run INFO: evo11-PKG #126 branches/evo11dx11 main build action completed: SUCCESS

          Richard Taylor added a comment -

          Below is a section of the build history (in text format).
          Builds with failed artifacts either do not show the size or the size has been added before the slave icon.
          Could be a timing/timeout issue when uploading large artifacts.

          Success > Console Output #126 branches/evo11dx11 05-Apr-2012 08:30:20 [run with label [gbwwsrunbld09] (node: gbwwsrunbld09)]
          Success > Console Output #125 branches/evo11dx11 05-Apr-2012 06:02:03 [run with label [gbwwsrunbld09] (node: gbwwsrunbld09)]
          Success > Console Output #124 branches/evo11dx11 04-Apr-2012 16:15:42 2GB [run with label [gbwwsrunbld09] (node: gbwwsrunbld09)]
          Success > Console Output #123 branches/evo11dx11 04-Apr-2012 12:24:48 [run with label [gbwwsrunbld09] (node: gbwwsrunbld09)] 2GB
          Success > Console Output #122 branches/evo11dx11 04-Apr-2012 06:02:40 [run with label [gbwwsrunbld09] (node: gbwwsrunbld09)] 2GB

          Richard Taylor added a comment - Below is a section of the build history (in text format). Builds with failed artifacts either do not show the size or the size has been added before the slave icon. Could be a timing/timeout issue when uploading large artifacts. Success > Console Output #126 branches/evo11dx11 05-Apr-2012 08:30:20 [run with label [gbwwsrunbld09] (node: gbwwsrunbld09)] Success > Console Output #125 branches/evo11dx11 05-Apr-2012 06:02:03 [run with label [gbwwsrunbld09] (node: gbwwsrunbld09)] Success > Console Output #124 branches/evo11dx11 04-Apr-2012 16:15:42 2GB [run with label [gbwwsrunbld09] (node: gbwwsrunbld09)] Success > Console Output #123 branches/evo11dx11 04-Apr-2012 12:24:48 [run with label [gbwwsrunbld09] (node: gbwwsrunbld09)] 2GB Success > Console Output #122 branches/evo11dx11 04-Apr-2012 06:02:40 [run with label [gbwwsrunbld09] (node: gbwwsrunbld09)] 2GB

          Richard Taylor added a comment -

          Updated description of issues after continued investigation.

          Richard Taylor added a comment - Updated description of issues after continued investigation.

          OHTAKE Tomohiro added a comment -

          Reproduced in Ubuntu 11.04 64bit, Jenkins 1.459, Winstone.
          In Winstone case, it seems that Winstone fails to parse Content-Length header.

          java.lang.NumberFormatException: For input string: "2147484672"
	at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
	at java.lang.Integer.parseInt(Integer.java:484)
	at java.lang.Integer.parseInt(Integer.java:514)
	at winstone.WinstoneOutputStream.write(WinstoneOutputStream.java:106)
	at org.kohsuke.stapler.Stapler.serveStaticResource(Stapler.java:418)
	at org.kohsuke.stapler.ResponseImpl.serveFile(ResponseImpl.java:150)

          Which servlet container do you use for Jenkins?

          OHTAKE Tomohiro added a comment - Reproduced in Ubuntu 11.04 64bit, Jenkins 1.459, Winstone. In Winstone case, it seems that Winstone fails to parse Content-Length header. java.lang.NumberFormatException: For input string: "2147484672" at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) at java.lang. Integer .parseInt( Integer .java:484) at java.lang. Integer .parseInt( Integer .java:514) at winstone.WinstoneOutputStream.write(WinstoneOutputStream.java:106) at org.kohsuke.stapler.Stapler.serveStaticResource(Stapler.java:418) at org.kohsuke.stapler.ResponseImpl.serveFile(ResponseImpl.java:150) Which servlet container do you use for Jenkins?

          Richard Taylor added a comment -

          Yes we are running jenkins as a service on the win2k machine with the default container.
          From the docs that makes it the Winstone container.

          Server is win2k 64bit and we are running 64bit JRE.

          Richard Taylor added a comment - Yes we are running jenkins as a service on the win2k machine with the default container. From the docs that makes it the Winstone container. Server is win2k 64bit and we are running 64bit JRE.

          OHTAKE Tomohiro added a comment -

          Fixed by JENKINS-12854.

          OHTAKE Tomohiro added a comment - Fixed by JENKINS-12854 .

            Unassigned Unassigned
            richardtaylor Richard Taylor
            Votes:
            1 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: