Probably a typical problem, but ...

I've got a user that tunnels over ssh to do his svn commit/updates.

The version of Berkeley DB is 4.1.25, Apache 2.0.52, and Subversion 1.1.3.

The update/commit works fine the first time he initiates it if the log.*
and __db* files are erased, but upon trying to commit again, the
following error message appears on his end:

> kaplan@capepanwa:~/projects/staq$ svn update svn: PROPFIND request
> failed on '/svn/repos/kaplan/staq/trunk' svn: Berkeley DB error while
> checkpointing after Berkeley DB transaction for filesystem
> /var/svn/repos/db: Invalid argument

Then I check the error_log for apache and the following is the latest entry:

> [Wed Jun 29 16:39:51 2005] [error] [client xxx.xxx.xxx.xxx] Could not
> fetch resource information. [500, #0] [Wed Jun 29 16:39:51 2005]
> [error] [client xxx.xxx.xxx.xxx] Could not determine the proper
> revision to access [500, #160029] [Wed Jun 29 16:39:51 2005] [error]
> [client xxx.xxx.xxx.xxx] Berkeley DB error while checkpointing after
> Berkeley DB transaction for filesystem /var/svn/repos/db:\nInvalid
> argument [500, #160029]

I've tried new version of Berkeley DB and recompiling Subversion
appropriately, but still result in this error.

Is there an easy solution or a lead that you guys know of to resolve
this issue?

Thanks!

-- 
.==== === --  - --  - - -        -   - ---.
| Nate Metheny            IT Group Leader ||
| Santa Fe Institute          505.946.2730 |
|| http://www.santafe.edu nate_at_santafe.edu |
`---   -   -- -    -        --  - = == ==='
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org