Hi Jake!
>> Please try something like
>> top -b0.1 | grep svnserve
>> while trying that commit; maybe there's some ulimit or memory leak, and the
>> server
>> process gets killed.
>
> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
> 29746 svnbacku 20 0 114m 3936 2936 S 27 0.2 0:00.03 svnserve
> 29746 svnbacku 20 0 115m 4676 3220 S 18 0.2 0:00.05 svnserve
> 29746 svnbacku 20 0 116m 5928 3224 S 9 0.3 0:00.06 svnserve
> 29746 svnbacku 20 0 119m 8180 3256 R 55 0.4 0:00.12 svnserve
> 29746 svnbacku 20 0 119m 8288 3256 R 73 0.4 0:00.20 svnserve
> 29746 svnbacku 20 0 119m 8420 3256 R 73 0.4 0:00.28 svnserve
> 29746 svnbacku 20 0 119m 8288 3256 R 73 0.4 0:00.36 svnserve
> 29746 svnbacku 20 0 119m 8288 3256 R 73 0.4 0:00.44 svnserve
> 29746 svnbacku 20 0 119m 8288 3256 R 55 0.4 0:00.50 svnserve
> 29746 svnbacku 20 0 119m 8288 3256 R 46 0.4 0:00.55 svnserve
> 29746 svnbacku 20 0 119m 8424 3256 R 64 0.4 0:00.62 svnserve
> 29746 svnbacku 20 0 119m 8288 3256 R 64 0.4 0:00.69 svnserve
> 29746 svnbacku 20 0 119m 8288 3256 R 73 0.4 0:00.77 svnserve
> 29746 svnbacku 20 0 119m 8420 3256 R 67 0.4 0:00.84 svnserve
These numbers look normal to me ...
Now, please try starting the commit, and while it's running do
strace -p `pidof svnserve` -tt -f -o /tmp/svnserve-trace.log
(possibly as root).
What does
tail -30 /tmp/svnserve-trace.log
grep -E'sbrk|mmap' /tmp/svnserve-trace.log | tail -30
give? Is there an error that would show something like out-of-memory?
> I changed all the limits in /etc/security/limits.conf to soft limits but that
> didn't fix
> the issue (maybe I missed something -- see below).
>
> Here is something that did work, although I don't want to do this on a
> regular basis...
>
> I enabled root login so that svnserve would launch as root, and an 80MB
> checkin took
> about 20 seconds. It completed successfully.
What do you get if you run
ulimits -a -H
as user svnbackup?
> # svn --version
> svn, version 1.5.4 (r33841)
>
> At least that rules out any firewall issues. Seems like a resource
> constraint as you
> suspected.
Well, maybe there's a memory leak or something like that in 1.5.4.
Possibly a limit on CPU time - but that's unlikely.
Regards,
Phil
--
Versioning your /etc, /home or even your whole installation?
Try fsvs (fsvs.tigris.org)!
------------------------------------------------------
http://fsvs.tigris.org/ds/viewMessage.do?dsForumId=3928&dsMessageId=2356110
To unsubscribe from this discussion, e-mail:
[[email protected]].
