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
On Tue, Mar 13, 2001 at 10:32:11AM -0500, Damian Gerow wrote:
> On Mon, Mar 12, 2001 at 10:39:52PM -0500, Seva Adari wrote:
> > Signal 11 death could come from any number of problems.
> > Check if there are any mis-matches with the shared
> > libraries, specially db3 files. Make sure that the run
On Mon, Mar 12, 2001 at 10:39:52PM -0500, Seva Adari wrote:
> Signal 11 death could come from any number of problems.
> Check if there are any mis-matches with the shared
> libraries, specially db3 files. Make sure that the running
> program is not picking up the old libraries lingering
> around.
Signal 11 death could come from any number of problems.
Check if there are any mis-matches with the shared
libraries, specially db3 files. Make sure that the running
program is not picking up the old libraries lingering
around. On Linux you could use "ldd" on the the programs
linked with shared l
