I've come across another instance of the problem described in the email
below (quoted in full, since it was from a few months ago). Basically, when
a commit is attempted, a message "Commit failed MKACTIVITY of ... 200 OK"
message is displayed and the commit fails. Retrying the commit immediately
often succeeds. In my case the versions are as described below.
Searching the archives I did find one thread with a similar error, but the
only response I saw referred to case-sensitivity issues, and that wouldn't
seem to apply here since (a) both systems are Unix-based and thus
case-sensitive, and (b) that sort of ptoblem shouldn't go away on a retry...
Does anybody have any insight into what might be wrong? I can provide more
details / debugging if needed.
Many thanks for your help,
Versions in my setup
% uname -a
SunOS <machine> 5.8 Generic_117350-12 sun4u sparc SUNW,Ultra-Enterprise
% svn --version
svn, version 1.3.2 (r19776)
compiled Jul 26 2006, 14:36:42
Copyright (C) 2000-2006 CollabNet.
Subversion is open source software, see http://subversion.tigris.org/
This product includes software developed by CollabNet
The following repository access (RA) modules are available:
* ra_dav : Module for accessing a repository via WebDAV (DeltaV) protocol.
- handles 'http' scheme
* ra_svn : Module for accessing a repository using the svn network
- handles 'svn' scheme
* ra_local : Module for accessing a repository on local disk.
- handles 'file' scheme
% uname -a
Linux <machine> 2.6.15-27-server #1 SMP Fri Dec 8 18:43:54 UTC 2006 i686
libapache2-svn/dapper uptodate 1.3.1-3ubuntu1
> -----Original Message-----
> From: Scheie, Eric [mailto:firstname.lastname@example.org]
> Sent: 03 November 2006 23:18
> To: email@example.com
> Subject: MKACTIVITY ERROR 200 OK during commit
> We've stood up 3 different subversion instances across the
> country, call them locations A, B, and C. We use apache
> 2.2.3 and WebDav for remote access. Location A users can
> commit to location A without any errors. Location B and C
> users can also commit to location B and C respectively
> without any errors. If a location A user tries to commit to
> location B or C, the user gets the following error:
> Commit failed
> MKACTIVITY of
> '/svn/!svn/act/35981eaa-0a77-1f44-924e-2f13c87c6555': 200 OK
> If the location A user tries again, the commit is successful.
> Same results with location B user commits to locations A
> and C and location C user commits to locations A and B.
> Commits after the first failed commit are always successful.
> The first commit of the day to a remote location always
> fails. This problem has been noticed with the TortoiseSVN
> client, the SVN command line tool, and the SVN plugin for
> IntelliJ. Does anybody have any clue of what's causing
> these commits to fail the first time they are issued?
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Fri Jan 26 18:22:20 2007