On Nov 12, 2008, at 10:26, Gleason, Todd wrote:
> We’re seeing failures a lot of the time (but not always) when we
> try to commit large amounts of data (this is an initial import with
> several hundred MB and over 20000 files). Here is a recent example:
>
> svn: Commit failed (details follow):
> svn: Server sent unexpected return value (401 Authorization
> Required) in response to PUT request for '/eng/[repo name]/!svn/wrk/
> ce3b1242-8c86-c340-ab31-857105e2e732/[some path/file]'
>
> We’re using NTLM with SSL cache timeout at 40,000 and
> Maxkeepaliverequests 0 (infinite). Prior to these settings we were
> seeing errors more like this:
>
> svn: Commit failed (details follow):
> svn: MKCOL of '/eng2/[repo name]/!svn/wrk/cb9d7151-437a-da41-
> b995-681352de7321/[some path] ': authorization failed (https://
> [server name])
>
> I don’t know whether these are essentially the same or different.
> We have also enabled basic authentication (I believe it’s
> SSPIOfferBasic On). Some of this is due to our network environment
> here, but some of it based on things I read athttp://www.nabble.com/
> SSPI-reauthentication-during-commit-fails-it-
> td9732674.html#a9868837 andhttp://www.nabble.com/TortoiseSVN,-
> HTTPS,-SSPI-combination-causes-(401-Authorization-Required)-errors-
> on-large-volume-repository-modifications-td15439239.html . It
> sounds like some of the problems may be with the neon Http library,
> but we’re using 1.5.2 (CollabNet client under Windows). The server
> is 1.5.2 running Apache 2.2 under Windows as well.
>
> We have also seen problems when trying to move multiple directories/
> files using the TortoiseSVN 1.5.3 repo-browser, but it appears to
> us as though one of the above settings may have resolved this
> issue. We’re not sure if these two problems are related or not.
>
> Note that most other operations seem to be working fine.
>
> Has anyone seen similar problems, or know what to try to make this
> more stable?
I don't know why you're running into that problem, but I wanted to
point out that there are other issues with having enormous commits
like this, such as anytime this initial revision is shown by "svn
log" it will take a long time. It might be better to break up your
initial import into several revisions (several imports). If you're
importing multiple projects, import each project separately. Or if
it's one large project, maybe import each folder separately. That may
coincidentally also avoid the problem you're having now.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-11-13 07:11:30 CET