Thanks,
That was it!
On 10.03.2016 17:08, Ken Gaillot wrote:
On 03/10/2016 04:42 AM, Klechomir wrote:
Hi List
I'm testing stonith now (pacemaker 1.1.8), and noticed that it properly kills
a node with stopped pacemaker, but ignores resource stop errors.
I'm pretty sure that the same version
Hi,
Does corosync provide mechanism to secure the communication path between
nodes of a cluster?
I would like all the data that gets exchanged between all nodes to be
encrypted.
A quick google threw up this link:
https://github.com/corosync/corosync/blob/master/SECURITY
Can I make use of it
On 03/10/2016 09:38 AM, Bernie Jones wrote:
> Hi Ken,
> Thanks for your response, I've now corrected the constraint order but the
> behaviour is still the same, the IP does not fail over (after the first
> time) unless I issue a pcs resource cleanup command on dirsrv-daemon.
>
> Also, I'm not
Dear List,
After the creation and testing of a simple 2 node active-passive
drbd+postfix cluster nearly everything works flawlessly (standby, failure
of a filesystem resource + failover, splitbrain + manual recovery) however
when delibarately killing the postfix instance, after reaching the
Hi Ken,
Thanks for your response, I've now corrected the constraint order but the
behaviour is still the same, the IP does not fail over (after the first
time) unless I issue a pcs resource cleanup command on dirsrv-daemon.
Also, I'm not sure why you advise against using is-managed=false in
On 03/10/2016 04:42 AM, Klechomir wrote:
> Hi List
>
> I'm testing stonith now (pacemaker 1.1.8), and noticed that it properly kills
> a node with stopped pacemaker, but ignores resource stop errors.
>
> I'm pretty sure that the same version worked properly with stonith before.
> Maybe I'm
On 03/10/2016 08:48 AM, Bernie Jones wrote:
> A bit more info..
>
>
>
> If, after I restart the failed dirsrv instance, I then perform a "pcs
> resource cleanup dirsrv-daemon" to clear the FAIL messages then the failover
> will work OK.
>
> So it's as if the cleanup is changing the status in
A bit more info..
If, after I restart the failed dirsrv instance, I then perform a "pcs
resource cleanup dirsrv-daemon" to clear the FAIL messages then the failover
will work OK.
So it's as if the cleanup is changing the status in some way..
From: Bernie Jones
Hi all, could you advise please?
I'm trying to configure a floating IP with an active/active deployment of
389 directory server. I don't want pacemaker to manage LDAP but just to
monitor and switch the IP as required to provide resilience. I've seen some
other similar threads and based my
