Could be these errors be a reason to make a database file extremely slow?

The errors 10061 & 10054 appeared in the log file 10 times each one in one
month.

The 'extremely slow' database file is while you ask records from a table of
2000 records and makes 4 minutes to return the first 30 records (not fetch).



Best regards

Dennis



From: firebird-support@yahoogroups.com
[mailto:firebird-support@yahoogroups.com] On Behalf Of Helen Borrie
Sent: Sunday, January 06, 2008 8:25 AM
To: firebird-support@yahoogroups.com
Subject: Re: [firebird-support] hello, can someone translate the follow
error messages? ref/eDN8022297953



At 08:36 PM 4/01/2008, you wrote:

>Hello to all. Can somebody explain with other words the follow error
>messages?
>
> REMOTE INTERFACE/gds__detach: Unsuccesful detach from database.

"One or more clients are left connected to a server that is no longer
responding to network requests."

>Uncommitted work may have been lost

"Updates, inserts or deletes that were not committed before the server
crashed might have disappeared".

>INET/inet_error: connect errno = 10060

That's a network error "Connection timed out". It means the established
connection failed because the connected host has stopped responding, i.e.,
it is the error that prompted the one from the remote interface module.

>INET/inet_error: connect errno = 10061

Also a network error "Connection refused". Some attempts were made to
reconnect to the server computer but the server computer actively refused
them. It usually means that the Firebird server is not running.

>INET/inet_error: connect errno = 10065

Another network error "No route to host". A socket operation tried to find
the server at the address specified but with no luck.

>INET/inet_error: read errno = 10054

Yet another network error, the first in the bunch, "Connection reset by
peer". That only tells you that the network connection was broken in the
middle of a network operation.

So - about all we can tell from this is that client applications are losing
their connections with the server. The fault seems to be on the server side.
You said you have other sites that have never seen this problem. Find out
what's different at *this* one: someone is rebooting the machine, perhaps,
or there is a bad cable or network card; or some other application is
installed on the server that is aggressively stealing or blocking Firebird's
service port, or......

For your own peace of mind, you might like to do a gstat -h on their
database and look at their transaction stats and creation date. If you find
that it has been a long time since the database has been restored, do a safe
backup and restore and see whether the problem goes away when the database
is clean.

./heLen





[Non-text portions of this message have been removed]