Re: could not create shared memory segment: Invalid argument

From: Ryan King - NOAA Affiliate <ryan(dot)king(at)noaa(dot)gov>
To: pgsql-general(at)postgresql(dot)org, pgsql-admin(at)postgresql(dot)org, pgsql-performance(at)postgresql(dot)org
Subject: Re: could not create shared memory segment: Invalid argument
Date: 2015-07-14 00:08:22
Message-ID: CAJAJqWHiAng_dKk7=S3HgiBQuF02PGSxxNS_cBFM0zY36ZqRJA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-general pgsql-performance

Apologies ahead of time for not knowing which group to send to, but I
wanted to see if anyone has encountered and resolved this type of error.
I'm setting up postgresql 9.2 streaming replication on RH and after copying
the master data directory over to the slave, the psql service refuses start
and gives the following errors.

2015-07-13 23:55:41.224 UTC FATAL: could not create shared memory
segment: Invalid argument
2015-07-13 23:55:41.224 UTC DETAIL: Failed system call was
shmget(key=5432001, size=1146945536, 03600).
2015-07-13 23:55:41.224 UTC HINT: This error usually means that
PostgreSQL's request for a shared memory segment exceeded your kernel's
SHMMAX parameter. You can either reduce the request size or reconfigure
the kernel with larger SHMMAX. To reduce the request size (currently
1146945536 bytes), reduce PostgreSQL's shared memory usage, perhaps by
reducing shared_buffers or max_connections.
If the request size is already small, it's possible that it is less
than your kernel's SHMMIN parameter, in which case raising the request size
or reconfiguring SHMMIN is called for.
The PostgreSQL documentation contains more information about shared
memory configuration.
2015-07-13 23:56:21.344 UTC FATAL: could not create shared memory
segment: Invalid argument
2015-07-13 23:56:21.344 UTC DETAIL: Failed system call was
shmget(key=5432001, size=58302464, 03600).
2015-07-13 23:56:21.344 UTC HINT: This error usually means that
PostgreSQL's request for a shared memory segment exceeded your kernel's
SHMMAX parameter. You can either reduce the request size or reconfigure
the kernel with larger SHMMAX. To reduce the request size (currently
58302464 bytes), reduce PostgreSQL's shared memory usage, perhaps by
reducing shared_buffers or max_connections.
If the request size is already small, it's possible that it is less
than your kernel's SHMMIN parameter, in which case raising the request size
or reconfiguring SHMMIN is called for.
The PostgreSQL documentation contains more information about shared
memory configuration.

I've set shared_buffer way down to next to nothing along with kernel.shmmax
and kernel.shmall per some blogs. However, the same error persists, and I'm
getting no where. I think ultimately the solution is to upgrade, but the
devs may not be ready for an upgrade at this point. Any help would be
greatly appreciated. Thanks!

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Scott Whitney 2015-07-14 00:15:19 Re: could not create shared memory segment: Invalid argument
Previous Message Melvin Davidson 2015-07-13 23:58:27 Re: PgAdmin 1.20 for Ubuntu Trusty Tahr?

Browse pgsql-general by date

  From Date Subject
Next Message Scott Whitney 2015-07-14 00:15:19 Re: could not create shared memory segment: Invalid argument
Previous Message Andreas Joseph Krogh 2015-07-13 14:39:01 Re: Obtaining advisory lock using ORDER BY

Browse pgsql-performance by date

  From Date Subject
Next Message Scott Whitney 2015-07-14 00:15:19 Re: could not create shared memory segment: Invalid argument
Previous Message Merlin Moncure 2015-07-13 21:01:35 Re: Query planner not using indexes with JOIN query and OR clause