Subject | FB CS-2.1 RC2 Crashing |
---|---|
Author | Arda |
Post date | 2008-04-09T09:06:37Z |
Hi,
I've switched to FirebirdCS-2.1.0.17755-ReleaseCandidate2 for over two
weeks and I'm facing frequent firebird crashes. When I was using
FbCS1.5.4 it wasn't crashing.
I've about 140 connections active, the database file size is about
7gb, the server have 32 bit fedora core4 installed , having 4gb of ram
and a 3.2ghz Xeon processor
Page buffers is set to 850, database is newly backed up and restored.
I don't see anything else than "INET/inet_error: read errno = 104" in
firebird.log
When it crashes the linux server keeps running but active connections
stop and no new connections can be established. After a reboot
everything runs fine.
I'm suspicious about the database monitoring queries. I was looking
who was doing what today and after I ran this exact query a few times,
the server crashed. But other people were using the database at the
same time too, I wasn't the only one connected.
This is probably a bug, so I wanted to mention about it.
Bye :)
---------
SELECT ATT.MON$USER,
ATT.MON$REMOTE_ADDRESS,
STMT.MON$SQL_TEXT,
STMT.MON$TIMESTAMP
FROM MON$ATTACHMENTS ATT
JOIN MON$STATEMENTS STMT
ON ATT.MON$ATTACHMENT_ID = STMT.MON$ATTACHMENT_ID
WHERE ATT.MON$ATTACHMENT_ID <> CURRENT_CONNECTION
AND STMT.MON$STATE = 1
---------
Note: I'll try to run this query over and over and see what happenes
when there's no one else using the database.
I've switched to FirebirdCS-2.1.0.17755-ReleaseCandidate2 for over two
weeks and I'm facing frequent firebird crashes. When I was using
FbCS1.5.4 it wasn't crashing.
I've about 140 connections active, the database file size is about
7gb, the server have 32 bit fedora core4 installed , having 4gb of ram
and a 3.2ghz Xeon processor
Page buffers is set to 850, database is newly backed up and restored.
I don't see anything else than "INET/inet_error: read errno = 104" in
firebird.log
When it crashes the linux server keeps running but active connections
stop and no new connections can be established. After a reboot
everything runs fine.
I'm suspicious about the database monitoring queries. I was looking
who was doing what today and after I ran this exact query a few times,
the server crashed. But other people were using the database at the
same time too, I wasn't the only one connected.
This is probably a bug, so I wanted to mention about it.
Bye :)
---------
SELECT ATT.MON$USER,
ATT.MON$REMOTE_ADDRESS,
STMT.MON$SQL_TEXT,
STMT.MON$TIMESTAMP
FROM MON$ATTACHMENTS ATT
JOIN MON$STATEMENTS STMT
ON ATT.MON$ATTACHMENT_ID = STMT.MON$ATTACHMENT_ID
WHERE ATT.MON$ATTACHMENT_ID <> CURRENT_CONNECTION
AND STMT.MON$STATE = 1
---------
Note: I'll try to run this query over and over and see what happenes
when there's no one else using the database.