Additional info:
After issueing 'svnadmin verify' I have in /var/log/messages
May 26 13:11:47 vcs kernel: Out of Memory: Killed process 11822
(svnadmin).
May 26 13:11:55 vcs kernel: Out of Memory: Killed process 11558 (sshd).
May 26 13:12:06 vcs su(pam_unix)[11602]: session closed for user root
Thank you.
Yours sincerely,
Natalya Pyalling.
> -----Original Message-----
> From: Natalya Pyalling
> Sent: Wednesday, May 26, 2004 1:06 PM
> To: John Szakmeister; users@subversion.tigris.org
> Subject: RE: Re: Suddenly corrupted Subversion repository.
>
> Hi John,
>
> Thank you in advance. I issued ' svnadmin verify'. Always was ok. The
> software checked about 21000 revisions.
>
> The problem is :
> When somebody tryes to access to specific directory or update it, the
> server will be very slow. Apache takes too much CPU time and process
> dies. After this I has broken repository. I repair it with svnadmin
> recover. Then case repeats ...
>
> Something like a bad cycle ...
>
> Any another ideas?
>
> Thank you.
>
> Yours sincerely,
> Natalya Pyalling.
>
>
> > -----Original Message-----
> > From: John Szakmeister [mailto:john@szakmeister.net]
> > Sent: Wednesday, May 26, 2004 12:15 PM
> > To: users@subversion.tigris.org
> > Subject: Re: Suddenly corrupted Subversion repository.
> >
> > On Wednesday 26 May 2004 03:50, you wrote:
> > [snip]
> > > /var/Repository/repos/db:
> > > total 2932360
> > > -rw-rw-r-- 1 svn svn 33140736 May 26 11:01 changes
> > > -rw-rw-r-- 1 svn svn 3084288 May 26 11:01 copies
> > > -rw-rw-r-- 1 svn svn 16384 May 25 20:49 __db.001
> > > -rw-rw-r-- 1 svn svn 278528 May 25 20:49 __db.002
> > > -rw-rw-r-- 1 svn svn 327680 May 25 20:49 __db.003
> > > -rw-rw-r-- 1 svn svn 892928 May 25 20:49 __db.004
> > > -rw-rw-r-- 1 svn svn 16384 May 25 20:49 __db.005
> > > -rw-rw-r-- 1 svn svn 1738 Apr 2 10:24 DB_CONFIG
> > > -rw-rw-r-- 1 apache svn 1048567 May 26 10:53 log.0000014239
> > > -rw-rw-r-- 1 apache svn 19419 May 26 11:01 log.0000014240
> > > -rw-rw-r-- 1 svn svn 45895680 May 26 11:01 nodes
> > > -rw-rw-r-- 1 svn svn 36950016 May 26 11:01 representations
> > > -rw-rw-r-- 1 svn svn 491520 May 26 11:01 revisions
> > > -rw-rw-r-- 1 svn svn 2871267328 May 26 11:01 strings
> > > -rw-rw-r-- 1 svn svn 6844416 May 26 11:01 transactions
> > > -rw-rw-r-- 1 svn svn 8192 May 26 11:01 uuids
> > >
> > > /var/Repository/repos/hooks:
> > > total 28
> > > -rw-r--r-- 1 akharchenko svn 7240 Apr 20 15:07 mailer.conf
> > > -rw-rw-r-- 1 svn svn 1411 Apr 2 10:24 post-commit.tmpl
> > > -rw-rw-r-- 1 svn svn 1475 Apr 2 10:24
> post-revprop-change.tmpl
> > > -rw-rw-r-- 1 svn svn 2216 Apr 2 10:24 pre-commit.tmpl
> > > -rw-rw-r-- 1 svn svn 1952 Apr 2 10:24
> pre-revprop-change.tmpl
> > > -rw-rw-r-- 1 svn svn 1500 Apr 2 10:24 start-commit.tmpl
> > >
> > > /var/Repository/repos/locks:
> > > total 8
> > > -rw-rw-r-- 1 svn svn 460 Apr 2 10:24 db.lock
> > > -rw-rw-r-- 1 svn svn 295 Apr 2 10:24 db-logs.lock
> > > [svn@vcs usual]$
> > >
> > > Always is ok in my point of view. And it worked fine before. :(
> > >
> > > Any ideas?
> >
> > It looks your permissions are fine then. I had to ask... it seems
to
> be
> > one
> > of the more common problems.
> >
> > The next action I would take is to verify that your repository is
okay
> by
> > running 'svnadmin verify' on it.
> >
> > -John
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> > For additional commands, e-mail: users-help@subversion.tigris.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed May 26 11:20:56 2004