Received: from localhost (unknown [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 6155F9FA24B for ; Fri, 19 Oct 2007 11:51:43 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 67376-01 for ; Fri, 19 Oct 2007 11:51:36 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from lists.commandprompt.com (host-254.commandprompt.net [207.173.203.254]) by postgresql.org (Postfix) with ESMTP id 9410E9FA12D for ; Fri, 19 Oct 2007 11:51:36 -0300 (ADT) Received: from perhan.alvh.no-ip.org (201-220-127-162.bk10-dsl.surnet.cl [201.220.127.162]) (authenticated bits=0) by lists.commandprompt.com (8.13.7/8.13.6) with ESMTP id l9JEpTM4023837; Fri, 19 Oct 2007 07:51:30 -0700 Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 37E7E47C79; Fri, 19 Oct 2007 11:51:27 -0300 (CLST) Date: Fri, 19 Oct 2007 11:51:27 -0300 From: Alvaro Herrera To: Bhella Paramjeet-PFCW67 Cc: pgsql-admin@postgresql.org, Subbiah Stalin-XCGF84 Subject: Re: Postgres database is not logging any messages after the reboot Message-ID: <20071019145127.GK16000@alvh.no-ip.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.16 (2007-06-11) X-Virus-Scanned: ClamAV 0.91.1/4545/Wed Oct 17 14:05:57 2007 on projects.commandprompt.com X-Virus-Status: Clean X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.6 (lists.commandprompt.com [192.168.2.159]); Fri, 19 Oct 2007 07:51:31 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200710/191 X-Sequence-Number: 27105 Bhella Paramjeet-PFCW67 wrote: > Hi > > The server that hosts our production postgres databases had to be > rebooted last night as the file systems got remounted as read only. > After the reboot we re-started the databases but now nothing is getting > logged into the pglogs. Can you please assist us in figuring out the > problem and help resolve it. Below listed are the error messages in the > /var/log/messages file due to which we had to reboot the server. This is > a linux x86-64 server. Your prompt response will be highly appreciated. When a filesystem is automatically remounted read-only by the operating system, it's because serious trouble is ahead. Rebooting to remount read-write seems a recipe for disaster unless you have corrected the problem. This may be a Linux kernel bug, a disk/cable/controller failure, or something else. -- Alvaro Herrera Valdivia, Chile ICBM: S 39º 49' 18.1", W 73º 13' 56.4" "The ability to monopolize a planet is insignificant next to the power of the source"