On 06/09/2014 07:28 AM, Khangelani Gama wrote:
Please please help
Before anyone can help you will need to provide more information on what
your archiving, replication setup is. To begin:
1)Are you doing both archiving and streaming replication?
2) What are the settings in the configuration files for those operations?
3) What is the layout for archiving, in other words do the archived
files get copied remotely to a third site or some other arrangement?
4) What caused the trigger file to be set?
*From:*Khangelani Gama [mailto:kg...@argility.com
<mailto:kg...@argility.com>]
*Sent:* Monday, June 09, 2014 1:42 PM
*To:* pgsql-general@postgresql.org <mailto:pgsql-general@postgresql.org>
*Subject:* pg_standby replication problem
Please help me with this, my secondary server shows a replication
problem. It stopped at the file called *0000000500004BAF000000AF …*then
from here primary server kept on sending walfiles, until the walfiles
used up the disc space in the data directory. How do I fix this problem.
It’s postgres 9.1.2.
*_Postgres log file Postgres-2014-06-08_000000.log file _*_has the
following details :_
2014-06-08 00:15:54 SAST LOG: restored log file
*"0000000500004BAF000000AF" from*archive
Trigger file: /tmp/recovery.pgsql.trigger.5432
Waiting for WAL file: 0000000500004BAF000000B0
WAL file path: /pgsql2/walfiles/0000000500004BAF000000B0
Restoring to: pg_xlog/RECOVERYXLOG
Sleep interval: 2 seconds
Max wait interval: 0 forever
*Command for restore: cp "/pgsql2/walfiles/0000000500004BAF000000B0"
"pg_xlog/RECOVERYXLOG"*
Keep archive history: 0000000500004BAE000000F7 and later
WAL file not present yet. Checking for trigger file...
WAL file not present yet. Checking for trigger file...
WAL file not present yet. Checking for trigger file...
WAL file not present yet. Checking for trigger file...
WAL file not present yet. Checking for trigger file...
CONFIDENTIALITY NOTICE
The contents of and attachments to this e-mail are intended for the addressee
only, and may contain the confidential
information of Argility (Proprietary) Limited and/or its subsidiaries. Any
review, use or dissemination thereof by anyone
other than the intended addressee is prohibited.If you are not the intended
addressee please notify the writer immediately
and destroy the e-mail. Argility (Proprietary) Limited and its subsidiaries
distance themselves from and accept no liability
for unauthorised use of their e-mail facilities or e-mails sent other than
strictly for business purposes.
--
Adrian Klaver
adrian.kla...@aklaver.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
