top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

E175002 error when trying to downloading svn data from jenkins

0 votes

We are frequently getting the below error when trying to downloading svn data from jenkins. Issue will get resolved when we restart jenkins slave node.
Any idea what is the root cause?

org.tmatesoft.svn.core.SVNException [1]: svn: E175002: OPTIONS /svn/repo/trunk failed    
Caused by: 
Remote call on channel failed  at  at 
... 36 more Caused by: java.lang.NoClassDefFoundError: hudson/remoting/RemoteClassLoader$RemoteIClassLoader  at   
hudson.remoting.RemoteClassLoader.export(  at hudson.remoting.UserRequest.
(  at  ... 37 more     
posted Jul 13, 2015 by anonymous

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

1 Answer

0 votes

This error is raised from SvnKit A pure java reimplementation of the Subversion libraries.

While it is possible that this error is caused by the/a Subversion server, the fact that you can fix it by restarting Jenkins points towards an issue in either SvnKit or Jenkins.

'Caused by: java.lang.NoClassDefFoundError: hudson/remoting/RemoteClassLoader$RemoteIClassLoader'
would point towards a bit more towards Jenkins, than to SvnKit.

answer Jul 13, 2015 by Dewang Chaudhary
Similar Questions
+2 votes

FATAL: Unexpected termination of the channel
hudson.remoting.RequestAbortedException: Unexpected termination of the channel

0 votes

I just moved a subversion repository from an ubuntu linux 12.04 server running subversion 1.6.12 to an ubuntu Linux 14.04.1 server running subversion 1.8.8.

I have been able to export the code to an ubuntu 14.04.1 client running subversion 1.8.8 and when I do a
svn -u status
W155007: ‘home/xxx/src/trunk/c/eco’ is not a working copy

I get this error no matter what directory I do it in and it used to work fine before the move when we were running Ubuntu 12.04 clients with the old repository.

We are using apache2 with ssl for old and new repository.

+5 votes

We access our Subversion repositories mainly via svn+ssh:// on a central server. We limit access to the repos using Unix group membership. For example, the repo for ProjectA has 770 permissions and belongs to GroupA and ProjectB also has 770 permission and belongs to GroupB. So users who are in GroupA can access ProjectA and users in GroupB can access ProjectB. The file permissions look like this:

 drwxrws--- 7 svn GroupA 4096 Dec 27 2009 ProjectA
 drwxrws--- 7 svn GroupB 4096 Dec 27 2009 ProjectB

Everything is working as expected so far. Users in each group can only access their respective projects, and users in both groups can access both projects. But now we want to prevent a subset of users in GroupB from accessing certain subtrees of ProjectB. Can this be done when using svn+ssh:// access? If so, how?