Subject Re: [firebird-support] Firebird - explanation of errors
Author Mark Rotteveel
On 19-7-2016 06:25, 'maciejlik@...' maciejlik@...
[firebird-support] wrote:
> I have a question about the information in the log Firebird (version
> Firebird: The server was installed as SuperServer. The
> problem occurs in Windows XP SP3.

2.1.5 is not the latest 2.1; that is 2.1.7; several critical bugs were
fixed since 2.1.5.

However 2.1.x is no longer supported, and you should serioulsy consider
upgrading 2.5 or 3.0.

> A customer who uses the software that runs on the database engine
> firebird I reported a problem with the operation of the application.
> Please explain in detail the following errors. What could be the cause
> of their occurrence? and *which ones are* *disturbing*? What should I
> do, that these errors do not appear in the future ?

Not all of these messages are errors.

> /1. //POS003 (Server) Fri Jul 15 11:56:32 2016/
> / Database: C:\GASTRO.FDB/
> / Index 6 is corrupt (missing entries) in table POZRACH
> (259)/

Potentially disturbing. A backup and (if successful) a restore might be
in order. If the backup fails, you may first need to repair the database

> /2. //POS003 (Server) //Fri Jul 15 12:17:29 2016/
> / INET/inet_error: read errno = 10053/

Error 10053 is winsock error WSAECONNABORTED:

"Software caused connection abort.

An established connection was aborted by the software in your host
computer, possibly due to a data transmission time-out or protocol error."

Not really important, but it might point to network problems or the
application ending without properly closing the connection. This may
indicate data loss of active (uncommitted) transaction of that process.

> /3. //POS00//3 (Server) Fri Jul 15 12:17:32 2016/
> / INET/inet_error: read errno = 10054/

Error 10054 is winsock error WSAECONNRESET:

"Connection reset by peer.

An existing connection was forcibly closed by the remote host. This
normally results if the peer application on the remote host is suddenly
stopped, the host is rebooted, the host or remote network interface is
disabled, or the remote host uses a hard close. This error may also
result if a connection was broken due to keep-alive activity detecting a
failure while one or more operations are in progress. Operations that
were in progress fail with WSAENETRESET. Subsequent operations fail with

Not important. May point to an application terminating abruptly, or to
an application not properly closing a connection.

> /4. //POS003 (Client) Fri Jul 15 12:47:58 2016/
> / INET/inet_error: connect errno = 10061/

Error 10061 is winsock error WSAECONNREFUSED:

"Connection refused.

No connection could be made because the target computer actively refused
it. This usually results from trying to connect to a service that is
inactive on the foreign host—that is, one with no server application

Harmless. This means that a client attempted to connect to a port that
wasn't open (eg no Firebird server running, wrong port number).

> /5. //POS003 (Client) Fri Jul 15 12:43:27 2016/
> / Guardian starting: "C:\Program
> Files\Firebird\Firebird_2_1\bin\fbserver.exe"/

Informational message. Note that you shouldn't be using Guardian, it is
an ancient way of keeping Firebird running (eg on process crash) that is
no longer necessary when running as a service.

> /6. //POS003 (Server) Mon Jul 18 12:51:48 2016/
> / Shutting down the Firebird service with 1 active
> connection(s) to 1 database(s)/

Informational message. Something or someone stopped the Firebird service
while there were still connections. This may indicate potentially cause
data loss if that connection had active transactions.

Mark Rotteveel