Problems when a new user wants to access our system - Firebird memory
MON$ATTACHMENTS HUNG - not access
-------------------------------------------------------------------------------------------------------
Key: CORE-4875
URL: http://tracker.firebirdsql.org/browse/CORE-4875
Project: Firebird Core
Issue Type: Bug
Affects Versions: 2.5.4
Environment: windows server 2012 R2 x64
RAM : 64 BG
Space Available : 743 GB
Reporter: Sebaot Software
Hi , we are trying to update our version of Firebird from 2.5.2 to 2.53 / 2.5.4
. We cannot do it because it does have a drawback with the database engine
version Firebird 2.5.3 and 2.5.4 . Our facilities run under Windows Server 2012
64-bit with Firebird Super Classic.
We currently have 25 different installations and we are the same thing happens
at all. The problem is the following : We have a system made for win32 desktop
which is accessed concurrently to perform normal operations (select - insert -
update - delete), without notice of any type of error the access to the
database or execution of any query is not possible, the program "freezes", this
error does not have a specific time interval or specific period.
Example:
you cannot access the system and those who are running is "hung" in this
example from the 14:00 approximately. Happened this verified the Firebird.log
which is shown as follows :
***************************************************************************
SERVER2K12R2 Thu Jun 18 14:04:34 2015 --> INET/inet_error: read errno = 10054
SERVER2K12R2 Thu Jun 18 14:04:34 2015 --> INET/inet_error: read errno = 10054
SERVER2K12R2 Thu Jun 18 14:04:34 2015 --> INET/inet_error: read errno = 10054
SERVER2K12R2 Thu Jun 18 14:04:34 2015 --> INET/inet_error: read errno = 10054
SERVER2K12R2 Thu Jun 18 14:04:34 2015 --> INET/inet_error: read errno = 10054
SERVER2K12R2 Thu Jun 18 14:04:34 2015 --> INET/inet_error: read errno = 10054
SERVER2K12R2 Thu Jun 18 14:05:55 2015 --> INET/inet_error: read errno = 10054
SERVER2K12R2 Thu Jun 18 14:05:55 2015 --> INET/inet_error: read errno = 10054
***************************************************************************
As noted in the log of the Firebird consecutively error 10054 with short
periods of time between one and another, after much study, we have detected
that the memory tables are hanging down and that are not accessible.
Using IBexpert connected to the database of a lot of time before, we proceeded
to open the MON$ATTACHMENTS to verify users and this no longer responded and
froze freezes. the program.
We proceeded to close and reopen again the program of IBexpert and it no longer
responded, staying hung in the login without being able to enter. We also
checked in another program previously activated call "TRACE Firebird - similar
to (Firebird TRACE" to display the behavior and shows us the following:
Normally displays the SQL statements in blue color (resume) (resumido)
[jue 18 jun, 14:00]
-------------------------------------------------------------------------------
[jue 18 jun, 14:00] select A.*
[jue 18 jun, 14:00] from FDENUN A
[jue 18 jun, 14:00] WHERE 0=1
[jue 18 jun, 14:00] 2015-06-18T14:00:23.6300 (2764:00000000CD73F0F8)
EXECUTE_STATEMENT_START
[jue 18 jun, 14:00] Intersebaot (ATT_13598, CONSUWEB:OPERADORES, ISO88591,
TCPv4:192.100.100.198)
[jue 18 jun, 14:00] F:\SEBAOT\INTERSEBAOT\SebaotWeb\SebaotWeb.exe:2504
[jue 18 jun, 14:00] (TRA_6965313, READ_COMMITTED | REC_VERSION |
NOWAIT | READ_WRITE)
[jue 18 jun, 14:00]
-------------------------------------------------------------------------------
[jue 18 jun, 14:00] select A.*
[jue 18 jun, 14:00] from FDENUN A
[jue 18 jun, 14:00] WHERE 0=1
[jue 18 jun, 14:00] Intersebaot (ATT_13598, CONSUWEB:OPERADORES, ISO88591,
TCPv4:192.100.100.198)
[jue 18 jun, 14:00] F:\SEBAOT\INTERSEBAOT\SebaotWeb\SebaotWeb.exe:2504
[jue 18 jun, 14:00] (TRA_6965313, READ_COMMITTED | REC_VERSION |
NOWAIT | READ_WRITE)
*****************************************************************************
AT THIS POINT NO LONGER DISPLAYS THE SQL Statements
[jue 18 jun, 14:00]
-------------------------------------------------------------------------------
[jue 18 jun, 14:00] Intersebaot (ATT_13598, CONSUWEB:OPERADORES, ISO88591,
TCPv4:192.100.100.198)
[jue 18 jun, 14:00] F:\SEBAOT\INTERSEBAOT\SebaotWeb\SebaotWeb.exe:2504
[jue 18 jun, 14:00] (TRA_6965314, READ_COMMITTED | REC_VERSION |
NOWAIT | READ_WRITE)
[jue 18 jun, 14:00] 2015-06-18T14:00:23.9430 (2764:00000000CD73F0F8)
START_TRANSACTION
[jue 18 jun, 14:00] Intersebaot (ATT_13598, CONSUWEB:OPERADORES, ISO88591,
TCPv4:192.100.100.198)
[jue 18 jun, 14:00] F:\SEBAOT\INTERSEBAOT\SebaotWeb\SebaotWeb.exe:2504
[jue 18 jun, 14:00] (TRA_6965315, READ_COMMITTED | REC_VERSION |
NOWAIT | READ_WRITE)
[jue 18 jun, 14:00] 2015-06-18T14:00:23.9580 (2764:00000000CD73F0F8)
COMMIT_TRANSACTION
[jue 18 jun, 14:00] Intersebaot (ATT_13598, CONSUWEB:OPERADORES, ISO88591,
TCPv4:192.100.100.198)
[jue 18 jun, 14:00] F:\SEBAOT\INTERSEBAOT\SebaotWeb\SebaotWeb.exe:2504
[jue 18 jun, 14:00] (TRA_6965315, READ_COMMITTED | REC_VERSION |
NOWAIT | READ_WRITE)
[jue 18 jun, 14:00] 0 ms, 1 read(s), 1 write(s), 1 fetch(es), 1 mark(s)
[jue 18 jun, 14:00] Intersebaot (ATT_13598, CONSUWEB:OPERADORES, ISO88591,
TCPv4:192.100.100.198)
[jue 18 jun, 14:00] F:\SEBAOT\INTERSEBAOT\SebaotWeb\SebaotWeb.exe:2504
[jue 18 jun, 14:00] Intersebaot (ATT_13598, CONSUWEB:OPERADORES, ISO88591,
TCPv4:192.100.100.198)
[jue 18 jun, 14:00] F:\SEBAOT\INTERSEBAOT\SebaotWeb\SebaotWeb.exe:2504
[jue 18 jun, 14:00] 2015-06-18T14:00:23.9580 (2764:00000000CD73F0F8)
START_TRANSACTION
[jue 18 jun, 14:00] Intersebaot (ATT_13598, CONSUWEB:OPERADORES, ISO88591,
TCPv4:192.100.100.198)
[jue 18 jun, 14:00] F:\SEBAOT\INTERSEBAOT\SebaotWeb\SebaotWeb.exe:2504
[jue 18 jun, 14:00] (TRA_6965316, READ_COMMITTED | REC_VERSION |
NOWAIT | READ_WRITE)
[jue 18 jun, 14:00] 2015-06-18T14:00:23.9740 (2764:00000000CD73F0F8)
COMMIT_TRANSACTION
[jue 18 jun, 14:00] Intersebaot (ATT_13598, CONSUWEB:OPERADORES, ISO88591,
TCPv4:192.100.100.198)
[jue 18 jun, 14:00] F:\SEBAOT\INTERSEBAOT\SebaotWeb\SebaotWeb.exe:2504
[jue 18 jun, 14:00] (TRA_6965316, READ_COMMITTED | REC_VERSION |
NOWAIT | READ_WRITE)
[jue 18 jun, 14:00] 0 ms, 1 read(s), 1 write(s), 1 fetch(es), 1 mark(s)
*****************************************************************************
Then we proceeded to restart the service for the Firebird to 2:08:27 PM with 87
active connections but the service did not respond in the lowering normally and
in the log shows:
14:08:37 --> "Firebird shutdown is still in progress after the specified
timeout"
Comment : The version of Firebird 2.5.3 presents the same drawback to the
current version 2.5.4 (current) , these were installed in the Super Classic
mode reported the same problem ,however with the Firebird 2.5.2 does not have
this drawback.
Unfortunately the hanging the Firebird does not display any type of error in
the Firebird.log or in the trace with which we can provide more information.
What is curious, we reiterate, is that with Firebird 2.5.2 do not have this
drawback.
**
windows server 2012 R2 x64
RAM : 64 BG
Space Available : 743 GB
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://tracker.firebirdsql.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
