X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id B1246D1D141 for ; Tue, 30 Mar 2004 18:22:05 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 06635-06 for ; Tue, 30 Mar 2004 14:22:00 -0400 (AST) Received: from 3times25.net (66-23-202-190.clients.speedfactory.net [66.23.202.190]) by svr1.postgresql.org (Postfix) with ESMTP id 10D78D1BAF7 for ; Tue, 30 Mar 2004 14:21:59 -0400 (AST) Received: from 3times25.net (localhost [127.0.0.1]) by 3times25.net (Postfix) with ESMTP id 04DCA4C167 for ; Tue, 30 Mar 2004 13:22:09 -0500 (EST) Message-ID: <4069BAD0.3050606@3times25.net> Date: Tue, 30 Mar 2004 13:22:08 -0500 From: Geoffrey User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Re: Spontaneous PostgreSQL Server Reboot? References: <4068F16C.6050800@e-greek.net> <26103.1080621215@sss.pgh.pa.us> <40699984.6030706@e-greek.net> In-Reply-To: <40699984.6030706@e-greek.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/389 X-Sequence-Number: 12958 Andrew Biagioni wrote: > I just got a suggestion to run badblocks and memtest86, to check the > hardware; that and an updated kernel should help me figure out what > is going on... It seems to me that since you reported the problem on three different machines, you should be looking for a common problem. Having bad ram in all three machines I would find unlikely, even if it is all the same batch. Same would seem to apply to hard drives. I'd be more suspect of power fluctuations, heat issues. Those things that can affect multiple machines the same way, that is, if they are in the same location, using the same power source. I wouldn't rule out memory or drives, but I'd likely look for something that affects all the machines. Common batches of ram, drives or identical motherboards could be a possibility, but I don't think as likely as power and/or heat issues. -- Until later, Geoffrey Registered Linux User #108567 Building secure systems in spite of Microsoft