Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id AB02A9FB474 for ; Tue, 26 Sep 2006 19:33:11 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 68602-06 for ; Tue, 26 Sep 2006 22:33:07 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.225]) by postgresql.org (Postfix) with ESMTP id A7A909FA4C5 for ; Tue, 26 Sep 2006 19:33:07 -0300 (ADT) Received: by wx-out-0506.google.com with SMTP id t13so2448885wxc for ; Tue, 26 Sep 2006 15:33:06 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=I3ir45C5UCVZKAoTDczrTzLaewfIFJ5WnZCbJ4XRxWRTnq3f34cQFlYZK7qBTzHtlvdhvNISc3Z8ZBk4CDEzu1F/33x/RoWulKerjZjWDBntL/U0ImUaKme9i+seBOQ2vp3U1m+greRt+zI+7UHpzhIFkCB7orYZQyxgPr97lNU= Received: by 10.70.74.6 with SMTP id w6mr1637404wxa; Tue, 26 Sep 2006 15:33:06 -0700 (PDT) Received: by 10.70.71.18 with HTTP; Tue, 26 Sep 2006 15:33:06 -0700 (PDT) Message-ID: Date: Tue, 26 Sep 2006 15:33:06 -0700 From: "Talha Khan" To: "Gregory S. Williamson" Subject: Re: Runtime error: could not open segment 1 of relation ... Cc: pgsql-admin@postgresql.org In-Reply-To: <71E37EF6B7DCC1499CEA0316A256832802B3E60D@loki.wc.globexplorer.net> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_21132_4540826.1159309986049" References: <71E37EF6B7DCC1499CEA0316A256832802B3E60A@loki.wc.globexplorer.net> <71E37EF6B7DCC1499CEA0316A256832802B3E60D@loki.wc.globexplorer.net> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.574 tagged_above=0 required=5 tests=DNS_FROM_RFC_ABUSE, HTML_30_40, HTML_MESSAGE, SPF_PASS X-Spam-Level: X-Archive-Number: 200609/317 X-Sequence-Number: 23231 ------=_Part_21132_4540826.1159309986049 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Try reindexing your database and see if that solves your problem. Regards Talha Khan On 9/26/06, Gregory S. Williamson wrote: > > Thanks for the suggestion ...no evidence of such a shutdown. The first of > these errors (since 2005-10-28) was at 2006-09-26 05:37:19.157 PDT today; > machine was last shut serveral weeks ago. There's been several large updates > since then (sort of batch process for updates, then the server is read-only > for 99.999 of the time). > > Greg > > -----Original Message----- > From: Talha Khan [mailto:talha.amjad@gmail.com] > Sent: Tue 9/26/2006 3:21 PM > To: Gregory S. Williamson > Cc: pgsql-admin@postgresql.org > Subject: Re: [ADMIN] Runtime error: could not open segment 1 of > relation ... > > Hi Greg, > > Is it possible that the server was shutdown using -mi switch? > > cuz immediate shutdown ends causing these problems. > > Regards > Talha Khan > > > On 9/26/06, Gregory S. Williamson wrote: > > > > This morning one of our production servers (8.1.1, Linux) threw a number > > of errors like these (different final number; first two [1663/43801] > are > > all the same]: > > > > 2006-09-26 10:02:15.124 PDT 1387333718 ERROR: could not open segment 1 > of > > relation 1663/43801/7274801 (target block 478216192): No such file or > > directory > > 2006-09-26 10:02:52.991 PDT 1387340456 ERROR: could not open segment 1 > of > > relation 1663/43801/7274801 (target block 478216192): No such file or > > directory > > 2006-09-26 10:02:53.002 PDT 1387340458 ERROR: could not open segment 1 > of > > relation 1663/43801/7274801 (target block 478216192): No such file or > > directory > > > > The server never really recovered -- it kept running but was horribly > > slow. Rebooting seems to have cured the problem, but I am wondering what > I > > made look into, etc. > > > > The server in question is really a read-only beast with several hundred > > connections, typically, 4 gigs of RAM, and has not misbehaved before. > > > > Any suggestions would be welcome! (Although I fear I know the answer -- > > disk issues.) > > > > Thanks, > > > > Greg Williamson > > DBA > > GlobeXplorer LLC > > > > ---------------------------(end of broadcast)--------------------------- > > TIP 2: Don't 'kill -9' the postmaster > > > > > > ------------------------------------------------------- > Click link below if it is SPAM gsw@globexplorer.com > " > https://mailscanner.globexplorer.com/dspam/dspam.cgi?signatureID=4519a6f898846491211187&user=gsw@globexplorer.com&retrain=spam&template=history&history_page=1 > " > !DSPAM:4519a6f898846491211187! > ------------------------------------------------------- > > > > ------=_Part_21132_4540826.1159309986049 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline
Try reindexing your database and see if that solves your problem.
 
Regards
Talha Khan

 
On 9/26/06, Gregory S. Williamson <gsw@globexplorer.com> wrote:
Thanks for the suggestion ...no evidence of such a shutdown. The first of these errors (since 2005-10-28) was at 2006-09-26 05:37: 19.157 PDT today; machine was last shut serveral weeks ago. There's been several large updates since then (sort of batch process for updates, then the server is read-only for 99.999 of the time).

Greg

-----Original Message-----
From:   Talha Khan [mailto:talha.amjad@gmail.com]
Sent:   Tue 9/26/2006 3:21 PM
To:     Gregory S. Williamson
Cc:     pgsql-admin@postgresql.org
Subject:        Re: [ADMIN] Runtime error: could not open segment 1 of relation ...

Hi Greg,

Is it possible that the server was shutdown using -mi switch?

cuz immediate shutdown ends causing these problems.

Regards
Talha Khan


On 9/26/06, Gregory S. Williamson <gsw@globexplorer.com> wrote:
>
> This morning one of our production servers (8.1.1, Linux) threw a number
> of  errors like these (different final number; first two [1663/43801] are
> all the same]:
>
> 2006-09-26 10:02:15.124 PDT 1387333718 ERROR:  could not open segment 1 of
> relation 1663/43801/7274801 (target block 478216192): No such file or
> directory
> 2006-09-26 10:02:52.991 PDT 1387340456 ERROR:  could not open segment 1 of
> relation 1663/43801/7274801 (target block 478216192): No such file or
> directory
> 2006-09-26 10:02: 53.002 PDT 1387340458 ERROR:  could not open segment 1 of
> relation 1663/43801/7274801 (target block 478216192): No such file or
> directory
>
> The server never really recovered -- it kept running but was horribly
> slow. Rebooting seems to have cured the problem, but I am wondering what I
> made look into, etc.
>
> The server in question is really a read-only beast with several hundred
> connections, typically, 4 gigs of RAM, and has not misbehaved before.
>
> Any suggestions would be welcome! (Although I fear I know the answer --
> disk issues.)
>
> Thanks,
>
> Greg Williamson
> DBA
> GlobeXplorer LLC
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
>



-------------------------------------------------------
Click link below if it is SPAM gsw@globexplorer.com
"https://mailscanner.globexplorer.com/dspam/dspam.cgi?signatureID=4519a6f898846491211187&user=gsw@globexplorer.com&retrain=spam&template=history&history_page=1 "
!DSPAM:4519a6f898846491211187!
-------------------------------------------------------




------=_Part_21132_4540826.1159309986049--