pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Chatur Gopalkrishna <chatur.gopalkrishna@ridenext.co.in>
To: pgsql-bugs@lists.postgresql.org
Subject: Unable to fork: Resource Unavailable
Date: Tue, 7 Jan 2020 14:45:44 +0530
Message-ID: <007001d5c53b$0db0ca90$29125fb0$@ridenext.co.in> (raw)

Hi!

 

Our system works in hot/standby mode. There are multiple tables with
multiple entries in the postgres sql database.

 

We observed that at times, observing the following prints:

 

2019-12-28T14:11:12.522653+09:00 localhost postgres[1355]: [3-1] 2019-12-28
05:11:12.521 GMT LOG:  could not fork autovacuum worker process: Resource
temporarily unavailable

2019-12-28T14:11:13.050796+09:00 localhost postgres[1355]: [4-1] 2019-12-28
05:11:13.050 GMT LOG:  archiver process (PID 27698) exited with exit code 1

2019-12-28T14:11:13.051514+09:00 localhost postgres[1355]: [5-1] 2019-12-28
05:11:13.051 GMT LOG:  archiver process (PID 17226) exited with exit code 1

2019-12-28T14:12:23.259291+09:00 localhost postgres[1355]: [6-1] 2019-12-28
05:12:23.259 GMT LOG:  could not fork new process for connection: Resource
temporarily unavailable

2019-12-28T14:12:23.267624+09:00 localhost postgres[1355]: [7-1] 2019-12-28
05:12:23.267 GMT LOG:  could not fork new process for connection: Resource
temporarily unavailable

2019-12-28T14:14:08.384115+09:00 localhost postgres[1355]: [8-1] 2019-12-28
05:14:08.383 GMT LOG:  could not fork new process for connection: Resource
temporarily unavailable

2019-12-28T14:14:08.384348+09:00 localhost postgres[1355]: [9-1] 2019-12-28
05:14:08.384 GMT LOG:  could not fork new process for connection: Resource
temporarily unavailable

2019-12-28T14:14:12.581409+09:00 localhost postgres[1355]: [10-1] 2019-12-28
05:14:12.581 GMT LOG:  could not fork autovacuum worker process: Resource
temporarily unavailable

2019-12-28T14:14:13.391192+09:00 localhost postgres[1355]: [11-1] 2019-12-28
05:14:13.391 GMT LOG:  could not fork new process for connection: Resource
temporarily unavailable

2019-12-28T14:14:13.391356+09:00 localhost postgres[1355]: [12-1] 2019-12-28
05:14:13.391 GMT LOG:  could not fork new process for connection: Resource
temporarily unavailable

2019-12-28T14:14:13.581992+09:00 localhost postgres[1355]: [13-1] 2019-12-28
05:14:13.581 GMT LOG:  could not fork autovacuum worker process: Resource
temporarily unavailable

.

.

 

 

Due to the above, our applications are unable to connect to Postgres and our
systems are rebooting.

 

Can someone please help me understand the reason of "Resource temporarily
unavailable" and any configuration / debug pointers?

 

 

Thanks,

Chatur G

 

 

 

view thread (2+ messages)  latest in thread

Message-ID: <007001d5c53b$0db0ca90$29125fb0$@ridenext.co.in>
Permalink:  ../007001d5c53b$0db0ca90$29125fb0$@ridenext.co.in/
Also on:    postgresql.org/message-id/007001d5c53b$0db0ca90$29125fb0$@ridenext.co.in

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-bugs@postgresql.org
  Cc: chatur.gopalkrishna@ridenext.co.in
  Subject: Re: Unable to fork: Resource Unavailable
  In-Reply-To: <007001d5c53b$0db0ca90$29125fb0$@ridenext.co.in>
  References: <007001d5c53b$0db0ca90$29125fb0$@ridenext.co.in>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox