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? Thanks, Dejan _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
