Issue Details (XML | Word | Printable)

Key: CORE-3328
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Minor Minor
Assignee: Vlad Khorsun
Reporter: Vlad Khorsun
Votes: 0
Watchers: 1

If you were logged in you would be able to see more operations.
Firebird Core

Client writes error messages into firebird.log when database is shutted down

Created: 02/Feb/11 09:12 AM   Updated: 03/Feb/16 08:53 AM
Component/s: Engine
Affects Version/s: 2.5.0
Fix Version/s: 2.5.1, 3.0 Alpha 1

QA Status: 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 =" in 3.0.

 Description  « Hide
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

 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Pierre Yager added a comment - 02/Feb/11 10:24 AM
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 (

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.