<div dir="ltr"><div class="gmail_extra">Hello,</div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Feb 20, 2016 at 1:50 PM, Bernie Jones <span dir="ltr"><<a href="mailto:bernie@securityconsulting.ltd.uk" target="_blank">bernie@securityconsulting.ltd.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div lang="EN-GB" link="blue" vlink="purple">
<div>
<p class="MsoNormal">Hi all,<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">I’m new to this list and fairly new to pacemaker and
have just spent a couple of days trying unsuccessfully to solve a configuration
challenge.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">I have seen a relevant post on this list from around four
years ago but it doesn’t seem to have helped – here’s what I
want to do.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">I have 389 directory server running on two Centos servers.
It’s configured for MMR and my plan is to use one replica as the primary
LDAP server, failing over to the secondary only if there’s a problem.
This is to avoid frequent writes to both replicas causing high levels of
bi-directional replication traffic. SO I’m looking for failover rather
than load balancing.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">This works fine using a traditional load balancer configured
appropriately for weighting and stickiness with a simple heartbeat to the LDAP
server but I’d like to see if I can use Pacemaker instead using a
floating IP across the two LDAP servers and appropriate monitoring to control
switch over.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">I’ve configured a floating IP resource OK but am
struggling with the question of how to monitor the 389 server.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">If I create a resource using lsb:dirsrv then I find that the
server is started up on the primary cluster node but not on the second –
which is understandable but not what I need.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">What I would like to be able to achieve is to have the 389
instances monitored but not controlled such that the floating IP address switches
across when required but without stopping or starting the 389 instances.<u></u><u></u><u></u> <u></u></p></div></div></blockquote><div><br></div><div>I'd say you want to create a clone resource from your 389 resource, so there is one instance running on each node.</div><div><br></div><div>Regards,</div><div>Andreas</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div lang="EN-GB" link="blue" vlink="purple"><div>
<p class="MsoNormal">Right now I’m not sure whether I should be using the
dirsrv resource or looking for some kind of simple ‘LDAP ping’
resource that could be used.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Any advice would be hugely appreciated.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Kind regards,<u></u><u></u></p>
<p class="MsoNormal">Bernie<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><img width="204" height="101" src="cid:image001.gif@01D16BDC.09F826D0" alt="scl_header14"><u></u><u></u></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125)">Tel: 01308
488392<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125)">Mob: 07770
587118<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125)">Profile: <a href="https://www.linkedin.com/in/berniejones" target="_blank">https://www.linkedin.com/in/berniejones</a></span><i><span style="color:rgb(31,73,125)"><u></u><u></u></span></i></p>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<br><br>
<hr style="border:none;color:rgb(144,144,144);min-height:1px;width:99%;background-color:rgb(176,176,176)">
<table style="border-collapse:collapse;border:none">
<tbody><tr>
<td style="border:none;padding:0px 15px 0px 8px">
<a href="https://www.avast.com/antivirus" target="_blank">
<img border="0" src="http://static.avast.com/emails/avast-mail-stamp.png" alt="Avast logo">
</a>
</td>
<td>
<p style="color:rgb(61,77,90);font-family:Calibri,Verdana,Arial,Helvetica;font-size:12pt">
This email has been checked for viruses by Avast antivirus software.
<br><a href="https://www.avast.com/antivirus" target="_blank">www.avast.com</a>
</p>
</td>
</tr>
</tbody></table>
<br>
<br><br>
<hr style="border:none;color:rgb(144,144,144);min-height:1px;width:99%;background-color:rgb(176,176,176)">
<table style="border-collapse:collapse;border:none">
<tbody><tr>
<td style="border:none;padding:0px 15px 0px 8px">
<a href="https://www.avast.com/antivirus" target="_blank">
<img border="0" src="http://static.avast.com/emails/avast-mail-stamp.png" alt="Avast logo">
</a>
</td>
<td>
<p style="color:rgb(61,77,90);font-family:Calibri,Verdana,Arial,Helvetica;font-size:12pt">
This email has been checked for viruses by Avast antivirus software.
<br><a href="https://www.avast.com/antivirus" target="_blank">www.avast.com</a>
</p>
</td>
</tr>
</tbody></table>
<br>
</div>
<br>_______________________________________________<br>
Users mailing list: <a href="mailto:Users@clusterlabs.org">Users@clusterlabs.org</a><br>
<a href="http://clusterlabs.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://clusterlabs.org/mailman/listinfo/users</a><br>
<br>
Project Home: <a href="http://www.clusterlabs.org" rel="noreferrer" target="_blank">http://www.clusterlabs.org</a><br>
Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" rel="noreferrer" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br>
Bugs: <a href="http://bugs.clusterlabs.org" rel="noreferrer" target="_blank">http://bugs.clusterlabs.org</a><br>
<br></blockquote></div><br></div></div>