Thread: BUG #15649: ERROR: terminating connection due to administrator command

The following bug has been logged on the website:

Bug reference:      15649
Logged by:          dheeraj ram
Email address:      dr00487751@techmahindra.com
PostgreSQL version: Unsupported/Unknown
Operating system:   Wind River Linux 8.0.0.26
Description:

Hi, 

I am using (PostgreSQL) Version- 9.2.4. 
I am observing below error logs continuously:

2019-02-18 07:46:28.831 GMT LOG:  database system was interrupted; last
known up at 2019-02-18 07:46:25 GMT
2019-02-18 07:46:28.832 GMT LOG:  creating missing WAL directory
"pg_xlog/archive_status"
cp: cannot stat '/disk/var/postgres/wal/00000092.history': No such file or
directory
cp: cannot stat '/disk/var/postgres/wal/00000091.history': No such file or
directory
2019-02-18 07:46:28.836 GMT LOG:  entering standby mode
2019-02-18 07:46:28.859 GMT LOG:  restored log file
"000000910000013A00000012" from archive
2019-02-18 07:46:28.864 GMT LOG:  redo starts at 13A/12000020
2019-02-18 07:46:28.866 GMT LOG:  consistent recovery state reached at
13A/120000E0
2019-02-18 07:46:28.867 GMT LOG:  database system is ready to accept read
only connections
cp: cannot stat '/disk/var/postgres/wal/000000910000013A00000013': No such
file or directory
cp: cannot stat '/disk/var/postgres/wal/00000092.history': No such file or
directory
2019-02-18 07:46:28.874 GMT LOG:  streaming replication successfully
connected to primary
2019-02-18 07:48:27.561 GMT LOG:  received promote request
2019-02-18 07:48:27.561 GMT FATAL:  terminating walreceiver process due to
administrator command
2019-02-18 07:48:27.685 GMT LOG:  restored log file
"000000910000013A00000014" from archive
cp: cannot stat '/disk/var/postgres/wal/000000910000013A00000015': No such
file or directory
2019-02-18 07:48:27.689 GMT LOG:  redo done at 13A/1404ABF8
2019-02-18 07:48:27.689 GMT LOG:  last completed transaction was at log time
2019-02-18 07:48:24.421979+00
2019-02-18 07:48:27.706 GMT LOG:  restored log file
"000000910000013A00000014" from archive
cp: cannot stat '/disk/var/postgres/wal/00000092.history': No such file or
directory
2019-02-18 07:48:27.711 GMT LOG:  selected new timeline ID: 146
cp: cannot stat '/disk/var/postgres/wal/00000091.history': No such file or
directory
2019-02-18 07:48:27.754 GMT LOG:  archive recovery complete
2019-02-18 07:48:27.859 GMT LOG:  autovacuum launcher started
2019-02-18 07:48:27.859 GMT LOG:  database system is ready to accept
connections
2019-02-18 07:53:21.296 GMT LOG:  received fast shutdown request
2019-02-18 07:53:21.296 GMT LOG:  aborting any active transactions
2019-02-18 07:53:21.296 GMT FATAL:  terminating connection due to
administrator command
2019-02-18 07:53:21.296 GMT FATAL:  terminating connection due to
administrator command
2019-02-18 07:53:21.296 GMT FATAL:  terminating connection due to
administrator command
2019-02-18 07:53:21.296 GMT FATAL:  terminating connection due to
administrator command
2019-02-18 07:53:21.296 GMT FATAL:  terminating connection due to
administrator command
2019-02-18 07:53:21.296 GMT FATAL:  terminating connection due to
administrator command
2019-02-18 07:53:21.297 GMT FATAL:  terminating connection due to
administrator command
2019-02-18 07:53:21.297 GMT FATAL:  terminating connection due to
administrator command
2019-02-18 07:53:21.297 GMT FATAL:  terminating connection due to
administrator command
2019-02-18 07:53:21.297 GMT FATAL:  terminating connection due to
administrator command
2019-02-18 07:53:21.297 GMT FATAL:  terminating connection due to
administrator command
2019-02-18 07:53:21.297 GMT FATAL:  terminating connection due to
administrator command
2019-02-18 07:53:21.297 GMT FATAL:  terminating connection due to
administrator command
2019-02-18 07:53:21.297 GMT FATAL:  terminating connection due to
administrator command
2019-02-18 07:53:21.297 GMT FATAL:  terminating connection due to
administrator command
2019-02-18 07:53:21.298 GMT FATAL:  terminating connection due to
administrator command
2019-02-18 07:53:21.297 GMT FATAL:  terminating connection due to
administrator command
2019-02-18 07:53:21.297 GMT FATAL:  terminating connection due to
administrator command
2019-02-18 07:53:21.297 GMT FATAL:  terminating connection due to
administrator command
2019-02-18 07:53:21.297 GMT FATAL:  terminating connection due to
administrator command
2019-02-18 07:53:21.297 GMT FATAL:  terminating connection due to
administrator command
2019-02-18 07:53:21.297 GMT FATAL:  terminating connection due to
administrator command
2019-02-18 07:53:21.297 GMT LOG:  autovacuum launcher shutting down
2019-02-18 07:53:21.297 GMT FATAL:  terminating connection due to
administrator command
2019-02-18 07:53:21.297 GMT FATAL:  terminating connection due to
administrator command
2019-02-18 07:53:21.297 GMT FATAL:  terminating connection due to
administrator command
2019-02-18 07:53:21.297 GMT FATAL:  terminating connection due to
administrator command
2019-02-18 07:53:21.297 GMT FATAL:  terminating connection due to
administrator command
2019-02-18 07:53:21.303 GMT LOG:  shutting down
2019-02-18 07:53:21.427 GMT LOG:  database system is shut down

Can you please help me to fix the issue.

Thanks And Regards
Dheeraj

Hello

> Can you please help me to fix the issue.

Where is issue?

> 2019-02-18 07:48:27.859 GMT LOG: database system is ready to accept
> connections
> 2019-02-18 07:53:21.296 GMT LOG: received fast shutdown request

Someone command shutdown database after about 5 min after promote.
This is not database issue. We received shutdown signal - we going to shutdown.

regards, Sergei