Did someone maybe upgrade Berkeley DB shared libraries on that system,
after you installed Subversion?
Geoff Smith <geoffrey.smith@nrl.navy.mil> writes:
> I am a very new subversion users (actually, user of version control at
> all), and I seem to have run into a problem. I have a small project
> which I decided to try subversion on, and things had been going ok for
> a few weeks, and a few revisions/commits. I use svnserve and svn+ssh
> to access the repository remotely. Running Mac OS X versions (1.1.1
> and 1.0.9) installed via fink.
>
> As I mentioned, everything seemed fine for a while, but a few days ago
> I lost access to the server --- when ever I tried any svn command I
> got the response:
>
> myBox:~/work/ASME gbsmith$ svn log
> gbsmith@my.server's password:
> svn: Connection closed unexpectedly
> myBox:~/work/ASME gbsmith$
>
> So, I logged into the machine directly and tried to update a local
> working copy, to which I got the following errors:
>
> my.server:~/ASME gbsmith$ svn log
> svn: Berkeley DB error while checkpointing after Berkeley DB
> transaction for filesystem /Users/gbsmith/svn-work/ASME/db:
> Invalid argument
> svn: bdb: Ignoring log file:
> /Users/gbsmith/svn-work/ASME/db/log.0000000029: magic number 0, not
> 40988
> svn: bdb: DB_ENV->log_put: 29: Invalid argument
> svn: bdb: txn_checkpoint: failed to flush the buffer cache Invalid argument
> Abort trap
> my.server:~/ASME gbsmith$
>
> not knowing what else to try, I tried a couple of admin commands to
> see if anything worked:
>
> my.server:~/svn-work/ASME gbsmith$ svnadmin lstxns
> /Users/gbsmith/svn-work/ASMEsvn: Berkeley DB error while checkpointing
> after Berkeley DB transaction for filesystem
> /Users/gbsmith/svn-work/ASME/db:
> Invalid argument
> svn: bdb: Ignoring log file:
> /Users/gbsmith/svn-work/ASME/db/log.0000000029: magic number 0, not
> 40988
> svn: bdb: DB_ENV->log_put: 29: Invalid argument
> svn: bdb: txn_checkpoint: failed to flush the buffer cache Invalid argument
> svn: Berkeley DB error while closing 'nodes' database for filesystem
> /Users/gbsmith/svn-work/ASME/db:
> Invalid argument
> svn: bdb: Ignoring log file:
> /Users/gbsmith/svn-work/ASME/db/log.0000000029: magic number 0, not
> 40988
> svn: bdb: DB_ENV->log_put: 29: Invalid argument
> svn: bdb: Ignoring log file:
> /Users/gbsmith/svn-work/ASME/db/log.0000000029: magic number 0, not
> 40988
> svn: bdb: DB_ENV->log_put: 29: Invalid argument
> my.server:~/svn-work/ASME gbsmith$ svnadmin list-dblogs
> /Users/gbsmith/svn-work/ASME
> svn: Invalid argument
> svn: bdb: Ignoring log file:
> /Users/gbsmith/svn-work/ASME/db/log.0000000029: magic number 0, not
> 40988
> svn: bdb: DB_ENV->log_put: 29: Invalid argument
> my.server:~/svn-work/ASME gbsmith$ svnadmin recover
> /Users/gbsmith/svn-work/ASMERepository lock acquired.
> Please wait; recovering the repository may take some time...
> svn: DB_RUNRECOVERY: Fatal error, run database recovery
> svn: bdb: Ignoring log file:
> /Users/gbsmith/svn-work/ASME/db/log.0000000029: magic number 0, not
> 40988
> svn: bdb: Invalid log file: log.0000000029: Invalid argument
> svn: bdb: First log record not found
> svn: bdb: PANIC: Invalid argument
> my.server:~/svn-work/ASME gbsmith$ ls
>
>
> Sorry for the longish post.... Any insight would be much appreciated --
>
> Thanks,
>
> -geoff
>
>
> --
> Geoff Smith voice: 202.404.6324
> Naval Research Laboratory; Code 7233 fax: 202.404.5689
> 4555 Overlook Ave., SW geoffrey.smith@nrl.navy.mil
> Washington, DC 20375
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Nov 18 19:45:06 2004