Subject Re: Newbie Solaris Server Setup Problem.
Author inoffensive_2006
--- In, Helen Borrie <helebor@...> wrote:
> At 07:55 AM 28/05/2006, you wrote:
> >Hi Folks:
> >
> > Let me start by thanking all who have contributed to Firebird
> >and IBPP.
> >
> > I'm finishing up development on a Windows app that uses the
> >Firebird 1.5.3 embedded server. It's been working great.
> >
> > I want to give the user the option of running this in client
> >server mode, so they can share their data with others in their
> >organization. The OS I'd like to use for the server is Solaris
> >10 on for X86, and because this particular machine has a single
> >processor, I'm trying to get the Firebird Super Server running.

< Snip >

> > Anyway, it's obvious that I don't know what I'm doing.
> :-) Solaris isn't Windoze! It's a POSIX OS, with all the filesystem
> security that goes with it.
> The first problem wasn't much - you just couldn't start the server
> because it was already started. You can actually replace the
> parameter '-start' with '-restart', which will shutdown the server if
> it is running, and get it...
Thanks Helen:

It seems to be running, I can ISQL from the Solaris system
or from Win2K. I find some of the following curious.

The Quickstart guide says the server will be running after
it's installed, and when the computer is turned on.

I think the Solaris install is an exception to this rule.
In fact fbmgr.bin didn't like the "-restart" argument:

$ pwd
$ ./fbmgr.bin -restart -forever
invalid switch
syntax error in command line

I copied the "firebird.init.d.example" to init.d and
linked it into any /etc/rc*.d that had an apache S or K
entry, one number higher than the apache link.

Things are working now.

> If you understand the scripts at all you could look at the various
> installation scripts and see what the firebird user was trying to do
> that the OS wouldn't let it do. I suspect that it it was trying to
> lock or create a file somewhere it doesn't have the permissions for.
> (The firebird user is a unix user that is created by the startup
> script for the purpose of running the server. Not all installation
> scripts do the right thing and create a firebird group and put all
> the perms in place, esp. when the build of the kit is outside the
> control of the core group, as the Solaris ones are. The guy who does
> the Solaris builds is Konstantin Kuznetsov and he hangs out in

The Solaris install for Firebird leaves the creation of
the "firebird" user and group for the person doing the install.

> Your isql problem relates not just to permissions but also to the
> Superserver architecture. Superserver on unix can't accept a local
> connection, so you'll need to use localhost. You will also need
> 1) a proper path for your database file name, including a directory
> location that actually exists
> 2) for the system user 'firebird' to have rwx permissions in that
> 3) to provide a username and password (i.e. Firebird security, not
> filesystem users) in the connect or create string
> Decide where you want to store databases and create that
> directory. Then make the (system) firebird user the owner of that
> directory. The user firebird and any other system users that are
> going to do stuff at file level to your database files should all be
> in a group named firebird and the group should have rwx perms on the
> directory (or directories) where databases are going to live and also
> where backups are going to be stored.
> Is that enough to get you onto the track? Anything that's
> Solaris-specific, or peculiar to the Solaris builds of Firebird, is
> beyond my ken but I doubt that Konstantin would be unwilling to help
> you out. :-)

As stated, the server seems to respond to ISQL, local
or remote, just fine. But the startup log entry looks
like a train wreck:


slowpoke (Client) Sun May 28 19:26:58 2006
INET/inet_error: connect errno = 146

slowpoke (Client) Sun May 28 19:26:59 2006
/usr/local/firebird/bin/fbguard: guardian starting bin/fbserver

slowpoke (Server) Sun May 28 19:26:59 2006
64 bit i/o support is on.

slowpoke (Server) Sun May 28 19:27:00 2006
Open file limit increased from 256 to 65536

slowpoke (Server) Sun May 28 19:27:02 2006
SERVER/process_packet: connection rejected for firebird


That last line was repeated, for a total of 30 entries,
over the next 10 seconds.

Subsequent ISQL sessions work fine and generate no
log entries.

Is this any cause for concern?

I'm very grateful for the Firebird and IBPP team's
hard work, and once I get this project on the market
and make some money, and have some time, I'll volunteer
some time to the effort.

I appreciate your assistance.