Connections closing due to "terminating connection due to administrator command" - Mailing list pgsql-general

From Herouth Maoz
Subject Connections closing due to "terminating connection due to administrator command"
Date
Msg-id BA2AEDD6-1B9E-4E3D-BD71-B6ABF2D0353A@unicell.co.il
Whole thread Raw
Responses Re: Connections closing due to "terminating connection due to administrator command"  (Adrian Klaver <adrian.klaver@aklaver.com>)
List pgsql-general
Hello everybody.

In the past week, it has happened to us twice already that we got an exception from our Java application, due to PostgreSQL "terminating connection due to administrator command”.

The problem is that I’m the administrator, and I issued no such command.

On the first opportunity that it happened, the PostgreSQL server actually seemed to have spontaneously shut itself down and restarted:

2015-07-21 15:37:59 IDT LOG:  received fast shutdown request
2015-07-21 15:37:59 IDT LOG:  aborting any active transactions
2015-07-21 15:37:59 IDT FATAL:  terminating connection due to administrator command
2015-07-21 15:38:01 IDT LOG:  shutting down
2015-07-21 15:38:02 IDT LOG:  database system is shut down
2015-07-21 15:40:16 IDT LOG:  database system was shut down at 2015-07-21 15:38:02 IDT

On today’s occasion, the server seems to be continuing as usual, and there is nothing whatsoever in the log.

So my questions are:

  • Given that I did not terminate any backend connection interactively, why did I get a  "terminating connection due to administrator command” message? Is there any situation where this message is issued without the administrator being involved?
  • What could have caused the shutdown on the 21st of July? Again, I did not issue a shutdown request for that server, and the machine didn’t restart.

The server is running PostgreSQL 9.1.16.

Thank you,
Herouth

pgsql-general by date:

Previous
From: Amit Bondwal
Date:
Subject: Postgres SSL connection without client certificates.
Next
From: Chris Withers
Date:
Subject: Re: pgbench tps drop from 5000 to 37 going from localhost to a server 13ms away