On 3/16/07, Tony Thompson <Tony.Thompson@stone-ware.com> wrote:
>
> Some more information about configuration and how the repository got into
> this state. We are using SVN through Apache with the SVN modules. We have
> a reverse proxy server sitting in front of the Apache server and are using
> the Tortoise client on developer workstations. Apparently the proxy server
> was the source of the corruption. I was able to go directly to the Apache
> server and not corrupt a new repository and also through another proxy and
> not corrupt the repository. So, a reboot of the proxy seemed to clear
> matters up.
>
> But, that concerns me a bit. To get it to corrupt, I could add 3 files to
> my working copy and use the tortoise client to commit them. It reported
> back that the three files had been committed but a check of the repository
> with the Tortoise repo browser showed that only two files were in the
> repository. I could not find any errors in the Apache access or error log
> that would indicate there was an issue committing files.
>
> Since the reboot, I can't reproduce the issue anymore so hopefully with
> that info and the bad repository I sent someone can come up with a good
> solution.
>
I entered an issue for you:
http://subversion.tigris.org/issues/show_bug.cgi?id=2744
You can get a tigris account and add yourself to the CC. If you still have
the bad proxy available, it might be helpful to capture the traffic between
the proxy and the server. The devs mentioned that on IRC.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
Received on Fri Mar 16 23:23:07 2007