Re: Total crash of my db-server

From: "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com>
To: Henrik Steffen <steffen(at)city-map(dot)de>
Cc: <pgsql-general(at)postgresql(dot)org>
Subject: Re: Total crash of my db-server
Date: 2002-12-16 16:23:29
Message-ID: Pine.LNX.4.33.0212160920590.22946-100000@css120.ihs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Henrik, have you tested the memory and drive subsystems on this machine?

All this sounds very much like how an old server of mine was behaving when
I had bad memory. No database can be expected to perform reliably on
unreliable hardware.

Look for memtest86 if you're on intel hardware. Look at badblocks on
linux, or whatever OS you're on, for mapping out bad drive blocks.

If your machine is dying with NO ping response, it has serious problems,
and postgresql is just revealing them.

Good luck on troubleshooting this problem.

On Sun, 15 Dec 2002, Henrik Steffen wrote:

>
> Hello all,
>
> sometimes I experience a total crash of my
> db-server while e.g. doing automated maintainance tasks:
>
> At 2:30 am every night the webserver is shut
> down, so there won't be any concurrent accesses to the
> db-server. then there will be done a
> VACUUM FULL
>
> This is what happened tonight while fully vacuuming:
>
> server closed the connection unexpectedly
> This probably means the server terminated abnormally
> before or while processing the request.
>
> Then, the script selects all user tables and starts
> reindexing them. Tonight, reindexeing the first table
> started and seconds later the whole server crashed.
>
> No ping, nothing else possible....
>
> This is the list of recent crashes:
> Tonight 02:42 am
> Yesterday night 02:39 am
> Tuesday at 10:34 am
> Last saturday at 10:44 am
> Last Tuesday at 02:19 am
> The saturday before at 04:01 am
> The thursday before at 04:02 am
> the tuesday before at 02:25 am
>
> Always complete crashes... only reset helped.
>
> Most crashes occur while maintainance tasks.
> However, there are some other crashes, too.
>
> There are never any hints in /var/log/messages
>
> I upgraded to postgresql 7.3 recently, but it doesn't
> seem to help either.
>
> I am almost desperate.
>
> We are running some mysql-servers here, too, and I
> more and more often try to imagine to move my whole
> system to a mysql-server... my collegues NEVER have
> had such trouble with their mysql-servers yet....
>
> Do you have any hints for me? What can I do? My last
> choice would be to move to mysql, but I am almost
> desperate....
>
> thanks for your help
>
> --
>
> Mit freundlichem Gruß
>
> Henrik Steffen
> Geschäftsführer
>
> top concepts Internetmarketing GmbH
> Am Steinkamp 7 - D-21684 Stade - Germany
> --------------------------------------------------------
> http://www.topconcepts.com Tel. +49 4141 991230
> mail: steffen(at)topconcepts(dot)com Fax. +49 4141 991233
> --------------------------------------------------------
> 24h-Support Hotline: +49 1908 34697 (EUR 1.86/Min,topc)
> --------------------------------------------------------
> Ihr SMS-Gateway: JETZT NEU unter: http://sms.city-map.de
> System-Partner gesucht: http://www.franchise.city-map.de
> --------------------------------------------------------
> Handelsregister: AG Stade HRB 5811 - UstId: DE 213645563
> --------------------------------------------------------
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Robert Treat 2002-12-16 16:23:33 working around setQuerySnapshot limitations in functions
Previous Message Tom Lane 2002-12-16 15:23:09 Re: Login Failures After Upgrade