Continuous maven repo 403

Hi, @lesv,

https://travis-ci.org/preesm/graphiti/builds/551545973#L2736-L2739 reads:

[INFO] Finished at: 2019-06-27T23:03:51Z

[INFO] ------------------------------------------------------------------------

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-checkstyle-plugin:3.1.0:check (check-checkstyle) on project org.ietr.graphiti.parent: Execution check-checkstyle of goal org.apache.maven.plugins:maven-checkstyle-plugin:3.1.0:check failed: Plugin org.apache.maven.plugins:maven-checkstyle-plugin:3.1.0 or one of its dependencies could not be resolved: Failed to collect dependencies at org.apache.maven.plugins:maven-checkstyle-plugin:jar:3.1.0 -> org.apache.maven.reporting:maven-reporting-impl:jar:2.3: Failed to read artifact descriptor for org.apache.maven.reporting:maven-reporting-impl:jar:2.3: Could not transfer artifact org.apache.maven.reporting:maven-reporting-impl:pom:2.3 from/to google-maven-central (https://maven-central.storage-download.googleapis.com/repos/central/data/): Checksum validation failed, no checksums available -> [Help 1]

org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-checkstyle-plugin:3.1.0:check (check-checkstyle) on project org.ietr.graphiti.parent: Execution check-checkstyle of goal org.apache.maven.plugins:maven-checkstyle-plugin:3.1.0:check failed: Plugin org.apache.maven.plugins:maven-checkstyle-plugin:3.1.0 or one of its dependencies could not be resolved: Failed to collect dependencies at org.apache.maven.plugins:maven-checkstyle-plugin:jar:3.1.0 -> org.apache.maven.reporting:maven-reporting-impl:jar:2.3

Does this help?

Done: Checksum validation fail using Maven

Thanks.

Yes - it helps – I’ll update Checksum validation fail using Maven
unless you’d prefer it here.

I’ve verified the data exists and appears correct on the mirror. I’m still concerned about the @smowton connection issue. If possible, could you re-run w/ mvn -X and paste the errors into a message?

We’ve worked around it by forcing the Maven mirror to Sonatype’s repository, since they fixed the original whitelisting problem. Therefore we’re unlikely to be able to provide a useful log, not that it showed anything more interesting than a bunch of fetches followed by a reset. There were two Maven processes running concurrently at the time, so according to default settings max 10 concurrent threads; lots of artefacts had been downloaded by that point so presumably each connection was being pipelined a bunch. Our other similar repository with only one concurrent Maven process did not exhibit the problem, so I’d guess at a threshold on requests per apparent origin per second, but can’t be sure. I tried replicating this by spamming curl requests but couldn’t elicit anything.

Let’s continue this issue in the more focused topic. :slight_smile:

I’m closing this topic now. The checksum issue will be tracked elsewhere.

I wasn’t sure if I should create a new issue or post in this old one. I am encountering 403 errors from maven again in my builds. Here is an example: https://travis-ci.org/prestodb/presto/jobs/569532285

Here is the error message:

    Exception in thread "main" java.io.IOException: Server returned HTTP response code: 403 for URL: https://repo1.maven.org/maven2/org/apache/maven/apache-maven/3.5.0/apache-maven-3.5.0-bin.zip
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1894)
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1492)
	at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:263)
	at org.apache.maven.wrapper.DefaultDownloader.downloadInternal(DefaultDownloader.java:73)
	at org.apache.maven.wrapper.DefaultDownloader.download(DefaultDownloader.java:60)
	at org.apache.maven.wrapper.Installer.createDist(Installer.java:64)
	at org.apache.maven.wrapper.WrapperExecutor.execute(WrapperExecutor.java:121)
	at org.apache.maven.wrapper.MavenWrapperMain.main(MavenWrapperMain.java:50)

Seems like a new issue. Are you having trouble using maven-central or the GCS mirror? Tag me in the issue if it’s the GCS mirror.

Thanks @lesv for the reply! It was the old issue resurfacing, but it’s been resolved. See: https://issues.sonatype.org/browse/MVNCENTRAL-4985?focusedCommentId=774922&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-774922

Is this happening again?
https://travis-ci.org/prestodb/presto/jobs/634314845?utm_medium=notification&utm_source=github_status

$ ./mvnw -v Downloading https://repo1.maven.org/maven2/org/apache/maven/apache-maven/3.5.0/apache-maven-3.5.0-bin.zip Exception in thread "main" java.io.IOException: Server returned HTTP response code: 403 for URL: https://repo1.maven.org/maven2/org/apache/maven/apache-maven/3.5.0/apache-maven-3.5.0-bin.zip at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1894) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1492) at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:263) at org.apache.maven.wrapper.DefaultDownloader.downloadInternal(DefaultDownloader.java:73) at org.apache.maven.wrapper.DefaultDownloader.download(DefaultDownloader.java:60) at org.apache.maven.wrapper.Installer.createDist(Installer.java:64) at org.apache.maven.wrapper.WrapperExecutor.execute(WrapperExecutor.java:121) at org.apache.maven.wrapper.MavenWrapperMain.main(MavenWrapperMain.java:50) The command "./mvnw -v" failed and exited with 1 during .

Yes it has been reappearing today also for me, let’s hope it goes away again. (Build log) Received status code 403 from server: Forbidden

Same here failing with 403 https://api.travis-ci.org/v3/job/634372699/log.txt

And for our builds e.g. https://travis-ci.org/akka/akka-persistence-cassandra/builds/634319505?utm_source=github_status&utm_medium=notification

Some of my travis-ci.com builds started failing b/c of 403s for checksum file requests against Maven Central (https://repo1.maven.org/maven2/).

The response body of the 403 included this message:

You’ve been blocked from this operation due to violation of the Central terms of service. Please see https://central.sonatype.org/blacklisted to remediate this issue.

To workaround this issue, I moved my repository url over to Google’s mirror (https://maven-central.storage-download.googleapis.com/repos/central/data/), as mentioned by @BanzaiMan above.

Actually, take a look at https://maven-central.storage.googleapis.com/index.html – the path was updated a few months ago (and now updates every 2 hours), and I’ve stopped maintaining the repos/central/data/ path this weekend.

The correct path for your settings.xml file is:

<settings>
  <mirrors>
    <mirror>
      <id>google-maven-central</id>
      <name>GCS Maven Central mirror</name>
      <url>https://maven-central.storage-download.googleapis.com/maven2/</url>
      <mirrorOf>central</mirrorOf>
    </mirror>
  </mirrors>
</settings>

Which should be the default for Travis builds. It’s my understanding that if you haven’t cleared your build cache in a while you might not be using the correct path.

Also, if there is a problem with the GCS based maven-central mirror, please email gcs-maven-mirror@googlegroups.com as it has special filters that push me to see the issue faster. (I missed the email this morning - sorry)

3 Likes

Also many build failing due to this kind of resolution error … Quite annoying …

Is this nat.travisci.net list maintained? I am using it as a security control, and am regularly having failures, where the IP assigned to the build env is not reflected in this ip list. Is there a frequency that this gets updated?

I can help w/ GCS Maven issues - I’m not seeing one. I’m not sure if Travis is still using the mirror or not.

Imprint