Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id B69D3475E30 for ; Fri, 24 Jan 2003 19:29:08 -0500 (EST) Received: from megazone.bigpanda.com (megazone.bigpanda.com [63.150.15.178]) by postgresql.org (Postfix) with ESMTP id 4EF4D4761A1 for ; Fri, 24 Jan 2003 19:27:48 -0500 (EST) Received: by megazone.bigpanda.com (Postfix, from userid 1001) id DC1E1D9A7; Fri, 24 Jan 2003 16:27:50 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by megazone.bigpanda.com (Postfix) with ESMTP id D13245C29; Fri, 24 Jan 2003 16:27:50 -0800 (PST) Date: Fri, 24 Jan 2003 16:27:50 -0800 (PST) From: Stephan Szabo To: Josh Berkus Cc: Noah Silverman , Subject: Re: WEIRD CRASH?!?! In-Reply-To: <200301241603.42263.josh@agliodbs.com> Message-ID: <20030124162229.K38264-100000@megazone23.bigpanda.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200301/303 X-Sequence-Number: 950 On Fri, 24 Jan 2003, Josh Berkus wrote: > Noah, > > > I think my server crashed and then restarted itself. Does anybody know > > what all this means: > > > > 2003-01-24 18:28:06 PANIC: link from > > /RAID/pgsql/pg_xlog/00000009000000BC to > > /RAID/pgsql/pg_xlog/00000009000000C4 (initialization of log file 9, > > segment 196) failed: File exists > > 2003-01-24 18:28:06 LOG: server process (pid 1574) was terminated by > > signal 6 > > 2003-01-24 18:28:06 LOG: terminating any other active server processes > > 2003-01-24 18:28:06 WARNING: Message from PostgreSQL backend: > > The Postmaster has informed me that some other backend > > died abnormally and possibly corrupted shared memory. > > I have rolled back the current transaction and am > > going to terminate your database system connection and exit. > > Please reconnect to the database system and repeat your query. > > This means that somebody KILL -9'd a postgres process or the postmaster, and > Postgres restarted in order to clear the shared buffers. If the database > started up again, you are fine. Actually, it looks like an abort() (signal 6) to me. Probably from the PANIC listed. The question is why did it get confused and end up linking to a filename that already existed?