Skip site navigation (1) Skip section navigation (2)

Re: Re: postmaster.pid still exists after pacemaker stopped postgresql - how to remove

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Mistina Michal <Michal(dot)Mistina(at)virte(dot)sk>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Re: postmaster.pid still exists after pacemaker stopped postgresql - how to remove
Date: 2013-08-26 13:24:32
Message-ID: CAHGQGwF1kEpVn+FFcF+AZhvV7BmMVOKiYcanhDMr0JgMfyp7PA@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-general
On Mon, Aug 26, 2013 at 9:53 PM, Mistina Michal <Michal(dot)Mistina(at)virte(dot)sk> wrote:
> Hi there.
>
> I didn’t find out why this issue happened. Only backup and format of the
> filesystem where corrupted postmaster.pid file existed helped to get rid of
> it. Hopefully the file won’t appear in the future.

I have encountered similar problem when I broke the filesystem by
a double mount. You may have gotten the same problem.

>  Master/Slave Set: ms_drbd_pg [drbd_pg]
>
>      Masters: [ tstcaps01 ]
>
>      Slaves: [ tstcaps02 ]

Why do you use DRBD with streaming replicatin? If you locates
the database cluster on DRBD, it's better to check the status of
DRBD filesystem.

Regards,

-- 
Fujii Masao


In response to

Responses

pgsql-general by date

Next:From: Samrat RevagadeDate: 2013-08-26 13:32:58
Subject: Re: effective_io_concurrency with an SSD SAN?
Previous:From: Mistina MichalDate: 2013-08-26 12:53:23
Subject: Re: postmaster.pid still exists after pacemaker stopped postgresql - how to remove

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group