You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Robin Becker <ro...@reportlab.com> on 2004/12/03 21:28:14 UTC

[Fwd: Re: svnadmin verify hangs]

> 
>>I am having a problem accessing one of several repositories on a
>>freeBSD 4.9 system with subversion 1.05 The repositories are normally
>>accessed via https and have been working fine for months.
>>
>>I tried
>>
>>svnadmin verify /svn/private
>>
>>to see if anything was up with the repository in question and the
>>command hangs. Anyone got any idea what's going on and how it might
>>occur?
> 
> 
> No idea.  Are you able to debug into it and see where it's hanging?
> 

sorry don't know enough to debug it.

> How long does it hang for?  (I.e., how long before you decided it was
> a "hang"?)  And what revision did it get to, out of how many?
>

it's hanging with state I or S and that means it's idle/sleeping. It
produces no output for several minutes.

I have checked that there appear to be no files with wrong ownership,
but I'm not really sure what the permissions should be. The owner/group
is www www so I am using sudo -u www to execute the svnadmin commands.

> 
>>Assuming it's broken is it ok to run svn recover without the verify?
> 
> 
> Shut off all other access first, then yes.
> 
> 

the recover command also hangs.

-- 
Robin Becker

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

Re: [Fwd: Re: svnadmin verify hangs]

Posted by Robin Becker <ro...@reportlab.com>.
Robin Becker wrote:
>>
>>> I am having a problem accessing one of several repositories on a
>>> freeBSD 4.9 system with subversion 1.05 The repositories are normally
>>> accessed via https and have been working fine for months.
>>>
>>> I tried
>>>
>>> svnadmin verify /svn/private
>>>
>>> to see if anything was up with the repository in question and the
>>> command hangs. Anyone got any idea what's going on and how it might
>>> occur?
.....
  I solved this after a while when I noticed three viewcvs.cgi processes 
which didn't seem to be doing anything. Even though I had terminated 
apache (our normal access method) it seemed that viewcvs was somehow 
preventing access to the db.

After killing these I was able to do a recover normally.

> 


-- 
Robin Becker

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