Subject | INET/inet_error: connect errno = 111 - absolutely expected? |
---|---|
Author | Smarts Broadcast Systems |
Post date | 2008-01-09T00:49:50Z |
There are a number of messages in this group and other resources
concerning the ``INET/inet_error: connect errno = 111'' message in the
{interbase,firebird}.log. It's not covered, per se, in the
firebirdsql.org FAQ.
Since this is where the experts are found -- can we have an
authoritative statement that, at service startup with Firebird (or
Interbase) SS startup, precisely one such message is expected and
normal. I presume it's due to fbmgr (or ibmgr) attempting to connect
before the server has begun listening.
This issue is covered at http://dn.codegear.com/article/27663. But I
am unaware of the credentials of the author. Moreover, there are a
couple of unanswered followup queries asking if there were plans to
eliminate this error message (since it is normal).
...and while I'm on a roll, short of changing the source code, is
there a way to configure Firebird's logging so that each new client
connection and disconnect to the server is logged (a la PostgreSQL's
``log_connections'' parameter).
concerning the ``INET/inet_error: connect errno = 111'' message in the
{interbase,firebird}.log. It's not covered, per se, in the
firebirdsql.org FAQ.
Since this is where the experts are found -- can we have an
authoritative statement that, at service startup with Firebird (or
Interbase) SS startup, precisely one such message is expected and
normal. I presume it's due to fbmgr (or ibmgr) attempting to connect
before the server has begun listening.
This issue is covered at http://dn.codegear.com/article/27663. But I
am unaware of the credentials of the author. Moreover, there are a
couple of unanswered followup queries asking if there were plans to
eliminate this error message (since it is normal).
...and while I'm on a roll, short of changing the source code, is
there a way to configure Firebird's logging so that each new client
connection and disconnect to the server is logged (a la PostgreSQL's
``log_connections'' parameter).