Subject Re: Firebird 2.1 on OSX Lion
Author guilherme.bradasch
Of course, clientes connect to the server. My mistake on the wording, sorry.

The firewall isn't enabled: it's a development machine, and SuperServer worked flawlessly in Snow Leopard, with Firebird 2.1.4.

I'm using flamerobin to connect to the database. AFAIK, it always uses the full connection string. Also, I'm using aliases (and have used before). Using it in a java application I'm working on (with Jaybird), where I know the full "servername:dbname" is being used also gives me the same error.

If I try to run "/Library/StartupItems/Firebird/Firebird start", as suggested in another thread, it also posts the same error on the log.

The message error is "INET/inet_error: connect errno = 61" (copied from firebird.log).

With the ClassicServer I am able to work without problems, now that I learned to set the file and directory permissions correctly.

Thanks a lot,


--- In, Helen Borrie <helebor@...> wrote:
> At 01:54 PM 11/08/2011, you wrote:
> >Thanks for the answer, putting it in a new folder under $HOME works, as long as I set the permissions correctly (as I have done before, but in my "Documents" folder under $HOME).
> >
> >Now to add to the plot, I tried the SuperServer version, and under Snow Leopard everything runs fine (including fdbs under the "Documents" folder), but in Lion I get "INET connect error: errorno = 61" (something near that).
> >
> >Trying to start the server manually doesn't work. It always gives me this error, and then I did not manage to connect to the server.
> >
> >Now, is that something that was included in Lion? Seems the server is not initializing, or is not able to make connections to the client.
> Server doesn't connect to clients: clients connect to server.
> Superserver on POSIX platforms does not have a "serverless" connection option. You need the full network path of hostname:/path/to/database_file or, better, hostname:alias. (Put /path/to/database_file in aliases.conf.)
> Also make sure that your firewall is allowing traffic through port 3050 and that your database is on a partition that is physically attached to the host machine.
> ./hb