Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id B3A322E2F45 for ; Tue, 4 Dec 2007 11:06:10 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 54355-02 for ; Tue, 4 Dec 2007 11:05:07 -0400 (AST) Received: from kuber.nabble.com (kuber.nabble.com [216.139.236.158]) by postgresql.org (Postfix) with ESMTP id 88F392E0156 for ; Tue, 4 Dec 2007 11:05:07 -0400 (AST) Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1IzZKb-0005Pg-HJ for pgsql-admin@postgresql.org; Tue, 04 Dec 2007 07:05:05 -0800 Message-ID: <14152262.post@talk.nabble.com> Date: Tue, 4 Dec 2007 07:05:05 -0800 (PST) From: KADDBA To: pgsql-admin@postgresql.org Subject: WAL archiving hangs due to missing WAL segment MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: sqlora@gmail.com X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.03 tagged_above=0 required=5 tests=BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, WHOIS_MYPRIVREG=1.499 X-Spam-Level: X-Archive-Number: 200712/8 X-Sequence-Number: 27525 Hi, I recently had set up WAL archiving in a testing environment and all went well. As a test I let the disk fill up until archiving no longer was possible. Then a co-worker noticed this disk filling up and removed some WALL segments, that were not yet archived. Now the archiving proces hangs. Messages in logfile: 2007-12-04 15:20:50 MET LOG: archive command "cp "pg_xlog/00000001000000010000003A" /u002/postgresql/admin/mdbp/arch/"archive_wal_00000001000000010000003A"" failed: return code 256 2007-12-04 15:20:51 MET DEBUG: executing archive command "cp "pg_xlog/00000001000000010000003A" /u002/postgresql/admin/mdbp/arch/"archive_wal_00000001000000010000003A"" cp: cannot access pg_xlog/00000001000000010000003A: No such file or directory 2007-12-04 15:20:51 MET LOG: archive command "cp "pg_xlog/00000001000000010000003A" /u002/postgresql/admin/mdbp/arch/"archive_wal_00000001000000010000003A"" failed: return code 256 2007-12-04 15:20:51 MET WARNING: transaction log file "00000001000000010000003A" could not be archived: too many failures How can I resolve this issue? I only have WALL segments from 000000010000000100000080 so I am missing all segments from 00000001000000010000003A upto 000000010000000100000080. -- View this message in context: http://www.nabble.com/WAL-archiving-hangs-due-to-missing-WAL-segment-tf4943617.html#a14152262 Sent from the PostgreSQL - admin mailing list archive at Nabble.com.