pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ahmed, Nawaz <Nawaz@fast.au.fujitsu.com>
To: Saeed Ahmed (DB) <saeed.ahmed1@telenor.com.pk>
To: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Cc: Database Services <db.is@telenor.com.pk>
Subject: Re: pg_basebackup: could not get write-ahead log end position from server: ERROR
Date: Fri, 8 Jun 2018 21:41:29 +0000
Message-ID: <BAAE097528E6CB4FB2BE65AEFA6EEE04939FC609@SYD1217> (raw)
In-Reply-To: <C35F307BE15BEA4585014E7B3753CC96014DCAF1A2F7@ISB-EXMB-CLUS.telenor.com.pk>
References: <C35F307BE15BEA4585014E7B3753CC96014DCAF1A2F7@ISB-EXMB-CLUS.telenor.com.pk>

<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style>
<!--
@font-face
	{font-family:"Cambria Math"}
@font-face
	{font-family:Calibri}
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif"}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline}
span.EmailStyle17
	{font-family:"Calibri","sans-serif";
	color:windowtext}
.MsoChpDefault
	{font-family:"Calibri","sans-serif"}
@page WordSection1
	{margin:1.0in 1.0in 1.0in 1.0in}
div.WordSection1
	{}
-->
</style>
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div style="font-family:Calibri,HelveticaNeue,sans-serif">
<div dir="auto">
<div dir="auto">
<div dir="auto">Hi,</div>
<div dir="auto"><br>
</div>
<div dir="auto">1) have you configured the archive_command to a script that archives the online WAL to the archive destination and deletes the file?</div>
<div dir="auto"><br>
</div>
<div dir="auto">2) As&nbsp;far as I know the cleanup of archive destination has to done manually.&nbsp;</div>
<div dir="auto"><br>
</div>
<div dir="auto">Regards,</div>
<div dir="auto">Nawaz<br>
<div dir="auto"><br>
</div>
</div>
</div>
</div>
</div>
<hr>
<div dir="auto" style="font-family:Calibri,HelveticaNeue,sans-serif"><br>
<b>From:</b> Saeed Ahmed (DB) &lt;saeed.ahmed1@telenor.com.pk&gt;<br>
<b>Date:</b> 9 June 2018 at 4:27:25 am AEST<br>
<b>To:</b> pgsql-admin@postgresql.org &lt;pgsql-admin@postgresql.org&gt;<br>
<b>Cc:</b> Database Services &lt;db.is@telenor.com.pk&gt;<br>
<b>Subject:</b> pg_basebackup: could not get write-ahead log end position from server: ERROR<br>
</div>
<br>
<div>
<div class="WordSection1">
<p class="MsoNormal">Dear Team,</p>
<p class="MsoNormal">&nbsp;</p>
<p class="MsoNormal">1)Whilst taking full backup via pg_basebackup I have facing below error. Backup is schedule via cronjob.</p>
<p class="MsoNormal">&nbsp;</p>
<p class="MsoNormal"><span style="background:yellow">================================================================================</span></p>
<p class="MsoNormal"><span style="background:yellow">****** Full Backup of posgresql database started Fri Jun 8 20:40:36 PKT 2018.</span></p>
<p class="MsoNormal"><span style="background:yellow">080618204036</span></p>
<p class="MsoNormal"><span style="background:yellow"></span></p>
<p class="MsoNormal"><span style="background:yellow">pg_basebackup: initiating base backup, waiting for checkpoint to complete</span></p>
<p class="MsoNormal"><span style="background:yellow">pg_basebackup: checkpoint completed</span></p>
<p class="MsoNormal"><span style="background:yellow">pg_basebackup: write-ahead log start point: 43/400252F8 on timeline 1</span></p>
<p class="MsoNormal"><span style="background:yellow">17624153/17624153 kB (100%), 2/2 tablespaces&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></p>
<p class="MsoNormal"><span style="background:yellow">pg_basebackup: could not get write-ahead log end position from server: ERROR:&nbsp; requested WAL segment 000000010000004300000040 has already been removed</span></p>
<p class="MsoNormal"><span style="background:yellow">pg_basebackup: removing data directory &quot;/db01/pgdata/hot_backup/080618204036&quot;</span></p>
<p class="MsoNormal">&nbsp;</p>
<p class="MsoNormal">&nbsp;</p>
<p class="MsoNormal">&nbsp;</p>
<p class="MsoNormal">&nbsp;</p>
<p class="MsoNormal">2)Also after complete backup I have to manually delete the wal archive files using pg_archivecleanup. Is there any way to automatically delete after full backup is complete and wal archive are no longer required.</p>
<p class="MsoNormal">&nbsp;</p>
<p class="MsoNormal">pg_archivecleanup -d /db01/wal_archive 00000001000000390000000A</p>
<p class="MsoNormal">&nbsp;</p>
<p class="MsoNormal">&nbsp;</p>
<p class="MsoNormal">Kindly let me know how to rectify. </p>
<p class="MsoNormal">&nbsp;</p>
<p class="MsoNormal">pg_basebackup -z -X fetch --progress -v --format=t -D /db01/pgdata/hot_backup/$DD --no-password</p>
<p class="MsoNormal">&nbsp;</p>
<p class="MsoNormal"><b><u><span style="text-decoration:none">&nbsp;</span></u></b></p>
<p class="MsoNormal"><b><u><span style="text-decoration:none">&nbsp;</span></u></b></p>
<p class="MsoNormal"><b><u>Current Version:</u></b></p>
<p class="MsoNormal">&nbsp;</p>
<p class="MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; version&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</p>
<p class="MsoNormal">---------------------------------------------------------------------------------------------------------</p>
<p class="MsoNormal">PostgreSQL 10.1 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-18), 64-bit</p>
<p class="MsoNormal">&nbsp;</p>
<p class="MsoNormal">&nbsp;</p>
<p class="MsoNormal"><b><u>LINUX : .10.0-327.el7.x86_64</u></b></p>
<p class="MsoNormal">&nbsp;</p>
<p class="MsoNormal">&nbsp;</p>
<p class="MsoNormal">Regards,</p>
<p class="MsoNormal">&nbsp;</p>
<p class="MsoNormal">Saeed Ahmed</p>
<p class="MsoNormal">&nbsp;</p>
</div>
</div>
<h3>Disclaimer</h3>
<p>The information in this e-mail is confidential and may contain content that is subject to copyright and/or is commercial-in-confidence and is intended only for the use of the above named addressee. If you are not the intended recipient, you are hereby notified
 that dissemination, copying or use of the information is strictly prohibited. If you have received this e-mail in error, please telephone Fujitsu Australia Software Technology Pty Ltd on &#43; 61 2 9452 9000 or by reply e-mail to the sender and delete the document
 and all copies thereof.</p>
