|
Classification: External Hi All I am unable to start the new standby after updating the archive_command (with new ip) [postgres@ log]$ cat postgresql-2020-04-28_124617.log 2020-04-28 12:46:17 GMT LOG: database system was shut down in recovery at 2020-04-28 12:36:41 GMT 2020-04-28 12:46:17 GMT LOG: restored log file "00000002.history" from archive cp: cannot stat ‘/data/ARCHIVELOG/00000003.history’: No such file or directory 2020-04-28 12:46:17 GMT LOG: entering standby mode 2020-04-28 12:46:17 GMT LOG: restored log file "00000002.history" from archive 2020-04-28 12:46:17 GMT LOG: restored log file "000000020000001D000000DA" from archive 2020-04-28 12:46:17 GMT LOG: invalid xl_info in primary checkpoint record 2020-04-28 12:46:17 GMT PANIC: could not locate a valid checkpoint record 2020-04-28 12:47:47 GMT [unknown] [unknown]LOG: connection received: host=[local] 2020-04-28 12:47:47 GMT postgres postgresFATAL: the database system is starting up 2020-04-28 12:47:49 GMT [unknown] [unknown]LOG: connection received: host=[local] 2020-04-28 12:47:49 GMT postgres postgresFATAL: the database system is starting up 2020-04-28 12:48:15 GMT LOG: startup process (PID 24654) was terminated by signal 6: Aborted 2020-04-28 12:48:15 GMT LOG: aborting startup due to startup process failure 2020-04-28 12:48:15 GMT LOG: database system is shut down [postgres@de284194 log]$ psql psql.bin: could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket "/tmp/.s.PGSQL.5432"? [postgres@ log]$ From: Ashok kumar Mani Classification: External Dear All, I have converted primary into slave today. After converting I made new slave as well but when I create new database in new database
Which is not replicating in new standby . Could you please confirm do I need update archive command and archive mode as well because in new standby it is still referring old ip address. Can any one help on this? Regards, Ashok |
