Re: [Pacemaker] A problem to fail in a stop of Pacemaker.

2009-09-30 Thread renayama19661014 
Hi Steven,

> Please note this could still be a bz in corosync related to service
> engine integration.  It is just too early to tell.  Andrew should be
> able to tell us for certain when he has an opportunity to take a look at
> it.

Yes. 
I think that unification will be still early. 

I hope that the release of the combination with corosync is given early.

Best Regards,
Hideo Yamauchi.


--- Steven Dake  wrote:

> On Wed, 2009-09-30 at 09:51 +0900, renayama19661...@ybb.ne.jp wrote:
> > Hi Remi,
> > 
> > > It appears that this is a similar problem to the one that I reported, 
> > > yes.  It appears to not be a bug in Corosync, but rather one in 
> > > Pacemaker.  This bug has been filed in Red Hat Bugzilla, see it at:
> > > 
> > > https://bugzilla.redhat.com/show_bug.cgi?id=525589
> > > 
> > > Perhaps you could add any additional details that you have found 
> > > (affected packages, etc.) to the bug; it may help the developers fix it.
> > 
> > All right.
> > Thank you.
> > 
> > Best Regards,
> > Hideo Yamauchi.
> > 
> 
> Please note this could still be a bz in corosync related to service
> engine integration.  It is just too early to tell.  Andrew should be
> able to tell us for certain when he has an opportunity to take a look at
> it.
> 
> Regards
> -steve
> 
> > --- Remi Broemeling  wrote:
> > 
> > > Hello Hideo,
> > > 
> > > It appears that this is a similar problem to the one that I reported, 
> > > yes.  It appears to not be a bug in Corosync, but rather one in 
> > > Pacemaker.  This bug has been filed in Red Hat Bugzilla, see it at:
> > > 
> > > https://bugzilla.redhat.com/show_bug.cgi?id=525589
> > > 
> > > Perhaps you could add any additional details that you have found 
> > > (affected packages, etc.) to the bug; it may help the developers fix it.
> > > 
> > > Thanks.
> > > 
> > > 
> > > renayama19661...@ybb.ne.jp wrote:
> > > > Hi,
> > > >
> > > > I started a Dummy resource in one node by the next combination.
> > > >  * corosync 1.1.0
> > > >  * Pacemaker-1-0-05c8b63cbca7
> > > >  * Reusable-Cluster-Components-6ef02517ee57
> > > >  * Cluster-Resource-Agents-88a9cfd9e8b5
> > > >
> > > > The Dummy resource started in a node.
> > > >
> > > > I was going to stop a node(service Corosync stop), but did not stop.
> > > >
> > > > --log--
> > > > (snip)
> > > >
> > > > Sep 29 13:52:01 rh53-1 crmd: [11193]: info: crm_signal_dispatch: 
> > > > Invoking handler for
> signal
> > > 15:
> > > > Terminated
> > > > Sep 29 13:52:01 rh53-1 crmd: [11193]: info: crm_shutdown: Requesting 
> > > > shutdown
> > > > Sep 29 13:52:01 rh53-1 crmd: [11193]: info: do_state_transition: State 
> > > > transition S_IDLE
> ->
> > > > S_POLICY_ENGINE [ input=I_SHUTDOWN cause=C_SHUTDOWN origin=crm_shutdown 
> > > > ]
> > > > Sep 29 13:52:01 rh53-1 crmd: [11193]: info: do_state_transition: All 1 
> > > > cluster nodes are
> > > eligible to
> > > > run resources.
> > > > Sep 29 13:52:01 rh53-1 crmd: [11193]: info: do_shutdown_req: Sending 
> > > > shutdown request to
> DC:
> > > rh53-1
> > > > Sep 29 13:52:30 rh53-1 corosync[11183]:   [pcmk  ] notice: 
> > > > pcmk_shutdown: Still waiting
> for
> > > crmd
> > > > (pid=11193) to terminate...
> > > > Sep 29 13:53:30 rh53-1 last message repeated 2 times
> > > > Sep 29 13:55:00 rh53-1 last message repeated 3 times
> > > > Sep 29 13:56:30 rh53-1 last message repeated 3 times
> > > > Sep 29 13:58:01 rh53-1 last message repeated 3 times
> > > > Sep 29 13:59:31 rh53-1 last message repeated 3 times
> > > > Sep 29 14:00:31 rh53-1 last message repeated 2 times
> > > > Sep 29 14:00:46 rh53-1 cib: [11189]: info: cib_stats: Processed 94 
> > > > operations (11489.00us
> > > average, 0%
> > > > utilization) in the last 10min
> > > > Sep 29 14:01:01 rh53-1 corosync[11183]:   [pcmk  ] notice: 
> > > > pcmk_shutdown: Still waiting
> for
> > > crmd
> > > > (pid=11193) to terminate...
> > > >
> > > > (snip)
> > > > --log--
> > > >
> > > >
> > > > Possibly is the cause same as the next email?
> > > >  * http://www.gossamer-threads.com/lists/linuxha/pacemaker/58127
> > > >
> > > > And, the same problem was taking place by the next combination.
> > > >  * corosync 1.0.1
> > > >  * Pacemaker-1-0-595cca870aff
> > > >  * Reusable-Cluster-Components-6ef02517ee57
> > > >  * Cluster-Resource-Agents-88a9cfd9e8b5
> > > >
> > > > I attach a file of hb_report.
> > > >
> > > > Best Regards,
> > > > Hideo Yamauchi.
> > > >   
> > > 
> > > -- 
> > > 
> > > Remi Broemeling
> > > Sr System Administrator
> > > 
> > > Nexopia.com Inc.
> > > direct: 780 444 1250 ext 435
> > > email: r...@nexopia.com 
> > > fax: 780 487 0376
> > > 
> > > www.nexopia.com 
> > > 
> > > You are only young once, but you can stay immature indefinitely.
> > > www.siglets.com
> > > > ___
> > > Pacemaker mailing list
> > > Pacemaker@oss.clusterlabs.org
> > > http://oss.clusterlabs.org/mailman/listinfo/pacema

