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: > > [r...@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) > > [r...@alamot80 ~]# > [r...@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. > > [r...@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. _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
