After the backup library is built, enter the backup library with the error psql: FATAL: the database system is starting up
Reason: The backup database configuration file does not have hot_standby = on
master
-bash-4.1$ ps aux |grep post
postgres897070.00.0 43196188 2872 ?Ss00:150:27 postgres: wal sender process rep 10.40.55.69(26717) streaming 9F6/E1DCC0D8
slave
[root@db-hx-55-69 bohai]# ps aux|grep post
postgres 140200.3 29.0 43132932 19181752 ?Ss00:154:26 postgres: startup processrecovering 00000001000009F6000000E7
postgres 140550.10.0 43137588 2204 ?Ss00:151:23 postgres: wal receiver processstreaming 9F6/E7F52960
[postgres@db-hx-55-69 ~]$ psql
psql: FATAL:the database system is starting up
[postgres@db-hx-55-69 pg_log]$ tail -fpostgresql-Sat.log
< 2018-03-10 22:59:51.188 CST >FATAL:the database system is starting up
[postgres@db-hx-55-69 data]$ vipostgresql.conf
hot_standby = on
[postgres@db-hx-55-69 data]$ pg_ctl restart-D /opt/tuniu/postgresql/data
< 2018-03-10 23:14:30.391 CST >LOG:received fast shutdown request
< 2018-03-10 23:14:30.391 CST >FATAL:terminating walreceiver process due to administrator command
< 2018-03-10 23:14:30.771 CST >LOG:shutting down
< 2018-03-10 23:14:30.772 CST >LOG:database system is shut down
< 2018-03-10 23:14:34.263 CST >LOG:database system was shut down in recovery at 2018-03-10 23:14:30 CST
< 2018-03-10 23:14:34.263 CST >LOG:entering standby mode
< 2018-03-10 23:14:34.264 CST >LOG:redo starts at 9F6/C4395020
< 2018-03-10 23:14:37.272 CST >FATAL:the database system is starting up
< 2018-03-10 23:14:39.167 CST >FATAL:the database system is starting up
< 2018-03-10 23:14:44.326 CST >LOG:consistent recovery state reached at 9F6/FF6393F0
< 2018-03-10 23:14:44.326 CST >LOG:invalid resource manager ID 255 at 9F6/FF6393F0
< 2018-03-10 23:14:44.327 CST >LOG:database system is ready to accept read only connections
< 2018-03-10 23:14:44.330 CST >LOG:started streaming WAL from primary at 9F6/FF000000 on timeline 1
[postgres@db-hx-55-69 data]$ psql
psql (9.5.4)
Type “help” for help.
postgres=# \l
Similar Posts:
- [How to Solve] psql: FATAL: role “postgres” does not exist
- [Solved] ORA-00245: control file backup failed; target is likely on a local file system
- How to Solve Error: FATAL: role “root” does not exist
- [Solved] createdb: could not connect to database postgres: FATAL: Peer authentication failed for user “postgres”
- [Solved] Psql reports “invalid command \N” error when restoring data
- [Solved] zabbix Monitor postgres Error: “sh:psql command not found”
- [Solved] Postgres Error: template1 is being accessed by other users
- PostgreSQL Connect Error: FATAL: no pg_hba.conf entry for host
- PING[ARC2]: Heartbeat failed to connect to standby ‘gqtzdb_dg’. Error is 16047
- Postgres invalid command data recovery processing