Databases
StackOverflow2013
Postsdbo
PORails produces "PGError: server closed the connection unexpectedly" after some timeout
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PORails produces "PGError: server closed the connection unexpectedly" after some timeout
    primarykey
    data
    text
    <p>I have the setup of my Rails app as following:</p> <ul> <li>Rails: 3.0.5 (under Apache proxy) running on RHEL 5.6</li> <li>Postgres: 8.4, running on Windows Server 2008 The 2 servers are on the same LAN.</li> </ul> <p>The problem is, after some idle time, when I make a new request to the Rails app, it gives me the following error:</p> <pre><code>ActiveRecord::StatementInvalid (PGError: server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request. </code></pre> <p>From what I have researched, it seems that the database connections are dropped after some timeout by Postgres. During this time, from the Rails side,</p> <ul> <li>if I make a request to Rails (1st request), it will display the connection error as above</li> <li>if I make another request to Rails (2nd request), Rails seems to reconnect to Postgres and functions correctly.</li> </ul> <p>It means that I will always experience the first connection error then will have all normal operation again, which is very serious in my case since I'd like to deliver a non-error response to my client.</p> <p>I have looked in following questions and answers, but they do not seem to be appropriate for my case:</p> <ul> <li><a href="https://stackoverflow.com/questions/4675380/pgerror-no-connection-to-the-server-after-idle">&quot;PGError: no connection to the server&quot; after idle</a> (Ubuntu for DB server)</li> <li><a href="https://stackoverflow.com/questions/2166872/how-to-use-tcp-keepalives-settings-in-postgresql">How to use tcp_keepalives settings in Postgresql?</a> (keepalives in MacOS)</li> </ul> <p>Do you have any advice in order to make my app free from db connection errors? Thank you.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USAnh Nguyen
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PORails produces "PGError: server closed the connection unexpectedly" after some timeout
      1. USSalil
      1. VTFavorite
    2. VO
      singulars
      1. PORails produces "PGError: server closed the connection unexpectedly" after some timeout
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PORails produces "PGError: server closed the connection unexpectedly" after some timeout
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI am getting same error while using postgresql with heroku
      singulars
      1. PORails produces "PGError: server closed the connection unexpectedly" after some timeout
      1. USSalil
    2. COIt is normal for connections to go away. It is not normal for Rails to treat it so ungracefully. Check your database driver (adapter)'s implementation of `verify!` and `active?`; normally `ActiveRecord::ConnectionAdapters::ConnectionPool` gives the adapter a chance to reconnect any stale connection immediately prior to checking it out from the pool. Which gem are you using for Postgres?
      singulars
      1. PORails produces "PGError: server closed the connection unexpectedly" after some timeout
      1. USvladr
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload