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 6B754D1DAB9 for ; Wed, 31 Mar 2004 06:30:58 +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 62670-10 for ; Wed, 31 Mar 2004 02:30:57 -0400 (AST) Received: from sycorax.affordablehost.com (sycorax.affordablehost.com [216.46.192.84]) by svr1.postgresql.org (Postfix) with ESMTP id 438A0D1C9ED for ; Wed, 31 Mar 2004 02:30:56 -0400 (AST) Received: from h0040054d8ee4.ne.client2.attbi.com ([66.31.57.228] helo=e-greek.net) by sycorax.affordablehost.com with esmtp (TLSv1:RC4-MD5:128) (Exim 4.24) id 1B8JaZ-00087i-5I; Tue, 30 Mar 2004 08:47:35 -0500 Message-ID: <40697A78.6070701@e-greek.net> Date: Tue, 30 Mar 2004 08:47:36 -0500 From: Andrew Biagioni User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en, it, it-ch, fr-fr, fr-ch, de-de, de-ch MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Re: Spontaneous PostgreSQL Server Reboot? References: <4068F16C.6050800@e-greek.net> <4068FB1B.30004@lintelsys.com.au> In-Reply-To: <4068FB1B.30004@lintelsys.com.au> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sycorax.affordablehost.com X-AntiAbuse: Original Domain - postgresql.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - e-greek.net X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/402 X-Sequence-Number: 12971 Alex, the answer is "no" to all of these. We are a tiny start-up (2 guys, and we do our own cleaning); ambient temperature varies significantly but is not related to the failure, and one machine starts beeping when it gets too hot (then we added an extra case fan); no fancy watchdogs (maybe someday... One can only dream :-> ); three different cases, power supplies, motherboards, etc., etc. (one power supply is extra-large, and that's the machine that started failing first!). We originally blamed the problem on hardware failure (first machine); then on OS version/configuration (second machine); now we're out of things to blame, except maybe unusually bad luck... Thanks, Andrew Alex Satrapa wrote: > Andrew Biagioni wrote: > >> On three different machines running the same PostgreSQL version >> (7.3.5) on Linux and almost identical databases, I have been plagued >> by occasional, unexplainable (to me) reboots of the computer. > > > 1) Do you have a software watchdog that is configured to reboot the > machine when it isn't tickled? The watchdog might possibly be rebooting > because the machine is under heavy load, or perhaps someone forgot to > enable the watchdog tickler. > > 2) Was there anyone in the machine room at the time? One office that I > worked in suffered random power outages to several machines for weeks on > end, until we figured out that the cleaner was unplugging the main > Ethernet switch to use the power point for their vacuum cleaner. > > 3) Are the power supplies up to scratch? some power supplies just can't > handle the load when you run disk and processor heavily for minutes on > end. The result is the same as a brown-out or black-out - power > disappears, machine reboots. > > Hope this helps prod someone's memory! > Alex > > ---------------------------(end of broadcast)--------------------------- > TIP 8: explain analyze is your friend > > > . >