Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 10A142E01ED for ; Wed, 13 Feb 2008 17:41:15 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 05513-02 for ; Wed, 13 Feb 2008 17:41:12 -0400 (AST) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.182]) by postgresql.org (Postfix) with ESMTP id DA5BF2E0139 for ; Wed, 13 Feb 2008 17:41:11 -0400 (AST) Received: by wa-out-1112.google.com with SMTP id m38so254389waf.5 for ; Wed, 13 Feb 2008 13:41:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=A4n6UwvJHWDZzt96tZjBI7k6hvZ/Y6ZN7jAZyEsHjOc=; b=AC8mQ8RozGMyd2aHartZhuHmPw62MMEfVxdagsR2fp59mtV3AEa8fmbp4T7Vh2oUhZGVuNtgBph/HDbruDWF7lkapchrnrnUdouQOcHoFaBR+scpoRLznKbMPr602x8+/p6CKkiOqQ5E0mSybs1W2FnNikeF0Z3bC5sFNcTRoaQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=VVdr0aD3ycxs5+nHIIPD4rSrE9ImTKyQWPws5Y1HYzSQZovOxnzirur6MhywKpoVujCT1ew1PGRrTMywrIJJA38KNwNI2jnMQ3qCW6m+Z7Yg2fWrRsWLomZVhQfe3qnx3CVhtICD/MZkiybe6KGsEflMEWllb3kKrHZ1ccSgsLQ= Received: by 10.114.79.1 with SMTP id c1mr484440wab.148.1202938870356; Wed, 13 Feb 2008 13:41:10 -0800 (PST) Received: by 10.114.131.4 with HTTP; Wed, 13 Feb 2008 13:41:10 -0800 (PST) Message-ID: Date: Wed, 13 Feb 2008 15:41:10 -0600 From: "Scott Marlowe" To: "Leticia Larrosa" Subject: Re: terminating connection because of crash of another server process Cc: pgsql-admin@postgresql.org In-Reply-To: <046e01c86e81$d9d79540$8d86bfc0$@cujae.edu.cu> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <046e01c86e81$d9d79540$8d86bfc0$@cujae.edu.cu> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200802/166 X-Sequence-Number: 28240 On Feb 13, 2008 2:48 PM, Leticia Larrosa wrote: > > Hello > > I have a postgres database version 8.1.11, in an Ubuntu Server 6.10. > > Some days before, I have a hardware failure in my server, and after recover > the database I get some problems with tables and I had to REINDEX some of > its. > But now, doing any actions in the database server (for example: SELECT * > from my_table), I continue getting the follow error: > > """ > WARNING: terminating connection because of crash of another server process > DETAIL: The postmaster has commanded this server process to roll back the > current transaction and exit, because another server process exited > abnormally and possibly corrupted shared memory. > HINT: In a moment you should be able to reconnect to the database and > repeat your command. > server closed the connection unexpectedly > This probably means the server terminated abnormally > before or while processing the request. > The connection to the server was lost. Attempting reset: Succeeded. > """ > > Any help, to solve this or an idea about anything I must check, will be > appreciated. > > The log of my server shows the follow messages over and over: > > LOG: database system was interrupted at 2008-02-13 15:37:00 EST > LOG: checkpoint record is at 1C/837496A0 > LOG: redo record is at 1C/837496A0; undo record is at 0/0; shutdown TRUE > LOG: next transaction ID: 1596704648; next OID: 2939703 > LOG: next MultiXactId: 1; next MultiXactOffset: 0 > LOG: database system was not properly shut down; automatic recovery in > progress > LOG: record with zero length at 1C/837496E4 > LOG: redo is not required > LOG: database system is ready > LOG: transaction ID wrap limit is 2147484146, limited by database > "postgres" > LOG: server process (PID 9747) was terminated by signal 11 > LOG: terminating any other active server processes Sig 11 is bad, mkay? basically it means the postgres process is crashing. It could be crashing because of a corrupted / buggy executable, or bad hardware. Do you have another machine you trust to move your pgsql database to? Because I wouldn't trust the one it's on right now until you can pull it from service, confirm the pg binaries aren't corrupted, and test your hardware.