I highly recommend you upgrade to 2.0.16. Your problem is most likely caused by a stale lock in the berkeley db code, and there is no solution besiders killing and restarting the master process. 2.0.16 fixes several db3 related problems and may fix your particular problem. Larry
