Re: pg_standby replication problem

From: Khangelani Gama <kgama(at)argility(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: pg_standby replication problem
Date: 2014-06-09 18:15:50
Message-ID: 6267849c04fc3de2d162701bf79a1188@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

This is the standby replication setting with archive_command sending the
WALs from master to standby.

-----Original Message-----
From: Khangelani Gama [mailto:kgama(at)argility(dot)com]
Sent: Monday, June 09, 2014 8:06 PM
To: pgsql-general(at)postgresql(dot)org
Subject: pg_standby replication problem

Hi All

I would like to re-post the problem we have. The secondary server ran out
the disc space due the replication problem (Connection Time out).Since there
was a Connection time out Problem in the primary server, how can I make disc
space in the secondary server for the replication to continue from where it
stopped. Do I remove walfiles from the secondary server?

Below it's the details of the log file from the primary server:

replication started: Sun Jun 8 00:05:26 SAST 2014 source:
pg_xlog/0000000500004BAF000000AF, dest: 0000000500004BAF000000AF replication
finished: Sun Jun 8 00:05:33 SAST 2014 replication started: Sun Jun 8
00:05:33 SAST 2014 source: pg_xlog/0000000500004BAF000000B0, dest:
0000000500004BAF000000B0
ssh: connect to host 10.58.101.10 port 22: Connection timed out^M
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: unexplained error (code 255) at io.c(600) [sender=3.0.6]
replication finished: Sun Jun 8 00:07:41 SAST 2014 replication started: Sun
Jun 8 00:07:41 SAST 2014 source: pg_xlog/0000000500004BAF000000B1, dest:
0000000500004BAF000000B1 replication finished: Sun Jun 8 00:07:53 SAST 2014
replication started: Sun Jun 8 00:07:53 SAST 2014 source:
pg_xlog/0000000500004BAF000000B2, dest: 0000000500004BAF000000B2 replication
finished: Sun Jun 8 00:07:57 SAST 2014 replication started: Sun Jun 8
00:07:58 SAST 2014 source: pg_xlog/0000000500004BAF000000B3, dest:
0000000500004BAF000000B3 replication finished: Sun Jun 8 00:08:06 SAST 2014
replication started: Sun Jun 8 00:08:06 SAST 2014 source:
pg_xlog/0000000500004BAF000000B4, dest: 0000000500004BAF000000B4 replication
finished: Sun Jun 8 00:08:11 SAST 2014 replication started: Sun Jun 8
00:08:11 SAST 2014 source: pg_xlog/0000000500004BAF000000B5, dest:
0000000500004BAF000000B5 replication finished: Sun Jun 8 00:08:16 SAST 2014
replication started: Sun Jun 8 00:08:16 SAST 2014 source:
pg_xlog/0000000500004BAF000000B6, dest: 0000000500004BAF000000B6 replication
finished: Sun Jun 8 00:08:22 SAST 2014

Disc space Breakdown:

4.0K ./backup
12K ./copy
4.9T ./data
204K ./test
16K ./lost+found
361G ./walfiles
5.3T .

Filesystem Size Used Avail Use% Mounted on
/dev/sda3 57G 15G 39G 28% /
/dev/mapper/vg0-pgsql2
5.4T 5.3T 0 100% /pgsql2
/dev/sda1 99M 12M 83M 13% /boot
tmpfs 30G 0 30G 0% /dev/shm

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.

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Alan Hodgson 2014-06-09 18:38:49 Re: pg_standby replication problem
Previous Message Khangelani Gama 2014-06-09 18:05:41 pg_standby replication problem