I hope this help!
(From http://community.borland.com/article/0,1410,27663,00.html)


INET/inet_error: connect errno = 111 - by Borland Developer Support Staff


Abstract: Why the error "INET/inet_error: connect errno = 111" is
entered in the interbase.log file.

Question: When I execute -start command with IBMGR the
server(SuperServer) successfully starts but in the interbase.log file
this message appears: INET/inet_error: connect errno = 111

Answer: After you execute the start command IBMGR immediately tries to
connect to isc4.gdb. This happens before the server is ready to accept
connections so it generates the error, "INET/inet_error: connect errno =
111". IBMGR will try again to connect to isc4.gdb and the usually the
server is ready to accept connections so the next entry in the log will
probably be, "/opt/interbase/bin/ibguard: guardian starting
bin/ibserver" indicating that the server has been successfully started.


Gentoolah Linuxlah wrote:

>
> When ever I start my super server firebird 1.5 at my gentoo I got this
> error in my firebird.log.
>
> INET/inet_error: connect errno = 111
>
> What does this tell me? What can I do to fix this?
>
> After knowing these error at my testing cum staging server, I then
> checked my 2 production servers which are running a classic server
> firebird 1.5 at RHEL.
>
> [root@db1 root]# tail -f /opt/firebird/firebird.log
>
> db1 Tue Jan 18 02:18:05 2005
> INET/inet_error: connect errno = 111
>
> db1 Tue Jan 18 02:18:07 2005
> INET/inet_error: connect errno = 111
>
> db1 Tue Jan 18 02:18:17 2005
> INET/inet_error: connect errno = 111
>
>
> [root@db3 root]# tail -f /opt/firebird/firebird.log
>
> db3 Mon Jan 17 16:32:01 2005
> INET/inet_error: read errno = 104
>
> db3 Mon Jan 17 16:32:01 2005
> INET/inet_error: read errno = 104
>
> db3 Mon Jan 17 16:49:26 2005
> INET/inet_error: read errno = 104
>
>
>
>
> p/s: Is there any reference about these errors?
>
>
>
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>
>