Re: PostgreSQL 9.0.1 PITR can not copy WAL file

From: tuanhoanganh <hatuan05(at)gmail(dot)com>
To: Christian Ullrich <chris(at)chrullrich(dot)net>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: PostgreSQL 9.0.1 PITR can not copy WAL file
Date: 2011-01-19 17:23:13
Message-ID: AANLkTikSH6jqSEfQcpUcG54DE80n=hnTsyhj5mAH6ms_@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I have checked your solution.
- Target disk full : No
- PostgreSQL user does not have write privilege for the target directory :
No
- Target file exists already (then you have a bigger problem) : Last file in
D:/3SDATABACKUP/PITR/WAL is 00000001000000040000005D
- PostgreSQL user does not have full control privileges for the source
file (the copy command needs them) : i switch to user postgres an copy
00000001000000040000005E from source to d:\temp and create new text file on
D:/3SDATABACKUP/PITR/WAL it is ok. No access denied

On Wed, Jan 19, 2011 at 6:56 PM, Christian Ullrich <chris(at)chrullrich(dot)net>wrote:

> * tuanhoanganh wrote:
>
> My PITR work well from 01/01/2011 to 06/01/2011. At 06/01/2011
>> postgresql log have issue
>>
>
> 2011-01-06 08:27:54 ICT LOG: archive command failed with exit code 1
>> 2011-01-06 08:27:54 ICT DETAIL: The failed archive command was: copy
>> pg_xlog\00000001000000040000005E
>> D:/3SDATABACKUP/PITR/WAL/00000001000000040000005E
>>
> [... lots more ...]
>
> 2011-01-06 08:28:58 ICT WARNING: transaction log file
>> "00000001000000040000005E" could not be archived: too many failures
>>
>> And my pg_xlog can not copy to D:/3SDATABACKUP/PITR/WAL from 06/01/2011.
>> How to fix error ? Please help me
>>
>
> Some possible reasons:
>
> - Target disk full
>
> - PostgreSQL user does not have write privilege for the target directory
>
> - Target file exists already (then you have a bigger problem)
>
> - PostgreSQL user does not have full control privileges for the source
> file (the copy command needs them)
>
> If you can stop your server, do so, then try to copy the file yourself on
> the command line. If that fails as well, you will get a better error
> message. If the server must stay up, copy the file to somwhere else on D:
> (assuming you don't have a volume mounted somewhere in the path).
>
> If you can copy the file yourself, you have a permissions problem. Make
> sure the PostgreSQL service user has full control on both the source and
> target directories.
>
> --
> Christian
>
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Andreas Kretschmer 2011-01-19 17:43:43 possible error in documentation for 9.1
Previous Message Esmin Gracic 2011-01-19 17:08:49 get referential values