Problem solved... a runaway process (puppet) had consumed all available real memory
Dave Cramer On 18 June 2014 15:24, Dave Cramer <davecra...@gmail.com> 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 that PostgreSQL's > request for a shared memory segment exceeded available memory or swap > space. To reduce the request size (currently 8826445824 bytes), reduce > PostgreSQL's shared memory usage, perhaps by reducing shared_buffers or > max_connections. > > ipcs -m > > ------ Shared Memory Segments -------- > key shmid owner perms bytes nattch status > > > > Dave Cramer > > > On 18 June 2014 15:15, Tom Lane <t...@sss.pgh.pa.us> wrote: > >> Dave Cramer <davecra...@gmail.com> 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 ~10G in shared memory >> segments? "sudo ipcs -m" might be illuminating. >> >> regards, tom lane >> > >
