[cbi-dev] Maven Central connection resets

Discussion:

Christoph Daniel Schulze

2018-07-28 19:02:52 UTC

Hello everyone,

we (the ELK project) are having lots of trouble with our automatic build
at the moment [1]. The problems used to be limited to connection
problems while publishing artifacts to Sonatype. By now, we cannot get a
single build to complete due to problems downloading plug-ins from Maven
Central.

In short, here's the problem:

Downloading from central:
http://central.maven.org/maven2/com/google/code/gson/gson/maven-metadata.xml
[WARNING] Could not transfer metadata
com.google.code.gson:gson/maven-metadata.xml from/to central
(http://central.maven.org/maven2): Connection reset

Sure enough, the file does exist on the server.

Have other projects seen similar issues? If so, how did you solve them?

Cheers,
Chris

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=537325

Ed Willink

2018-07-28 20:02:00 UTC

Permalink

Hi

Yes, I have regular build fails. Trying again later works eventually,
probably because each attempt completes a few downloads till there is
nothing left to fetch.

If you look at the log in detail you will see that the transfer rate for
some successful downloads is only a few KB/s suggesting that the problem
is probably at the Maven end. I guess that such pathetic transfer rates
can vary a bit and when the rate drops it is a failure. Perhaps there is
a tomeout that Eclipse IT can set to be more tolerant.

Â Â Â Regards

Â Â Â Â Â Â Ed Willink

Post by Christoph Daniel Schulze
Hello everyone,
we (the ELK project) are having lots of trouble with our automatic build
at the moment [1]. The problems used to be limited to connection
problems while publishing artifacts to Sonatype. By now, we cannot get a
single build to complete due to problems downloading plug-ins from Maven
Central.
http://central.maven.org/maven2/com/google/code/gson/gson/maven-metadata.xml
[WARNING] Could not transfer metadata
com.google.code.gson:gson/maven-metadata.xml from/to central
(http://central.maven.org/maven2): Connection reset
Sure enough, the file does exist on the server.
Have other projects seen similar issues? If so, how did you solve them?
Cheers,
Chris
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=537325
_______________________________________________
cbi-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cbi-dev

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

Christoph Daniel Schulze

2018-07-30 08:19:53 UTC

Permalink

Hi Ed,

well, it's out nightly build, I don't really want to try it later. Also,
as it is now, it fails 100% of the time.

I just stumbled upon bug 492412 [1], which is about a mirror of Maven
Central. Should that mirror be used by default? Because that does not
seem to be the case in our build.

Cheers,
Chris

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=492412

Post by Ed Willink
Hi
Yes, I have regular build fails. Trying again later works eventually,
probably because each attempt completes a few downloads till there is
nothing left to fetch.
If you look at the log in detail you will see that the transfer rate for
some successful downloads is only a few KB/s suggesting that the problem
is probably at the Maven end. I guess that such pathetic transfer rates
can vary a bit and when the rate drops it is a failure. Perhaps there is
a tomeout that Eclipse IT can set to be more tolerant.
Â Â Â Regards
Â Â Â Â Â Â Ed Willink

<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
Virus-free. www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
_______________________________________________
cbi-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cbi-dev

Ed Willink

2018-07-30 09:09:34 UTC

Permalink

Hi

I just tried the cat ${HOME}/.m2/settings.xml on the OCL HIPP and it
differs from David's result:

+2 additonal server declarations
=1 same mirror declation
-1 proxy declaration

Perhaps the missing proxy is a concern.

Â Â Â Regards

Â Â Â Â Â Â Ed Willink

Post by Christoph Daniel Schulze
Hi Ed,
well, it's out nightly build, I don't really want to try it later. Also,
as it is now, it fails 100% of the time.
I just stumbled upon bug 492412 [1], which is about a mirror of Maven
Central. Should that mirror be used by default? Because that does not
seem to be the case in our build.
Cheers,
Chris
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=492412

_______________________________________________
cbi-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cbi-dev

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

Christoph Daniel Schulze

2018-07-30 09:21:00 UTC

Permalink

Hi Ed,

according to [1] the proxy doesn't seem to be necessary anymore.

I've been running the cat command as well. Indeed, the mirror is defined
in our settings file as well, but the Jenkins settings specify a
different settings file in order for us to be able to publish Maven
artifacts to the Sonatype servers. I'll check with the administrators
whether this setting causes ~/.m2/settings.xml to not be loaded.

Cheers,
Chris

[1] https://wiki.eclipse.org/Jenkins#Proxies

Post by Ed Willink
Hi
I just tried the cat ${HOME}/.m2/settings.xml on the OCL HIPP and it
+2 additonal server declarations
=1 same mirror declation
-1 proxy declaration
Perhaps the missing proxy is a concern.
Â Â Â Regards
Â Â Â Â Â Â Ed Willink

Christoph Daniel Schulze

2018-07-30 10:30:24 UTC

Permalink

Hi,

just to wrap this up: the problem seems to have been solved solved by
adding the Maven Central mirror to our custom settings file. Thanks for
the idea of looking at our settings file, Ed -- I must have missed that
while reading through the comments on bug 492412.

Cheers,
Chris

Post by Christoph Daniel Schulze
Hi Ed,
according to [1] the proxy doesn't seem to be necessary anymore.
I've been running the cat command as well. Indeed, the mirror is defined
in our settings file as well, but the Jenkins settings specify a
different settings file in order for us to be able to publish Maven
artifacts to the Sonatype servers. I'll check with the administrators
whether this setting causes ~/.m2/settings.xml to not be loaded.
Cheers,
Chris
[1] https://wiki.eclipse.org/Jenkins#Proxies

Frederic Gurr

2018-07-30 10:45:56 UTC

Permalink

Hi,

FYI:
We will add the missing Maven Central mirror to all existing Maven
settings files that are used for deployment to OSSRH.

Regards,

Fred

Post by Christoph Daniel Schulze
Hi,
just to wrap this up: the problem seems to have been solved solved by
adding the Maven Central mirror to our custom settings file. Thanks for
the idea of looking at our settings file, Ed -- I must have missed that
while reading through the comments on bug 492412.
Cheers,
Chris

--
Frederic Gurr
Release Engineer | Eclipse Foundation Europe GmbH

Annastr. 44, D-64673 Zwingenberg
Handelsregister: Darmstadt HRB 92821
Managing Directors: Ralph Mueller, Mike Milinkovich, Chris Laroque

Ed Willink

2018-07-30 12:05:24 UTC

Permalink

Hi

Could you please clarify?Sonatype/OSSRJ mean nothing to me.

Is the standard Jenkins / HIPP ok, or is that what you are fixing?

Is some action needed for a local Tycho build? Perhaps it was on a local
rather than Jenkins build that I observed very slow Maven connections.

Â Â Â Regards

Â Â Â Â Â Â Ed Willink

Post by Frederic Gurr
Hi,
We will add the missing Maven Central mirror to all existing Maven
settings files that are used for deployment to OSSRH.
Regards,
Fred

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

Christoph Daniel Schulze

2018-07-30 12:13:02 UTC

Permalink

Ed,

the ELK project publishes some of its compiled libraries as Maven
artifacts. Doing so includes pushing those artifacts to Sonatype's
servers (OSSRH refers to those same servers), which then distribute them
to be available through Maven Central. It's a bit of a mess regarding
the names...

Builds that do not publish to Sonatype servers are fine since they rely
on ~/.m2/settings.xml, where the Maven Central mirror is correctly
configured.

Builds that do publish to Sonatype servers need credentials to do so
securely. Those credentials are provided in a separate settings.xml file
which is used instead of ~/.m2/settings.xml and -- this is the problem
-- did not include the Maven Central mirror configuration.

The way I understand it, everything is fine as long as you don't have a
build that pushes to Maven Central, and even those builds are fixed as
we speak, according to Frederic's mail below.

Cheers,
Chris

Post by Ed Willink
Hi
Could you please clarify?Sonatype/OSSRJ mean nothing to me.
Is the standard Jenkins / HIPP ok, or is that what you are fixing?
Is some action needed for a local Tycho build? Perhaps it was on a local
rather than Jenkins build that I observed very slow Maven connections.
Â Â Â Regards
Â Â Â Â Â Â Ed Willink

Post by Frederic Gurr
Hi,
We will add the missing Maven Central mirror to all existing Maven
settings files that are used for deployment to OSSRH.
Regards,
Fred

Ed Willink

2018-07-30 13:09:38 UTC

Permalink

Hi

Thanks for clarifying Sonatype/OSSRH.

But what about a local M2E build (on my workstation)? I appear to have
no ~/.m2/settings.xml and so no mirror configuration. Since I'm in
Europe (UK), [1] suggests that I should have a mirror.

Â Â Â Regards

Â Â Â Â Â Â Ed Willink

[1] https://maven.apache.org/guides/mini/guide-mirror-settings.html

Post by Christoph Daniel Schulze
Ed,
the ELK project publishes some of its compiled libraries as Maven
artifacts. Doing so includes pushing those artifacts to Sonatype's
servers (OSSRH refers to those same servers), which then distribute them
to be available through Maven Central. It's a bit of a mess regarding
the names...
Builds that do not publish to Sonatype servers are fine since they rely
on ~/.m2/settings.xml, where the Maven Central mirror is correctly
configured.
Builds that do publish to Sonatype servers need credentials to do so
securely. Those credentials are provided in a separate settings.xml file
which is used instead of ~/.m2/settings.xml and -- this is the problem
-- did not include the Maven Central mirror configuration.
The way I understand it, everything is fine as long as you don't have a
build that pushes to Maven Central, and even those builds are fixed as
we speak, according to Frederic's mail below.
Cheers,
Chris

Post by Frederic Gurr
Hi,
We will add the missing Maven Central mirror to all existing Maven
settings files that are used for deployment to OSSRH.
Regards,
Fred

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

Christoph Daniel Schulze

2018-07-30 14:08:39 UTC

Permalink

Hi,

well, the websites says 'you _may_ want to use an alternative mirror for
a particular repository'. I interpret that as you can either leave you
configuration as is, or add a settings.xml with an appropriate mirror
configuration if you wish.

Why not add a local settings.xml file with the UK mirror and see if that
makes a discernible difference?

Cheers,
Chris

Post by Ed Willink
Hi
Thanks for clarifying Sonatype/OSSRH.
But what about a local M2E build (on my workstation)? I appear to have
no ~/.m2/settings.xml and so no mirror configuration. Since I'm in
Europe (UK), [1] suggests that I should have a mirror.
Â Â Â Regards
Â Â Â Â Â Â Ed Willink
[1] https://maven.apache.org/guides/mini/guide-mirror-settings.html