After migrating to a new machine (running Ubuntu + Plesk) and setting up SVN over HTTP (via libapache2-svn) we recently faced the problem that under some circumstances some new files could not be committed to the repo anymore. TortoiseSVN just returned the well known but unspecific error Could not open the requested SVN filesystem. After checking the web server logs (be sure to locate the right ones if you are using Plesk - by default they are located in the vhosts dir, e.g. /var/www/vhosts/yourdomain/statistics/logs/error_log) the following kind of internal errors showed up:
(20014)Internal error: Can't open file '/srv/svn/error/format': No such file or directory
(20014)Internal error: Can't open file '/srv/svn/error_docs/format': No such file or directory
For some bizarre reasons Apache tried to fetch information from a repository called error resp. error_docs (depending on environment). After hours of research it showed up this has to do with Plesk's custom error docs which are activated by default.
Solution: Disable custom error docs for your domain. To do so, log in to Plesk, navigate to the domain and uncheck the "Custom error documents" box in hosting settings.
Alternativ solution: Create a repo named error (or error_docs or whatever you find in the logs).
(20014)Internal error: Can't open file '/srv/svn/error/format': No such file or directory
(20014)Internal error: Can't open file '/srv/svn/error_docs/format': No such file or directory
For some bizarre reasons Apache tried to fetch information from a repository called error resp. error_docs (depending on environment). After hours of research it showed up this has to do with Plesk's custom error docs which are activated by default.
Solution: Disable custom error docs for your domain. To do so, log in to Plesk, navigate to the domain and uncheck the "Custom error documents" box in hosting settings.
Alternativ solution: Create a repo named error (or error_docs or whatever you find in the logs).




