From: Andrew Biagioni <andrew.biagioni@e-greek.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: Spontaneous PostgreSQL Server Reboot?
Date: Tue, 30 Mar 2004 11:00:04 -0500
Message-ID: <40699984.6030706@e-greek.net> (raw)
In-Reply-To: <26103.1080621215@sss.pgh.pa.us>
References: <4068F16C.6050800@e-greek.net>
<26103.1080621215@sss.pgh.pa.us>
Tom Lane wrote:
> Andrew Biagioni <andrew.biagioni@e-greek.net> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: andrew.biagioni@e-greek.net, tgl@sss.pgh.pa.us
Subject: Re: Spontaneous PostgreSQL Server Reboot?
In-Reply-To: <40699984.6030706@e-greek.net>
References: <4068F16C.6050800@e-greek.net> <26103.1080621215@sss.pgh.pa.us> <40699984.6030706@e-greek.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox