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 3BB63D1D0B6 for ; Tue, 30 Mar 2004 04:02:53 +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 41799-01 for ; Tue, 30 Mar 2004 00:02:50 -0400 (AST) Received: from sycorax.affordablehost.com (sycorax.affordablehost.com [216.46.192.84]) by svr1.postgresql.org (Postfix) with ESMTP id 2DBF1D1B4CB for ; Tue, 30 Mar 2004 00:02:49 -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 1B8ASb-0006fJ-0j; Mon, 29 Mar 2004 23:02:45 -0500 Message-ID: <4068F16C.6050800@e-greek.net> Date: Mon, 29 Mar 2004 23:02:52 -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: Spontaneous PostgreSQL Server Reboot? 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/381 X-Sequence-Number: 12950 Help! I'm having a severe problem with my production PostgreSQL servers, and I'm running out of ideas as to what could be the problem. 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. On the first two machines it was clearly connected to running a very complex query (multi-hour processing time); on the third, I could find no such correlation. Please note that only one machine was Production at any one time; the problem never occurred with the Development servers (equivalent configuration). This in and of itself may hint to a threading issue (the DB is serving web servers, plus the occasional maintenance cron job - no cron job running when the last reboot occurred). When the last reboot occurred (this past Friday evening), I scoured all logs for any information; the only log that shows any activity in within 5 minutes of the restart is $PG_DATA/serverlog: 2004-03-26 21:46:59 [10534] LOG: query: SELECT v.* FROM [...] 2004-03-26 21:46:59 [10534] LOG: duration: 0.049330 sec The machine restarted around 21:50 (based on syslog): Mar 26 21:50:33 prod-db-2-1 syslogd 1.4.1#10: restart. I especially found no panics, errors, warnings, ... The machine is used only as a DB server, nothing else running (not even a mail server). I'm running out of things to look for! I'm running PostgreSQL 7.3.5 on Linux (pentium machines), configured as follows: 1. Red Hat 7.3 with 120 GB HDD and 1 GB RAM; 2. Red Hat 7.3 with 80 GB HDD and 512 MB RAM; 3. Debian with a 2.2.20 kernel, 5.5 GB HDD and 384 MB RAM. This is the latest one in use. Note that even the 5.5 GB machine has over 1 GB spare on the /usr/local/pgsql/ partition. Thanks for any and all help! Andrew Biagioni