Subject | Lock manager out of room |
---|---|
Author | Aldo Caruso |
Post date | 2007-02-23T02:04:49Z |
Hi,
I'm running Firebird SS on Linux Debian Etch on a rather medium
sized database ( 600 MBytes aprox. ).
After some days running I got the following error when an attempt to
connect to the database is made:
"Lock manager out of room"
Watching into the firebird log file, I found the following trace of
error messages:
servin (Server) Thu Feb 22 12:11:23 2007
INET/inet_error: read errno = 88
servin (Server) Thu Feb 22 12:11:23 2007
INET/inet_error: send errno = 88
servin (Server) Thu Feb 22 12:11:23 2007
Database:
I/O error for file "/var/lib/firebird2
/data/mydatabase.fdb"
Error while trying to write to file
Bad file descriptor.
If I stop and start the server, back up and restore the database, it
returns to normality for a few days and then, back to the same error,
with the same trace in the /var/log/firebird.log file.
I'm not sure of the origin of the problem because previously I run for
months the same database in another server with Fedora Core 2, with no
problems at all.
So Hardware and OS changed and both are under my suspect ...
Thanks for any help,
Aldo
I'm running Firebird SS on Linux Debian Etch on a rather medium
sized database ( 600 MBytes aprox. ).
After some days running I got the following error when an attempt to
connect to the database is made:
"Lock manager out of room"
Watching into the firebird log file, I found the following trace of
error messages:
servin (Server) Thu Feb 22 12:11:23 2007
INET/inet_error: read errno = 88
servin (Server) Thu Feb 22 12:11:23 2007
INET/inet_error: send errno = 88
servin (Server) Thu Feb 22 12:11:23 2007
Database:
I/O error for file "/var/lib/firebird2
/data/mydatabase.fdb"
Error while trying to write to file
Bad file descriptor.
If I stop and start the server, back up and restore the database, it
returns to normality for a few days and then, back to the same error,
with the same trace in the /var/log/firebird.log file.
I'm not sure of the origin of the problem because previously I run for
months the same database in another server with Fedora Core 2, with no
problems at all.
So Hardware and OS changed and both are under my suspect ...
Thanks for any help,
Aldo