You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2010/10/18 15:14:23 UTC
[jira] Created: (INFRA-3078) Occasional 502 errors from
repository.apache.org
Occasional 502 errors from repository.apache.org
------------------------------------------------
Key: INFRA-3078
URL: https://issues.apache.org/jira/browse/INFRA-3078
Project: Infrastructure
Issue Type: Bug
Security Level: public (Regular issues)
Components: Nexus
Reporter: Jukka Zitting
Assignee: Brian Fox
The Jackrabbit Hudson builds have recently been failing fairly often due to problems in deploying snapshots to repository.apache.org. See for example https://hudson.apache.org/hudson/job/Jackrabbit-trunk/org.apache.jackrabbit$jackrabbit-spi-commons/1326/console for one such error.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (INFRA-3078) Occasional 502 errors
from repository.apache.org
Posted by "Ted Dunning (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924262#action_12924262 ]
Ted Dunning edited comment on INFRA-3078 at 10/23/10 7:11 PM:
--------------------------------------------------------------
Mahout just had a problem like this. Note that this occurred after INFRA-3067 was resolved. Gavin has suggested that we verify that Maven 2.2.1 was used, but I don't see anything in the 2.2.1 release notes that is a smoking gun. We will definitely verify that Sean was using >2.2.0
From: Sean Owen [mailto:srowen@gmail.com]
Sent: Friday, 22 October 2010 5:31 PM
To: infrastructure@apache.org
Cc: Mahout Dev List
Subject: HTTP 502 from https://repository.apache.org during Maven release process?
Hi infra, I'm hoping someone there may have an insight on the problem below. During our release process for Apache Mahout, it attempts to deploy artifacts to https://repository.apache.org. This is failing, for certain (large) files, with an HTTP 502 error.
Does that indicate we're doing something wrong? or is it a glitch / file size limit on the repo server?
Any ideas appreciated.
Sean
---------- Forwarded message ----------
From: Sean Owen <sr...@gmail.com>
Date: Thu, Oct 21, 2010 at 8:11 PM
Subject: Next build error
To: Mahout Dev List <de...@mahout.apache.org>
Latest is that I get very far in pushing the release to staging, and hit this:
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [ERROR] BUILD ERROR
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [INFO] Error deploying artifact: Failed to transfer file: https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/mahout/mahout-distribution/0.4/mahout-distribution-0.4.tar.gz. Return code is: 502
I'm investigating. Keeping you guys informed in case there are any bright ideas.
was (Author: tdunning):
Mahout just had a problem like this. Note that this occurred after INFRA-3067 was resolved. Gavin has suggested that we verify that Maven 2.2.1 was used, but I don't see anything in the 2.2.1 release notes that is a smoking gun. We will definitely verify that Sean was using >2.2.0
{verbatim}
From: Sean Owen [mailto:srowen@gmail.com]
Sent: Friday, 22 October 2010 5:31 PM
To: infrastructure@apache.org
Cc: Mahout Dev List
Subject: HTTP 502 from https://repository.apache.org during Maven release process?
Hi infra, I'm hoping someone there may have an insight on the problem below. During our release process for Apache Mahout, it attempts to deploy artifacts to https://repository.apache.org. This is failing, for certain (large) files, with an HTTP 502 error.
Does that indicate we're doing something wrong? or is it a glitch / file size limit on the repo server?
Any ideas appreciated.
Sean
---------- Forwarded message ----------
From: Sean Owen <sr...@gmail.com>
Date: Thu, Oct 21, 2010 at 8:11 PM
Subject: Next build error
To: Mahout Dev List <de...@mahout.apache.org>
Latest is that I get very far in pushing the release to staging, and hit this:
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [ERROR] BUILD ERROR
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [INFO] Error deploying artifact: Failed to transfer file: https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/mahout/mahout-distribution/0.4/mahout-distribution-0.4.tar.gz. Return code is: 502
I'm investigating. Keeping you guys informed in case there are any bright ideas.
{verbatim}
> Occasional 502 errors from repository.apache.org
> ------------------------------------------------
>
> Key: INFRA-3078
> URL: https://issues.apache.org/jira/browse/INFRA-3078
> Project: Infrastructure
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Nexus
> Reporter: Jukka Zitting
> Assignee: Brian Fox
>
> The Jackrabbit Hudson builds have recently been failing fairly often due to problems in deploying snapshots to repository.apache.org. See for example https://hudson.apache.org/hudson/job/Jackrabbit-trunk/org.apache.jackrabbit$jackrabbit-spi-commons/1326/console for one such error.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-3078) Occasional 502 errors from
repository.apache.org
Posted by "Ted Dunning (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924262#action_12924262 ]
Ted Dunning commented on INFRA-3078:
------------------------------------
Mahout just had a problem like this. Note that this occurred after INFRA-3067 was resolved. Gavin has suggested that we verify that Maven 2.2.1 was used, but I don't see anything in the 2.2.1 release notes that is a smoking gun. We will definitely verify that Sean was using >2.2.0
{verbatim}
From: Sean Owen [mailto:srowen@gmail.com]
Sent: Friday, 22 October 2010 5:31 PM
To: infrastructure@apache.org
Cc: Mahout Dev List
Subject: HTTP 502 from https://repository.apache.org during Maven release process?
Hi infra, I'm hoping someone there may have an insight on the problem below. During our release process for Apache Mahout, it attempts to deploy artifacts to https://repository.apache.org. This is failing, for certain (large) files, with an HTTP 502 error.
Does that indicate we're doing something wrong? or is it a glitch / file size limit on the repo server?
Any ideas appreciated.
Sean
---------- Forwarded message ----------
From: Sean Owen <sr...@gmail.com>
Date: Thu, Oct 21, 2010 at 8:11 PM
Subject: Next build error
To: Mahout Dev List <de...@mahout.apache.org>
Latest is that I get very far in pushing the release to staging, and hit this:
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [ERROR] BUILD ERROR
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [INFO] Error deploying artifact: Failed to transfer file: https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/mahout/mahout-distribution/0.4/mahout-distribution-0.4.tar.gz. Return code is: 502
I'm investigating. Keeping you guys informed in case there are any bright ideas.
{verbatim}
> Occasional 502 errors from repository.apache.org
> ------------------------------------------------
>
> Key: INFRA-3078
> URL: https://issues.apache.org/jira/browse/INFRA-3078
> Project: Infrastructure
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Nexus
> Reporter: Jukka Zitting
> Assignee: Brian Fox
>
> The Jackrabbit Hudson builds have recently been failing fairly often due to problems in deploying snapshots to repository.apache.org. See for example https://hudson.apache.org/hudson/job/Jackrabbit-trunk/org.apache.jackrabbit$jackrabbit-spi-commons/1326/console for one such error.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-3078) Occasional 502 errors from
repository.apache.org
Posted by "Brian Demers (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926372#action_12926372 ]
Brian Demers commented on INFRA-3078:
-------------------------------------
found the problem, see INFRA-3126
> Occasional 502 errors from repository.apache.org
> ------------------------------------------------
>
> Key: INFRA-3078
> URL: https://issues.apache.org/jira/browse/INFRA-3078
> Project: Infrastructure
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Nexus
> Reporter: Jukka Zitting
> Assignee: Brian Fox
>
> The Jackrabbit Hudson builds have recently been failing fairly often due to problems in deploying snapshots to repository.apache.org. See for example https://hudson.apache.org/hudson/job/Jackrabbit-trunk/org.apache.jackrabbit$jackrabbit-spi-commons/1326/console for one such error.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (INFRA-3078) Occasional 502 errors from
repository.apache.org
Posted by "Tony Stevenson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tony Stevenson closed INFRA-3078.
---------------------------------
Resolution: Fixed
We currently believe this was caused by the zone exhasting all it's ram and swap. A reboot has cured the issue and for now this is sufficient.
> Occasional 502 errors from repository.apache.org
> ------------------------------------------------
>
> Key: INFRA-3078
> URL: https://issues.apache.org/jira/browse/INFRA-3078
> Project: Infrastructure
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Nexus
> Reporter: Jukka Zitting
> Assignee: Brian Fox
>
> The Jackrabbit Hudson builds have recently been failing fairly often due to problems in deploying snapshots to repository.apache.org. See for example https://hudson.apache.org/hudson/job/Jackrabbit-trunk/org.apache.jackrabbit$jackrabbit-spi-commons/1326/console for one such error.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.