Hi,

using 2.1.4 (epel) on centos 5.5, We had a firebird crash with this message:

Fatal lock manager error: invalid lock id (0), errno: 4

The system was under heavy load and it happened just after nbackup level 2
started (which may be related)

We need to work out how to avoid it happening again but currently don't
know why it happened.

any pointers or suggestions gratefully received.

Nick Upson


[Non-text portions of this message have been removed]