Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 323873

Summary:	Bad Gateway Proxy Error
Product:	Community	Reporter:	David Carver <d_a_carver>
Component:	CI-Jenkins	Assignee:	Eclipse Webmaster <webmaster>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	david_williams, kaloyan, pwebster
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:

Description David Carver

2010-08-27 18:19:40 EDT

When trying to access an archived artifact in a Hudson job, from another hudson job, I'm getting the following error.

[WARNING] Failed to access p2 repository psychopath-processor (https://hudson.eclipse.org/hudson/view/WTP/job/cbi-wtp-wst.xsl.psychopath/lastSuccessfulBuild/artifact/sourceediting/development/org.eclipse.wst.xml.xpath2.processor.site/target/site/site.xml), will try to use local cache. Reason: org.eclipse.equinox.p2.core.ProvisionException: HTTP Server 'Bad Gateway' : https://hudson.eclipse.org/hudson/view/WTP/job/cbi-wtp-wst.xsl.psychopath/lastSuccessfulBuild/artifact/sourceediting/development/org.eclipse.wst.xml.xpath2.processor.site/target/site/site.xml

I can access it fine running the same job and configuration from the command line locally.  The error only occurs when running on the new eclipse hudson, master or slave machine.

Comment 1 Kaloyan Raev

2010-08-30 07:19:56 EDT

I have similar error when trying the install the result from a build in Eclipse using the p2 repository generated on the Hudson server. 

HTTP Server 'Bad Gateway' : https://hudson.eclipse.org/hudson/view/WTP/job/cbi-wtp.inc-jpaeditor/4/artifact/targetPlatform/content.jar
HTTP Server 'Bad Gateway' : https://hudson.eclipse.org/hudson/view/WTP/job/cbi-wtp.inc-jpaeditor/4/artifact/targetPlatform/content.jar
HttpClient connection error response code 502.

Comment 2 Eclipse Webmaster

2010-08-30 16:42:34 EDT

I think this bug is related to 322234.

I'm not seeing anything in the log file.  Is it possible your trying to access something that is being 'built' so it doesn't exist yet?

-M.

Comment 3 David Carver

2010-08-30 16:54:49 EDT

(In reply to comment #2)
> I think this bug is related to 322234.
> 
> I'm not seeing anything in the log file.  Is it possible your trying to access
> something that is being 'built' so it doesn't exist yet?

In my case no.  I'm trying access only the Last Successful Build artifacts, which are already built.

Comment 4 Kaloyan Raev

2010-08-31 02:35:05 EDT

Yes, looks like the same issue as in bug 322234.

Definitely, I was not trying to access files that are being built at that time.

Comment 5 Eclipse Webmaster

2010-08-31 09:55:37 EDT

Can you folks point me at the build logs where this occurred?  

Also where these 'automated'(scm triggered) builds or did you start them manually?

-M.

Comment 6 Kaloyan Raev

2010-09-15 11:48:57 EDT

I haven't experienced this problem lately.

Comment 7 David Carver

2010-09-20 16:17:50 EDT

Okay, I'm getting this pretty regularly again from jobs running on hudson.eclipse.org.

[WARNING] Failed to access p2 repository psychopath-processor (https://hudson.eclipse.org/hudson/view/WTP/job/cbi-wtp-wst.xsl.psychopath/lastSuccessfulBuild/artifact/sourceediting/development/org.eclipse.wst.xml.xpath2.processor.site/target/site), will try to use local cache. Reason: org.eclipse.equinox.p2.core.ProvisionException: HTTP Server 'Bad Gateway' : https://hudson.eclipse.org/hudson/view/WTP/job/cbi-wtp-wst.xsl.psychopath/lastSuccessfulBuild/artifact/sourceediting/development/org.eclipse.wst.xml.xpath2.processor.site/target/site/content.xml

I can hit this just fine from outside of eclipse.

Comment 8 Eclipse Webmaster

2010-09-20 17:00:57 EDT

(In reply to comment #7)
> Okay, I'm getting this pretty regularly again from jobs running on
> hudson.eclipse.org.

The strange thing is hudson is trying to connect to itself via the proxy, even though the exclude list is *.eclipse.org. I've updated the proxy to point requests for hudson back at it.

-M.

Comment 9 David Carver

2010-09-20 18:04:24 EDT

(In reply to comment #8)
> (In reply to comment #7)
> > Okay, I'm getting this pretty regularly again from jobs running on
> > hudson.eclipse.org.
> 
> The strange thing is hudson is trying to connect to itself via the proxy, even
> though the exclude list is *.eclipse.org. I've updated the proxy to point
> requests for hudson back at it.
> 
> -M.

Thanks, that seems to have fixed it.  I've got another issue to open for p2 related downloads to speed things up on that end.

Comment 10 Eclipse Webmaster

2010-09-30 15:58:59 EDT

Sounds like this is fixed.

-M.