Dave Cramer writes:
> 2014-06-18 13:37:15 EDT FATAL: could not map anonymous shared memory:
> Cannot allocate memory
> 2014-06-18 13:37:15 EDT HINT: This error usually means that PostgreSQL's
> request for a shared memory segment exceeded available memory or swap
> space. To reduce the request s
Problem solved... a runaway process (puppet) had consumed all available
real memory
Dave Cramer
On 18 June 2014 15:24, Dave Cramer wrote:
> 2014-06-18 13:37:15 EDT FATAL: could not map anonymous shared memory:
> Cannot allocate memory
> 2014-06-18 13:37:15 EDT HINT: This error usually means
2014-06-18 13:37:15 EDT FATAL: could not map anonymous shared memory:
Cannot allocate memory
2014-06-18 13:37:15 EDT HINT: 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 8826445824 bytes
Dave Cramer writes:
> To reduce the request size [FAILently 2232950784 bytes), reduce
> PostgreSQL's shared memory usage,
This error message is a bit garbled :-(. It would've been useful
to know the specific errno, but you've trimmed out that info.
Perhaps it's failing because you already have
Here are my kernel settings
kernel.shmmax = 10737418240
# Maximum total size of all shared memory segments in pages (normally 4096
bytes)
kernel.shmall = 2621440
kernel.sem = 250 32000 32 1200
They are actually set...
sysctl -a | grep shm
kernel.shmmax = 10737418240
kernel.shmall = 2621440
kern