Transient errors with SBT/Maven repo downloads


#1

Hi there,

yesterday we had a quite annoying problem where the download of different JARs from maven repos would fail (jcenter.bintray.com mainly, but that’s also where most of our dependencies are at). When rebuilt with SSH, it would sometimes be different ones (even though there was a core set of JARs that would fail very often) and when trying to get them with curl it would be a success. Local builds (with wiped caches) finished without showing the same problem.

The same commit on a different branch worked 1-2 hours before we tried it on master and also built correctly on master just now (2016-09-28 6:30 UTC). The first build on master that failed because of the problem started around 2016-09-27 9:50 UTC. All in all we had 19 failed builds with some attempts to fix the problem by changing the resolvers in build.sbt and the repos in ~/.sbt/repositories (plus struggling with YAML ;-)).

Build output (with some omitted lines):

[info] Set current project to xxx (in build file:/home/ubuntu/yyy/xxx)
[info] Updating {file:/home/ubuntu/yyy/xxx/}xxx...
[info] Resolving org.scala-lang#scala-library;2.11.8 ...
[info] Resolving org.scala-lang#scala-library;2.11.8 ...
[info] Resolving org.apache.solr#solr-core;6.2.1 ...
[info] Resolving org.apache.solr#solr-core;6.2.1 ...
(...)
[info] Resolving org.sonatype.oss#oss-parent;7 ...
[info] downloading https://jcenter.bintray.com/org/scala-lang/scala-library/2.11.8/scala-library-2.11.8.jar ...
[info] 	[SUCCESSFUL ] org.scala-lang#scala-library;2.11.8!scala-library.jar (2235ms)
[info] downloading https://jcenter.bintray.com/org/apache/solr/solr-core/6.2.1/solr-core-6.2.1.jar ...
[warn] 	[FAILED     ] org.apache.solr#solr-core;6.2.1!solr-core.jar: The HTTP response code for https://jcenter.bintray.com/org/apache/solr/solr-core/6.2.1/solr-core-6.2.1.jar did not indicate a success. See log for more detail. (25ms)
[warn] 	[FAILED     ] org.apache.solr#solr-core;6.2.1!solr-core.jar: The HTTP response code for https://jcenter.bintray.com/org/apache/solr/solr-core/6.2.1/solr-core-6.2.1.jar did not indicate a success. See log for more detail. (25ms)
[warn] ==== jcenter: tried
[warn]   https://jcenter.bintray.com/org/apache/solr/solr-core/6.2.1/solr-core-6.2.1.jar
(...)
[info] downloading https://jcenter.bintray.com/jline/jline/2.12.1/jline-2.12.1.jar ...
[warn] 	[FAILED     ] jline#jline;2.12.1!jline.jar: The HTTP response code for https://jcenter.bintray.com/jline/jline/2.12.1/jline-2.12.1.jar did not indicate a success. See log for more detail. (22ms)
[warn] 	[FAILED     ] jline#jline;2.12.1!jline.jar: The HTTP response code for https://jcenter.bintray.com/jline/jline/2.12.1/jline-2.12.1.jar did not indicate a success. See log for more detail. (22ms)
[warn] ==== jcenter: tried
[warn]   https://jcenter.bintray.com/jline/jline/2.12.1/jline-2.12.1.jar
[warn] 	::::::::::::::::::::::::::::::::::::::::::::::
[warn] 	::              FAILED DOWNLOADS            ::
[warn] 	:: ^ see resolution messages for details  ^ ::
[warn] 	::::::::::::::::::::::::::::::::::::::::::::::
[warn] 	:: org.apache.solr#solr-core;6.2.1!solr-core.jar
[warn] 	:: org.apache.lucene#lucene-analyzers-common;6.2.1!lucene-analyzers-common.jar
[warn] 	:: org.apache.lucene#lucene-analyzers-kuromoji;6.2.1!lucene-analyzers-kuromoji.jar
[warn] 	:: org.apache.lucene#lucene-codecs;6.2.1!lucene-codecs.jar
[warn] 	:: org.apache.lucene#lucene-core;6.2.1!lucene-core.jar
[warn] 	:: org.apache.lucene#lucene-queries;6.2.1!lucene-queries.jar
[warn] 	:: org.apache.lucene#lucene-queryparser;6.2.1!lucene-queryparser.jar
[warn] 	:: org.apache.lucene#lucene-suggest;6.2.1!lucene-suggest.jar
[warn] 	:: org.apache.solr#solr-solrj;6.2.1!solr-solrj.jar
[warn] 	:: com.carrotsearch#hppc;0.7.1!hppc.jar
[warn] 	:: com.facebook.presto#presto-parser;0.122!presto-parser.jar
[warn] 	:: com.fasterxml.jackson.core#jackson-core;2.5.4!jackson-core.jar(bundle)
[warn] 	:: com.github.ben-manes.caffeine#caffeine;1.0.1!caffeine.jar
[warn] 	:: com.google.guava#guava;14.0.1!guava.jar(bundle)
[warn] 	:: com.google.protobuf#protobuf-java;2.5.0!protobuf-java.jar(bundle)
[warn] 	:: commons-codec#commons-codec;1.10!commons-codec.jar
[warn] 	:: commons-collections#commons-collections;3.2.2!commons-collections.jar
[warn] 	:: commons-configuration#commons-configuration;1.6!commons-configuration.jar
[warn] 	:: commons-io#commons-io;2.5!commons-io.jar
[warn] 	:: commons-lang#commons-lang;2.6!commons-lang.jar
[warn] 	:: dom4j#dom4j;1.6.1!dom4j.jar
[warn] 	:: joda-time#joda-time;2.2!joda-time.jar
[warn] 	:: log4j#log4j;1.2.17!log4j.jar(bundle)
[warn] 	:: org.antlr#antlr4-runtime;4.5.1-1!antlr4-runtime.jar
[warn] 	:: org.apache.curator#curator-recipes;2.8.0!curator-recipes.jar(bundle)
[warn] 	:: org.apache.hadoop#hadoop-common;2.7.2!hadoop-common.jar
[warn] 	:: org.apache.hadoop#hadoop-hdfs;2.7.2!hadoop-hdfs.jar
[warn] 	:: org.apache.htrace#htrace-core;3.2.0-incubating!htrace-core.jar
[warn] 	:: org.apache.httpcomponents#httpclient;4.4.1!httpclient.jar
[warn] 	:: org.apache.httpcomponents#httpcore;4.4.1!httpcore.jar
[warn] 	:: org.apache.zookeeper#zookeeper;3.4.6!zookeeper.jar
[warn] 	:: org.codehaus.woodstox#woodstox-core-asl;4.4.1!woodstox-core-asl.jar
[warn] 	:: org.eclipse.jetty#jetty-server;9.3.8.v20160314!jetty-server.jar
[warn] 	:: org.eclipse.jetty#jetty-util;9.3.8.v20160314!jetty-util.jar
[warn] 	:: org.restlet.jee#org.restlet;2.3.0!org.restlet.jar
[warn] 	:: org.scala-lang#scala-compiler;2.11.8!scala-compiler.jar
[warn] 	:: org.scala-lang#scala-reflect;2.11.8!scala-reflect.jar
[warn] 	:: org.scala-lang.modules#scala-xml_2.11;1.0.4!scala-xml_2.11.jar(bundle)
[warn] 	:: org.scala-lang.modules#scala-parser-combinators_2.11;1.0.4!scala-parser-combinators_2.11.jar(bundle)
[warn] 	:: jline#jline;2.12.1!jline.jar
[warn] 	::::::::::::::::::::::::::::::::::::::::::::::
(...)

Can you check what caused that problem?

Thanks,
Martin


#2

Having the same issue quite frequently with a private bintray repo. Happens in both api versions 1 and 2.


#3

Duplicate question with answer: Error Downloading Dependencies for Android with Gradle


#4

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.