Unable to commit to Subversion

Question

I have a client who had to rebuild his automated build server. He checked out his project folder from my subversion server but is now no longer able to commit - he gets this err

Answer 1

Just an ownership issue probably. Try recursively changing the ownership of the directory like this:

chmod -R 777 /path/to/repo

Answer 2

I haven't seen it, but going on the error message I'm guessing something has gotten stuck writing a file. I'd try restarting your svn server process / reboot server.

Answer 3

i got such a problem recently(eclipse 3.7+svn plugin) and reboot my computer.it works now!

Answer 4

We have have the same issue come up from time to time. We have tried to:

Locally: Retry svn clean svn update kill all svn processes

Server: Check for open threads Bounce SVN

Currently the only fix we have is delete all the contents from the file and commit. After the success, we paste the contents of the file back in and commit again. If this gets the same error, we slowly fill up the file again a few bytes at a time until we can commit the whole thing.

Usually this occurs on one file in a commit and we commit each one individually until we figure out what FILE is causing the problem. Then we proceed with the above mentioned process.

Answer 5

Your repository has a stuck transaction. You can use the svnadmin command to repair it. Like all the other svn utilities, svnadmin takes a command followed by options (usually just the repository directory). svnadmin has to be run on the server with the repository.

Do something like this:

svnadmin lstxns /path/to/repository

to get a list of transactions in process (you should see your offending 551-1 there). You can then decide how best to recover from this error... svnadmin also has a command rmtxns to delete the offending transaction. For more information, issue:

svnadmin help

or see the tigris website: http://subversion.tigris.org/. You can also get more detailed help on specific commands by following the help command with the name of the command you're interested in. For example:

svnadmin help lstxns

Obviously you will need shell access to the repository server and write permissions on the repository to use svnadmin. If you're repository format is Berkely DB you should suspend your svnserve daemon (if you use it) and any web_dav/web_svn access to ensure you don't corrupt the database while issuing svnadmin commands.

Answer 6

Ran into this same issue after I cancelled a commit in progress. After doing the svnadm rmtxns with the transaction number to remove, I still got the message. I am using webdav with apache, so I restarted apache as suggested (/sbin/service httpd restart). Worked.