Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Client writes error messages into firebird.log when database is shutted down [CORE3328] #3694

Closed
firebird-automations opened this issue Feb 2, 2011 · 6 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @hvlad

If database was shut down by the DBA, existing client connections are received appropriate error and should close its connection. Since v2.5 network server don't wait for client to close connection, instead server waits for any packet from client, responded with shutdown error and closed connection immediately. In some cases client could wrongly detect it as error and put following messages into firebird.log :

INET/inet\_error: read errno = 10054

REMOTE INTERFACE/gds\_\_detach: Unsuccesful detach from database\. 
Uncommitted work may have been lost

Commits: d1f9eb9 aaf8f90

====== Test Details ======

Delta in firebird.log is checked on presence of either "gds__detach" or "lost" words.
If one of them will be found after shutdown then it will be considered as regression.
NB: delta will be empty for 2.5 and contain somewhat like "INET/inet_error: read errno = 10054, server host = localhost, address = 127.0.0.1/3333" in 3.0.

@firebird-automations
Copy link
Collaborator Author

Modified by: @hvlad

assignee: Vlad Khorsun [ hvlad ]

@firebird-automations
Copy link
Collaborator Author

Commented by: Pierre Yager (pierrey)

I just encountered a similar situation on a Ubuntu Server 10.10/AMD64 distribution using the Firebird 2.5 packages for Ubuntu compiled by Mariuz (https://launchpad.net/~mapopa/+archive/ppa)

I tried to restore a Firebird 2.1 transportable backup made with a Windows Machine using Firebird 2.1 superserver.

I tried many ways to restore it on the Ubuntu Server : remote restore using Firebird 2.1 gbak, local restore using direct connection, local restore with tcp/ip connection and local restore using services manager. Each of these tries failed :
* The Firebird server has been killed (WITH the guardian if the server is Superserver)
* After restarting the server the database is shut down (gstat -h) !
* I cannot tell exactly but at the end of the restore, right after the last restore message, there is an error message about the remote connection
* When put online, the database seems to be valid and accessible
* And the message in the firebird.log file is the same as your's

I had to ask the customer to send me the server back. I will be able to double check on Friday or soon next week.

@firebird-automations
Copy link
Collaborator Author

Modified by: @hvlad

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 2.5.1 [ 10333 ]

Fix Version: 3.0 Alpha 1 [ 10331 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

status: Resolved [ 5 ] => Closed [ 6 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

QA Status: No test

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

status: Closed [ 6 ] => Closed [ 6 ]

QA Status: No test => Done successfully

Test Details: Delta in firebird.log is checked on presence of either "gds__detach" or "lost" words.
If one of them will be found after shutdown then it will be considered as regression.
NB: delta will be empty for 2.5 and contain somewhat like "INET/inet_error: read errno = 10054, server host = localhost, address = 127.0.0.1/3333" in 3.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants