Thread

1. problems with postmaster

   rocael@usa.net — 2000-11-24T11:12:26Z

   Hi all!
   I couldn't find a way to make my DB server work again.
   I did this:
   in postgres user  killall -9 postmaster (I wanted to stop the server)
   then  rm /tmp/.s.PGSQL.5432
   
   I tried to restart the server but I got this error:
   [postgres@aux-209-217-53-170 postgres]$ postmaster -D /usr/local/pgsql/data/
   IpcMemoryCreate: shmget failed (Identifier removed) key=5432010, size=144,
   permi
   ssion=700
   This type of error is usually caused by an improper
   shared memory or System V IPC semaphore configuration.
   For more information, see the FAQ and platform-specific
   FAQ's in the source directory pgsql/doc or on our
   web site at http://www.postgresql.org.
   IpcMemoryIdGet: shmget failed (Identifier removed) key=5432010, size=144,
   permis
   sion=0
   IpcMemoryAttach: shmat failed (Invalid argument) id=-2
   FATAL 1:  AttachSLockMemory: could not attach segment      
   
   
   What I can do?? Help me please!
   
   Thank you for your replys, also I want to know how to stop a pg server that is
   running in the background.
   
   Rocael.
   
   ____________________________________________________________________
   Get free email and a permanent address at http://www.netaddress.com/?N=1
   
   

2. Re: problems with postmaster

   Mike Castle <dalgoda@ix.netcom.com> — 2000-11-24T18:34:29Z

   ipcclean
   pg_ctl stop
   
   Though finding out about ipcclean was not easy considering the output
   given.  There is no mention of it in any of the FAQs.
   
   mrc
   -- 
          Mike Castle       Life is like a clock:  You can work constantly
     dalgoda@ix.netcom.com  and be right all the time, or not work at all
   www.netcom.com/~dalgoda/ and be right at least twice a day.  -- mrc
       We are all of us living in the shadow of Manhattan.  -- Watchmen
   
   

3. Re: problems with postmaster

   Mathijs Brands <mathijs@ilse.nl> — 2000-11-24T19:49:04Z

   On Fri, Nov 24, 2000 at 12:34:29PM -0600, Mike Castle allegedly wrote:
   > ipcclean
   > pg_ctl stop
   > 
   > Though finding out about ipcclean was not easy considering the output
   > given.  There is no mention of it in any of the FAQs.
   > 
   > mrc
   
   You could also use ipcrm manually to clean up the shm segments postgresql
   left lying around. Moral of the story: DON'T USE A SIGKILL TO STOP
   POSTGRESQL.
   
   Of course, there are times when you need to be somewhat crude.
   
   Mathijs
   -- 
   It's not that perl programmers are idiots, it's that the language
   rewards idiotic behavior in a way that no other language or tool has
   ever done.
                                                       Erik Naggum