Обсуждение: Error starting postmaster

Поиск
Список
Период
Сортировка

Error starting postmaster

От
Gregg Berkholtz
Дата:
I am running Slackware 3.5, PostgreSQL 6.4.
I was able to start and run PostgreSQL and run the initial regression
test with only a failure in geometry and misc.
Overall it worked well.
I kill the postmaster process.

I got an error:
FATAL: StreamServerPort: bind() failed: errno=98
        Is another postmaster already running on that port?
        If not, remove socket node (/tmp/.s.PGSQL.5432) and retry

I deleted this .s.PGSQL.5432 file and am now getting this error on
startup:
IpcMemoryCreate: shmget failed (Identifier removed) key=5432010,
size=24588, per
mission=700
IpcMemoryIdGet: shmget failed (Identifier removed) key=5432010,
size=24588, perm
ission=0
IpcMemoryAttach: shmat failed (Invalid argument) id=-2
FATAL 1:  AttachSLockMemory: could not attach segment

I have also tried deleting the '/usr/local/pgsql/data' directory and
then run initdb again -- didn't work.

Any help please -- thanks greatly!
--
-----------------------------------------------------
/////////////   Gregg Berkholtz - Owner/Consultant
|    G B    |    PC, Novell, and Linux Support/Sales
| Computers |     info: www.gbcomputers.com
\\\\\\\\\\\\\


Re: [ADMIN] Error starting postmaster

От
Benjamin Gonay
Дата:
Hi Gregg,

Try to remove the old ipc from system memory using the 'ipcrm' command.
(You can view ipcs with the 'ipcs' command, see man's if troubles)

Hope this help you...

On Sun, 3 Jan 1999, Gregg Berkholtz wrote:

> I am running Slackware 3.5, PostgreSQL 6.4.
> I was able to start and run PostgreSQL and run the initial regression
> test with only a failure in geometry and misc.
> Overall it worked well.
> I kill the postmaster process.
>
> I got an error:
> FATAL: StreamServerPort: bind() failed: errno=98
>         Is another postmaster already running on that port?
>         If not, remove socket node (/tmp/.s.PGSQL.5432) and retry
>
> I deleted this .s.PGSQL.5432 file and am now getting this error on
> startup:
> IpcMemoryCreate: shmget failed (Identifier removed) key=5432010,
> size=24588, per
> mission=700
> IpcMemoryIdGet: shmget failed (Identifier removed) key=5432010,
> size=24588, perm
> ission=0
> IpcMemoryAttach: shmat failed (Invalid argument) id=-2
> FATAL 1:  AttachSLockMemory: could not attach segment
>
> I have also tried deleting the '/usr/local/pgsql/data' directory and
> then run initdb again -- didn't work.
>
> Any help please -- thanks greatly!
> --
> -----------------------------------------------------
> /////////////   Gregg Berkholtz - Owner/Consultant
> |    G B    |    PC, Novell, and Linux Support/Sales
> | Computers |     info: www.gbcomputers.com
> \\\\\\\\\\\\\
>
>

Cybersalutations.
Benjamin Gonay
---------------------------------------------------------------------------
_/        Email internet : Benjamin.Gonay@ltlg1.is.belgacom.be           _/
_/  ~~ Soyons realistes, exigeons l'impossible.    (E. Che Guevara)  ~~  _/
_/  - - [Belgium - Liege] - - - - - - - - - - - - - - - - - - - - - - -  _/
_/  linux forever...Linux Forever...LINUX Forever...LINUX FOREVER !!!!!  _/
---------------------------------------------------------------------------


Re: Error starting postmaster

От
khansen
Дата:
I'm not currently able to access my system but will try to do this from memory...

First, I'd do a man lookup on ipcclean (I think).  This will attempt to
clean out the shared memory segments that may be reserved but not in use.

If that doesn't work, there is a startup option (-B nnn) where you can
specify the number of default buffers when you start the postmaster.  I
don't know what the default is right off hand, but on Redhat I could
make it start by setting this number to around 100.

Unfortunately, the only way I found to _permanently_ get rid of this
problem with the Redhat distribution was to increase the value of SHMMAX
in /usr/src/linux/include/asm-i386/shmparam.h.  After doing that I
recompiled the kernel and haven't had a problem since.

Now, two disclaimers on this.  I have _no_ idea what other effects
making this kernel change will have on your system.  I've been running
this way for 2+ months without seeing any problems.  I could never find
anyone that could answer that question to my satisfaction.  The second
disclaimer is that some say recompiling the kernel is not for the faint
of heart.  It didn't bother me, but I had good backups...    :-)

Hope this helps.


> Date: Sun, 03 Jan 1999 15:55:55 -0800
> From: Gregg Berkholtz <gregg@gbcomputers.com>
> Subject: Error starting postmaster
>
> I am running Slackware 3.5, PostgreSQL 6.4.
> I was able to start and run PostgreSQL and run the initial regression
> test with only a failure in geometry and misc.
> Overall it worked well.
> I kill the postmaster process.
>
> I got an error:
> FATAL: StreamServerPort: bind() failed: errno=98
>         Is another postmaster already running on that port?
>         If not, remove socket node (/tmp/.s.PGSQL.5432) and retry
>
> I deleted this .s.PGSQL.5432 file and am now getting this error on
> startup:
> IpcMemoryCreate: shmget failed (Identifier removed) key=5432010,
> size=24588, per
> mission=700
> IpcMemoryIdGet: shmget failed (Identifier removed) key=5432010,
> size=24588, perm
> ission=0
> IpcMemoryAttach: shmat failed (Invalid argument) id=-2
> FATAL 1:  AttachSLockMemory: could not attach segment
>
> I have also tried deleting the '/usr/local/pgsql/data' directory and
> then run initdb again -- didn't work.
>
> Any help please -- thanks greatly!
> - --
> - -----------------------------------------------------
> /////////////   Gregg Berkholtz - Owner/Consultant
> |    G B    |    PC, Novell, and Linux Support/Sales
> | Computers |     info: www.gbcomputers.com
> \\\\\\\\\\\\\
>
> ------------------------------
>
> End of pgsql-admin-digest V1 #122
> *********************************