Error after server upgrade to 1.8.3 - E160052: Revprop caching disabled

2013-09-05 Thread Gordon Moore
I just upgraded my subversion server software from 1.7.2 to to 1.8.3, running 
on RedHat Linux 6.2.  Almost everything seems to be functioning correctly, 
however when I try to do an svnadmin dump or svnadmin verify of any of my 
repositories I get an error like this:

svnadmin: E160052: Revprop caching for '/svn/repos/build/db' disabled because 
SHM infrastructure for revprop caching failed to initialize.
svnadmin: E13: Can't open file 
'/svn/repos/build/db/rev-prop-atomics.mutex': Permission denied

Is this a known issue with 1.8.3? Any ideas on what is going on, how I can 
investigate, or what I might do to correct this?

    Gordon


Re: Error after server upgrade to 1.8.3 - E160052: Revprop caching disabled

2013-09-06 Thread Gordon Moore
I was just using a regular user, using command line SVN on the server with 
SELinux set to permissive.

I was finally able to figure out what was going on after seeing that doing an 
svnadmin verify with sudo worked. I guess 1.8 now needs to create files in the 
db directory, both a "rev-prop-atomics.shm" file which remains and a temporary 
.mutex file. After adjusting permissions to make the db directory writable, 
svnadmin verify is working again.

 


 From: Thomas Harold 
To: Gordon Moore  
Cc: "users@subversion.apache.org"  
Sent: Friday, September 6, 2013 12:34 AM
Subject: Re: Error after server upgrade to 1.8.3 - E160052: Revprop caching 
disabled
  

On 9/5/2013 6:41 PM, Gordon Moore wrote:
>
> Is this a known issue with 1.8.3? Any ideas on what is going on, how I
> can investigate, or what I might do to correct this?

I'd start with:

- How are you accessing the SVN repository? http? svn+ssh? svn?

- What are the ownership and permissions on the /svn/repos/build folder, 
the build/db folder, and the contents of the build/db
 folder?

- If you are running with SELinux set to Enforcing, try setting it 
temporarily to Permissive and see if the issue goes away.

- What user account are you using when trying to svnadmin dump / 
svnadmin verify?