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

Поиск
Список
Период
Сортировка
Искать
От
Fujii Masao
Тема
Re: Re: postmaster.pid still exists after pacemaker stopped postgresql - how to remove
Дата
Msg-id
CAHGQGwF1kEpVn+FFcF+AZhvV7BmMVOKiYcanhDMr0JgMfyp7PA@mail.gmail.com
Ответ на
Список
Дерево обсуждения
postmaster.pid still exists after pacemaker stopped postgresql - how to remove Mistina Michal <Michal.Mistina@virte.sk>
Re: postmaster.pid still exists after pacemaker stopped postgresql - how to remove Mistina Michal <Michal.Mistina@virte.sk>
Re: Re: postmaster.pid still exists after pacemaker stopped postgresql - how to remove Fujii Masao <masao.fujii@gmail.com>
Re: Re: postmaster.pid still exists after pacemaker stopped postgresql - how to remove Mistina Michal <Michal.Mistina@virte.sk>
Re: Re: postmaster.pid still exists after pacemaker stopped postgresql - how to remove Fujii Masao <masao.fujii@gmail.com>
On Mon, Aug 26, 2013 at 9:53 PM, Mistina Michal  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

В списке pgsql-general по дате отправления
От: Mistina Michal
Дата:
От: Samrat Revagade
Дата:
FAQ