Good Afternoon,
I am having loads of trouble with pacemaker/corosync/postgres. Defining
the symptoms is rather difficult. The primary being that postgres
starts as slave on both nodes. I have tested the pgsqlRA
start/stop/status/monitor and they work from the command line after I
setup t
sorry for my mistyping,
it's res.vBKN6
--teenigma
On Thu, Dec 4, 2014 at 4:23 PM, Andrei Borzenkov wrote:
> On Thu, Dec 4, 2014 at 9:52 AM, Teerapatr Kittiratanachai
> wrote:
>> Dear Andrei,
>>
>> Since the failed over is uncompleted so all the resource isn't failed
>> over to another node.
>>
On Thu, Dec 4, 2014 at 9:52 AM, Teerapatr Kittiratanachai
wrote:
> Dear Andrei,
>
> Since the failed over is uncompleted so all the resource isn't failed
> over to another node.
>
> I think this case happened because of the res.vBKN is go into unmanaged state.
>
There is no resource res.vBKN in y
Andrew Beekhof writes:
> What version of pacemaker is this?
> Some very old versions wanted the agent to be installed on all nodes.
It's 1.1.10+git20130802-1ubuntu2.1 on Trusty Tahr.
Regards.
--
Daniel Dehennin
Récupérer ma clef GPG: gpg --recv-keys 0xCC1E9E5B7A6FE2DF
Fingerprint: 3E69 014E 5C
