Re: MKACTIVITY Issue

Silverman, Josh wrote:
> We have run into a difficulty when we switched servers. We are no
> longer able to commit our files. When we attempt to do so, we get the
> following message:
>
> “MKACTIVITY of ‘/svn/svn/act/cd86dda0-68a2-784a-a013-7f03ec6b5c9f’:
> Could not read status line: An existing connection was forcibly closed
> by the remote host.”
>
> This is true for users for used the “relocate” command for their copies
> of the repository and for those who reloaded the repository directly
> from the new server.
>
> Does anyone have an idea of what could be causing this? It appears to
> be a network issue, but of what nature? And how do we overcome it? I
> tried searching through the Internet for guidance, but it was a
> frustrating experience: the searches directed me to a number of forums
> in which users **asked** about this issue (or a similar MKACTIVITY
> issue) – apparently this problem comes up a lot – but relatively few
> that attempted to **answer** it.

There are several possible reasons for this:
* server is not configured correctly
   -> check the apache error log, you might find some information
      in there which will help.
* when you moved the repository, you forgot to do a dump/reload
   of the repository (that is necessary especially if the repository
   was moved between different OS)
* you're trying to acess the repository with the wrong url (svn://
   instead of http:// or vice-versa)
* if your new server is on linux, you used the wrong gcc version
   to compile the Subversion package
* a proxy rejects connections to the new server repo - most proxies
   or routers need a while (or even need a manual reset!) until they
   'learn' the new route to the server

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net