Re: Large Commits Fail

On 8/21/06, Erik Huelsmann <ehuels@gmail.com> wrote:

> Subversion+Apache can put a lot of strain on your server/network. Are
> you sure there's nothing such as bad RAM or network cards playing up?
> I don't know which other way to search... But, as always (still don't
> know your svn version): the latest official release is more stable
> than the previous ones: even in 'the core 1.0 functionality' we put
> out fixes in newer releases.

Sorry, I thought you were referring to the storage mechanism. I'm on
1.3.2. Similarly, my server is FC5/Apache 2.2.2. My client is WinXP.

> > > Did you have a look in the error log? Maybe one of the Apache childs
> > > is segfaulting?
> > >
> > I've looked at the apache error and access logs and everything looks
> > pretty normal. Nothing gets reported at all when the failure occurs.
> > Are there any svn logs I can look at? I've tried to find some, but
> > either they don't exist or I can't find them.
>
> No, there are none other than the standard Apache logs. All low-level
> requests (HTTP) are logged there. I think there is now in 1.3 or 1.4
> some higher level logging available which you need to configure, but
> that won't be helpfull here.

Too bad. Apache is giving me nothing to work with. :-) What is the
order of operations for a commit? When I try to commit from the
command line or using TSVN, I see a lot of output indicating that
changes are being sent, but then it aborts with the error reported.

-- 
Rob Wilkerson
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org