At 06:29 PM 12/08/2004 +0000, you wrote:

>Hi
>
>could anybody help to decipher the mistakes below or to inform
>documentation to have the subject?

You are looking at network errors here, not database errors - the Firebird
log reports them but it doesn't have any way to know why they
occurred. For details of what the various error codes mean, consult some
documentation about TCP/IP.

If you take note of any exception messages that occurred around the time
the network problems happened, you can work out whether the network
messages can be ignored. If nobody is reporting any problems, then
recovery is happening OK, without intervention by humans.

Just looking through the timings of these, it's possible you have an
application that is crashing the server; and then the 104 ("connection
reset by peer") and 111 ("connection refused") network errors tell you
variously that the network can "hear" both the server and the problem
client some of the time, but the client and the server can't hear each
other at those points.

A bad client connection path (e.g. trying to local-connect without the
localhost server), using the wrong client, running a UDF that corrupts the
server's memory, faulty network hardware, a misconfigured network node, a
firewall on the server's service port, etc. etc., even sometimes just
crashing out of a client application; all are things that could cause these
errors to appear in the log.

If those batteries of 111 errors are associated with a client that is
experiencing slow connection time, it might indicate that something is a
bit wild in your network's DNS setup.

/heLen