On Sun, Jun 22, 2008 at 3:11 AM, Stuart Luppescu <slu@ccsr.uchicago.edu> wrote:
> On 木, 2008-06-19 at 11:57 +0200, David wrote:
>> > pg_restore: [tar archiver] could not open TOC file for input: No
>> such
>> > file or directory
>>
>> It sounds like the tar file is no longer being created.
>>
>> Try manually running the commands, and verify that the dump, restore,
>> and rsync still work correctly at each step.
>
> It looks like it's working:
> file postgresql_database-db-backup
> postgresql_database-db-backup: tar archive
>
> tar tfv postgresql_database-db-backup
> -rw------- 2048/1024 62764 2008-06-20 03:00 toc.dat
> -rw------- 2048/1024 4590795 2008-06-20 03:00 1765.dat
> -rw------- 2048/1024 391040 2008-06-20 03:00 1771.dat
> -rw------- 2048/1024 1262932 2008-06-20 03:00 1770.dat
> -rw------- 2048/1024 4472 2008-06-20 03:00 1769.dat
> -rw------- 2048/1024 5 2008-06-20 03:00 1796.dat
> -rw------- 2048/1024 5 2008-06-20 03:00 1787.dat
> -rw------- 2048/1024 5456 2008-06-20 03:00 1762.dat
> -rw------- 2048/1024 435981 2008-06-20 03:00 1767.dat
> -rw------- 2048/1024 54185 2008-06-20 03:00 1774.dat
> -rw------- 2048/1024 109 2008-06-20 03:00 1764.dat
>
> etc.
>
> This only weird thing is the ownership is weird. Where did that
> 2048/1024 come from?
>
I'm not sure about that. But if your manual process is working, then
your script should work fine too. Try adding more logging & error
checking/capturing to your mirroring scripts to check where the
problem is occurring. Debug lines like 'echo "TESTING ($LINENO) -
<Description>"' to trace which parts of the scripts get run when can
also help.
David.
