Обсуждение: Connection rejected: could not fork new process for connection: Unknown error
Hello, The above error occurs approx 2 out of 3 times when attempting to connect to server/database from pgadmin3 or eclipse. Any assistance would be appreciated. Thanks, Sam -- View this message in context: http://postgresql.1045698.n5.nabble.com/Connection-rejected-could-not-fork-new-process-for-connection-Unknown-error-tp5793119.html Sent from the PostgreSQL - novice mailing list archive at Nabble.com.
samcoffey <samcoffey82@gmail.com> writes:
> The above error occurs approx 2 out of 3 times when attempting to connect to
> server/database from pgadmin3 or eclipse.
What platform is this? Does any additional information appear in the
postmaster log?
At face value, this indicates you've got a heavily overloaded server
machine, but perhaps something else is going on.
regards, tom lane
Hi Tom, The following is appearing in postgresql-2014-02-21_090639.log (This is the only log file I can find): 2014-02-21 09:08:10 GMT LOG: could not reserve shared memory region (addr=0000000002300000) for child 00000000000004FC: error code 487 2014-02-21 09:08:10 GMT LOG: could not fork autovacuum worker process: A blocking operation was interrupted by a call to WSACancelBlockingCall. This is the PostgreSQL 9.3 (localhost:5432) server running on Windows. Thanks, Sam. -- View this message in context: http://postgresql.1045698.n5.nabble.com/Connection-rejected-could-not-fork-new-process-for-connection-Unknown-error-tp5793119p5793126.html Sent from the PostgreSQL - novice mailing list archive at Nabble.com.
samcoffey <samcoffey82@gmail.com> writes: > The following is appearing in postgresql-2014-02-21_090639.log (This is the > only log file I can find): > 2014-02-21 09:08:10 GMT LOG: could not reserve shared memory region > (addr=0000000002300000) for child 00000000000004FC: error code 487 > 2014-02-21 09:08:10 GMT LOG: could not fork autovacuum worker process: A > blocking operation was interrupted by a call to WSACancelBlockingCall. > This is the PostgreSQL 9.3 (localhost:5432) server running on Windows. Hm ... recent Windows? You may need to turn off ASLR, see for instance http://www.postgresql.org/message-id/52EB4751.2060205@2ndquadrant.com AFAIK the proposed code changes to handle this automatically haven't been committed yet, much less made it into any released version of PG. regards, tom lane
Hi Tom, The issue is now resolved. Downloaded zip archive of PostgreSQL and followed this guide: http://www.petrikainulainen.net/programming/tips-and-tricks/installing-postgresql-9-1-to-windows-7-from-the-binary-zip-distribution/ Thanks for your help. Sam. -- View this message in context: http://postgresql.1045698.n5.nabble.com/Connection-rejected-could-not-fork-new-process-for-connection-Unknown-error-tp5793119p5793677.html Sent from the PostgreSQL - novice mailing list archive at Nabble.com.