Re: Restart after poweroutage

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: lapham(at)jandr(dot)org
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Restart after poweroutage
Date: 2007-03-13 19:28:05
Message-ID: 8442.1173814085@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Jon Lapham <lapham(at)jandr(dot)org> writes:
> chdir("/var/lib/pgsql/data") = 0
> open("postmaster.pid", O_RDWR|O_CREAT|O_EXCL, 0600) = -1 EEXIST (File
> exists)
> open("postmaster.pid", O_RDONLY) = 3
> read(3, "2809\n/var/lib/pgsql/data\n 54320"..., 1123) = 45
> close(3) = 0
> getppid() = 4150
> kill(2809, SIG_0) = -1 ESRCH (No such process)
> shmctl(32768, IPC_STAT, 0x7fffd6144e00) = -1 EIDRM (Identifier removed)

Oh, that's interesting. The code is barfing on this because

/*
* Otherwise, we had better assume that the segment is in use. The
* only likely case is EIDRM, which implies that the segment has been
* IPC_RMID'd but there are still processes attached to it.
*/

It would seem that maybe your kernel has a different idea of what EIDRM
means than we do. You say this persists across a reboot?

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Jon Lapham 2007-03-13 19:43:19 Re: Restart after poweroutage
Previous Message Jon Lapham 2007-03-13 19:13:00 Re: Restart after poweroutage