From: | Rick Dicaire <kritek(at)gmail(dot)com> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: WAL recovery failure |
Date: | 2012-09-26 11:35:13 |
Message-ID: | CA+Cc--ePJ8wHox3mjV-g07N03otf1BXLZHE3LfFVMJdWD08yjg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Wed, Sep 26, 2012 at 5:21 AM, Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> wrote:
> But according to what you wrote before you start the server
> with -D /staging/9.1/main.
> That means that /staging/9.1/main/pg_xlog contains the active
> WAL files, right?
>
> So the restore_command 'cp /staging/9.1/main/pg_xlog/%f "%p"'
> would just try to cp the files onto themselves, right?
>
> The WAL archive directory must be different from the
> active WAL directory. Check if that's your problem!
/staging/9.1/main/pg_xlog/ was a symlink to /staging/9.1/pg_xlog/,
removed the link, created
the directory, restarted postgres:
2012-09-26 06:29:20.094 CDT,,,13904,,5062e710.3650,1,,2012-09-26
06:29:20 CDT,,0,LOG,00000,"database system was interrupted while in
recovery at log time 2012-09-25 09:33:28 CDT",,"If this has occurred
more than once some data might be corrupted and you might need to
choose an earlier recovery target.",,,,,,,""
2012-09-26 06:29:20.094 CDT,,,13904,,5062e710.3650,2,,2012-09-26
06:29:20 CDT,,0,LOG,00000,"creating missing WAL directory
""pg_xlog/archive_status""",,,,,,,,,""
2012-09-26 06:29:20.117 CDT,,,13904,,5062e710.3650,3,,2012-09-26
06:29:20 CDT,,0,LOG,00000,"starting archive recovery",,,,,,,,,""
2012-09-26 06:29:20.361 CDT,,,13904,,5062e710.3650,4,,2012-09-26
06:29:20 CDT,,0,LOG,00000,"restored log file
""000000010000074D000000EE"" from archive",,,,,,,,,""
2012-09-26 06:29:20.498 CDT,,,13904,,5062e710.3650,5,,2012-09-26
06:29:20 CDT,,0,LOG,00000,"restored log file
""000000010000074D000000E2"" from archive",,,,,,,,,""
2012-09-26 06:29:20.498 CDT,,,13904,,5062e710.3650,6,,2012-09-26
06:29:20 CDT,,0,PANIC,XX000,"unexpected pageaddr 74D/7C000000 in log
file 1869, segment 226, offset 0",,,,,,,,,""
2012-09-26 06:29:20.499 CDT,,,13902,,5062e70f.364e,1,,2012-09-26
06:29:19 CDT,,0,LOG,00000,"startup process (PID 13904) was terminated
by signal 6: Aborted",,,,,,,,,""
2012-09-26 06:29:20.499 CDT,,,13902,,5062e70f.364e,2,,2012-09-26
06:29:19 CDT,,0,LOG,00000,"terminating any other active server
processes",,,,,,,,,""
Two WAL files are read in, choking on the third. Is it a corrupt WAL file?
From | Date | Subject | |
---|---|---|---|
Next Message | Volkmar Herbst | 2012-09-26 18:07:19 | Debian Squeeze - no xml support for Pg 9.2 |
Previous Message | Albe Laurenz | 2012-09-26 09:21:08 | Re: WAL recovery failure |