On Mar 28, 2010, at 17:10, Ryan Schmidt wrote:
> On Mar 28, 2010, at 16:53, Ion Jaureguialzo Sarasola wrote:
>
>> I've setup a new repository with apache svn and everything works fine except commiting new files. Those which already exist behave well.
>>
>> My repositories are in a machine with Ubuntu 9.10 Server and the path for the repos is /var/subversion. All the repos are inside it.
>>
>> Here's the vhost for apache:
>>
>> <IfModule mod_ssl.c>
>> <VirtualHost 82.223.117.122:443>
>> ServerName svn.iosistemas.com
>>
>> <Location />
>> DAV svn
>> SVNParentPath /var/subversion/
>> AuthType Basic
>> AuthName "IO Sistemas SVN"
>> AuthUserFile /etc/subversion/passwd
>> Require valid-user
>> </Location>
>>
>>
>> SSLEngine on
>> SSLCertificateFile /etc/ssl/certs/server.crt
>> SSLCertificateKeyFile /etc/ssl/private/server.key
>>
>> </VirtualHost>
>> </IfModule>
>
> Don't forget to set a DocumentRoot. I use "DocumentRoot /var/empty" but you may want to set up a new directory to be this vhost's document root, so you can add things like a favicon.ico, xslt stylesheets, etc.
Upon further reflection, this doesn't work when the vhost is set up to serve repositories out of the root of the webspace. All requests, even those for e.g. favicon.ico, go to mod_dav_svn and are not handled by Apache. It may be possible to work around this using complicated mod_rewrite rules, but it's simpler to use a subdirectory of the webspace as discussed below.
>> [Sun Mar 28 23:22:56 2010] [error] [client 85.87.32.155] (20014)Internal error: Can't open file '/var/subversion/error/format': No such file or directory
>> [Sun Mar 28 23:22:56 2010] [error] [client 85.87.32.155] Could not fetch resource information. [500, #0]
>> [Sun Mar 28 23:22:56 2010] [error] [client 85.87.32.155] Could not open the requested SVN filesystem [500, #2]
>> [Sun Mar 28 23:22:56 2010] [error] [client 85.87.32.155] Could not open the requested SVN filesystem [500, #2]
>
> And presumably the repository's name is not "error"? I'm not sure why this is happening, but trying to put a repository at the root of a vhost is often problematic for a variety of reasons. I mean it works for me, but many others have reported problems. I have no slash at the end of my SVNParentPath definition and you do, so maybe that's part of it. If you can't resolve the problem, consider trying to place the repositories in a subdirectory of the webspace, e.g. "<Location /svn>", and see if that clears up the error.
Probably somehow your regular Apache error handling is kicking in here -- does your regular Apache error handling use resources from an "error" directory, or redirect to one? If so, that's why "error" is being requested here, and Subversion is rightly replying there's no such repository. So I'm not sure this is necessarily related to your inability to commit new files.
Received on 2010-03-29 00:46:13 CEST