P
P
Petr Belyakov2014-12-22 23:10:40
subversion
Petr Belyakov, 2014-12-22 23:10:40

Why doesn't SVN allow commit?

The problem is as follows: The CentOS Minimal 6.3 x64 server with SVN repository on board was restored from a backup. SVN for the client is available, the checkout command runs without problems, viewing the change history too. Problems occur when trying to Commit a file.
The error output is:
Error Commit failed (detailis follow):
Error POST of '/svn/reponame/!svn/me': 404 Not Found ( http://192.168.xx.xx)
Completed!
Colleagues, tell me where to dig?
Just in case, I attach the Apache logs:
acces_log:
192.168.xx.xx - reponame [23/Dec/2014:00:07:13 +0400] "OPTIONS /svn/reponame/trunk HTTP/1.1" 200 193 "-" "SVN /1.8.11 (x64-microsoft-windows)serf/1.3.8 TortoiseSVN-1.8.9.26117"
192.168.xx.xx - reponame [23/Dec/2014:00:07:13 +0400] "OPTIONS /svn/reponame/trunk HTTP/1.1" 200 97 "-" "SVN/1.8.11 (x64-microsoft- windows) serf/1.3.8 TortoiseSVN-1.8.9.26117"
192.168.10.54 - reponame [23/Dec/2014:00:07:13 +0400] "POST /svn/reponame/!svn/me HTTP/1.1" 404 4486 "-" "SVN/1.8.11 (x64-microsoft-windows) serf/1.3.8 TortoiseSVN-1.8.9.26117"
error_log:
[Mon Dec 22 23:43:14 2014] [error] [client 192.168.xx.xx ] Could not fetch resource information. [403, #0]
[Mon Dec 22 23:43:14 2014] [error] [client 192.168.xx.xx] (2)No such file or directory: The URI does not contain the name of a repository. [403, #190001]
Thanks in advance to everyone who responds.

Answer the question

In order to leave comments, you need to log in

1 answer(s)
P
Petr Belyakov, 2014-12-23
@keptelr

The problem was solved by adding the following parameter to the Apache configuration file in the settings for accessing svn via http:
SVNAdvertiseV2Protocol off
Perhaps this solution will help someone.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question