Mailing List Archive: Why wont ocf:heartbeat:Xen check the current status?

Hello List,

i have a two node Cluster with Debian 7 and this configuation:

node proxy01-example.net
node proxy02-example.net
primitive login.example.net ocf:heartbeat:Xen \
params xmfile="/etc/xen/login.example.net.cfg" \
op monitor interval="30s" timeout="600" \
op start interval="0" timeout="60" \
op stop interval="0" timeout="40" \
meta target-role="Started" allow-migrate="true" is-managed="false"
property $id="cib-bootstrap-options" \
dc-version="1.1.7-ee0730e13d124c3d58f00016c3376a1de5323cff" \
cluster-infrastructure="openais" \
expected-quorum-votes="2" \
stonith-enabled="false" \
no-quorum-policy="ignore" \
last-lrm-refresh="1393067803"
rsc_defaults $id="rsc-options" \
resource-stickiness="100"

The resource login.example.net is already running because this is a
existing setup and i would like to add the linux-ha stuff.

So lets say login.example.net is already running on proxy01-example.net.

If i now activate this configuration, the Xen Instance
login.example.netwill be started on the
proxy02-example.net node.

Now i have then running twice!!

Why does it not check IF the resource is already running somewhere?

How can i integrate linux-ha with ocf:heartbeat:Xen to a existing setup
WITHOUT shutting every resource down and then manage it with corosync from
the start?!

Thanks,
Mario
_______________________________________________
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

On 2014-02-22T12:35:42, ml ml <mliebherr99@googlemail.com> wrote:

> Hello List,
>
> i have a two node Cluster with Debian 7 and this configuation:
>
> node proxy01-example.net
> node proxy02-example.net
> primitive login.example.net ocf:heartbeat:Xen \
> params xmfile="/etc/xen/login.example.net.cfg" \
> op monitor interval="30s" timeout="600" \
> op start interval="0" timeout="60" \
> op stop interval="0" timeout="40" \
> meta target-role="Started" allow-migrate="true" is-managed="false"
> property $id="cib-bootstrap-options" \
> dc-version="1.1.7-ee0730e13d124c3d58f00016c3376a1de5323cff" \
> cluster-infrastructure="openais" \
> expected-quorum-votes="2" \
> stonith-enabled="false" \
> no-quorum-policy="ignore" \
> last-lrm-refresh="1393067803"
> rsc_defaults $id="rsc-options" \
> resource-stickiness="100"
>
> The resource login.example.net is already running because this is a
> existing setup and i would like to add the linux-ha stuff.
>
> So lets say login.example.net is already running on proxy01-example.net.
>
> If i now activate this configuration, the Xen Instance
> login.example.netwill be started on the
> proxy02-example.net node.
>
> Now i have then running twice!!
>
> Why does it not check IF the resource is already running somewhere?

It does.

It also obviously isn't working for you.

The RA tries to determine the name of the domain to look for from the
configuration file; perhaps that's not working for you? You can manually
set that for the resource too.

The log messages from the agent are probably enlightening, or try
running it manually with "monitor" and see why it doesn't pick up. The
answers are always in the logs (or if that fails, in the code ;-).

On the other hand, you don't really care if guests run twice, right?
Otherwise you'd not have disabled stonith ...

Regards,
Lars

--
Architect Storage/HA
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde

_______________________________________________
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems