Subject Re: [firebird-support] Fb won't start if laptop not connected to network (and getting worse)!
Author John vd Waeter
Didier Gasser-Morlay wrote:
> Hello!
>
> 1- my configuration
> OS Linux 2.6
> FB 1.5.2 SS
>
> 2- extract of Firebird.log
> Quaddra (Client) Sun Jan 15 11:07:02 2006
> INET/inet_error: connect errno = 111
>
> Quaddra (Client) Sun Jan 15 11:07:02 2006
> /opt/firebird/bin/fbguard: guardian starting bin/fbserver
>
>
> Quaddra (Server) Sun Jan 15 11:07:02 2006
> Database:
> operating system directive open failed
> Permission denied
>
> Quaddra (Client) Sun Jan 15 11:07:02 2006
> /opt/firebird/bin/fbguard: bin/fbserver terminated due to startup
> error (2)
>
>
> Quaddra (Client) Sun Jan 15 11:07:02 2006
> /opt/firebird/bin/fbguard: bin/fbserver terminated due to startup
> error (2)
>
> 3- when does this happens
>
> the above error (and it's symptom: FB won't start) happens when my
> laptop is not connected to a network, and firthermore when my laptop's
> IP address and gateway does not match the network the laptop is
> connected to.
>
> I have tried several combinations
> - laptop standalone (not connected to a network), with a fixed IP
> address result: FB does not start
> - laptop connected to a hub, hub not connected to a network, fixed IP
> address result: FB does not start
> - laptop connected to a hub, hub connected to a network, fixed IP
> address, but in a range outside the networks address range result: FB
> does not start
> - laptop connected to a hub, hub connected to a network, DHCP
> address, (so in the range of the network's address range result: FB DOES
> START AND WORKS HAPPILY)
>
> Since I started writing this email, I did some more experiment and I
> managed to stop FB from working completely in any configuration! :(((
> same permission denied.
>
>
> 4- help !
>
>

Looks like not a Firebird-issue. If You have ONE way of coonecting FB
via the network, then FB is ok. If other ways fail, it has nothing to do
with FB.

Try ping the FB-server first (assumed it replies to ping). If that
fails, don't look further: it's the network, its setup, its mask, its
routes or whatever. If ping works, the most parts of your nework is ok.
Then start looking further...

regards
John'