Re: Berkeley DB problem: "Could not allocate memory"

Nicolás Lichtmaier <nick@reloco.com.ar> writes:

> The problem is happening right now. I've ran "db_stat -c -h" and I see
> the maximums "at any one time" haven't reached the maximuns. Doesn't
> that eliminates the posibility of having ran out of locks?

[...]

> 184 Number of current locks.
> 380 Number of current lockers.
> 7 Number of current lock objects.

Your repository should never have an lock accumulation when there are
no attached processes. If you did this db_stat during such a time,
then the fact that you have lock accumulation at all means that some
processes didn't cleanly detach from the Berkeley DB environment.
When this occurs, you can start seeing "Cannot allocate memory" errors
well before the reported lock accumulation nears the maximums.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Feb 8 16:55:50 2005