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 3B845D1E0FD for ; Tue, 30 Mar 2004 16:00:45 +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 38182-10 for ; Tue, 30 Mar 2004 12:00:32 -0400 (AST) Received: from e-greek.net (dev.e-greek.net [66.92.67.95]) by svr1.postgresql.org (Postfix) with SMTP id 7D6F9D1E137 for ; Tue, 30 Mar 2004 12:00:16 -0400 (AST) Received: (qmail 9241 invoked from network); 30 Mar 2004 16:00:03 -0000 Received: from 192.168.1.111 (HELO e-greek.net) (192.168.1.111) by e-greek.net with SMTP; 30 Mar 2004 16:00:03 -0000 Message-ID: <40699984.6030706@e-greek.net> Date: Tue, 30 Mar 2004 11:00:04 -0500 From: Andrew Biagioni User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tom Lane Cc: pgsql-admin@postgresql.org Subject: Re: Spontaneous PostgreSQL Server Reboot? References: <4068F16C.6050800@e-greek.net> <26103.1080621215@sss.pgh.pa.us> In-Reply-To: <26103.1080621215@sss.pgh.pa.us> 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/385 X-Sequence-Number: 12954 Tom Lane wrote: > Andrew Biagioni writes: > >>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. > > > Postgres can *not* cause a system reboot; it's only an unprivileged user > process. (but see *) You are dealing with either kernel bugs, hardware > errors, or some other root-level process requesting a reboot. This is one thing I was hoping to hear; any hints on kernel bug issues (or logs of causes)? > Even though it being three different machines would seem to rule out > hardware issues, I'd not jump to that conclusion ... you might be having > some kind of common-mode hardware failure. Two questions to ask here: > * did you buy all the RAM from the same vendor? > * is the power utility flaky where you live? (If you say "but > I've got a UPS", how old are its batteries?) > > My money would be on a kernel bug though. Are you up2date on kernel > patches? kernel patches, yes; kernel versions, no... > regards, tom lane > > (*) ObFinePrint: at least, PG can't directly trigger a reboot. One > scenario to think about is flaky RAM in an address range that doesn't > get used until the machine is under significant load --- since you say > Postgres is the only significant load on the machine, it's entirely > possible that triggering of a hardware failure is closely correlated to > what Postgres is doing. Similar remarks apply to broken disk hardware. 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... Thanks, Andrew > ---------------------------(end of broadcast)--------------------------- > TIP 4: Don't 'kill -9' the postmaster