Firebird 2.0.3.12981 had been running without incident for 3 weeks on
a Red Hat Linux server, with typically 25 connections. At 10:33 this
morning, one of the clients disconnected uncleanly (``Connection reset
by peer''). As a result, ``fbguard'' caught this and restarted the server:

XXX (Server) Thu Mar 27 10:33:45 2008
INET/inet_error: read errno = 104

XXX (Client) Thu Mar 27 10:33:46 2008
/opt/firebird/bin/fbguard: bin/fbserver terminated abnormally (-1)

XXX (Client) Thu Mar 27 10:33:46 2008
/opt/firebird/bin/fbguard: guardian starting bin/fbserver

When the guardian restarted the server, ``fbserver'' was no longer
listening on the canonical port of 3050. In this case, it was
listening on port 58798. A check of ``netstat'' showed that both the
standard port of 3050 was still listening as well as the ``new'' port
of 58798.

However, only connections made to port 58798 were possible. Any
attempt to connect to port 3050 just timed out.

We've made no configuration changes and have no idea of what egregious
action may have been taken by the client to cause the abnormal
termination of ``fbserver''.

So, what caused ``fbserver'' to start listening on a port other than
3050 after the guardian restarted it? And what can we do to prevent
this from recurring?