From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
---|---|
To: | manish singh <delhi(dot)manish(at)gmail(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #6037: error on restarting slave - cp: cannot stat `pg_xlog....`: no such file or ... |
Date: | 2011-05-25 05:35:17 |
Message-ID: | 4DDC9515.2000003@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On 24.05.2011 18:27, manish singh wrote:
> When ever i am restarting postgresql slave (Service postgresql restart -
> made a script) or even just stopping and starting a postgresql slave.. it
> displays a a message, although slave get's started and working fine...
>
> server starting
> cp: cannot stat
> `/usr/local/pgsql/data/pg_xlogarch/000000010000000300000026': No such file
> or directory
> cp: cannot stat
> `/usr/local/postgres/data/pg_xlogarch/000000010000000300000026': No such
> file or directory
The standby server periodically checks if new WAL has arrived by
executing the restore_command. Your restore_command uses 'cp', which
prints out that message if the target file can't be found.
In other words, your system seems to be working correctly, and those
messages are harmless. You could silence it by replacing plain 'cp' with
a shell script that checks if the file exists first and calls 'cp' only
if it does.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Pascal Borschneck | 2011-05-25 08:06:04 | Re: BUG #5984: Got FailedAssertion("!(opaque->btpo_prev == target)", File: "nbtpage.c", Line: 1166) |
Previous Message | nikolairoman | 2011-05-25 04:54:40 | Re: BUG #5807: psql fails to launch with "Cannot read termcap database; using dumb terminal settings. Aborted" |