Error Propfind Request Failed On

here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about propfind request failed 405 Stack Overflow the company Business Learn more about hiring developers or posting ads with propfind request failed method not allowed us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is propfind request failed 403 a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up SVN “PROPFIND request failed on…” up vote 18 down vote favorite 1 Having an

Propfind Request Failed 403 Forbidden

SVN issue here. Here's the scenario. I was checking out a repo (say foo) from SVN while doing some other commits / updates. My server died and I was left with an incomplete checkout. Fine. Problem is when I go back to access the foo repo, I am unable to. It just hangs forever. So, I went to http://subversion.apache.org/faq.html#bdb-recovery and ran svnadmin recover. I received an error so I ended up ra layer request failed propfind request failed on having to use db_recover and the command said it completed successfully. Now when I try to access repo, I am getting: svn: PROPFIND request failed on '/foo' svn: PROPFIND of '/foo': 500 Internal Server Error (https://svn.foobar.com) Also, if I navigate to https://svn.foobar.com/foo I see: Could not open the requested SVN filesystem Anyone have any thoughts? Note: All other repos work. It is just this one. svn share|improve this question edited Feb 25 '12 at 0:40 thekbb 4,64911944 asked May 26 '09 at 19:29 frio80 5882919 What was the error from svnadmin recover? –thekbb Feb 24 '12 at 23:19 add a comment| 8 Answers 8 active oldest votes up vote 3 down vote Did you run 'svnadmin recover' as the user usually using the repository (e.g. apache account)? If not the reason could be that some files are now owned by the user running 'svnadmin recover' leaving the apache account without rights to change the repository files. share|improve this answer answered May 27 '09 at 9:08 Bert Huijben 16.9k44165 1 In which case a simple chown apache.apache -R /path/to/repos should rectify the problem... –stephendl Sep 28 '09 at 11:50 add a comment| up vote 2 down vote i got this propfind error because the power went o

failed on '/some/repo/somewhere/with/a/trunk' svn: PROPFIND of '/some/repo/somewhere/with/a/trunk': Could not resolve hostname `some.host.org': Unknown host (http://some.host.org) Well, you are not alone. svn propfind request failed 405 method not allowed You are probably behind a proxy server (like Squid) that filters

Svn Propfind Request Failed Eclipse

and/or caches incoming and outgoing traffic. try doing what I did ... $ vi ~/.subversion/servers

Svn Propfind Request Failed On 403 Forbidden

then go down to the [global] section of the file where you might see soemthing like this: [global] # http-proxy-exceptions = *.exception.com, www.internal-site.org # http-proxy-host = http://stackoverflow.com/questions/912277/svn-propfind-request-failed-on defaultproxy.whatever.com # http-proxy-port = 7000 Uncomment some of the lines, and fill this section out with the name of your favorite proxy that your business throttles you with, so that it looks something like this: http-proxy-host = web-proxy.mycompany.com http-proxy-port = 8080 And then retry your subversion command. If your company's proxy server supports http://vsingleton.blogspot.com/2008/04/svn-propfind-request-failed-on.html all of the HTTP methods that Subversion uses like PROPFIND, REPORT, MERGE, MKACTIVITY, and CHECKOUT, then you should be fine. If something in the way does not support HTTP methods such as REPORT (like our proxy), then you might get subsequent errors like this: svn: REPORT request failed on '/repos/asf/!svn/vcc/default' svn: REPORT of '/repos/asf/!svn/vcc/default': Could not read response body: Connection reset by peer (http://some.host.org) Hope that helps. If anyone understands this issue better, and can shed some light on it, please give us a link that shows us how to avoid these issues completely. BOLD UPPERCASE WARNING! I AM GLAD THAT THE SOLUTION PROVIDED HAS HELPED SOME OF YOU, BUT 100s OF PEOPLE HAVE BEEN READING THIS POST EVERYDAY, AND WE WANT A MORE DEFINITIVE AND CLEAR ANSWER TO THESE ISSUES THAN WHAT YOU SEE ABOVE. WHY ARE PEOPLE HAVING ALL OF THESE ISSUES? THOSE OF YOU WHO FIGURE THIS OUT ... POST YOUR COMME

- 15th for workshops, presentations and all things Jenkins Learn more https://answers.atlassian.com/questions/111946/unable-to-connect-to-svn-repository Export Tools JenkinsJENKINS-32553svn: PROPFIND request failed can we add a retry after timeout?Log In propfind request ExportXMLWordPrintable Details Type: Bug Status: Open Priority: Minor Resolution: Unresolved Component/s: subversion-plugin Labels: None Environment: Windows 1.608 Similar Issues: Show Description Hello Is there a way for Jenkins to propfind request failed have a retry mechanism? The server is available.. so I can only think for an instant there was an intermittent network issue. Could Jenkins retry for 30 seconds? ERROR: Failed to update https://myserver/svn/trunk/ org.tmatesoft.svn.core.SVNException: svn: E175002: PROPFIND /svn/trunk failed at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51) at org.tmatesoft.svn.core.internal.io.dav.DAVUtil.findStartingProperties(DAVUtil.java:136) at org.tmatesoft.svn.core.internal.io.dav.DAVUtil.getVCCPath(DAVUtil.java:172) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.runReport(DAVRepository.java:1284) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.update(DAVRepository.java:839) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.updateInternal(SvnNgAbstractUpdate.java:192) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.update(SvnNgAbstractUpdate.java:76) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgUpdate.run(SvnNgUpdate.java:38) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgUpdate.run(SvnNgUpdate.java:18) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgOperationRunner.run(SvnNgOperationRunner.java:20) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1238) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:311) at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:291) at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:387) at hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:157) at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:161) at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:908) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:889) at hudson.scm.

to SVN repository10-1Zach MillerDec 03, 2012Using SVN 1.4.2 and FishEye 2.8.1 When I add a repo and try to "Test Connection", I receive the following error: Unable to get info for the repository root for [Repo Name] connect timed out and also: Unable to get Repository Root URL for [Repo Name]:https://repository.xxxx.com/xxx/xxx/ Exception getting FishEye access control connect timed out If I add the repo anyway, and then attempt to enable and start it, I receive this error: Unable to initialise repository [Repo Name] due to com.cenqua.fisheye.config.ConfigException:Could not access ... org.tigris.subversion.javahl.ClientException: svn: E175002: timed out waiting for server svn: E175002: PROPFIND request failed on ... Help? :csvnfisheyeCommentCommentAdd your comment...1 answer210Conor MacNeillDec 03, 2012All the errors seem to have the same root cause which looks to be that the Subversion server is not responding when FishEye attempts to connect to it. One thing to try, when logged in as the user which is used to run FishEye, is to see if you can connect to the svn repository using a command like svn info https://repository.xxxx.com/xxx/xxx/ I'd double check for typos in the configured URL, etc. BTW, I assume you meant FishEye 2.8.1 and not 1.8.1 CommentZach MillerDec 04, 2012Logged into my Fisheye server, 'svn info' returns an error: "could not connect to server" I can't even ping the SVN server from there. I know the SVN server is up and functioning, I can reach them via browser and committing works. What might this mean? Douglas FabrettiDec 04, 2012Hi Zach. Maybe there is a firewall blocking the connection - can be a outgoing rule from the FishEye Server or a incoming rule in the SVN Server. Another valid test would be trying to ping the svn server (or even trying to run the svn info command) from another host inside yo