From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Bhella Paramjeet-PFCW67 <PBhella(at)Motorola(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org, Subbiah Stalin-XCGF84 <SSubbiah(at)Motorola(dot)com> |
Subject: | Re: Postgres database is not logging any messages after the reboot |
Date: | 2007-10-19 14:51:27 |
Message-ID: | 20071019145127.GK16000@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
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"
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2007-10-19 14:57:07 | Re: Continuous archiving and wal generation |
Previous Message | yogesh | 2007-10-19 07:09:22 | Trigger AFTER UPDATE OR INSERT |