Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

I got error on postgres

45 views
Skip to first unread message

sout saret

unread,
Jan 19, 2014, 11:55:40 PM1/19/14
to
cp: cannot stat `/home/postlog/archive/0000000100000010000000A8': No such file or directory
cp: cannot stat `/home/postlog/archive/0000000100000010000000A8': No such file or directory
cp: cannot stat `/home/postlog/archive/00000002.history': No such file or directory
LOG: streaming replication successfully connected to primary
FATAL: could not receive data from WAL stream: FATAL: requested WAL segment 0000000100000010000000A8 has already been removed

cp: cannot stat `/home/postlog/archive/0000000100000010000000A8': No such file or directory
cp: cannot stat `/home/postlog/archive/0000000100000010000000A8': No such file or directory
cp: cannot stat `/home/postlog/archive/00000002.history': No such file or directory
LOG: streaming replication successfully connected to primary
FATAL: could not receive data from WAL stream: FATAL: requested WAL segment 0000000100000010000000A8 has already been removed

cp: cannot stat `/home/postlog/archive/0000000100000010000000A8': No such file or directory
cp: cannot stat `/home/postlog/archive/0000000100000010000000A8': No such file or directory
cp: cannot stat `/home/postlog/archive/00000002.history': No such file or directory
LOG: streaming replication successfully connected to primary
FATAL: could not receive data from WAL stream: FATAL: requested WAL segment 0000000100000010000000A8 has already been removed

cp: cannot stat `/home/postlog/archive/0000000100000010000000A8': No such file or directory
cp: cannot stat `/home/postlog/archive/0000000100000010000000A8': No such file or directory
cp: cannot stat `/home/postlog/archive/00000002.history': No such file or directory
LOG: streaming replication successfully connected to primary
FATAL: could not receive data from WAL stream: FATAL: requested WAL segment 0000000100000010000000A8 has already been removed

cp: cannot stat `/home/postlog/archive/0000000100000010000000A8': No such file or directory
cp: cannot stat `/home/postlog/archive/0000000100000010000000A8': No such file or directory
cp: cannot stat `/home/postlog/archive/00000002.history': No such file or directory
LOG: streaming replication successfully connected to primary
FATAL: could not receive data from WAL stream: FATAL: requested WAL segment 0000000100000010000000A8 has already been removed

cp: cannot stat `/home/postlog/archive/0000000100000010000000A8': No such file or directory
cp: cannot stat `/home/postlog/archive/0000000100000010000000A8': No such file or directory
cp: cannot stat `/home/postlog/archive/00000002.history': No such file or directory
LOG: streaming replication successfully connected to primary
FATAL: could not receive data from WAL stream: FATAL: requested WAL segment 0000000100000010000000A8 has already been removed

evi...@ezakus.com

unread,
Sep 1, 2014, 3:46:06 AM9/1/14
to
Seem's that your primary server is not able to copy wals in your /home/postlog/archive/ path.
Try to empty it and verify if it's filled.

Modify you're primary and secondary postgresql.conf file increasing the wal_keep_segments value to have time to make you're pg_basebackup.

It seems that when you finish you're pg_basebackup, the wal's are out of date and the secondary can not resynchronize.

#------------------------------------------------------------------------------
# REPLICATION
#------------------------------------------------------------------------------

# - Sending Server(s) -

# Set these on the master and on any standby that will send replication data.

max_wal_senders = 5 # max number of walsender processes
# (change requires restart)
wal_keep_segments = 64 # in logfile segments, 16MB each; 0 disables

Fernando Moreira

unread,
Nov 12, 2014, 8:28:18 AM11/12/14
to
I suggest you perform the rsync again, this error has happened to me and to accomplish RSYNC returned to work again.

Fernando Moreira

unread,
Nov 12, 2014, 8:28:39 AM11/12/14
to
Em segunda-feira, 20 de janeiro de 2014 02h55min40s UTC-2, sout saret escreveu:
0 new messages