RE: Hang on import, update

I have an update on my hang on import problem. In review, I was getting a hang on import using subversion 0.36 on Fedora Core 1 (running server here) and running a 0.35.1 client on Windows. The hang was the result of either a segfault in apache or in one of apache's threads going "out to lunch" (100 % CPU usage) during an svn import (and only during an import, co, ci all seemed fine).

I *thought* I was building apache 2.0.48 and subversion 0.36 against Berkeley DB version 4.2 that I had built from source. As it turns out, ldd showed me that I was still linking in libdb-4.1.so. I have no idea why this was happening as I specified --with-berkeley-db=/usr/local/BerkeleyDB.4.2 on both the apache build and the svn build. I don't have the apr or apr-util rpms installed, nor the httpd rpm from fedora. Nothing I did would keep configure from picking up that shared object until I removed db4.1 from my sysem (rpm -e --nodeps db4, ouch! lots of broken packages now :-/). Can anyone explain why configure kept picking this up? Is there some other package that was built against db4.1 that subversion uses (besides apache, apr, and apr-util)?

As to the hang, I've done numerous imports and haven't had my server hang yet. I'm chalking this one up to an apache/db4.1 problem, though it could still be a race condition waiting to happen in 4.2. The long and short is, though, that I'm happy for now!

Cheers,
Craig

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jan 23 18:08:39 2004