My organization has adopted SVN for revision control over other popular
choices like CVS.
I have successfully maintained repositories on a local(LAN) server providing
access to the
clients using svnserve as a demon process for about 2 months.
But now, the new server is located at a geographically distant location and
hence there is a need for
a more secure access method. We moved from using the svnserve process to
using svn over a ssh tunnel.
Ever since I started access using ssh, my repository seems to get corrupted.
When I run 'svnadmin recover', the recovery process itself fails because the
is in an inconsistant state.
If I remove the log file(delete -- an incorrect thing to do), the recovery
process works fine.
I can checkout one copy of the code and the next immediate attempt to
or any access to the repository fails since the database goes into a
I have read through a lot of websites/forums trying to find some query
matching my problems.
I have also read the svn-bean-book but have not found anything specific in
The errors are listed below.
Error Berkeley DB error while checkpointing after Berkeley DB transaction of
Error Invalid argument
Error bdb: DB_ENV->log_flush:LSN of 51/193480 past current end-of-log of
Error bdb: Database environment corrupt; the wrong log files may have been
removed or incompatible database files imported from another environment.
These errors keep coming back even after a clean database recovery.
Could anyone please tell me what is causing this error/corruption?
Have I set the incorrect access permissions to the reposotory? I don't think
Also, this error happens irrespective of whether different users are
accessing the repo or the same user is accessing the repo multiple times.
I am completely stuck and have run out of ideas. Any help/clues/pointers are
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Tue Aug 23 23:18:48 2005