<br>
<p>Whereas Fujitsu Australia Software Technology Pty Ltd would not knowingly transmit a virus within an email communication, it is the receiver’s responsibility to scan all communication and any files attached for computer viruses and other defects. Fujitsu
 Australia Software Technology Pty Ltd does not accept liability for any loss or damage (whether direct, indirect, consequential or economic) however caused, and whether by negligence or otherwise, which may result directly or indirectly from this communication
 or any files attached.</p>
<br>
<p>If you do not wish to receive commercial and/or marketing email messages from Fujitsu Australia Software Technology Pty Ltd, please email unsubscribe@fast.au.fujitsu.com</p>
<p></p>
</body>
</html>


view thread (7+ messages)  latest in thread

Message-ID: <BAAE097528E6CB4FB2BE65AEFA6EEE04939FC609@SYD1217>
Permalink:  ../BAAE097528E6CB4FB2BE65AEFA6EEE04939FC609@SYD1217/
Also on:    postgresql.org/message-id/BAAE097528E6CB4FB2BE65AEFA6EEE04939FC609@SYD1217

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: Nawaz@fast.au.fujitsu.com, saeed.ahmed1@telenor.com.pk, db.is@telenor.com.pk
  Subject: Re: pg_basebackup: could not get write-ahead log end position from server: ERROR
  In-Reply-To: <BAAE097528E6CB4FB2BE65AEFA6EEE04939FC609@SYD1217>
  References: <C35F307BE15BEA4585014E7B3753CC96014DCAF1A2F7@ISB-EXMB-CLUS.telenor.com.pk> <BAAE097528E6CB4FB2BE65AEFA6EEE04939FC609@SYD1217>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox