Re: [GENERAL] LOG: could not fork new process for connection: Cannot allocate memory

2016-08-28 Thread Jeff Janes
On Sun, Aug 28, 2016 at 5:18 PM, Jim Nasby wrote: > On 8/25/16 7:45 PM, Ahsan Ali wrote: > > Please don't top-post; it's harder to read. > >> On Thu, Aug 25, 2016 at 5:29 PM, John R Pierce > > wrote: >> so there were 1818 postgres client processes at the time it co

Re: [GENERAL] LOG: could not fork new process for connection: Cannot allocate memory

2016-08-28 Thread Jim Nasby
On 8/25/16 7:45 PM, Ahsan Ali wrote: Please don't top-post; it's harder to read. On Thu, Aug 25, 2016 at 5:29 PM, John R Pierce mailto:pie...@hogranch.com>> wrote: so there were 1818 postgres client processes at the time it coudln't create a new process. thats certainly a larger number

Re: [GENERAL] LOG: could not fork new process for connection: Cannot allocate memory

2016-08-25 Thread Ahsan Ali
we have a pooling on the application level. however we never had this issues before this start happning since last couple of days in past we had over 2300 sessions but no issues. On Thu, Aug 25, 2016 at 5:29 PM, John R Pierce wrote: > On 8/25/2016 5:10 PM, Ahsan Ali wrote: > >> yes it is older h

Re: [GENERAL] LOG: could not fork new process for connection: Cannot allocate memory

2016-08-25 Thread John R Pierce
On 8/25/2016 5:10 PM, Ahsan Ali wrote: yes it is older however we do apply security patches now a then. redhat doesn't really support mixing packages from different releases, they only test things with all packages from the same snapshot. "yum update" should bring the whole system up to cur

Re: [GENERAL] LOG: could not fork new process for connection: Cannot allocate memory

2016-08-25 Thread Ahsan Ali
yes it is older however we do apply security patches now a then. regarding max connection its the application design however it does not have that many active session. postgres=# select count(*) from pg_stat_activity; count --- 1818 Please let me know if you like to see any other logs and

Re: [GENERAL] LOG: could not fork new process for connection: Cannot allocate memory

2016-08-25 Thread John R Pierce
On 8/25/2016 3:54 PM, Ahsan Ali wrote: Red Hat Enterprise Linux Server release 6.3 (Santiago) that was released in June 2012, you're missing 4+ years of bug fixes, 6.8 is current. max_connections = 3000 thats insanely high for most purposes unless you have several 100 CPU cores. otherwi

Re: [GENERAL] LOG: could not fork new process for connection: Cannot allocate memory

2016-08-25 Thread Ahsan Ali
Hi John, Thanks for replying. Below are all the details I am using psql (PostgreSQL) 9.5.2 Error we got in postgresql log* 2016-08-25 11:15:55 PDT [60739]: [10282-1] LOG: could not fork new process for connection: Cannot allocate memory 2016-08-25 11:15:55 PDT [60739]: [10283-1] LOG: co

Re: [GENERAL] LOG: could not fork new process for connection: Cannot allocate memory

2016-08-25 Thread John R Pierce
On 8/25/2016 11:49 AM, Ahsan Ali wrote: I having my production server service intruption because of this "Cannot allocate memory" error in the db log. could you paste the whole error message? what version of postgres is this? what OS (if linux, distribution) version is this? older version

[GENERAL] LOG: could not fork new process for connection: Cannot allocate memory

2016-08-25 Thread Ahsan Ali
Hi Support I having my production server service intruption because of this "Cannot allocate memory" error in the db log. because of this error even DBA's cant login to the db server unless we kill one of the existing sessions. Please help me resolve this issue. 1. $ grep Commit /proc/meminf