Detailed information in firebird.log when a connection is lost [CORE4129] #4456
Comments
Modified by: Jesus Angel Garcia Zarco (cointec)description: In current version, when a client disconnect abnormally from server, an entry is logged in Firebird.log. This entry is different from Superserver and classic server. While in Superserver the log records "INET/inet_error: read errno = 10054", in classic records "Unable to complete network request to....". The information that is logged is not sufficient, and does not analyze where is the source of the issue. To detect problems with application or machines, it would be interesting record also information related to the connection from mon$attachments, like MON$USER, MON$ATTACHMENT_NAME, MON$REMOTE_ADDRESS, MON$REMOTE_PROCESS. => In current version, when a client disconnect abnormally from server, an entry is logged in Firebird.log. This entry is different from Superserver and classic server. While in Superserver the log records "INET/inet_error: read errno = 10054", in classic records "Unable to complete network request to....". The information that is logged is not sufficient, and does not gives information about where is the source of the issue. To detect problems with application or machines, it would be interesting record also information related to the connection from mon$attachments, like MON$USER, MON$ATTACHMENT_NAME, MON$REMOTE_ADDRESS, MON$REMOTE_PROCESS. |
|
Commented by: Jesus Angel Garcia Zarco (cointec) Yes it is duplicate, but CORE2493 is for 3.0. Is posible in 2.5.X add at least the source IP address? |
|
Commented by: @dyemanov Some parts of the solution could be backported into v2.5, if it gonna be feasible. |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Submitted by: Jesus Angel Garcia Zarco (cointec)
In current version, when a client disconnect abnormally from server, an entry is logged in Firebird.log. This entry is different from Superserver and classic server.
While in Superserver the log records "INET/inet_error: read errno = 10054", in classic records "Unable to complete network request to....". The information that is logged is not sufficient, and does not gives information about where is the source of the issue.
To detect problems with application or machines, it would be interesting record also information related to the connection from mon$attachments, like MON$USER, MON$ATTACHMENT_NAME, MON$REMOTE_ADDRESS, MON$REMOTE_PROCESS.
The text was updated successfully, but these errors were encountered: