Bug 327859 - "proxy error: Forbidden" when building on master
Summary: "proxy error: Forbidden" when building on master
Status: RESOLVED FIXED
Alias: None
Product: Community
Classification: Eclipse Foundation
Component: CI-Jenkins (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Eclipse Webmaster CLA
QA Contact:
URL: https://hudson.eclipse.org/hudson/job...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-15 03:17 EDT by Dennis Huebner CLA
Modified: 2011-03-30 03:54 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dennis Huebner CLA 2010-10-15 03:17:55 EDT
Our builds fail since yesterday 14.10.2010 12:05:08 with the following error:

master
master
com.jcraft.jsch.JSchException: ProxyHTTP: java.io.IOException: proxy error: Forbidden
        at com.jcraft.jsch.ProxyHTTP.connect(ProxyHTTP.java:158)
        at org.eclipse.jsch.internal.core.JSchProvider.connect(JSchProvider.java:141)
        at org.eclipse.team.internal.ccvs.core.connection.PServerConnection.open(PServerConnection.java:116)
        at org.eclipse.team.internal.ccvs.core.connection.Connection.open(Connection.java:132)
        at org.eclipse.team.internal.ccvs.core.connection.CVSRepositoryLocation.createConnection(CVSRepositoryLocation.java:545)
        at org.eclipse.team.internal.ccvs.core.connection.CVSRepositoryLocation.openConnection(CVSRepositoryLocation.java:806)
        at org.eclipse.team.internal.ccvs.core.client.Session.open(Session.java:159)
        at org.eclipse.buckminster.cvspkg.internal.CVSSession.getReaderSession(CVSSession.java:98)
        at org.eclipse.buckminster.cvspkg.internal.RepositoryMetaData.getMetaData(RepositoryMetaData.java:76)
        at org.eclipse.buckminster.cvspkg.internal.VersionFinder.getMetaData(VersionFinder.java:97)
        at org.eclipse.buckminster.cvspkg.internal.VersionFinder.getTrunk(VersionFinder.java:86)
        at org.eclipse.buckminster.core.version.AbstractSCCSVersionFinder.getBestTrunkMatch(AbstractSCCSVersionFinder.java:320)
        at org.eclipse.buckminster.core.version.AbstractSCCSVersionFinder.getBestVersion(AbstractSCCSVersionFinder.java:151)
        at org.eclipse.buckminster.core.rmap.model.Provider.findMatch(Provider.java:220)
        at org.eclipse.buckminster.core.rmap.model.SearchPath.getProvider(SearchPath.java:100)
        at org.eclipse.buckminster.core.rmap.model.ResourceMap.resolve(ResourceMap.java:293)
        at org.eclipse.buckminster.core.rmap.model.ResourceMap.resolve(ResourceMap.java:212)
        at org.eclipse.buckminster.core.resolver.ResourceMapResolver.innerResolve(ResourceMapResolver.java:202)
        at org.eclipse.buckminster.core.resolver.ResolverNodeWithJob.resolve(ResolverNodeWithJob.java:190)
        at org.eclipse.buckminster.core.resolver.ResolverNodeWithJob.run(ResolverNodeWithJob.java:87)
        at org.eclipse.buckminster.core.resolver.ResolverNodeWithJob$NodeResolutionJob.run(ResolverNodeWithJob.java:44)
        at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Caused by: java.io.IOException: proxy error: Forbidden
        at com.jcraft.jsch.ProxyHTTP.connect(ProxyHTTP.java:122)
        ... 21 more
Comment 1 Denis Roy CLA 2010-10-15 09:19:37 EDT
I think your pserver CVS is trying to use the Proxy server, when it should not.

Please read this thread -- I think it is related, and contains the proper config.

http://www.eclipse.org/forums/index.php?t=tree&goto=628738#page_top
Comment 3 Dennis Huebner CLA 2010-10-15 11:15:49 EDT
(In reply to comment #2)
> > http://www.eclipse.org/forums/index.php?t=tree&goto=628738#page_top
> 
> This message seems to contain the actual fix.
> 
> http://www.eclipse.org/forums/index.php?t=tree&goto=628738#page_top

I changed anything, since the last successful build. The proxy settings are still the same:

[MWE-nightly-HEAD] $ /shared/common/jdk-1.5.0-22.x86_64/bin/java -Dbuckminster.output.root=/opt/users/hudsonbuild/workspace/MWE-nightly-HEAD/buckminster.output -Dbuckminster.temp.root=/opt/users/hudsonbuild/workspace/MWE-nightly-HEAD/buckminster.temp '-Dhttp.proxyHost=proxy.eclipse.org -Dhttp.proxyPort=9898 -Dhttps.proxyHost=proxy.eclipse.org -Dhttps.proxyPort=9898 -Dhttp.nonProxyHosts="*.eclipse.org" -Dhttps.nonProxyHosts="*.eclipse.org"'

I don't really understand, how they can suddenly became wrong...
Comment 4 Eclipse Webmaster CLA 2010-10-15 11:37:24 EDT
The only 403 I see recorded in the proxy logs is:

[15/Oct/2010:11:06:38 -0400] "CONNECT dev.eclipse.org:2401 HTTP/1.0" 403 1038 "-" "-"

Which is at the approximate time your job ran.

Is there anyway to determine what the job is trying to resolve?

-M.
Comment 5 Denis Roy CLA 2010-10-15 11:39:14 EDT
Martin, isn't this the exact problem you had?  Would you be so kind as to help us out here?
Comment 6 Denis Roy CLA 2010-10-15 11:40:45 EDT
From bug 325786 comment 12:

Thank you!
adding  export no_proxy="dev.eclipse.org"  solved the problem.


Dennis, have you tried that?
Comment 7 Martin Taal CLA 2010-10-15 11:48:52 EDT
Yes seems to be the same problem and the same solution would help (hopefully!).

gr. Martin
Comment 8 Dennis Huebner CLA 2010-10-18 06:41:17 EDT
(In reply to comment #6)
> From bug 325786 comment 12:
> 
> Thank you!
> adding  export no_proxy="dev.eclipse.org"  solved the problem.
> 
> 
> Dennis, have you tried that?

I use hudson plugin to run buckminster, so I think no_proxy should be exported in the hudson global settings to get this work.
Comment 9 Eclipse Webmaster CLA 2010-10-18 10:40:07 EDT
no_proxy is already set(user shell), but I've updated the settings for .eclipse.org to try and exclude the entire domain.

I'll need to restart Hudson for these changes to take effect on the master.

-M.
Comment 10 Dennis Huebner CLA 2010-10-19 04:46:21 EDT
(In reply to comment #9)
> no_proxy is already set(user shell), but I've updated the settings for
> .eclipse.org to try and exclude the entire domain.
> 
> I'll need to restart Hudson for these changes to take effect on the master.
> 
> -M.

Works for me.
What is the current value of the no_proxy?
Comment 11 Eclipse Webmaster CLA 2010-10-19 09:42:36 EDT
Using Denis test job I've confirmed that:

no_proxy=localhost,127.0.0.1,dev.eclipse.org,.eclipse.org

On the master and both slaves.

-M.
Comment 12 Dennis Huebner CLA 2011-03-30 03:54:27 EDT
I think we can close this one.