Cygwin-Postgres-IpcMemoryCreate - Mailing list pgsql-cygwin

From Saravanan Bellan
Subject Cygwin-Postgres-IpcMemoryCreate
Date
Msg-id A37D6E7E941A1E498B4B98F3E4AFA92035CAE6@MAIL.design2deploy.com
Whole thread Raw
Responses Re: Cygwin-Postgres-IpcMemoryCreate
List pgsql-cygwin
This was initially posted in comp.databases.postgresql.ports.cygwin.

Updates:

If using the rename() instead of link() the following error is not
experienced anymore.

> 1) FATAL 2:  link from /cygdrive/C/pg/data/pg_xlog/0000000000000004 to
> /cygdrive/C/pg/data/pg_xlog/0000000000000007 (initialization of log
> file 0, segment 7) failed: Permission denied

But the following error,I think, is independent of the above one.

> DEBUG:  all server processes terminated; reinitializing shared memory
> and semaphores
> IpcMemoryCreate: shmget(key=5432001, size=1441792, 03600) failed: Not
> enough memory

Please the read the following initial post anyway.

Thanks,


> > Sorry about including a large section of the log file in the end.
> >
> > I'm Running Postgres 7.2.1 on W2K box, Cygwin DLL 1.3.10 with 384M
> > Memory.
> >
> > I'm pretty sure I have around 200M free memory when this error occurs.
> >
> > If I look at the sequence of actions in the log,
> >
> > 1) FATAL 2:  link from /cygdrive/C/pg/data/pg_xlog/0000000000000004 to
> > /cygdrive/C/pg/data/pg_xlog/0000000000000007 (initialization of log
> > file 0, segment 7) failed: Permission denied
> > 2) One child process exits
> > 3) SIGQUIT is sent to the other processes.
> > 4) All the other children die
> > 5) Reinitialize processes (all server processes terminated;
> > reinitializing shared memory and semaphores)
> > 6) Then the error reads, IpcMemoryCreate: shmget(key=5432001,
> > size=1441792, 03600) failed: Not enough memory
> >
> >
> > Please help.
> >
> >
> > The actual log file section is below.
> >
> >
> >
> > FATAL 2:  link from /cygdrive/C/pg/data/pg_xlog/0000000000000004 to
> > /cygdrive/C/pg/data/pg_xlog/0000000000000007 (initialization of log
> > file 0, segment 7) failed: Permission denied
> > ...
> > ...
> > ...
> > ...
> > ....
> > ...
> > DEBUG:  reaping dead processes
> > DEBUG:  child process (pid 488) exited with exit code 2
> > DEBUG:  server process (pid 488) exited with exit code 2
> > DEBUG:  terminating any other active server processes
> > DEBUG:  CleanupProc: sending SIGQUIT to process 320
> > DEBUG:  CleanupProc: sending SIGQUIT to process 2920
> > DEBUG:  CleanupProc: sending SIGQUIT to process 1996
> > DEBUG:  CleanupProc: sending SIGQUIT to process 2940
> > NOTICE:  Message from PostgreSQL backend:
> >     The Postmaster has informed me that some other backend
> >     died abnormally and possibly corrupted shared memory.
> >     I have rolled back the current transaction and am
> >     going to terminate your database system connection and exit.
> >     Please reconnect to the database system and repeat your query.
> > DEBUG:  StartTransactionCommand
> > DEBUG:  CommitTransactionCommand
> > DEBUG:  StartTransactionCommand
> > DEBUG:  CommitTransactionCommand
> > DEBUG:  StartTransactionCommand
> > DEBUG:  CommitTransactionCommand
> > DEBUG:  StartTransactionCommand
> > DEBUG:  CommitTransactionCommand
> > NOTICE:  Message from PostgreSQL backend:
> >     The Postmaster has informed me that some other backend
> >     died abnormally and possibly corrupted shared memory.
> >     I have rolled back the current transaction and am
> >     going to terminate your database system connection and exit.
> >     Please reconnect to the database system and repeat your query.
> > NOTICE:  Message from PostgreSQL backend:
> >     The Postmaster has informed me that some other backend
> >     died abnormally and possibly corrupted shared memory.
> >     I have rolled back the current transaction and am
> >     going to terminate your database system connection and exit.
> >     Please reconnect to the database system and repeat your query.
> > NOTICE:  Message from PostgreSQL backend:
> >     The Postmaster has informed me that some other backend
> >     died abnormally and possibly corrupted shared memory.
> >     I have rolled back the current transaction and am
> >     going to terminate your database system connection and exit.
> >     Please reconnect to the database system and repeat your query.
> > DEBUG:  reaping dead processes
> > DEBUG:  child process (pid 320) exited with exit code 1
> > DEBUG:  reaping dead processes
> > DEBUG:  child process (pid 2920) exited with exit code 1
> > DEBUG:  child process (pid 1996) exited with exit code 1
> > DEBUG:  reaping dead processes
> > DEBUG:  reaping dead processes
> > DEBUG:  child process (pid 2940) exited with exit code 1
> > DEBUG:  all server processes terminated; reinitializing shared memory
> > and semaphores
> > IpcMemoryCreate: shmget(key=5432001, size=1441792, 03600) failed: Not
> > enough memory
> >
> > This error usually means that PostgreSQL's request for a shared
> > memory segment exceeded available memory or swap space.
> > To reduce the request size (currently 1441792 bytes), reduce
> > PostgreSQL's shared_buffers parameter (currently 64) and/or
> > its max_connections parameter (currently 32).
> >
> > The PostgreSQL Administrator's Guide contains more information about
> > shared memory configuration.

pgsql-cygwin by date:

Previous
From: "Steve Slatcher"
Date:
Subject: Re: PostgreSQL and Cygwin as production database
Next
From: Leandro Guimarães Faria Corsetti Dutra
Date:
Subject: Re: PostgreSQL and Cygwin as production database