[Pacemaker] Fedora 11 - OCFS2 - Pacemaker

2009-09-30 Thread Fausto Lombardi 
Hi of all,
I'm trying to setup a dual primary DRDB with Pacemaker and OCFS2.

I have followed the 'Clusters from Scratch - Apache on Fedora11' pdf but
when mount the ocfs2 partition I'm receiving this error message:

Sep 30 00:03:17 fedora-kvm1 kernel: dlm: TCP protocol can't handle
multi-homed hosts, try SCTP
Sep 30 00:03:17 fedora-kvm1 kernel: dlm: cannot start dlm lowcomms -22
Sep 30 00:03:17 fedora-kvm1 kernel: (7101,1):ocfs2_dlm_init:2828 ERROR:
status = -22
Sep 30 00:03:17 fedora-kvm1 kernel: (7101,1):ocfs2_mount_volume:1741 ERROR:
status = -22
Sep 30 00:03:17 fedora-kvm1 kernel: ocfs2: Unmounting device (147,1) on
(node 0)

DLM and O2CB are started.

Why?

Furthermore in this manual it is suggested to modify the OCF sript o2cb to
improve the compatibility with fedora 11.

sed -i.gres s/start_daemon//g /usr/lib/ocf/resource.d/ocfs2/o2cb
sed -i.gres s/pidofproc/pidof/g /usr/lib/ocf/resource.d/ocfs2/o2cb

What are the incompatibility with this release?

Thanks.
___
Pacemaker mailing list
Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Re: [Pacemaker] Fedora 11 - OCFS2 - Pacemaker

2009-09-30 Thread Errol Neal 
On Wed, Sep 30, 2009 03:45  AM, Fausto Lombardi  wrote:
> Hi of all,
> I'm trying to setup a dual primary DRDB with Pacemaker and OCFS2.
> 
> I have followed the 'Clusters from Scratch - Apache on Fedora11' pdf but when 
> mount the ocfs2 partition I'm receiving this error message:
> 
> Sep 30 00:03:17 fedora-kvm1 kernel: dlm: TCP protocol can't handle 
> multi-homed hosts, try SCTP
> Sep 30 00:03:17 fedora-kvm1 kernel: dlm: cannot start dlm lowcomms -22
> Sep 30 00:03:17 fedora-kvm1 kernel: (7101,1):ocfs2_dlm_init:2828 ERROR: 
> status = -22
> Sep 30 00:03:17 fedora-kvm1 kernel: (7101,1):ocfs2_mount_volume:1741 ERROR: 
> status = -22
> Sep 30 00:03:17 fedora-kvm1 kernel: ocfs2: Unmounting device (147,1) on (node 
> 0)
> 
> DLM and O2CB are started.
> 
> Why?

I followed the same guide. Did you download ocfs2 from the same repo?

> Furthermore in this manual it is suggested to modify the OCF sript o2cb to 
> improve the compatibility with fedora 11.
> 
> sed -i.gres s/start_daemon//g /usr/lib/ocf/resource.d/ocfs2/o2cb
> sed -i.gres s/pidofproc/pidof/g /usr/lib/ocf/resource.d/ocfs2/o2cb
> 
> What are the incompatibility with this release?
> 
The sed removes start_daemon and replaced pidofproc with pidof. I neglected to 
do this step on the second node and realized it right away. 



> 
> 
> _
> This email was transferred using an evaluation version
> of AXIGEN Mail Server.
> 
> ___
> Pacemaker mailing list
> Pacemaker@oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> 
> _
> This email was transferred using an evaluation version
> of AXIGEN Mail Server.
> 
> 

_
This email was transferred using an evaluation version
of AXIGEN Mail Server.


