Re: Hot standby stops after a few days of inactivity (i.e. no new WAL)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Marc Schablewski <ms(at)clickware(dot)de>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Hot standby stops after a few days of inactivity (i.e. no new WAL)
Date: 2008-11-04 13:44:53
Message-ID: 16504.1225806293@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Marc Schablewski <ms(at)clickware(dot)de> writes:
> ... When looking for a reason why the WAL weren't shipped, we found
> the following error message:

> 2008-10-31 17:07:52 CET 9162LOG: received smart shutdown request
> 2008-10-31 17:07:52 CET 9178FATAL: could not restore file
> "000000010000008600000018" from archive: return code 15

Something sent SIGTERM to both your postmaster (hence the "smart
shutdown" message) and the recovery_command script (causing it to
exit with code 15, which is probably SIGTERM though you might want
to check kill -l to be sure). You need to find out what's doing that
and make it stop.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Marc Schablewski 2008-11-04 14:05:47 Re: Hot standby stops after a few days of inactivity (i.e. no new WAL)
Previous Message Merlin Moncure 2008-11-04 13:42:19 Re: Hot standby stops after a few days of inactivity (i.e. no new WAL)