Re: IpcSemaphoreKill: ...) failed: Invalid argument

From: "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>
To: "Christoph Haller" <ch(at)rodos(dot)fzk(dot)de>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: IpcSemaphoreKill: ...) failed: Invalid argument
Date: 2003-02-18 01:34:02
Message-ID: 043501c2d6ed$d2266500$6500a8c0@fhp.internal
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> This is a fairly spectacular failure :-(. As far as I can see from the
> semctl and shmctl man pages, the only plausible reason for EINVAL is
> that something had deleted the semaphores and shared memory out from
> under Postgres. I do not believe that Postgres itself could have done
> that --- it had to be some external agency. Unless the kernel is
> broken, whatever requested those deletions had to be running as root or
> as postgres in order to have the necessary permissions. You sure you
> didn't have some loose-cannon script running around issuing ipcrm
> commands?

Or ipcclean?

Chris

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2003-02-18 02:14:18 Re: [HACKERS] lock.h and proc.h
Previous Message Gavin Sherry 2003-02-18 01:10:30 Re: deadlock in REINDEX