___
Pacemaker mailing list
Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Re: [Pacemaker] Fedora 11 - OCFS2 - Pacemaker

2009-09-30 Thread Fausto Lombardi 
I download the ocfs2 package from the same repo.
I don't follow the guide step by step. I'm configuring the first node
(the second is a production machine!).
So now the cluster is composed with one node.

The difference from the guide that I have implemented in my configuration is
the rrp openais feature; so I have configured another ethernet card for
multicast communications.

I believe that the 'dlm: TCP protocol can't handle multi-homed hosts, try
SCTP' error is related to rrp ais feature, so dlm refuses to mount the
filesystem.

Could it be?


2009/9/30 Errol Neal 

> On Wed, Sep 30, 2009 03:45  AM, Fausto Lombardi  wrote:
> > Hi of all,
> > I'm trying to setup a dual primary DRDB with Pacemaker and OCFS2.
> >
> > I have followed the 'Clusters from Scratch - Apache on Fedora11' pdf but
> when mount the ocfs2 partition I'm receiving this error message:
> >
> > Sep 30 00:03:17 fedora-kvm1 kernel: dlm: TCP protocol can't handle
> multi-homed hosts, try SCTP
> > Sep 30 00:03:17 fedora-kvm1 kernel: dlm: cannot start dlm lowcomms -22
> > Sep 30 00:03:17 fedora-kvm1 kernel: (7101,1):ocfs2_dlm_init:2828 ERROR:
> status = -22
> > Sep 30 00:03:17 fedora-kvm1 kernel: (7101,1):ocfs2_mount_volume:1741
> ERROR: status = -22
> > Sep 30 00:03:17 fedora-kvm1 kernel: ocfs2: Unmounting device (147,1) on
> (node 0)
> >
> > DLM and O2CB are started.
> >
> > Why?
>
> I followed the same guide. Did you download ocfs2 from the same repo?
>
> > Furthermore in this manual it is suggested to modify the OCF sript o2cb
> to improve the compatibility with fedora 11.
> >
> > sed -i.gres s/start_daemon//g /usr/lib/ocf/resource.d/ocfs2/o2cb
> > sed -i.gres s/pidofproc/pidof/g /usr/lib/ocf/resource.d/ocfs2/o2cb
> >
> > What are the incompatibility with this release?
> >
> The sed removes start_daemon and replaced pidofproc with pidof. I neglected
> to do this step on the second node and realized it right away.
>
>
>
> >
> >
> > _
> > This email was transferred using an evaluation version
> > of AXIGEN Mail Server.
> >
> > ___
> > Pacemaker mailing list
> > Pacemaker@oss.clusterlabs.org
> > http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> >
> > _
> > This email was transferred using an evaluation version
> > of AXIGEN Mail Server.
> >
> >
>
> _
> This email was transferred using an evaluation version
> of AXIGEN Mail Server.
>
>
> ___
> Pacemaker mailing list
> Pacemaker@oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
___
Pacemaker mailing list
Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

[Pacemaker] pacemaker on different networks

2009-09-30 Thread Fabrizio Mancini 
Hi guys,
sorry for the dumb question but i'm totally new to pacemaker.
I have 2 node with debian lenny on board and i've followed this tutorial for
the setup part.
http://www.clusterlabs.org/wiki/Debian_Lenny_HowTo
On every node i have 2 nics with 2 different networks
nic1 on net 1 -> 10.0.0.1
nic2 on net 2 -> 192.168.1.1
the two networks are isolated, they don't speak each other. The box act as a
router for the two networks only for some services (http) in both the way.
It uses iptables for this.
I should need to have one ip clustered on the first network and one ip
clustered on the second network.
Which kind of resources should i add to the CIB?
of course ocf:heartbeat:IPaddr
What kink of ports should i open in iptables to allow the two nodes to speak
each other?
I've read even this tutorial
http://www.clusterlabs.org/wiki/Pingd_with_resources_on_different_networks
but i've not understood if pingd is the right choice for this work.
Any help appreciated
Thanks in advance
Fabrizio
___
Pacemaker mailing list
Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Re: [Pacemaker] OCF RA KVM

2009-09-30 Thread Thomas Mueller 
On Mon, 28 Sep 2009 09:02:16 +0200, Michael Schwartzkopff wrote:

> Am Montag, 28. September 2009 00:11:35 schrieb Fausto Lombardi:
>> Hi of all,
>> there is a resource agent for KVM virtual machines?
>>
>> Thanks.
> 
> Yes. VirtualDomain.

VirtualDomain is for libvirtd - wheras libvirtd supports kvm . but 
libvirtd doesn't support all features supported by kvm (all features in 
sense of "a feature that i was in need of").

i once posted my kvm resource agent on the heartbeat list. 

http://thread.gmane.org/gmane.linux.highavailability.user/27315

as there was very few responses, i haven't cleand it up for "public use" 
as it works for me. 

- Thomas


___
Pacemaker mailing list
Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker