SVN 工作正常，然后“svn: OPTIONS 200 OK"错误和“不存在" [英] SVN working fine and then "svn: OPTIONS 200 OK" error and "does not exist"

问题描述

SVN 工作得很好，直到几分钟前——我仍然可以在 http://浏览我的存储库svn.example.com/myrepo 但是当我尝试执行任何操作时，包括 svn up，我得到:

SVN was working just fine until a few minutes ago -- I can still browse my repository at http://svn.example.com/myrepo but when I try to perform any operation, including svn up, I get:

svn: OPTIONS of 'http://svn.example.com/myrepo': 200 OK (http://svn.example.com)

当我尝试 svn cleanup http://svn.example.com/myrepo 只是想看看会发生什么时，我得到了:

And when I tried svn cleanup http://svn.example.com/myrepo just to see what would happen, I got:

svn: 'http://svn.example.com/myrepo' does not exist

再次 -- 在浏览器中输入，我仍然可以很好地浏览存储库.怎么回事??

Again -- typing that into the browser, I can still browse the repository just fine. Whats going on??

推荐答案

好吧，原来这个问题的解决方案非常基础 –而且也很复杂.

Okay, so it turns out the solution to this problem was very basic – and also very complicated.

简单的答案:

主机名 svn.mywebsite.com 不存在(至少，就我的开发服务器而言不存在).

The hostname svn.mywebsite.com does not exist (at least, not as far as my development server is concerned).

对于遇到此问题的其他任何人，我强烈建议您从假设无论出于何种原因，您的客户端根本无法找到 SVN 服务器来解决问题.

For anyone else who's getting this problem, I strongly advise approaching the problem from the assumption that for whatever reason, your client simply cannot locate the SVN server.

--

复杂性:

现在对我来说，它变得有点复杂，因为正如我之前提到的，它正在工作 - 然后它停止了.

Now for me, it turned out to be a little more complex, because as I mentioned before, it WAS working -- and then it stopped.

这样做的原因是，如果您有兴趣，我们的 SVN 服务器与我们的主应用程序(位于 http://www.mywebsite.com)一起位于 Web 服务器上，这恰好镜像在另一台服务器上，mywebsite.com 的 DNS 记录以 AB 模式分布在两台服务器之间.由于我的开发服务器上的 SVN 客户端找不到 svn.mywebsite.com，它只是在寻找 mywebsite.com.一旦它连接到A"服务器，其中存在 SVN 服务器的虚拟主机记录，Apache 就会接管并提供适合 svn.mywebsite.com 的内容.

The reason for this, in case you are interested, is that our SVN server lives on a web server along with our main application (located at http://www.mywebsite.com), which happens to be mirrored on another server, and the DNS records for mywebsite.com are being distributed on an A-B pattern between the two servers. Since the SVN client on my development server couldn't find svn.mywebsite.com, it was looking for simply mywebsite.com. Once it connected to the "A" server, where the virtualhost records exist for the SVN server, Apache took over and served the content appropriate to svn.mywebsite.com.

但在某些时候，我的 DNS 缓存被刷新，并且没有可用的应用程序逻辑来悄悄地将用户发送回A"服务器，我的开发服务器开始将 mywebsite.com 解析到B"服务器 - 甚至还没有安装 SVN.

But at some point, my DNS cache was refreshed, and with no application logic available to quietly send the user back to the "A" server, my development server began resolving mywebsite.com to the "B" server -- where SVN hasn't even been installed.

显然，那是 SVN 客户端开始说呃，天哪，没有这样的服务器"的时候.(谁知道这就是 OPTIONS blah blah 200 OK 的意思?)

Obviously, that's when the SVN client started saying "uh, gee, there ain't no such server." (Who knew thats what OPTIONS blah blah 200 OK meant?)

为什么我是个白痴

这是不可避免的 ID10T 错误发挥作用的地方.我可以在 Firefox 中始终浏览到http://svn.mywebsite.com/myrepo"的原因是因为我在我的 PC 上手动创建了一个指向A"服务器 IP 地址的主机条目.

Here's where the inevitable ID10T error comes into play. The reason I could consistently browse to "http://svn.mywebsite.com/myrepo" in Firefox, was because I had manually created a host entry on my PC pointing to the IP address of the "A" server.

如果我早点记住这一点，我会节省很多时间–和几片珍贵的布洛芬片.:)

If I'd remembered that sooner, I would have saved myself a lot of time – and a few precious Ibuprofen tablets. :)

这篇关于SVN 工作正常，然后“svn: OPTIONS 200 OK"错误和“不存在"的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！