I just filed issue #1011 on a problem I ran into where update crapped
out due to a timeout and wouldn't restart because of an obstructing
object error.
I deleted the obstructing directory from my WC and restarted my
update, which seemed to be doing fine, but then it crapped out thusly:
[bartleby:~/Developer/FreeMethods/freemethods] wsanchez% svn up
subversion/libsvn_ra_dav/util.c:332: (apr_err=175002, src_err=0)
svn: RA layer request failed
svn: REPORT request failed on /
subversion/libsvn_ra_dav/util.c:81: (apr_err=175002, src_err=0)
svn: REPORT of /: Could not read status line: connection was closed by
server.
[bartleby:~/Developer/FreeMethods/freemethods] wsanchez% svn up
subversion/libsvn_ra_dav/util.c:332: (apr_err=160029, src_err=0)
svn: Berkeley DB error
svn: REPORT request failed on /
subversion/libsvn_ra_dav/util.c:163: (apr_err=160029, src_err=0)
svn:
Berkeley DB error while reading node revision for filesystem
/Volumes/data/Library/Subversion/FreeMethods/db:
Invalid argument
"Berkeley DB error" seems like a scary error. At this point, my
entire EC is hosed. Oh, worse, looks like the repository got borked.
If you go to the repository using a web browser:
Berkeley DB error while checkpointing after Berkeley DB transaction for
filesystem /Volumes/data/Library/Subversion/FreeMethods/db:
DB_INCOMPLETE: Cache flush was unable to complete
Uh oh.
-wsv
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Nov 23 21:50:34 2002