Mike,
Here is what I received when I started heartbeat and ran crm_mon.
============
Last updated: Wed Jun 9 12:53:12 2010
Current DC: warning1 (687650eb-f2a3-4667-82f8-c93ff4f75827)
2 Nodes configured.
1 Resources configured.
============
Node: warning2 (ef4c2790-5dc8-4572-9086-46328be53ced): OFFLINE
Node: warning1 (687650eb-f2a3-4667-82f8-c93ff4f75827): online
Resource Group: group_1
IPaddr_101_202_40_47 (ocf::heartbeat:IPaddr): Started
warning1
Filesystem_2 (ocf::heartbeat:Filesystem): Started warning1
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of
[email protected]
Sent: Wednesday, June 09, 2010 11:36 AM
To: [email protected]
Subject: Linux-HA Digest, Vol 79, Issue 19
Send Linux-HA mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.linux-ha.org/mailman/listinfo/linux-ha
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Linux-HA digest..."
Today's Topics:
1. Re: tracking down reason for crash? (Miles Fidelman)
2. Re: tracking down reason for crash? (Michael)
3. Re: tracking down reason for crash? (Michael)
4. Re: tracking down reason for crash? (Miles Fidelman)
5. Re: Colocation, location, auto-failback=off (Andrew Beekhof)
6. Re: cl_status nodetstatus behavior (Dejan Muhamedagic)
7. HA configuration problems (Tim Macking)
8. Re: HA configuration problems (Heiko Schellhorn)
9. Re: HA configuration problems (mike)
----------------------------------------------------------------------
Message: 1
Date: Tue, 08 Jun 2010 14:28:09 -0400
From: Miles Fidelman <[email protected]>
Subject: Re: [Linux-HA] tracking down reason for crash?
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Florian Haas wrote:
> I know you're not going to like to hear this, but _please_ grab the
> squeeze packages for heartbeat, pacemaker, cluster-glue, and
> cluster-agents, dpkg-buildpackage it on lenny, and install those.
>
>
you're right, I don't like hearing that, I really don't like mixing
stable and unstable packages :--(
but... if that turns out to be the best answer, three questions:
1. Anybody have a sense of how well this works in practice, on Lenny?
2. Can you be a little more specific about the steps involved (I've
never assembled a backport before).
3. Any thoughts on whether it would be easier to simply download the
latest tarballs, and ./configure, make, make install?
Thanks!
Miles Fidelman
--
In theory, there is no difference between theory and practice.
In<fnord> practice, there is. .... Yogi Berra
------------------------------
Message: 2
Date: Wed, 9 Jun 2010 07:12:06 +1200
From: Michael <[email protected]>
Subject: Re: [Linux-HA] tracking down reason for crash?
To: General Linux-HA mailing list <[email protected]>
Message-ID:
<[email protected]>
Content-Type: text/plain; charset=ISO-8859-1
On Wed, Jun 9, 2010 at 6:28 AM, Miles Fidelman
<[email protected]>wrote:
> Florian Haas wrote:
> > I know you're not going to like to hear this, but _please_ grab the
> > squeeze packages for heartbeat, pacemaker, cluster-glue, and
> > cluster-agents, dpkg-buildpackage it on lenny, and install those.
> >
> >
> you're right, I don't like hearing that, I really don't like mixing
> stable and unstable packages :--(
>
> but... if that turns out to be the best answer, three questions:
>
> 1. Anybody have a sense of how well this works in practice, on Lenny?
>
> 2. Can you be a little more specific about the steps involved (I've
> never assembled a backport before).
>
> 3. Any thoughts on whether it would be easier to simply download the
> latest tarballs, and ./configure, make, make install?
>
> Thanks!
>
> Miles Fidelman
>
> --
> In theory, there is no difference between theory and practice.
> In<fnord> practice, there is. .... Yogi Berra
>
>
> _______________________________________________
> Linux-HA mailing list
> [email protected]
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
>
There is a very nice howto:
http://www.clusterlabs.org/wiki/Debian_Lenny_HowTo
Using it in production now ( moved to corosync from heartbeat )
--
--
Michael
------------------------------
Message: 3
Date: Wed, 9 Jun 2010 07:12:06 +1200
From: Michael <[email protected]>
Subject: Re: [Linux-HA] tracking down reason for crash?
To: General Linux-HA mailing list <[email protected]>
Message-ID:
<[email protected]>
Content-Type: text/plain; charset=ISO-8859-1
On Wed, Jun 9, 2010 at 6:28 AM, Miles Fidelman
<[email protected]>wrote:
> Florian Haas wrote:
> > I know you're not going to like to hear this, but _please_ grab the
> > squeeze packages for heartbeat, pacemaker, cluster-glue, and
> > cluster-agents, dpkg-buildpackage it on lenny, and install those.
> >
> >
> you're right, I don't like hearing that, I really don't like mixing
> stable and unstable packages :--(
>
> but... if that turns out to be the best answer, three questions:
>
> 1. Anybody have a sense of how well this works in practice, on Lenny?
>
> 2. Can you be a little more specific about the steps involved (I've
> never assembled a backport before).
>
> 3. Any thoughts on whether it would be easier to simply download the
> latest tarballs, and ./configure, make, make install?
>
> Thanks!
>
> Miles Fidelman
>
> --
> In theory, there is no difference between theory and practice.
> In<fnord> practice, there is. .... Yogi Berra
>
>
> _______________________________________________
> Linux-HA mailing list
> [email protected]
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
>
There is a very nice howto:
http://www.clusterlabs.org/wiki/Debian_Lenny_HowTo
Using it in production now ( moved to corosync from heartbeat )
--
--
Michael
------------------------------
Message: 4
Date: Tue, 08 Jun 2010 20:27:31 -0400
From: Miles Fidelman <[email protected]>
Subject: Re: [Linux-HA] tracking down reason for crash?
To: General Linux-HA mailing list <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Michael wrote:
> There is a very nice howto:
> http://www.clusterlabs.org/wiki/Debian_Lenny_HowTo
> Using it in production now ( moved to corosync from heartbeat )
>
Thanks for the pointer!
Those seem to be start-from-scratch instructions. Since I'm currently
running heartbeat 2, can you say a little more about "moved from
corosync from heartbeat." I'm just a little leery about simply putting
the new source line in apt, doing an apt-get update and then apt-get
install pacemaker.
Thanks very much,
Miles Fidelman
--
In theory, there is no difference between theory and practice.
In<fnord> practice, there is. .... Yogi Berra
------------------------------
Message: 5
Date: Wed, 9 Jun 2010 08:30:08 +0200
From: Andrew Beekhof <[email protected]>
Subject: Re: [Linux-HA] Colocation, location, auto-failback=off
To: [email protected], General Linux-HA mailing list
<[email protected]>
Message-ID:
<[email protected]>
Content-Type: text/plain; charset=ISO-8859-1
On Fri, Jun 4, 2010 at 11:25 PM, Tony Hunter <[email protected]> wrote:
> On Thu, Jun 03, 2010 at 07:18:16PM -0300, Diego Woitasen wrote:
>> On Wed, Jun 2, 2010 at 7:43 AM, Andrew Beekhof <[email protected]>
wrote:
>>
>> > On Sat, May 29, 2010 at 3:54 AM, Diego Woitasen <[email protected]>
>> > wrote:
>> > > Hi,
>> > > ?* I have three nodes: "ha1", "ha2" y "ha3".
>> > > ?* Three resources: "sfex", "xfs_fs", "ip".
>> > > ?* "sfex" and "xfs_fs" are members of a group called "xfs_grp".
>> > > ?* "xfs_grp" can run on any node but "ip" resource can run on "ha1"
or
>> > > "ha2" only.
>> > > ?* When "xfs_grp" is running on "ha1" or "ha2", "ip" must run on the
same
>> > > node.
>> > > ?* One last thing, I need manual failback.
>> > >
>> > > My current configuration works except for the "manual failback"
(a.k.a.
>> > > auto_failback off).
>> > >
>> > > node $id="0ace77ab-600a-4541-a682-ab0534bb3fc4" ha3
>> > > node $id="3d1f07b5-a79b-478f-b07c-02a7a5c5106c" ha2
>> > > node $id="c44a3a26-35d4-476e-a1e6-49f03f068f12" ha1
>> > > primitive ip ocf:heartbeat:IPaddr \
>> > > ? ? ? ?params ip="192.168.1.147"
>> > > primitive sfex ocf:heartbeat:sfex \
>> > > ? ? ? ?params device="/dev/sdb1" \
>> > > ? ? ? ?op monitor interval="10" timeout="10" depth="0"
>> > > primitive xfs_fs ocf:heartbeat:Filesystem \
>> > > ? ? ? ?params device="/dev/sdb2" directory="/shared" fstype="xfs" \
>> > > ? ? ? ?op monitor interval="20" timeout="40" depth="0"
>> > > group xfs_grp sfex xfs_fs
>> > > location srv_loc ip -inf: ha3
>> > > colocation srv_col inf: ip xfs_grp
>> > > property $id="cib-bootstrap-options" \
>> > > ? ? ? ?no-quorum-policy="ignore" \
>> > > ? ? ? ?expected-quorum-votes="1" \
>> > > ? ? ? ?stonith-enabled="0" \
>> > > ? ? ? ?default-resource-stickiness="INFINITY"
>> > >
>> > > When "xfs_grp" is running in "ha3" and "ha1" or "ha2" are alive
again,
>> > the
>> > > resources ("xfs_grp" and "ip") move to any of them.
>> > >
>> > > Any ideas?
>> >
>> > Not really, I don't understand what the problem is.
>> > ip can only run on ha1 or ha2, so its not surprising that it gets
>> > stopped occasionally (ie. when you shut down one node and make the
>> > other standby) while the group remains running.
>> > _______________________________________________
>> > Linux-HA mailing list
>> > [email protected]
>> > http://lists.linux-ha.org/mailman/listinfo/linux-ha
>> > See also: http://linux-ha.org/ReportingProblems
>> >
>>
>> May be my explanation was wrong.
>>
>> xfs_grp can run on ha1, ha2 or ha3.
>> ip can run on ha1 or ha2.
>>
>> If I shutdown ha1 and ha2, xfs_grp moves to ha3 without "ip". If ha1 (or
>> ha2) returns back, xfs_grp moves to ha1 and "ip" are started. I have
>> default-resource-stickiness="
>> INFINITY" so I think that xfs_grp should stays in ha3 until manual
failback.
>
> I'm fairly new to pacemaker/corosync but I haven't seen a reply to your
mail,
> so I'll take a shot. It seems your colocation rule below prevents xfs_grp
> from running on ha3 unless ip is also running there:
> colocation srv_col inf: ip xfs_grp
>
> And this rule seems to suggest the ip resource should _never_ run on ha3.
> location srv_loc ip -inf: ha3
>
> So, as far as I can see, the cluster is behaving as configured - ha1 or
ha2
> takes over ip when one of them comes back online, since ip is not running
> anywhere. And of course xfs_grp is migrated because of the colocation
> constraint.
exactly
------------------------------
Message: 6
Date: Wed, 9 Jun 2010 14:33:00 +0200
From: Dejan Muhamedagic <[email protected]>
Subject: Re: [Linux-HA] cl_status nodetstatus behavior
To: General Linux-HA mailing list <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
Hi,
On Mon, Jun 07, 2010 at 11:07:05AM +0530, Satish Burnwal (sburnwal) wrote:
> Hi All,
>
> I am little new to Linux HA library and I am having this problem in my
> HA setup. Node1 has correct info about node2's hostname but wrong info
> about node2's ip address. From node1, I am trying to use 'cl_status
> nodestatus node2-hostname' and it returns me the status as 'active' but
> when I use 'cl_status nodestatus node2-ip-address', it returns as
> 'Error. May be due to incorrect node name'. Heartbeat test from node1 to
> node2 is failing as shown in /var/log/messages logs since that is ip
> based. I want to know by hostname based 'cl_status nodestatus
> <node2-hostname> is giving me as 'active' if at all heartbeat is
> actually failing. Any help is appreciated.
You can supply only the node name, not the IP address. The IP
address is irrelevant in this case.
Thanks,
Dejan
>
>
>
> Thanks
>
> -Satish
>
> _______________________________________________
> Linux-HA mailing list
> [email protected]
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
------------------------------
Message: 7
Date: Wed, 9 Jun 2010 10:30:29 -0400
From: "Tim Macking" <[email protected]>
Subject: [Linux-HA] HA configuration problems
To: <[email protected]>
Message-ID: <000601cb07e0$52395970$f6ac0c...@com>
Content-Type: text/plain; charset="us-ascii"
I am fairly new to Linux, specifically RedHat Enterprise.
The project I have now is unraveling how 2 servers were setup with HA, why
it is working (but not entirely), and how to get it configured correctly.
I have read over the documentation at http://www.linux-ha.org/doc/
Currently I know there are 2 servers, both have HA setup and if one server
fails it will switch over to the 2nd server with only 1 problem. MySQL
fails to "always" load. The MySQL database is located on a SAN.
When I do: /etc/init.d/heartbeat status it says "heartbeat is stopped. No
process".
When I do: rpm -q heartbeat -d it says "package heartbeat is not installed".
If that is the case on both servers, how is it that it is working and that
it switches over to the 2nd machine?
Is there any other method that would be used? If so, how can I find out
what/where this is?
If it is using heartbeat, what am I missing?
THEN, on the MySQL part, what process or script runs to restart MySQL and
attach it to the SAN where the DB is located?
I really appreciate any help.
------------------------------
Message: 8
Date: Wed, 9 Jun 2010 16:51:38 +0200
From: Heiko Schellhorn <[email protected]>
Subject: Re: [Linux-HA] HA configuration problems
To: [email protected], "General Linux-HA mailing list"
<[email protected]>
Message-ID: <[email protected]>
Content-Type: Text/Plain; charset="iso-8859-1"
Hi Tim
> The project I have now is unraveling how 2 servers were setup with HA, why
> it is working (but not entirely), and how to get it configured correctly.
It sounds to me that you inherited two servers which were already installed.
Am I right ?
> Currently I know there are 2 servers, both have HA setup and if one server
> fails it will switch over to the 2nd server with only 1 problem. MySQL
> fails to "always" load. The MySQL database is located on a SAN.
>
> When I do: /etc/init.d/heartbeat status it says "heartbeat is stopped. No
> process".
>
> When I do: rpm -q heartbeat -d it says "package heartbeat is not
> installed".
>
>
>
> If that is the case on both servers, how is it that it is working and that
> it switches over to the 2nd machine?
It may be that heartbeat was installed from sources.
> THEN, on the MySQL part, what process or script runs to restart MySQL and
> attach it to the SAN where the DB is located?
Depends on your configuration.
I guess the SAN is mounted by drbd or something else. So the start of mysql
depends on the successfull start of this service.
Maybe also other services depend on this service and have to be colocated.
Depending on the age of your installation you can check your config with the
crm tool or the cibadmin tool or have a look at /etc/ha.d.
Best wishes
Heiko
--
---------------------------------------------------------------------------
ATTENTION !!!!! New Phone-Number: 62091
---------------------------------------------------------------------------
Dipl. Inf. Heiko Schellhorn
University of Bremen Room: NW1-U 2065
Inst. of Environmental Physics Phone: +49(0)421 218 62091
P.O. Box 33 04 40 Fax: +49(0)421 218 98 62091
D-28334 Bremen Mail: mailto:[email protected]
Germany www: http://www.iup.uni-bremen.de
http://www.sciamachy.de
http://www.geoscia.de
The Greatest burden in the world is the weight of you childs coffin on
your shoulder. Nothing in the universe can be heavier than that.
------------------------------
Message: 9
Date: Wed, 09 Jun 2010 12:36:18 -0300
From: mike <[email protected]>
Subject: Re: [Linux-HA] HA configuration problems
To: General Linux-HA mailing list <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Tim Macking wrote:
> I am fairly new to Linux, specifically RedHat Enterprise.
>
>
>
> The project I have now is unraveling how 2 servers were setup with HA, why
> it is working (but not entirely), and how to get it configured correctly.
>
>
>
> I have read over the documentation at http://www.linux-ha.org/doc/
>
>
>
> Currently I know there are 2 servers, both have HA setup and if one server
> fails it will switch over to the 2nd server with only 1 problem. MySQL
> fails to "always" load. The MySQL database is located on a SAN.
>
>
>
> When I do: /etc/init.d/heartbeat status it says "heartbeat is stopped. No
> process".
>
> When I do: rpm -q heartbeat -d it says "package heartbeat is not
installed".
>
>
>
> If that is the case on both servers, how is it that it is working and that
> it switches over to the 2nd machine?
>
>
>
> Is there any other method that would be used? If so, how can I find out
> what/where this is?
>
>
>
> If it is using heartbeat, what am I missing?
>
>
>
> THEN, on the MySQL part, what process or script runs to restart MySQL and
> attach it to the SAN where the DB is located?
>
>
>
> I really appreciate any help.
>
>
>
> _______________________________________________
> Linux-HA mailing list
> [email protected]
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
>
>
Hi Tim,
ITs quite possible that this was not installed from rpm. In my case, all
my installations were done via tar file and config scripts. Sounds
daunting but it really isn't.
Try this - reboot both servers so we know things are clean. Go to the
primary node and issue service heartbeat start. Wait a few minutes and
issue crm_mon and see if that shows you the status of the cluster. If it
does, do a copy and paste the results in here. Then we can see what is
running and what isn't.
Mike
------------------------------
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
End of Linux-HA Digest, Vol 79, Issue 19
****************************************
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
