Thread: start error - pgsql

On Thursday 06 Feb 2003 3:42 pm, you wrote:
> IpcSemaphoreCreate: semget(key=5432006, num=17, 03600) failed: No space
> left on device
>
> This error does *not* mean that you have run out of disk space.


Run SAM as root and tune the shared memory parameters. As you have read in the
error messages, the instructions are in Admin. guides.

 Shridhar

P.S. Did you read admin guide for tuning shared memory?

Hi,

On Thu, 2003-02-06 at 12:12, kanchana wrote:

> I treid to compile and install postgresql on PA-RISC.
> it is insatlled , but while trying to start as
> ./pg_ctl -D data -l logfile
> i got following messages in logfile.
>
> plz tell me how to overcome this.
>
>
> IpcSemaphoreCreate: semget(key=5432006, num=17, 03600) failed: No space left on
> device

Maybe you should read this:

http://www.ca.postgresql.org/docs/faq-english.html#3.4

It tells what you should do.

Best regards,
--
Devrim GUNDUZ
TR.NET System Support Specialist

Tel : (312) 295 93 18  Fax : (312) 295 94 94 Tel : (216) 542 90 00

Well what does:

    df -k

and

    df -i

tell you about disk usage, you're mostly interested in the partition the
postgres data directory is in, although whatever /tmp is on may be significant
as well.

Have you tried reducing the max_connections parameter in postgres.conf?

--
Nigel Andrews


On Thu, 6 Feb 2003, kanchana wrote:

> Hello all,
>
>
> I treid to compile and install postgresql on PA-RISC.
> it is insatlled , but while trying to start as
> ./pg_ctl -D data -l logfile
> i got following messages in logfile.
>
> plz tell me how to overcome this.
>
>
> IpcSemaphoreCreate: semget(key=5432006, num=17, 03600) failed: No space left on
> device
>
> This error does *not* mean that you have run out of disk space.
>
> It occurs when either the system limit for the maximum number of
> semaphore sets (SEMMNI), or the system wide maximum number of
> semaphores (SEMMNS), would be exceeded.  You need to raise the
> respective kernel parameter.  Alternatively, reduce PostgreSQL's
> consumption of semaphores by reducing its max_connections parameter
> (currently 32).
>
> The PostgreSQL Administrator's Guide contains more information about
> configuring your system for PostgreSQL.
>
> Thanks and Regards,
> -kanchana
>

On 6 Feb 2003, Devrim GUNDUZ wrote:

> Hi,
>
> On Thu, 2003-02-06 at 12:12, kanchana wrote:
>
> > I treid to compile and install postgresql on PA-RISC.
> > it is insatlled , but while trying to start as
> > ./pg_ctl -D data -l logfile
> > i got following messages in logfile.
> >
> > plz tell me how to overcome this.
> >
> >
> > IpcSemaphoreCreate: semget(key=5432006, num=17, 03600) failed: No space left on
> > device
>
> Maybe you should read this:
>
> http://www.ca.postgresql.org/docs/faq-english.html#3.4
>
> It tells what you should do.

And maybe I should _read_ the error message before posting a reply. D'oh.

--
Nigel J. Andrews

Hello Niqel,

I started postgresql by tried with "postmaster -D data -N 16", now it is ok.

but i want to avoid this without using -N switch. (i.e i want to start
without -N)
is it possible? if so how.

thanks a lot for your efforts.

Regards,
-Kanchana


>
>
> Well what does:
>
> df -k
>
> and
>
> df -i
>
> tell you about disk usage, you're mostly interested in the partition the
> postgres data directory is in, although whatever /tmp is on may be
significant
> as well.
>
> Have you tried reducing the max_connections parameter in postgres.conf?
>
> --
> Nigel Andrews
>
>
> On Thu, 6 Feb 2003, kanchana wrote:
>
> > Hello all,
> >
> >
> > I treid to compile and install postgresql on PA-RISC.
> > it is insatlled , but while trying to start as
> > ./pg_ctl -D data -l logfile
> > i got following messages in logfile.
> >
> > plz tell me how to overcome this.
> >
> >
> > IpcSemaphoreCreate: semget(key=5432006, num=17, 03600) failed: No space
left on
> > device
> >
> > This error does *not* mean that you have run out of disk space.
> >
> > It occurs when either the system limit for the maximum number of
> > semaphore sets (SEMMNI), or the system wide maximum number of
> > semaphores (SEMMNS), would be exceeded.  You need to raise the
> > respective kernel parameter.  Alternatively, reduce PostgreSQL's
> > consumption of semaphores by reducing its max_connections parameter
> > (currently 32).
> >
> > The PostgreSQL Administrator's Guide contains more information about
> > configuring your system for PostgreSQL.
> >
> > Thanks and Regards,
> > -kanchana
> >
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
>

