Re: apache configuration (solved, mod_include conflict?)

[Jason Aubrey <au...@gmail.com>]

Hi All,

I've "solved" this problem - it seems to have been caused by loading
mod_include. Commenting out

Alias /pod  /var/www/wwdocs
<Location "/pod">
AddOutputFilter INCLUDES .html
</Location>

did not solve the problem, but commenting this out and disabling mod_include
did.  That seems odd to me; is it known that dav_svn and mod_include can
conflict like this?  I found this thread,

http://svn.haxx.se/users/archive-2003-08/0508.shtml

<http://svn.haxx.se/users/archive-2003-08/0508.shtml>but the question didn't
seem to get resolved.

Thanks,
Jason

On Thu, Jul 22, 2010 at 7:58 AM, Jason Aubrey <au...@gmail.com> wrote:

> Hi All,
>
> We are using svn over http and it was working perfectly until yesterday.
> SVN is configured to
> be served from the virtual host svn.webwork.maa.org on an ubuntu server as
> follows:
>
> <VirtualHost *:80>
>     ServerName svn.webwork.maa.org
>     DocumentRoot /var/www
>
> <Location />
>  DAV svn
>  SVNParentPath /var/svn
> etc...
>
> Yesterday, I added to the apache config file
>
> Alias /pod  /var/www/wwdocs
> <Location "/pod">
> AddOutputFilter INCLUDES .html
> </Location>
>
> to serve html versions of our pod docuemntation from webwork.maa.org/pod
>
> That seemed to work fine, but it didn't occur to me to check svn commits.
> But
> today I discover that commits are met wtih the message
>
> svn: Commit failed (details follow):
> svn: Could not open the requested SVN filesystem
>
> Unfortunately, this is all apache's error.log tells me too,  This persists
> even when I comment out the pod directive above and restart.
> Also, checkouts work, webwork.maa.org/viewvc works, and the repos are
> directly accessible over the web.
>
> Any suggestions for troubleshooting this?
>
> Thanks,
> Jason
>
>
>