Re: Pgsql crashes frequently

From: "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com>
To: Ganesan Kanavathy <ganesh(at)magnusquest(dot)com>
Cc: <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Pgsql crashes frequently
Date: 2003-10-08 15:31:43
Message-ID: Pine.LNX.4.33.0310080931150.13727-100000@css120.ihs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

this page should have the information you need to fix that problem:

http://www.postgresql.org/docs/7.3/static/kernel-resources.html

Let me know if that doesn't take care of the issue.

On Wed, 8 Oct 2003, Ganesan Kanavathy wrote:

> When I check the logfile it is stated there:
>
> "pcMemoryCreate: shmget(key=5432001, size=1466368, 03600) failed:
> Invalid argument
>
> This error usually means that PostgreSQL's request for a shared memory
> segment exceeded your kernel's SHMMAX parameter. You can either reduce
> the request size or reconfigure the kernel with larger SHMMAX.
>
> To reduce the request size (currently 1466368 bytes), reduce
> PostgreSQL's shared_buffers parameter (currently 64) and/or its
> max_connections parameter (currently 32).
>
> If the request size is already small, it's possible that it is less than
> your kernel's SHMMIN parameter, in which case raising the request size
> or reconfiguring SHMMIN is called for.
>
> The PostgreSQL Administrator's Guide contains more information about
> shared memory configuration."
>
> I really got no idea what this means. How do I solve this?
>
> What SHMMAX and SHMMIN and how I calculate this value? I have a 1GB of
> memory.
>
> Regards,
> ganesh
>
>
>
>
>
> -----Original Message-----
> From: pgsql-admin-owner(at)postgresql(dot)org
> [mailto:pgsql-admin-owner(at)postgresql(dot)org] On Behalf Of scott.marlowe
> Sent: Tuesday, October 07, 2003 10:36 PM
> To: Ganesan Kanavathy
> Cc: pgsql-admin(at)postgresql(dot)org
> Subject: Re: [ADMIN] Pgsql crashes frequently
>
>
> On Tue, 7 Oct 2003, Ganesan Kanavathy wrote:
>
> > We are running Postgresql db and it crashes almost every hour Unable
> > to load up pgsql after a crash.
> >
> > We need to restart the server to start back pg.
> >
> > What would be the cause of this problem. Please help.
>
> Bad hardware. Check for bad memory, CPU, or hard drive.
>
> Or, your machine is running low on memory and the kernel is killing
> processes randomly to free up memory. That's not as likely, but it does
> happen in some setups.
>
> www.memtest86.com for a decent free memory tester for X86 architecture.
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faqs/FAQ.html
>
>
>

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Oliver Elphick 2003-10-08 15:55:03 Re: Upgrade questions - backup OIDs? Upgrade pg_dumpall
Previous Message Jeff Harr 2003-10-08 15:25:51 Upgrade questions - backup OIDs? Upgrade pg_dumpall first? Tips?