The simple solution if 16 is enough for you is to edit the max_connections
parameter in $PGDATA/postgres.conf By default it is 32 so change it to 16.

However, your system could be low on resources and you may just be delaying
the problems. I don't know if HP-UX gives something like sysctl, if so try and
find out about what and how it let's you change in the kernel
configuration. Alternatively, someone else already mentioned using SAM. You
should be able to change kernel settings through that tool. You do need root
priviledges to change the kernel though.

Good luck,

Nigel Andrews


On Thu, 6 Feb 2003, kanchana wrote:

> Hello Niqel,
>
> I started postgresql by tried with "postmaster -D data -N 16", now it is ok.
>
> but i want to avoid this without using -N switch. (i.e i want to start
> without -N)
> is it possible? if so how.
>
> thanks a lot for your efforts.
>
> Regards,
> -Kanchana
>
>
> >
> >
> > Well what does:
> >
> > df -k
> >
> > and
> >
> > df -i
> >
> > tell you about disk usage, you're mostly interested in the partition the
> > postgres data directory is in, although whatever /tmp is on may be
> significant
> > as well.
> >
> > Have you tried reducing the max_connections parameter in postgres.conf?
> >
> > --
> > Nigel Andrews
> >
> >
> > On Thu, 6 Feb 2003, kanchana wrote:
> >
> > > Hello all,
> > >
> > >
> > > I treid to compile and install postgresql on PA-RISC.
> > > it is insatlled , but while trying to start as
> > > ./pg_ctl -D data -l logfile
> > > i got following messages in logfile.
> > >
> > > plz tell me how to overcome this.
> > >
> > >
> > > IpcSemaphoreCreate: semget(key=5432006, num=17, 03600) failed: No space
> left on
> > > device
> > >
> > > This error does *not* mean that you have run out of disk space.
> > >
> > > It occurs when either the system limit for the maximum number of
> > > semaphore sets (SEMMNI), or the system wide maximum number of
> > > semaphores (SEMMNS), would be exceeded.  You need to raise the
> > > respective kernel parameter.  Alternatively, reduce PostgreSQL's
> > > consumption of semaphores by reducing its max_connections parameter
> > > (currently 32).
> > >
> > > The PostgreSQL Administrator's Guide contains more information about
> > > configuring your system for PostgreSQL.
> > >
> > > Thanks and Regards,
> > > -kanchana
> > >
>

--
Nigel J. Andrews

"kanchana" <pkkanchana@gmx.net> writes:
> plz tell me how to overcome this.

Isn't the error message clear enough?

> This error does *not* mean that you have run out of disk space.
> It occurs when either the system limit for the maximum number of
> semaphore sets (SEMMNI), or the system wide maximum number of
> semaphores (SEMMNS), would be exceeded.  You need to raise the
> respective kernel parameter.

Run SAM, adjust those kernel parameters, make a new kernel, reboot.

            regards, tom lane

Hello Tom and all,

Thanks for reply. I'm able to understand, but previously(2 to 3 weeks back)
with same machine i can able to run withour any problem. But after
recompilation, this runtime pbl areises.

Just to clear myself i'm sending the mail.

If only way is to change the kernel parameters, then i'll try and let you
all lnow if any pbl arises.


Regards,
-Kanchana

> "kanchana" <pkkanchana@gmx.net> writes:
> > plz tell me how to overcome this.
>
> Isn't the error message clear enough?
>
> > This error does *not* mean that you have run out of disk space.
> > It occurs when either the system limit for the maximum number of
> > semaphore sets (SEMMNI), or the system wide maximum number of
> > semaphores (SEMMNS), would be exceeded.  You need to raise the
> > respective kernel parameter.
>
> Run SAM, adjust those kernel parameters, make a new kernel, reboot.
>
> regards, tom lane
>