#1
  1. No Profile Picture
    Mentat of IX
    Devshed Newbie (0 - 499 posts)

    Join Date
    Mar 2003
    Location
    Bucuresti / Toronto
    Posts
    112
    Rep Power
    12

    problems creating a db in freeBSD


    Hey ppl ,
    So I have used FirebirdSQL with Windows XP and had no problems with it , however my platform of choice for such things is freeBSD therefore I am now trying to get it working in there .

    Unfortunately , I can't seem to be able to create a database in freeBSD here are some messages :

    Code:
    SQL> create database 'f.gdb';
    Statement failed, SQLCODE = -902
    
    operating system directive semget failed
    -No such file or directory
    SQL> create database 'localhost:/usr/proj/test.gdb';
    Statement failed, SQLCODE = -902
    
    Unable to complete network request to host "localhost".
    -Failed to establish a connection.
    -Connection refused
    SQL> create database '/usr/proj/test.fdb';
    Statement failed, SQLCODE = -902
    
    operating system directive semget failed
    -No such file or directory
    FreeBSD , dooing more with less since 10 years ago
  2. #2
  3. Bug Hunter
    Devshed Newbie (0 - 499 posts)

    Join Date
    May 2003
    Location
    Transylvania (Romania)
    Posts
    309
    Rep Power
    23
    firebird server is runing ?

    telnet localhost 3050
    and take a look in the logs ...
    any messages ?
  4. #3
  5. Bug Hunter
    Devshed Newbie (0 - 499 posts)

    Join Date
    May 2003
    Location
    Transylvania (Romania)
    Posts
    309
    Rep Power
    23
    from Firebird 1.0 FreeBSD Release Notes
    Firebird is installed SUID with owner and group `firebird'.
    This does affect where you can and cannot create databases when
    connecting remotely, as well as which existing databases you can
    access. If you want a database to be available remotely, be sure
    it's readable and writeable to group firebird.

    There may be times when you manage to get your system into a
    state where using any of the Firebird utilites (isql, gbak, gsec,
    etc.) gives you the message "semget failed". One surefire way to
    do this is to build and install the port. If this happens,
    make sure that the lock manager is not running and its semaphores
    have been removed. The former can be accomplished with 'ps ax
    |grep gds' and 'kill'; the latter with 'ipcs -s' and 'ipcrm -s'.

    For example, after building and installing the port, you will
    probably go through something like this:

    # isql /usr/interbase/isc4.gdb
    Statement failed, SQLCODE = -902

    operating system directive semget failed
    -No such file or directory

    # ipcs -s
    Semaphores:
    T ID KEY MODE OWNER GROUP
    s 1310720 252034728 --rw-rw-rw- root wheel

    # ipcrm -s 1310720

    and you should be in business.

    Once this is done, you should be able to connect normally to
    databases. Your first connection will restart the lock manager.

    There may be times, however, when you still get "semget failed"
    even though the lock manager is not running and the semaphores have
    been cleaned up. There seems to be a conflict with this release
    and the PostgreSQL 7 release as installed from the ports collection.
    If you're having trouble with Firebird and you're running PostgreSQL,
    try stopping PostgreSQL:

    /usr/local/etc/rc.d/pgsql.sh stop

    and see if that helps.

    Super Server support has recently been added. However, there is
    anecdotal evidence that it is not as reliable nor as scalable as the
    Classic Server version. For this reason, I have not included a
    start up method for Super Server. For those that are interested,
    traversing to /usr/interbase/misc will find the startup scripts for
    the various flavours of Linux.
  6. #4
  7. No Profile Picture
    Mentat of IX
    Devshed Newbie (0 - 499 posts)

    Join Date
    Mar 2003
    Location
    Bucuresti / Toronto
    Posts
    112
    Rep Power
    12
    ah thanx ...

    i'm curently running postgreSQL and there is a good chance that's what the problem is , i'll look into it right away

IMN logo majestic logo threadwatch logo seochat tools logo