Thread: shared memory problem
HI all! I did this: /usr/local/pgsql/bin/postmaster -B 1000 -o "-S 2000" -S -D /usr/local/pgsql/data and it says: IpcMemoryCreate: shmget failed (Invalid argument) key=5432001, size=8899584,permission=600 This type of erro is usually caused by an improper shared memory or System V IPC semaphore configuration. Form more information.... what should I do, I am running a 600Mhz Celeron with 512RAM, I have tried the same command in others machines and works fine, thank you for your help, Rocael. ____________________________________________________________________ Get free email and a permanent address at http://www.netaddress.com/?N=1
<rocael@usa.net> writes: > /usr/local/pgsql/bin/postmaster -B 1000 -o "-S 2000" -S -D > /usr/local/pgsql/data > and it says: > IpcMemoryCreate: shmget failed (Invalid argument) key=5432001, > size=8899584,permission=600 > This type of erro is usually caused by an improper shared memory or System V > IPC semaphore configuration. Form more information.... Most likely your kernel isn't set to allow shared memory blocks as large as 8M. regards, tom lane
I'm not sure if this is related, and unfortunately I don't have the specific error in front of me, but on occasion when I restart postgresql, using $ /etc/rc.d/init.d/postgresql restart I'll see the shutdown message, then I'll see a shared memory creation error, which I think looked similar to the one below. In the past I would just boot the box, and postgresql naturally would start up just fine. But last time it happened I waited a minute, then attempted the restart again (which obviously would just do a start, as postgresql wasn't running because of previous failure.) It started up fine that time. Perhaps there's some issue with the shared memory not being freed quickly enough by the kernel? michael --- Tom Lane <tgl@sss.pgh.pa.us> wrote: > <rocael@usa.net> writes: > > /usr/local/pgsql/bin/postmaster -B 1000 -o "-S > 2000" -S -D > > /usr/local/pgsql/data > > > and it says: > > IpcMemoryCreate: shmget failed (Invalid argument) > key=5432001, > > size=8899584,permission=600 > > This type of erro is usually caused by an improper > shared memory or System V > > IPC semaphore configuration. Form more > information.... > > Most likely your kernel isn't set to allow shared > memory blocks as > large as 8M. > > regards, tom lane __________________________________________________ Do You Yahoo!? Yahoo! Calendar - Get organized for the holidays! http://calendar.yahoo.com/
Michael Teter <michael_teter@yahoo.com> writes: > Perhaps there's some issue with the shared memory not > being freed quickly enough by the kernel? Never heard of that before. There is an issue with time delays on release of port addresses --- sometimes you may get a failure to bind() to a port address that was just released by a previous incarnation of the postmaster. But I haven't heard of such a thing for shared memory or semaphores. regards, tom lane