Uploaded image for project: 'Infrastructure'
  1. Infrastructure
  2. INFRA-7812

Deploys to Nexus staging repo randomly fail

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Blocker
    • Resolution: Fixed
    • Fix Version/s: Jul 2014
    • Component/s: Nexus
    • Labels:
      None
    • Environment:
      Nexus version: 2.7.2-03
      Apache Maven 3.2.1
      Java version: 1.6.0_65, vendor: Apple Inc.
      OS name: "mac os x", version: "10.9.2", arch: "x86_64", family: "mac"

      Description

      I'm trying to deploy jclouds to a Nexus staging repo with the following command.

          mvn clean release:perform -Papache-release -DconnectionUrl=scm:git:file://`pwd`/.git -Dtag=jclouds-1.7.3-rc1 -Darguments="-DskipTests"

      The staging repo gets created and some project's artifacts upload but it fails randomly when uploading the artifacts from any particular project with an error message like.

          [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project byon: Failed to deploy artifacts: Could not transfer artifact org.apache.jclouds.api:byon:jar:1.7.3 from/to apache.releases.https (https://repository.apache.org/service/local/staging/deploy/maven2): The target server failed to respond

      In this case it was the byon project that died but it could have been any other. A full log with the relevant text is attached.

      Currently this is blocking the jclouds project from doing a release.
      1. release-fail.log
        29 kB
        Everett Toews

        Issue Links

          Activity

          Hide
          dashorst Martijn Dashorst added a comment -
          Today the uploads fail intermittently again.
          Show
          dashorst Martijn Dashorst added a comment - Today the uploads fail intermittently again.
          Hide
          rmetzger Robert Metzger added a comment -
          I experienced a similar issue when deploying.
          I tried using the {{-DretryFailedDeploymentCount=10}} flag of the maven deploy plugin and indeed, I saw the following behavior:

          {code}
          Uploaded: https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/flink/flink-tests/0.6-incubating-hadoop2/flink-tests-0.6-incubating-hadoop2.pom (8 KB at 1.7 KB/sec)
          [WARNING] Encountered issue during deployment: Failed to deploy artifacts: Could not transfer artifact org.apache.flink:flink-tests:jar:0.6-incubating-hadoop2 from/to apache.releases.https (https://repository.apache.org/service/local/staging/deploy/maven2): The target server failed to respond
          [INFO] Retrying deployment attempt 2 of 10
          Uploading: https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/flink/flink-tests/0.6-incubating-hadoop2/flink-tests-0.6-incubating-hadoop2.jar
          Uploaded: https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/flink/flink-tests/0.6-incubating-hadoop2/flink-tests-0.6-incubating-hadoop2.jar (11 KB at 9.2 KB/sec)
          {code}

          So maybe the flag is helpful for you as well.
          Show
          rmetzger Robert Metzger added a comment - I experienced a similar issue when deploying. I tried using the {{-DretryFailedDeploymentCount=10}} flag of the maven deploy plugin and indeed, I saw the following behavior: {code} Uploaded: https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/flink/flink-tests/0.6-incubating-hadoop2/flink-tests-0.6-incubating-hadoop2.pom (8 KB at 1.7 KB/sec) [WARNING] Encountered issue during deployment: Failed to deploy artifacts: Could not transfer artifact org.apache.flink:flink-tests:jar:0.6-incubating-hadoop2 from/to apache.releases.https ( https://repository.apache.org/service/local/staging/deploy/maven2): The target server failed to respond [INFO] Retrying deployment attempt 2 of 10 Uploading: https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/flink/flink-tests/0.6-incubating-hadoop2/flink-tests-0.6-incubating-hadoop2.jar Uploaded: https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/flink/flink-tests/0.6-incubating-hadoop2/flink-tests-0.6-incubating-hadoop2.jar (11 KB at 9.2 KB/sec) {code} So maybe the flag is helpful for you as well.
          Hide
          dashorst Martijn Dashorst added a comment -
          Today I got the same failure trying to release Wicket. No information other than:


          [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project wicket-jmx: Failed to deploy artifacts: Could not transfer artifact org.apache.wicket:wicket-jmx:jar:6.16.0 from/to apache.releases.https (https://repository.apache.org/service/local/staging/deploy/maven2): The target server failed to respond -> [Help 1]
          Show
          dashorst Martijn Dashorst added a comment - Today I got the same failure trying to release Wicket. No information other than: [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project wicket-jmx: Failed to deploy artifacts: Could not transfer artifact org.apache.wicket:wicket-jmx:jar:6.16.0 from/to apache.releases.https ( https://repository.apache.org/service/local/staging/deploy/maven2): The target server failed to respond -> [Help 1]
          Hide
          everett-toews Everett Toews added a comment - Reporter
          It was happening consistently randomly on May 26 and 27.

          I'm not sure how much help it is but this is what my traceroute looks like right now.

           1 router.asus.com (192.168.2.1) 1.424 ms 0.804 ms 0.852 ms
           2 * * *
           3 tge2-3.rdrktxaz01h.texas.rr.com (66.68.5.245) 22.312 ms 16.465 ms 7.233 ms
           4 tge0-8-0-6.ausutxla01r.texas.rr.com (66.68.0.10) 16.246 ms 19.139 ms 7.858 ms
           5 agg22.dllatxl301r.texas.rr.com (24.175.41.46) 23.579 ms 23.565 ms 20.060 ms
           6 ae-8-0.cr0.dfw10.tbone.rr.com (66.109.6.52) 23.667 ms 22.659 ms 20.409 ms
           7 ae-3-0.pr0.dfw10.tbone.rr.com (66.109.6.209) 22.279 ms
              ae-1-0.pr0.dfw10.tbone.rr.com (66.109.6.179) 21.405 ms 19.655 ms
           8 * * *
           9 4.69.146.9 (4.69.146.9) 57.248 ms
              4.69.146.25 (4.69.146.25) 65.425 ms
              4.69.146.5 (4.69.146.5) 53.343 ms
          10 ae-82-82.ebr2.dallas1.level3.net (4.69.151.154) 63.254 ms
              ae-72-72.ebr2.dallas1.level3.net (4.69.151.142) 60.973 ms
              ae-62-62.ebr2.dallas1.level3.net (4.69.151.130) 60.991 ms
          11 ae-2-2.ebr1.denver1.level3.net (4.69.132.105) 63.640 ms 65.914 ms 59.933 ms
          12 ae-1-100.ebr2.denver1.level3.net (4.69.151.182) 66.169 ms 60.560 ms 65.125 ms
          13 ae-2-2.ebr2.seattle1.level3.net (4.69.132.53) 63.170 ms 58.377 ms 63.153 ms
          14 ae-21-52.car1.seattle1.level3.net (4.69.147.163) 59.489 ms 66.088 ms 60.706 ms
          15 4.53.150.46 (4.53.150.46) 75.036 ms 68.226 ms 72.653 ms
          16 ptck-core2-gw.nero.net (207.98.64.138) 71.087 ms 67.644 ms 80.644 ms
          17 eugn-core2-gw.nero.net (207.98.64.9) 81.077 ms 71.390 ms 79.583 ms
          18 eugn-core1-gw.nero.net (207.98.64.161) 70.657 ms 86.018 ms 75.459 ms
          19 corv-car1-gw.nero.net (207.98.64.18) 72.595 ms 73.747 ms 90.530 ms
          20 * * *
          21 * * *
          22 * * *
          ...to infinity.
          Show
          everett-toews Everett Toews added a comment - Reporter It was happening consistently randomly on May 26 and 27. I'm not sure how much help it is but this is what my traceroute looks like right now.  1 router.asus.com (192.168.2.1) 1.424 ms 0.804 ms 0.852 ms  2 * * *  3 tge2-3.rdrktxaz01h.texas.rr.com (66.68.5.245) 22.312 ms 16.465 ms 7.233 ms  4 tge0-8-0-6.ausutxla01r.texas.rr.com (66.68.0.10) 16.246 ms 19.139 ms 7.858 ms  5 agg22.dllatxl301r.texas.rr.com (24.175.41.46) 23.579 ms 23.565 ms 20.060 ms  6 ae-8-0.cr0.dfw10.tbone.rr.com (66.109.6.52) 23.667 ms 22.659 ms 20.409 ms  7 ae-3-0.pr0.dfw10.tbone.rr.com (66.109.6.209) 22.279 ms     ae-1-0.pr0.dfw10.tbone.rr.com (66.109.6.179) 21.405 ms 19.655 ms  8 * * *  9 4.69.146.9 (4.69.146.9) 57.248 ms     4.69.146.25 (4.69.146.25) 65.425 ms     4.69.146.5 (4.69.146.5) 53.343 ms 10 ae-82-82.ebr2.dallas1.level3.net (4.69.151.154) 63.254 ms     ae-72-72.ebr2.dallas1.level3.net (4.69.151.142) 60.973 ms     ae-62-62.ebr2.dallas1.level3.net (4.69.151.130) 60.991 ms 11 ae-2-2.ebr1.denver1.level3.net (4.69.132.105) 63.640 ms 65.914 ms 59.933 ms 12 ae-1-100.ebr2.denver1.level3.net (4.69.151.182) 66.169 ms 60.560 ms 65.125 ms 13 ae-2-2.ebr2.seattle1.level3.net (4.69.132.53) 63.170 ms 58.377 ms 63.153 ms 14 ae-21-52.car1.seattle1.level3.net (4.69.147.163) 59.489 ms 66.088 ms 60.706 ms 15 4.53.150.46 (4.53.150.46) 75.036 ms 68.226 ms 72.653 ms 16 ptck-core2-gw.nero.net (207.98.64.138) 71.087 ms 67.644 ms 80.644 ms 17 eugn-core2-gw.nero.net (207.98.64.9) 81.077 ms 71.390 ms 79.583 ms 18 eugn-core1-gw.nero.net (207.98.64.161) 70.657 ms 86.018 ms 75.459 ms 19 corv-car1-gw.nero.net (207.98.64.18) 72.595 ms 73.747 ms 90.530 ms 20 * * * 21 * * * 22 * * * ...to infinity.
          Hide
          brianf Brian Fox added a comment -
          This could be some kind of timeout anywhere in the network between you and Nexus, including the reverse proxy. Is this still happening consistently or was it only at some point in time?
          Show
          brianf Brian Fox added a comment - This could be some kind of timeout anywhere in the network between you and Nexus, including the reverse proxy. Is this still happening consistently or was it only at some point in time?
          Hide
          abayer Andrew Bayer added a comment -
          fwiw, this doesn't seem to be general, in that I've been able to do the same commands from my laptop with no problem.
          Show
          abayer Andrew Bayer added a comment - fwiw, this doesn't seem to be general, in that I've been able to do the same commands from my laptop with no problem.

            People

            • Assignee:
              Unassigned
              Reporter:
              everett-toews Everett Toews
              Request participants:
              None
            • Votes:
              2 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: