From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
---|---|
To: | Jon Lapham <lapham(at)jandr(dot)org> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Restart after poweroutage |
Date: | 2006-09-24 15:29:56 |
Message-ID: | 20060924152956.GB26805@svana.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sun, Sep 24, 2006 at 10:11:00AM -0300, Jon Lapham wrote:
> I recently had another electrical power outage that left my machine
> unable to restart postgresql. I had previously reported this a while ago:
FWIW, I've crashed my machine a lot of times and never run into this
problem. However, I run Debian, maybe they do something different.
> Looking at $PGLOG, I discovered:
> FATAL: pre-existing shared memory block (key 5432001, ID 65536) is
> still in use
> HINT: If you're sure there are no old server processes still running,
> remove the shared memory block with the command "ipcclean", "ipcrm", or
> just delete the file "postmaster.pid".
This doesn't make sense to me. A reboot will absolutly kill any
existing shared memory blocks, how can it possibly be complaining about
it?
What does ipcs show after the failure to start postgres?
Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.
From | Date | Subject | |
---|---|---|---|
Next Message | Ben | 2006-09-24 15:33:21 | Re: powerset? |
Previous Message | Bobby Gontarski | 2006-09-24 15:20:36 | copy db1 to db2 |