Subject Re: [firebird-support] INET/inet_error: read errno
Author Helen Borrie
At 05:47 PM 25/10/2005 +1000, you wrote:
>we are running Debian Sarge with firebird2-classic-server installed,
>actual version is ISQL Version: LI-V1.5.1.4500 Firebird 1.5

OK, the first thing I suggest you try to do is get in touch with the Debian
package maintainer for Firebird 1.5.x to find out whether you can get a
newer, more stable deb package for Firebird 1.5. Those original Debian
Sarge builds were not stable. Unfortunately, the Firebird project doesn't
have any control over what Debian distributes; but those old 1.5.1 builds
should be considered suspect.

Try this page:

There you can find links to the appropriate forum, list, etc. (alioth is
like a Sourceforge-for-Debian).

>having experienced crashes at least once a week with the super server I
>removed it and installed classic, it appeared to be working great but
>we're experiencing the same kind of errors we did under super server...
>that is to say I'm not sure if it's the same error but it's definitely
>having the same result and that is that no users are able to connect to
>the db. Error messages in the logs haven't been terribly helpful, and
>I've been searching for a while to try and find their meaning... if
>someone could give me a clue as to what they mean it would be great.

Well, they are network (socket) errors. The log info is faulty (unless you
replaced the real hostname of your server with the word "hostname"!) We
should see the network node name of the server in these messages.

>hostname Tue Oct 4 15:55:41 2005
> INET/inet_error: read errno = 104

The 104 error is "Connection reset by peer". It means the server lost the
connection to the client. Reasons for this? Many! Client terminated the
connection abnormally, somehow. Application crash? Server crash? (Using a
bad UDF?) Using a wireless network? Or are you trying to access a
database that is located on a network drive? (DBs must be on a local
drive), etc., etc.

>hostname Tue Oct 25 16:05:01 2005
> INET/inet_error: read errno = 88

"Socket operation on non-socket". Client or host is trying to access a
socket that's not there. It follows on from 104, probably. But it will
also show up if your server has been connected to a database on a network
drive and *that* socket has been lost...

So - no short answers. It's impossible to tell from this info whether this
is problems with your Debian package, network configuration or the physical
layout of the network.