Daniel Albuschat wrote:

> The server-load is zero and the fbserver-process takes up 0% cpu-time.

Is it a SMP machine perhaps?

The best way to detect these kind of problems is to install the debug
build. When it 'hangs' use gdb -p to attach to it and get the backtrace
(using 'bt' command) and then send that to FB-devel for analysis.

> 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?

Firebird client does not, but your connectivity library might.

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

Can you check the firewall settings at the client? IIRC, there are some
firewall software that cut the connection when there is no traffic for
some time. Try removing the existing and installing another FW software
(it helped me a few times).

HTH

--
Milan Babuskov
http://www.flamerobin.org