<br><br><div class="gmail_quote">On Mon, Jun 27, 2011 at 3:33 PM, veghead <span dir="ltr"><<a href="mailto:sean@studyblue.com">sean@studyblue.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Sorry for the questions. Some days my brain is just slow. :)<br>
<div class="im"><br>
Serge Dubrouski <sergeyfd@...> writes:<br>
> If you want to make your LDAP independent from IP just remove your<br>
> collocation:colocation ldap-with-eip inf: elastic_ip ldap-clone<br>
<br>
</div>Is that really what I want to do? I mean, I need the elastic ip assigned to<br>
~one~ of the machines... And if LDAP fails on that machine, I need Pacemaker to<br>
start the Elastic IP on the other machine.<br>
<br>
If I remove the co-location, won't the elastic_ip resource just stay where it<br>
is? Regardless of what happens to LDAP?<br></blockquote><div><br>Right. That's why I think that you don't really want to do it. You have to make sure that your IP is up where you LDAP is up.<br> <br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im"><br>
> But I'd rather try to find out why monitoring for IP fails. May bet<br>
> it just needs an increased timeout on monitor operation, though it<br>
> looks like you've already increased it. What's in your log files<br>
> when that monitor fails?<br>
<br>
</div>Originally, I had the monitor on the elastic_ip resource set to 10 seconds. The<br>
error in the logs was:<br>
<br>
---snip---<br>
pengine: [16980]: notice: unpack_rsc_op: Operation elastic_ip_monitor_0 found<br>
resource elastic_ip active on ldap1.example.ec2<br>
pengine: [16980]: WARN: unpack_rsc_op: Processing failed op<br>
elastic_ip_monitor_10000 on ldap1.example.ec2: unknown exec error (-2)<br>
pengine: [16980]: WARN: unpack_rsc_op: Processing failed op elastic_ip_stop_0 on<br>
ldap1.example.ec2: unknown exec error (-2)<br>
pengine: [16980]: info: native_add_running: resource elastic_ip isnt managed<br></blockquote><div><br>Why it's "unmanaged"?<br> <br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
pengine: [16980]: notice: unpack_rsc_op: Operation ldap:1_monitor_0 found<br>
resource ldap:1 active on ldap2.example.ec2<br>
pengine: [16980]: WARN: unpack_rsc_op: Processing failed op elastic_ip_start_0<br>
on ldap2.example.ec2: unknown exec error (-2)<br>
pengine: [16980]: notice: native_print: elastic_ip (lsb:elastic-ip):<br>
Started ldap1.example.ec2 (unmanaged) FAILED<br>
pengine: [16980]: notice: clone_print: Clone Set: ldap-clone<br>
pengine: [16980]: notice: short_print: Stopped: [ ldap:0 ldap:1 ]<br>
pengine: [16980]: info: get_failcount: elastic_ip has failed INFINITY times on<br>
ldap1.example.ec2<br>
pengine: [16980]: WARN: common_apply_stickiness: Forcing elastic_ip away from<br>
ldap1.example.ec2 after 1000000 failures (max=1000000)<br>
pengine: [16980]: info: get_failcount: elastic_ip has failed INFINITY times on<br>
ldap2.example.ec2<br>
pengine: [16980]: WARN: common_apply_stickiness: Forcing elastic_ip away from<br>
ldap2.example.ec2 after 1000000 failures (max=1000000)<br>
pengine: [16980]: info: native_color: Unmanaged resource elastic_ip allocated to<br>
'nowhere': failed<br>
pengine: [16980]: notice: RecurringOp: Start recurring monitor (15s) for ldap:0<br>
on ldap1.example.ec2<br>
pengine: [16980]: notice: RecurringOp: Start recurring monitor (15s) for ldap:1<br>
on ldap2.example.ec2<br>
pengine: [16980]: notice: LogActions: Leave resource elastic_ip<br>
(Started unmanaged)<br>
pengine: [16980]: notice: LogActions: Start ldap:0 (ldap1.example.ec2)<br>
pengine: [16980]: notice: LogActions: Start ldap:1 (ldap2.example.ec2)<br>
---snip---<br>
<br>
Now that I have set the monitor interval for the elastic_ip resource to "0", it<br>
keeps thinking everything is either stopped or should be stopped:<br></blockquote><div><br>You can't have monitoring interval set to 0. It makes no sense and actually reserved for probs AFAIK. <br> <br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
---snip---<br>
pengine: [7287]: notice: unpack_rsc_op: Operation elastic_ip_monitor_0 found<br>
resource elastic_ip active on ldap1.example.ec2<br>
pengine: [7287]: notice: unpack_rsc_op: Operation ldap:0_monitor_0 found<br>
resource ldap:0 active on ldap2.example.ec2<br>
pengine: [7287]: notice: native_print: elastic_ip (lsb:elastic-ip):<br>
Stopped<br>
pengine: [7287]: notice: clone_print: Clone Set: ldap-clone<br>
pengine: [7287]: notice: short_print: Stopped: [ ldap:0 ldap:1 ]<br>
pengine: [7287]: notice: LogActions: Leave resource elastic_ip (Stopped)<br>
pengine: [7287]: notice: LogActions: Leave resource ldap:0 (Stopped)<br>
pengine: [7287]: notice: LogActions: Leave resource ldap:1 (Stopped)<br>
---snip---<br>
<br>
Very strange.<br>
<div><div></div><div class="h5"><br>
<br>
_______________________________________________<br>
Pacemaker mailing list: <a href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a><br>
<a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>
<br>
Project Home: <a href="http://www.clusterlabs.org" target="_blank">http://www.clusterlabs.org</a><br>
Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br>
Bugs: <a href="http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker" target="_blank">http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Serge Dubrouski.<br>