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

Ah, ok. I somehow missed the first line of the message an the rest of it
left the impression that "something" must be wrong with replication.

I guess one of my colleagues might have shut down the database by
accident and forgot to tell me.

Anyway, thanks for your reply.

Marc

Alvaro Herrera wrote:
> Marc Schablewski wrote:
>
>> Hi,
>>
>> we are running a PostgreSQL 8.3.3 on a Linux box (SuSE 10.3, 2.6.22
>> kernel) as a hot standby. After some maintenances work the WAL files
>> couldn't be shipped to that system (which had nothing to do with
>> postgres, as we found out later). The problem was not noticed for about
>> a week. 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
>>
>
> This server was stopped intentionally by someone or something, external
> to Postgres itself. "Smart shutdown" means the postmaster got SIGTERM.
>
>