среда, 19 октября 2011 г.

PostgreSQL: server closed connection

Today I got a ton of messages

DBI connect('dbname=xxx;host=yyy','username',...) failed: server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request. at....

from our network statistic collector.
I spent some time trying to understand what had happened (besides yesterdays power fail). I looked at PostgreSQL server debug log (it honestly told that client just closed connection). There were no traces of dying postgres backend. I rolled back some minor configuration changes which I made yesterday... And later it downed upon me: it was just one old server which was supposed to have its network interface shut down waked after power failure... It was seen in dmesg:

arp: x.y.z.w moved from AA:AA:AA:AA:AA:AA to BB:BB:BB:BB:BB:BB on em0
arp: x.y.z.w moved from BB:BB:BB:BB:BB:BB to AA:AA:AA:AA:AA:AA on em0

Really, power cycling is neccessary sometimes to ascertain that all your services are configured properly :)

1 комментарий:

  1. What would i be able to do if PostgreSQL Connection Closed Unexpectedly? Contact to PostgreSQL Relational Database Service
    On the off chance that you have an issue with Postgres associations and in logs then you will see a mistake message which hint that "Ending association in light of crash of another server procedure". To take care of this issue first you need to check which PostgreSQL adaptation you are utilizing then you need to likewise check which OS you are running. On the off chance that as yet confronting a similar association issue then without going out on a limb contact to Postgres SQL Support for Linux or Postgres SQL Support for Windows to tackle your specialized glitches.
    For More Info: https://cognegicsystems.com/
    Contact Number: 1-800-450-8670
    Email Address- info@cognegicsystems.com
    Company’s Address- 507 Copper Square Drive Bethel Connecticut (USA) 06801