--- On Wed, 5/18/11, Alex Peshkoff <peshk...@mail.ru> wrote:

> From: Alex Peshkoff <peshk...@mail.ru>
> Subject: Re: [Firebird-devel] Cannot connect (errors on firebird.log)
> To: firebird-devel@lists.sourceforge.net
> Date: Wednesday, May 18, 2011, 9:58 AM
>  On 05/18/11 16:50, Leonardo M. Ramé
> wrote:
> > --- On Wed, 5/18/11, Alex Peshkoff <peshk...@mail.ru>
> wrote:
> >
> >> From: Alex Peshkoff <peshk...@mail.ru>
> >> Subject: Re: [Firebird-devel] Cannot connect
> (errors on firebird.log)
> >> To: firebird-devel@lists.sourceforge.net
> >> Date: Wednesday, May 18, 2011, 9:34 AM
> >>  On 05/18/11 16:07, Leonardo M. Ramé
> >> wrote:
> >>> Sorry for cross posting, I asked this in
> >> firebird-support but I got no answer so far.
> >>> I recently installed Firebird 2.5 on a
> FreeBSD, it was
> >> running ok
> >>> until this moring when suddendly it stopped
> accepting
> >> connections.
> >>> The server runs via inetd.
> >>>
> >>> Here is a copy of the last lines of
> firebird.log:
> >>>
> >>>
> -----------------------------------------------
> >>> server.rame.local Tue May 17 16:15:33 2011
> >>>    ISC_event_wait: semop failed
> with
> >> errno =3D 22
> >>>
> >>> server.rame.local Tue May 17 16:15:33 2011
> >>>    create_semaphores failed:
> >>>    operating system directive
> semget
> >> failed
> >>>    No space left on device
> >>>
> >>>
> >>> server.rame.local Tue May 17 16:15:33 2011
> >>>    ISC_event_wait: semop failed
> with
> >> errno =3D 22
> >>>
> >>> server.rame.local Tue May 17 16:15:33 2011
> >>>    create_semaphores failed:
> >>>    operating system directive
> semget
> >> failed
> >>>    No space left on device
> >> Should rebuild kernel with more SysV semaphores.
> >>
> > Thanks, I have to add that I'm using inetd instead of
> running the process on boot. Do you think the situation will
> improve if I run the server as a service instead of inetd?
> 
> No.
> Situation will improve only if you rebuild kernel.
> 
> But if you write startup script for freebsd, please send it
> here - looks
> like this is the only thing port is missing to be able to
> run
> superclassic and superserver.
> 

Well, I just added firebird_enable="YES" to rc.conf and removed gds from 
inetd.conf. Restarted /usr/local/etc/rc.d/firebird and /etc/rc.d/inetd, now it 
seems to be working ok.

Leonardo.

------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its 
next-generation tools to help Windows* and Linux* C/C++ and Fortran 
developers boost performance applications - including clusters. 
http://p.sf.net/sfu/intel-dev2devmay
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

Reply via email to