Re: [HACKERS] backend crashing on NetBSD 1.3.2/i386 - Mailing list pgsql-hackers

From The Hermit Hacker
Subject Re: [HACKERS] backend crashing on NetBSD 1.3.2/i386
Date
Msg-id Pine.BSF.4.05.9811011858220.316-100000@thelab.hub.org
Whole thread Raw
In response to Re: [HACKERS] backend crashing on NetBSD 1.3.2/i386  (Brook Milligan <brook@trillium.NMSU.Edu>)
Responses Re: [HACKERS] backend crashing on NetBSD 1.3.2/i386
List pgsql-hackers
On Sun, 1 Nov 1998, Brook Milligan wrote:

>    You have to run the backend using gdb, and get a backtrace of the crash,
>    or check the postmaster logs for any information.
> 
> No core dump that I can find.  But, the logs are reporting errors from
> semget in ipc.c.  Specifically, it is complaining of not enough space,
> but I have no full filesystems.  This stuff is part of the locking
> code isn't it?  Did that get tweaked with the NetBSD/vax patches
> recently?
semget deals with shared memory, not file systems...under FreeBSD,
you do:

%ipcs
Message Queues:
T     ID     KEY        MODE       OWNER    GROUP

Shared Memory:
T     ID     KEY        MODE       OWNER    GROUP
m 131072 2063597841 --rw-rw-rw-  scrappy    staff

Semaphores:
T     ID     KEY        MODE       OWNER    GROUP

To see what is being used.  ipcrm to remove 'stale'
handles...sounds like your system isn't releasing when you kill of
postgres daemon...

Marc G. Fournier                                
Systems Administrator @ hub.org 
primary: scrappy@hub.org           secondary: scrappy@{freebsd|postgresql}.org 



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] A small problem with the new inet and cidr types
Next
From: Brook Milligan
Date:
Subject: Re: [HACKERS] backend crashing on NetBSD 1.3.2/i386