Hello Andrew,

Glad to hear that you have got it fixed.  I am going to give it another try
and hopefully I will get it working this time.  I am sure I am going to back
here giving you guys headache till I get the feel of pacemaker CRM.

Thanks,

Avestan :drunk:



Andrew Beekhof-3 wrote:
> 
> On Tue, Jan 11, 2011 at 12:21 PM, Avestan <[email protected]>
> wrote:
>>
>> Hello Andrew,
>>
>> I have actually read some of the documents that you have created, such as
>> "Cluster from Scratch - Apache" which is on Fedora 11 and Cluster from
>> Scratch - Apache, DRBD, and GFS2 which is on Fedora 12.  I would also
>> like
>> to take this opportunity to thank you for these two Great documents which
>> I
>> have read.
>>
>> The reason for my migration to Heartbeat + Pacemaker CRM at this point
>> was
>> to take advantage of Floating MAC address functionality in addition to
>> some
>> of other features.  Last night after spending few hours trying to figure
>> out
>> the problem, I decided to write my own little init script for Heartbeat
>> R1
>> to add the Floating MAC functionality to my production which is using
>> Fedora
>> 7 + heartbeat 2.0 as shown here:
>>
>> [root@Alamot ~]# rpm -qa|grep -i heartbeat
>> heartbeat-2.0.8-1.fc7
>>
>> It was actually under impression that from Fedora 12, the Heartbeat and
>> Pacemaker are added to the distribution.  I guess I was wrong...
> 
> No, they're there.
> I just rebuilt them to resolve the issue of heartbeat support:
>    https://bugzilla.redhat.com/show_bug.cgi?id=666041#c11
> 
>>
>> For now, I have to depend to my little script to take care of the
>> floating
>> MAC address but it would have be great if Heartbeat and Pacemaker CRM
>> could
>> work together with the newer version of Fedora Distribution just out of
>> the
>> box.
> 
> They normally do.  Evidently I messed up and no-one noticed for a while.
> 
>>
>> Thanks,
>>
>> Avestan :drunk:
>>
>>
>>
>> Andrew Beekhof-3 wrote:
>>>
>>> On Tue, Jan 11, 2011 at 8:15 AM, Andrew Beekhof <[email protected]>
>>> wrote:
>>>> On Mon, Jan 10, 2011 at 7:05 PM, Avestan <[email protected]>
>>>> wrote:
>>>>>
>>>>> Hello Dejan,
>>>>>
>>>>> Thank you for taking the time to look into this.  In regard with the
>>>>> using
>>>>> null modem serial cable and the bandwidth, it doesn't seem to be
>>>>> problematic
>>>>> running Heartbeat R1 but I will take your advice and slide in a second
>>>>> Network Card for Heartbeat keepalive signaling.
>>>>>
>>>>> In regard with where I got the Pacemaker, as I am using Fedora
>>>>> distribution
>>>>> (Fedora 14) for this testing, I used the yum command to install both
>>>>> Heartbeat and Pacemaker and I believe they come from Fedora
>>>>> repository!
>>>>>
>>>>> Here is what I can get out of my system in regard with the Heartbeat
>>>>> and
>>>>> Pacemaker installed:
>>>>>
>>>>> [root@alamot80 ~]# yum info heartbeat
>>>>> Loaded plugins: langpacks, presto, refresh-packagekit
>>>>> Adding en_US to language list
>>>>> Installed Packages
>>>>> Name        : heartbeat
>>>>> Arch        : i686
>>>>> Version     : 3.0.0
>>>>> Release     : 0.7.0daab7da36a8.hg.fc14
>>>>> Size        : 339 k
>>>>> Repo        : installed
>>>>> From repo   : fedora
>>>>> Summary     : Messaging and membership subsystem for High-Availability
>>>>> Linux
>>>>> URL         : http://linux-ha.org/
>>>>> License     : GPLv2 and LGPLv2+
>>>>> Description : heartbeat is a basic high-availability subsystem for
>>>>> Linux-HA.
>>>>>            : It will run scripts at initialization, and when machines
>>>>> go
>>>>> up
>>>>> or down.
>>>>>            : This version will also perform IP address takeover using
>>>>> gratuitous ARPs.
>>>>>            :
>>>>>            : Heartbeat contains a cluster membership layer, fencing,
>>>>> and
>>>>> local and
>>>>>            : clusterwide resource management functionality.
>>>>>            :
>>>>>            : When used with Pacemaker, it supports "n-node" clusters
>>>>> with
>>>>> significant
>>>>>            : capabilities for managing resources and dependencies.
>>>>>            :
>>>>>            : In addition it continues to support the older release 1
>>>>> style
>>>>> of
>>>>>            : 2-node clustering.
>>>>>            :
>>>>>            : It implements the following kinds of heartbeats:
>>>>>            :         - Serial ports
>>>>>            :         - UDP/IP multicast (ethernet, etc)
>>>>>            :         - UDP/IP broadcast (ethernet, etc)
>>>>>            :         - UDP/IP heartbeats
>>>>>            :         - "ping" heartbeats (for routers, switches, etc.)
>>>>>            :            (to be used for breaking ties in 2-node
>>>>> systems)
>>>>>
>>>>> [root@alamot80 ~]#
>>>>> [root@alamot80 ~]# yum info pacemaker
>>>>> Loaded plugins: langpacks, presto, refresh-packagekit
>>>>> Adding en_US to language list
>>>>> Installed Packages
>>>>> Name        : pacemaker
>>>>> Arch        : i686
>>>>> Version     : 1.1.4
>>>>> Release     : 4.fc14
>>>>> Size        : 2.0 M
>>>>> Repo        : installed
>>>>> From repo   : updates
>>>>> Summary     : Scalable High-Availability cluster resource manager
>>>>> URL         : http://www.clusterlabs.org
>>>>> License     : GPLv2+ and LGPLv2+
>>>>> Description : Pacemaker is an advanced, scalable High-Availability
>>>>> cluster
>>>>> resource
>>>>>            : manager for Linux-HA (Heartbeat) and/or OpenAIS.
>>>>>            :
>>>>>            : It supports "n-node" clusters with significant
>>>>> capabilities
>>>>> for
>>>>>            : managing resources and dependencies.
>>>>>            :
>>>>>            : It will run scripts at initialization, when machines go
>>>>> up
>>>>> or
>>>>> down,
>>>>>            : when related resources fail and can be configured to
>>>>> periodically check
>>>>>            : resource health.
>>>>>
>>>>> [root@alamot80 ~]#
>>>>>
>>>>> Should I have installed the Heartbeat and Pacemaker from a different
>>>>> place?
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Babak
>>>>>
>>>>>
>>>>>
>>>>> Dejan Muhamedagic wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> On Sun, Jan 09, 2011 at 10:59:15PM -0800, Avestan wrote:
>>>>>>>
>>>>>>> Hello,
>>>>>>>
>>>>>>> The problem with the using Heartbeat R1 was the serial cable "Null
>>>>>>> Cable".
>>>>>>> I have replace that and I am able to get the Heartbeat going using
>>>>>>> R1
>>>>>>> approach.
>>>>>>>
>>>>>>> As I mentioned before, I am trying to take advantage of Pacemaker
>>>>>>> CRM
>>>>>>> and
>>>>>>> here is my current ha.cf file which reflect some minor changes but I
>>>>>>> am
>>>>>>> still unable to get it working for Heartbeat + Pacemaker CRM.
>>>>>>>
>>>>>>> ha.cf
>>>>>>>
>>>>>>> # Heartbeat logging configuration
>>>>>>> debug           1
>>>>>>> debugfile       /var/log/ha-debug
>>>>>>> logfile         /var/log/ha-log
>>>>>>> logfacility     local0
>>>>>>>
>>>>>>> # Heartbeat cluster members
>>>>>>> node damavand80
>>>>>>> node alamot80
>>>>>>>
>>>>>>> # Heartbeat communication timing
>>>>>>> keepalive 2
>>>>>>> deadtime 32
>>>>>>> initdead 64
>>>>>>>
>>>>>>> # Heartbeat communication paths
>>>>>>> udpport 694
>>>>>>> #bcast  eth0
>>>>>>> #ucast eth1 192.168.1.XX
>>>>>>> #ucast eth1 192.168.1.XX
>>>>>>> #ucast eth0 192.168.1.XX
>>>>>>> #ucast eth0 192.168.1.XX
>>>>>>> baud 19200
>>>>>>
>>>>>> 19.2k won't do with the CRM, not enough bandwidth. Please use
>>>>>> one of the network links. Or at least 115.2k.
>>>>>>
>>>>>>> serial /dev/ttyS0
>>>>>>>
>>>>>>> # Don't fail back automatically - on/off
>>>>>>> auto_failback on
>>>>>>>
>>>>>>> # Monitoring of network connection to default gateway
>>>>>>> ping 70.90.189.190
>>>>>>>
>>>>>>> #respawn hacluster /usr/lib64/heartbeat/ipfail
>>>>>>>
>>>>>>> # Activate Heartbeat 2 Configuration
>>>>>>> #crm yes
>>>>>>> crm respawn
>>>>>>>
>>>>>>> # Allow to add dynamically a new node to the cluster
>>>>>>> #autojoin any
>>>>>>>
>>>>>>>
>>>>>>> As I was reading the log file and trying to figure out the issue,
>>>>>>> two
>>>>>>> things
>>>>>>> cought my attention which are:
>>>>>>>
>>>>>>> 1. Jan 09 22:40:02 alamot80 attrd: [3580]: CRIT: get_cluster_type:
>>>>>>> This
>>>>>>> installation of Pacemaker does not support the '(null)' cluster
>>>>>>> infrastructure.  Terminating.
>>>>>>
>>>>>> No heartbeat support in pacemaker? Where did you get the
>>>>>> pacemaker packages?
>>>>
>>>> Thats odd - fedora packages are still built with heartbeat support.
>>>>
>>>
>>> Or are supposed to at least, but clearly don't
>>>
>>> [root@pcmk-1 ~]# crm_report --features
>>> 1.1.4 - ac608e3491c7dfc3b3e3c36d966ae9b016f77065:  manpages ncurses
>>> cman cs-quorum corosync
>>> _______________________________________________
>>> Linux-HA mailing list
>>> [email protected]
>>> http://lists.linux-ha.org/mailman/listinfo/linux-ha
>>> See also: http://linux-ha.org/ReportingProblems
>>>
>>>
>>
>> --
>> View this message in context:
>> http://old.nabble.com/Problem-with-Heartbeat-3.0-%2B-Pacemaker-1.1-tp30629395p30642594.html
>> Sent from the Linux-HA mailing list archive at Nabble.com.
>>
>> _______________________________________________
>> Linux-HA mailing list
>> [email protected]
>> http://lists.linux-ha.org/mailman/listinfo/linux-ha
>> See also: http://linux-ha.org/ReportingProblems
> _______________________________________________
> Linux-HA mailing list
> [email protected]
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
> 
> 

-- 
View this message in context: 
http://old.nabble.com/Problem-with-Heartbeat-3.0-%2B-Pacemaker-1.1-tp30629395p30659593.html
Sent from the Linux-HA mailing list archive at Nabble.com.

_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to