Subject | firebird.log: ISC_kill: error 2 starting gds_relay /opt/firebird//bin/gds_relay |
---|---|
Author | koehnfb |
Post date | 2007-03-07T10:07:19Z |
Hello,
we' re using FirebirdCS-1.5.1.4481-0 on Linux. Our Database size is
around 66 GB. Every application connects to the 66GB-Database and a
small database. The small Database (less than 1 MB) has only
generators and holds no data.
Yesterday we had a problem in connection the small database. No
connection was possible. In firebird.log the following error messages
appears: "Fatal lock manager error: semaphores are exhausted, errno: 4".
Connections to the 66GB-DB was possible. After a reboot of the Server,
we could connect to both databases.
Every night runs a sweep (gfix). This night the sweep hangs and
produces the error: "ISC_kill: error 2 starting gds_relay
/opt/firebird//bin/gds_relay" in the Firebird.log.
Who can us please explain what this error means and what we can do to
solve the problem?
Thanks.
we' re using FirebirdCS-1.5.1.4481-0 on Linux. Our Database size is
around 66 GB. Every application connects to the 66GB-Database and a
small database. The small Database (less than 1 MB) has only
generators and holds no data.
Yesterday we had a problem in connection the small database. No
connection was possible. In firebird.log the following error messages
appears: "Fatal lock manager error: semaphores are exhausted, errno: 4".
Connections to the 66GB-DB was possible. After a reboot of the Server,
we could connect to both databases.
Every night runs a sweep (gfix). This night the sweep hangs and
produces the error: "ISC_kill: error 2 starting gds_relay
/opt/firebird//bin/gds_relay" in the Firebird.log.
Who can us please explain what this error means and what we can do to
solve the problem?
Thanks.