Hi there, again

I got the same error message today and the firebird-server became
inaccessible. It seems that the error-message itself is meaningless
and that it's created by some Windows-component, not by the server.
The server-load is zero and the fbserver-process takes up 0% cpu-time.

I noticed that there are 50 to 80 entries per day (!!) like this in
firebird.log:

voyager (Server) Wed Jan 16 14:13:36 2008
INET/inet_error: read errno = 104

In linux/errno.h errno 104 is "connection reset by peer", 32, which
occurs about as much as 104, is "broken pipe".
I wonder how this can happen that often without any client-software
malfunctioning?
Does the client-lib try to reconnect automatically on such errors?

There's nothing in dmesg or /var/log/messages that might indicate
network problems and there's no problem in accessing large files on
the same server via SMB.

This is with Firebird LI-V1.5.3.4870 Firebird 1.5 on a Ubuntu Server
with a (ubuntu-patched) 2.6.15 kernel.

Perhaps someone can help me debugging and ultimately fixing this
problem, since I'm at a loss of ideas.

Regards,

Daniel Albuschat

--
eat(this); // delicious suicide