Thread: Re: [SQL] PostgreSQL server terminated by signal 11

Re: [SQL] PostgreSQL server terminated by signal 11

From
"Daniel Caune"
Date:
> -----Message d'origine-----
> De : jeff@glacier.frostconsultingllc.com
> [mailto:jeff@glacier.frostconsultingllc.com] De la part de Jeff Frost
> Envoyé : jeudi, juillet 27, 2006 15:36
> À : Daniel Caune
> Cc : pgsql-admin@postgresql.org
> Objet : Re: [ADMIN] [SQL] PostgreSQL server terminated by signal 11
>
> On Thu, 27 Jul 2006, Daniel Caune wrote:
>
> > Actually ulimit is unlimited for user postgres and when the server was
> terminated the memory used was not that much compared to the machine
> capacity:
> >
> > Mem:   2075860k total,  1663520k used,   412340k free,     5620k buffers
> > Swap:   369452k total,        0k used,   369452k free,  1626176k cached
> >
> > I feel a bit lost, because it was running pretty well for the last
> couple months.  This table is a data stage table where some data are
> imported in from OLTP databases, this every day.  Indexes are dropped
> before inserting data and created when insertion has finished.  The
> structure didn't change since a while.
>
> Daniel,
>
> Was this 'free' output before or after the crash?
>

Yes, it was before the crash.

> Also, have you combed through /var/log/messages for anything interesting
> that happened around the time of the crash?
>

Actually nothing from the last boot...

Jul 27 18:30:40 localhost kernel: FDC 0 is a post-1991 82077
Jul 27 18:30:40 localhost kernel: NET: Registered protocol family 10
Jul 27 18:30:40 localhost kernel: Disabled Privacy Extensions on device c031f0c0(lo)
Jul 27 18:30:40 localhost kernel: IPv6 over IPv4 tunneling driver
Jul 27 18:30:41 localhost lpd[2394]: restarted
Jul 27 18:50:40 localhost -- MARK --
Jul 27 19:10:41 localhost -- MARK --
Jul 27 19:30:41 localhost -- MARK --
Jul 27 19:50:41 localhost -- MARK --

It's easy for me to make the postgres server crashing and tailing the /var/log/messages.  Nothing is logged.

> Which postgresql version is this?
>

PostgreSQL 8.1.4

I suspect a database corruption or something like this, but I don't know how/what to check and how to fix it if any.

--
Daniel