Just speculating here, but the error message seems to indicate a lock file that it expected to be there, but isn't.
Maybe there is a cron job cleaning up /tmp?

Jason

Photios Loupis (4T) wrote:

> I am having a similar problem on Firebird 1.5.3.4870 CS (Linux) where
> I get the following error:
>
> Fatal lock manager error: invalid lock id (<id>) errno: 2
> --No such file or directory
>
> However, when I copy the database file to another server running
> Firebird 1.5.2.4731 CS (Linux) the database works fine, ie. I can
> MEND, BACKUP and RESTORE without any problems. The 1.5.3.4870 version
> still to this day gives me problems.
>
>
> --- In firebird-support@yahoogroups.com, "Milan Babuskov" <milanb@...>
> wrote:
>> Jason Dodson <jasond@...> wrote:
>>> Are you missing something like /tmp or /var?
>> No.
>>
>> Everything is fine and I can work. Only when I stop for a few
> minutes, the
>> error happens. Is it possible that Firebird drops ISQL's connection
> after
>> some time?
>>
>> The error message still confuses me:
>>
>>>> Fatal lock manager error: invalid lock id (18588), errno: 22
>>>> --No such file or directory
>> </M>
>>
>> ___________________________________________________________________
>> This mail sent using PanonNet Webmail - http://webmail.panonnet.net
>>
>
>
>
>
>
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Visit http://firebird.sourceforge.net and click the Resources item
> on the main (top) menu. Try Knowledgebase and FAQ links !
>
> Also search the knowledgebases at http://www.ibphoenix.com
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Yahoo! Groups Links
>
>
>
>
>
>
>
>

--
The information transmitted herewith is sensitive information intended only for use to the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon, this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer.