You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Paul Smith <ps...@aconex.com> on 2007/08/01 07:52:49 UTC
Very odd central maven repo problem
This has happened before, and then appeared to magically resolve
itself, but it's quite sticky at the moment.
It seems to stem from this weirdness. Given a URL on the central Repo:
http://repo1.maven.org/maven2/org/apache/maven/maven/2.0.6/
maven-2.0.6.pom
1) I can browse using Firefox - OK
2) I can use command line 'curl' to view (curl http://repo1.maven.org/
maven2/org/apache/maven/maven/2.0.6/maven-2.0.6.pom)
3) I CANNOT use 'wget' to retrieve it (wget http://repo1.maven.org/
maven2/org/apache/maven/maven/2.0.6/maven-2.0.6.pom)
wget reports 403 Forbidden:
[psmith@forge tmp]$ wget http://repo1.maven.org/maven2/org/apache/
maven/maven/2.0.4/maven-2.0.4.pom-2.0.4.pom
--15:37:16-- http://repo1.maven.org/maven2/org/apache/maven/maven/
2.0.4/maven-2.0.4.pom
=> `maven-2.0.4.pom'
Resolving repo1.maven.org... 63.246.20.112
Connecting to repo1.maven.org|63.246.20.112|:80... connected.
HTTP request sent, awaiting response... 403 Forbidden
15:37:18 ERROR 403: Forbidden.
[psmith@forge tmp]$ wget http://repo1.maven.org/maven2/org/apache/
maven/maven/2.0.6/maven-2.0.6.pom
--15:38:22-- http://repo1.maven.org/maven2/org/apache/maven/maven/
2.0.6/maven-2.0.6.pom
=> `maven-2.0.6.pom'
Resolving repo1.maven.org... 63.246.20.112
Connecting to repo1.maven.org|63.246.20.112|:80... connected.
HTTP request sent, awaiting response... 403 Forbidden
15:38:22 ERROR 403: Forbidden.
[
I think this is why our Archiva repo says this:
337271615 [SocketListener0-0] ERROR
org.apache.maven.archiva.policies.PreDownloadPolicy:cache-failures -
Unknown checksum policyCode [cache]
337271615 [SocketListener0-0] INFO
org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default -
Failed pre-download policies - /volume2/maven2/org/apache/maven/maven/
2.0.6/maven-2.0.6.pom
337273843 [SocketListener0-0] WARN
org.apache.maven.archiva.policies.PostDownloadPolicy:checksum - SHA1
is incorrect for /volume2/maven2/org/apache/maven/maven/2.0.6/
maven-2.0.6.pom
337273843 [SocketListener0-0] WARN
org.apache.maven.archiva.policies.PostDownloadPolicy:checksum - MD5
is incorrect for /volume2/maven2/org/apache/maven/maven/2.0.6/
maven-2.0.6.pom
337273843 [SocketListener0-0] INFO
org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default -
Failed post-download policies - /volume2/maven2/org/apache/maven/
maven/2.0.6/maven-2.0.6.pom
And why when I temporarily remove the mirror settings to archiva and
manually move an originally downloaded 2.0.6 set of pom details, I
still get this:
....
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
'1991be0ed3e1820e135201406d5acabf8c08d426'; remote =
'218016709d90d14b64bfb1de3a86a2247e8873db' - RETRYING
Downloading: http://repo1.maven.org/maven2/org/apache/maven/maven/
2.0.6/maven-2.0.6.pom
8K downloaded
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
'1991be0ed3e1820e135201406d5acabf8c08d426'; remote =
'218016709d90d14b64bfb1de3a86a2247e8873db' - IGNORING
Is there something wacky with the repository? It seems to eventually
go away.
Paul Smith
Core Engineering Manager
Aconex
The easy way to save time and money on your project
696 Bourke Street, Melbourne,
VIC 3000, Australia
Tel: +61 3 9240 0200 Fax: +61 3 9240 0299
Email: psmith@aconex.com www.aconex.com
This email and any attachments are intended solely for the addressee.
The contents may be privileged, confidential and/or subject to
copyright or other applicable law. No confidentiality or privilege is
lost by an erroneous transmission. If you have received this e-mail
in error, please let us know by reply e-mail and delete or destroy
this mail and all copies. If you are not the intended recipient of
this message you must not disseminate, copy or take any action in
reliance on it. The sender takes no responsibility for the effect of
this message upon the recipient's computer system.
Re: Very odd central maven repo problem
Posted by Paul Smith <ps...@aconex.com>.
On 01/08/2007, at 4:01 PM, Milos Kleint wrote:
> AFAIK that's intentional. To avoid people downloading the whole
> repo through wget. rsynch is the preferred method I think.
>
Then why is curl not rejected? Why is Archiva failing? Why is my
local mvn retrieval also failing?
I'm happy to rsync, but I don't understand why I have to do this,
given it should be one of the initial things that a fresh maven
install would need to pull down?
cheers,
Paul
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Very odd central maven repo problem
Posted by Milos Kleint <Mi...@Sun.COM>.
AFAIK that's intentional. To avoid people downloading the whole repo
through wget. rsynch is the preferred method I think.
Milos
Paul Smith wrote:
> This has happened before, and then appeared to magically resolve
> itself, but it's quite sticky at the moment.
>
> It seems to stem from this weirdness. Given a URL on the central Repo:
>
> http://repo1.maven.org/maven2/org/apache/maven/maven/2.0.6/maven-2.0.6.pom
>
>
> 1) I can browse using Firefox - OK
> 2) I can use command line 'curl' to view (curl
> http://repo1.maven.org/maven2/org/apache/maven/maven/2.0.6/maven-2.0.6.pom)
>
> 3) I CANNOT use 'wget' to retrieve it (wget
> http://repo1.maven.org/maven2/org/apache/maven/maven/2.0.6/maven-2.0.6.pom)
>
>
>
> wget reports 403 Forbidden:
>
> [psmith@forge tmp]$ wget
> http://repo1.maven.org/maven2/org/apache/maven/maven/2.0.4/maven-2.0.4.pom-2.0.4.pom
>
> --15:37:16--
> http://repo1.maven.org/maven2/org/apache/maven/maven/2.0.4/maven-2.0.4.pom
>
> => `maven-2.0.4.pom'
> Resolving repo1.maven.org... 63.246.20.112
> Connecting to repo1.maven.org|63.246.20.112|:80... connected.
> HTTP request sent, awaiting response... 403 Forbidden
> 15:37:18 ERROR 403: Forbidden.
>
> [psmith@forge tmp]$ wget
> http://repo1.maven.org/maven2/org/apache/maven/maven/2.0.6/maven-2.0.6.pom
>
> --15:38:22--
> http://repo1.maven.org/maven2/org/apache/maven/maven/2.0.6/maven-2.0.6.pom
>
> => `maven-2.0.6.pom'
> Resolving repo1.maven.org... 63.246.20.112
> Connecting to repo1.maven.org|63.246.20.112|:80... connected.
> HTTP request sent, awaiting response... 403 Forbidden
> 15:38:22 ERROR 403: Forbidden.
>
> [
>
> I think this is why our Archiva repo says this:
>
> 337271615 [SocketListener0-0] ERROR
> org.apache.maven.archiva.policies.PreDownloadPolicy:cache-failures -
> Unknown checksum policyCode [cache]
> 337271615 [SocketListener0-0] INFO
> org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default -
> Failed pre-download policies -
> /volume2/maven2/org/apache/maven/maven/2.0.6/maven-2.0.6.pom
> 337273843 [SocketListener0-0] WARN
> org.apache.maven.archiva.policies.PostDownloadPolicy:checksum - SHA1
> is incorrect for
> /volume2/maven2/org/apache/maven/maven/2.0.6/maven-2.0.6.pom
> 337273843 [SocketListener0-0] WARN
> org.apache.maven.archiva.policies.PostDownloadPolicy:checksum - MD5 is
> incorrect for
> /volume2/maven2/org/apache/maven/maven/2.0.6/maven-2.0.6.pom
> 337273843 [SocketListener0-0] INFO
> org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default -
> Failed post-download policies -
> /volume2/maven2/org/apache/maven/maven/2.0.6/maven-2.0.6.pom
>
>
> And why when I temporarily remove the mirror settings to archiva and
> manually move an originally downloaded 2.0.6 set of pom details, I
> still get this:
> ....
> [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
> '1991be0ed3e1820e135201406d5acabf8c08d426'; remote =
> '218016709d90d14b64bfb1de3a86a2247e8873db' - RETRYING
> Downloading:
> http://repo1.maven.org/maven2/org/apache/maven/maven/2.0.6/maven-2.0.6.pom
>
> 8K downloaded
> [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
> '1991be0ed3e1820e135201406d5acabf8c08d426'; remote =
> '218016709d90d14b64bfb1de3a86a2247e8873db' - IGNORING
>
>
>
> Is there something wacky with the repository? It seems to eventually
> go away.
>
> Paul Smith
> Core Engineering Manager
>
> Aconex
> The easy way to save time and money on your project
>
> 696 Bourke Street, Melbourne,
> VIC 3000, Australia
> Tel: +61 3 9240 0200 Fax: +61 3 9240 0299
> Email: psmith@aconex.com www.aconex.com
>
> This email and any attachments are intended solely for the addressee.
> The contents may be privileged, confidential and/or subject to
> copyright or other applicable law. No confidentiality or privilege is
> lost by an erroneous transmission. If you have received this e-mail in
> error, please let us know by reply e-mail and delete or destroy this
> mail and all copies. If you are not the intended recipient of this
> message you must not disseminate, copy or take any action in reliance
> on it. The sender takes no responsibility for the effect of this
> message upon the recipient's computer system.
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Very odd central maven repo problem
Posted by Paul Smith <ps...@aconex.com>.
> It looks like your running a *nix, but can you tell us specifically
> what OS, JDK version, Maven version, etc? We've had Windows users run
> into similar problems who were having troubles due to overzealous
> antivirus software, etc.
>
maven 2.0.6 running on both OSX and RedHat EL3 (happens across
everything at the moment).
If I manually install that 2.0.6 pom from the one copy I have locally
(I must have retrieved it successfully through maven at one point) it
works fine, obviously because it doesn't have to download it.
Can someone please try moving aside their 2.0.6 maven plugin pom
directory and seeing if they get the same thing?
Paul
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Very odd central maven repo problem
Posted by Wayne Fay <wa...@gmail.com>.
Others have reported similar problems with wget. Without knowing this
for certain, I would assume that the repo1 owners simply do not like
people using wget to pull their entire repo down, so they might be
blocking it somehow. I believe the Maven website instructs people to
use rsync if they want to pull down their own copy of the repo (its
well over 10gb at this point, I'm sure).
It looks like your running a *nix, but can you tell us specifically
what OS, JDK version, Maven version, etc? We've had Windows users run
into similar problems who were having troubles due to overzealous
antivirus software, etc.
Wayne
On 8/1/07, Paul Smith <ps...@aconex.com> wrote:
> This has happened before, and then appeared to magically resolve
> itself, but it's quite sticky at the moment.
>
> It seems to stem from this weirdness. Given a URL on the central Repo:
>
> http://repo1.maven.org/maven2/org/apache/maven/maven/2.0.6/
> maven-2.0.6.pom
>
> 1) I can browse using Firefox - OK
> 2) I can use command line 'curl' to view (curl http://repo1.maven.org/
> maven2/org/apache/maven/maven/2.0.6/maven-2.0.6.pom)
> 3) I CANNOT use 'wget' to retrieve it (wget http://repo1.maven.org/
> maven2/org/apache/maven/maven/2.0.6/maven-2.0.6.pom)
>
>
> wget reports 403 Forbidden:
>
> [psmith@forge tmp]$ wget http://repo1.maven.org/maven2/org/apache/
> maven/maven/2.0.4/maven-2.0.4.pom-2.0.4.pom
> --15:37:16-- http://repo1.maven.org/maven2/org/apache/maven/maven/
> 2.0.4/maven-2.0.4.pom
> => `maven-2.0.4.pom'
> Resolving repo1.maven.org... 63.246.20.112
> Connecting to repo1.maven.org|63.246.20.112|:80... connected.
> HTTP request sent, awaiting response... 403 Forbidden
> 15:37:18 ERROR 403: Forbidden.
>
> [psmith@forge tmp]$ wget http://repo1.maven.org/maven2/org/apache/
> maven/maven/2.0.6/maven-2.0.6.pom
> --15:38:22-- http://repo1.maven.org/maven2/org/apache/maven/maven/
> 2.0.6/maven-2.0.6.pom
> => `maven-2.0.6.pom'
> Resolving repo1.maven.org... 63.246.20.112
> Connecting to repo1.maven.org|63.246.20.112|:80... connected.
> HTTP request sent, awaiting response... 403 Forbidden
> 15:38:22 ERROR 403: Forbidden.
>
> [
>
> I think this is why our Archiva repo says this:
>
> 337271615 [SocketListener0-0] ERROR
> org.apache.maven.archiva.policies.PreDownloadPolicy:cache-failures -
> Unknown checksum policyCode [cache]
> 337271615 [SocketListener0-0] INFO
> org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default -
> Failed pre-download policies - /volume2/maven2/org/apache/maven/maven/
> 2.0.6/maven-2.0.6.pom
> 337273843 [SocketListener0-0] WARN
> org.apache.maven.archiva.policies.PostDownloadPolicy:checksum - SHA1
> is incorrect for /volume2/maven2/org/apache/maven/maven/2.0.6/
> maven-2.0.6.pom
> 337273843 [SocketListener0-0] WARN
> org.apache.maven.archiva.policies.PostDownloadPolicy:checksum - MD5
> is incorrect for /volume2/maven2/org/apache/maven/maven/2.0.6/
> maven-2.0.6.pom
> 337273843 [SocketListener0-0] INFO
> org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default -
> Failed post-download policies - /volume2/maven2/org/apache/maven/
> maven/2.0.6/maven-2.0.6.pom
>
>
> And why when I temporarily remove the mirror settings to archiva and
> manually move an originally downloaded 2.0.6 set of pom details, I
> still get this:
> ....
> [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
> '1991be0ed3e1820e135201406d5acabf8c08d426'; remote =
> '218016709d90d14b64bfb1de3a86a2247e8873db' - RETRYING
> Downloading: http://repo1.maven.org/maven2/org/apache/maven/maven/
> 2.0.6/maven-2.0.6.pom
> 8K downloaded
> [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
> '1991be0ed3e1820e135201406d5acabf8c08d426'; remote =
> '218016709d90d14b64bfb1de3a86a2247e8873db' - IGNORING
>
>
>
> Is there something wacky with the repository? It seems to eventually
> go away.
>
> Paul Smith
> Core Engineering Manager
>
> Aconex
> The easy way to save time and money on your project
>
> 696 Bourke Street, Melbourne,
> VIC 3000, Australia
> Tel: +61 3 9240 0200 Fax: +61 3 9240 0299
> Email: psmith@aconex.com www.aconex.com
>
> This email and any attachments are intended solely for the addressee.
> The contents may be privileged, confidential and/or subject to
> copyright or other applicable law. No confidentiality or privilege is
> lost by an erroneous transmission. If you have received this e-mail
> in error, please let us know by reply e-mail and delete or destroy
> this mail and all copies. If you are not the intended recipient of
> this message you must not disseminate, copy or take any action in
> reliance on it. The sender takes no responsibility for the effect of
> this message upon the recipient's computer system.
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org