I have found a solution:
The problem occurred due to the fact that the slave and master repositories
did not have the same name. One of the operations performed by SVN against
the slave server was using the master repository path and failed the
process. The solution was creating another location on the slave with the
same name as the master repository.
On Mon, May 25, 2009 at 5:21 PM, Tal Abramson <tala_at_alphacsp.com> wrote:
> Hi all
> i hope someone has encounter this behavior
> All my searches came out with no answer for this problem
> The situation is like so :
> we have a customer in a different continent , and we wish to have a
> mirror(slave) repository locally there
> So we have the master in here (executing the sync on a hook), and the slave
> other there (with SVNMasterURI to https)
> But any time we try to commit to the slave repository we are getting:
> svn ci -m"xx"
> svn: Commit failed (details follow):
> svn: At least one property change failed; repository is unchanged
> svn: Server sent unexpected return value (405 Method Not Allowed) in
> response to PROPPATCH request for
> I set up a different slave environment with the exact same settings , and
> it worked perfect
> When i looked at each server ssl_request_log , i see that the remote slave
> [25/May/2009:22:21:33 +0800] xx.xx.xx.xx TLSv1 DHE-RSA-AES128-SHA
> "PROPPATCH /svn-master/!svn/wbl/dda6c9ab-dd18-4520-ab9c-476a8200feb4/24
> HTTP/1.1" 976 "-" "SVN/1.5.4 (r33841) neon/0.28.2"
> While the local slave does not have it
> What is the sourse of this request?
> How do i investigate this ?
> we tried committing directly to the master from the remote network with
> The syncs works fine
> there are no authentications currently (as we are still in test phase)
> Thanks in advanced
> Best Regards
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-06-01 09:00:41 CEST