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
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.

2. Jan 09 22:40:02 alamot80 cib: [3577]: WARN: retrieveCib: Cluster
configuration not found: /var/lib/heartbeat/crm/cib.xml

and the cib.xml is never generated when I check it under location "ls -la
/var/lib/heartbeat/crm/" as shown here:

[r...@alamot80 ~]# ls -la /var/lib/heartbeat/crm/
total 8
drwxr-x---. 2 hacluster haclient 4096 Dec  8 02:59 .
drwxr-xr-x. 4 root      root     4096 Jan  9 22:40 ..
[r...@alamot80 ~]#

And here is the what I get in my log file when I set the "debug 1" in the
configuration file:

[r...@alamot80 ~]# tail -f /var/log/ha-log
Jan 09 19:58:34 alamot80 heartbeat: [1824]: info: killing HBREAD process
1849 with signal 15
Jan 09 19:58:34 alamot80 heartbeat: [1824]: info: killing HBWRITE process
1851 with signal 15
Jan 09 19:58:34 alamot80 heartbeat: [1824]: info: killing HBREAD process
1852 with signal 15
Jan 09 19:58:34 alamot80 heartbeat: [1824]: info: killing HBFIFO process
1844 with signal 15
Jan 09 19:58:34 alamot80 heartbeat: [1824]: info: Core process 1852 exited.
5 remaining
Jan 09 19:58:34 alamot80 heartbeat: [1824]: info: Core process 1851 exited.
4 remaining
Jan 09 19:58:34 alamot80 heartbeat: [1824]: info: Core process 1849 exited.
3 remaining
Jan 09 19:58:34 alamot80 heartbeat: [1824]: info: Core process 1844 exited.
2 remaining
Jan 09 19:58:34 alamot80 heartbeat: [1824]: info: Core process 1848 exited.
1 remaining
Jan 09 19:58:34 alamot80 heartbeat: [1824]: info: alamot80 Heartbeat
shutdown complete.
Jan 09 22:38:56 alamot80 heartbeat: [3557]: info: Version 2 support: respawn
Jan 09 22:38:56 alamot80 heartbeat: [3557]: WARN: File
/etc/ha.d//haresources exists.
Jan 09 22:38:56 alamot80 heartbeat: [3557]: WARN: This file is not used
because crm is enabled
Jan 09 22:38:56 alamot80 heartbeat: [3557]: info: respawn directive: 
hacluster /usr/lib/heartbeat/ccm
Jan 09 22:38:56 alamot80 heartbeat: [3557]: info: respawn directive: 
hacluster /usr/lib/heartbeat/cib
Jan 09 22:38:56 alamot80 heartbeat: [3557]: info: respawn directive: root
/usr/lib/heartbeat/lrmd -r
Jan 09 22:38:56 alamot80 heartbeat: [3557]: info: respawn directive: root
/usr/lib/heartbeat/stonithd
Jan 09 22:38:56 alamot80 heartbeat: [3557]: info: respawn directive: 
hacluster /usr/lib/heartbeat/attrd
Jan 09 22:38:56 alamot80 heartbeat: [3557]: info: respawn directive: 
hacluster /usr/lib/heartbeat/crmd
Jan 09 22:38:56 alamot80 heartbeat: [3557]: info: AUTH: i=1: key =
0x89da790, auth=0x3edc30, authname=sha1
Jan 09 22:38:56 alamot80 heartbeat: [3557]: WARN: Logging daemon is disabled
--enabling logging daemon is recommended
Jan 09 22:38:56 alamot80 heartbeat: [3557]: info: **************************
Jan 09 22:38:56 alamot80 heartbeat: [3557]: info: Configuration validated.
Starting heartbeat 3.0.0
Jan 09 22:38:56 alamot80 heartbeat: [3557]: info: Heartbeat Hg Version:
node: 0daab7da36a8a3b9c29f6b2955a0f9613bf0be8d
Jan 09 22:38:56 alamot80 heartbeat: [3558]: info: heartbeat: version 3.0.0
Jan 09 22:38:56 alamot80 heartbeat: [3558]: info: Heartbeat generation:
1294595277
Jan 09 22:38:57 alamot80 heartbeat: [3558]: info: glib: Starting serial
heartbeat on tty /dev/ttyS0 (19200 baud)
Jan 09 22:38:57 alamot80 heartbeat: [3558]: info: glib: ping heartbeat
started.
Jan 09 22:38:57 alamot80 heartbeat: [3558]: info: G_main_add_TriggerHandler:
Added signal manual handler
Jan 09 22:38:57 alamot80 heartbeat: [3558]: info: G_main_add_TriggerHandler:
Added signal manual handler
Jan 09 22:38:57 alamot80 heartbeat: [3558]: info: G_main_add_SignalHandler:
Added signal handler for signal 17
Jan 09 22:38:57 alamot80 heartbeat: [3558]: info: Local status now set to:
'up'
Jan 09 22:38:57 alamot80 heartbeat: [3558]: info: Managed
write_hostcachedata process 3568 exited with return code 0.
Jan 09 22:39:05 alamot80 heartbeat: [3558]: info: Link damavand80:/dev/ttyS0
up.
Jan 09 22:39:05 alamot80 heartbeat: [3558]: info: Status update for node
damavand80: status up
Jan 09 22:39:05 alamot80 heartbeat: [3558]: info: Managed
write_hostcachedata process 3569 exited with return code 0.
Jan 09 22:40:01 alamot80 heartbeat: [3558]: WARN: node 70.90.189.190: is
dead
Jan 09 22:40:02 alamot80 heartbeat: [3558]: info: Comm_now_up(): updating
status to active
Jan 09 22:40:02 alamot80 heartbeat: [3558]: info: Local status now set to:
'active'
Jan 09 22:40:02 alamot80 heartbeat: [3558]: info: Starting child client
"/usr/lib/heartbeat/ccm" (489,480)
Jan 09 22:40:02 alamot80 heartbeat: [3558]: info: Starting child client
"/usr/lib/heartbeat/cib" (489,480)
Jan 09 22:40:02 alamot80 heartbeat: [3558]: info: Starting child client
"/usr/lib/heartbeat/lrmd -r" (0,0)
Jan 09 22:40:02 alamot80 heartbeat: [3558]: info: Starting child client
"/usr/lib/heartbeat/stonithd" (0,0)
Jan 09 22:40:02 alamot80 heartbeat: [3558]: info: Starting child client
"/usr/lib/heartbeat/attrd" (489,480)
Jan 09 22:40:02 alamot80 heartbeat: [3558]: info: Starting child client
"/usr/lib/heartbeat/crmd" (489,480)
Jan 09 22:40:02 alamot80 heartbeat: [3581]: info: Starting
"/usr/lib/heartbeat/crmd" as uid 489  gid 480 (pid 3581)
Jan 09 22:40:02 alamot80 heartbeat: [3579]: info: Starting
"/usr/lib/heartbeat/stonithd" as uid 0  gid 0 (pid 3579)
Jan 09 22:40:02 alamot80 heartbeat: [3578]: info: Starting
"/usr/lib/heartbeat/lrmd -r" as uid 0  gid 0 (pid 3578)
Jan 09 22:40:02 alamot80 heartbeat: [3580]: info: Starting
"/usr/lib/heartbeat/attrd" as uid 489  gid 480 (pid 3580)
Jan 09 22:40:02 alamot80 heartbeat: [3577]: info: Starting
"/usr/lib/heartbeat/cib" as uid 489  gid 480 (pid 3577)
Jan 09 22:40:02 alamot80 heartbeat: [3576]: info: Starting
"/usr/lib/heartbeat/ccm" as uid 489  gid 480 (pid 3576)
Jan 09 22:40:02 alamot80 heartbeat: [3558]: info: Managed
write_hostcachedata process 3582 exited with return code 0.
Jan 09 22:40:02 alamot80 heartbeat: [3558]: info: Managed write_delcachedata
process 3583 exited with return code 0.
Jan 09 22:40:02 alamot80 lrmd: [3578]: info: G_main_add_SignalHandler: Added
signal handler for signal 15
Jan 09 22:40:02 alamot80 attrd: [3580]: info: Invoked:
/usr/lib/heartbeat/attrd
Jan 09 22:40:02 alamot80 attrd: [3580]: info: crm_log_init_worker: Changed
active directory to /var/lib/heartbeat/cores/hacluster
Jan 09 22:40:02 alamot80 attrd: [3580]: info: main: Starting up
Jan 09 22:40:02 alamot80 attrd: [3580]: CRIT: get_cluster_type: This
installation of Pacemaker does not support the '(null)' cluster
infrastructure.  Terminating.
Jan 09 22:40:02 alamot80 heartbeat: [3558]: WARN: Managed
/usr/lib/heartbeat/attrd process 3580 exited with return code 100.
Jan 09 22:40:02 alamot80 heartbeat: [3558]: ERROR: Client
/usr/lib/heartbeat/attrd exited with return code 100.
Jan 09 22:40:02 alamot80 crmd: [3581]: info: Invoked:
/usr/lib/heartbeat/crmd
Jan 09 22:40:02 alamot80 crmd: [3581]: info: crm_log_init_worker: Changed
active directory to /var/lib/heartbeat/cores/hacluster
Jan 09 22:40:02 alamot80 crmd: [3581]: info: main: CRM Hg Version:
ac608e3491c7dfc3b3e3c36d966ae9b016f77065

Jan 09 22:40:02 alamot80 crmd: [3581]: info: crmd_init: Starting crmd
Jan 09 22:40:02 alamot80 crmd: [3581]: info: G_main_add_SignalHandler: Added
signal handler for signal 17
Jan 09 22:40:02 alamot80 stonith-ng: [3579]: info: Invoked:
/usr/lib/heartbeat/stonithd
Jan 09 22:40:02 alamot80 stonith-ng: [3579]: info: crm_log_init_worker:
Changed active directory to /var/lib/heartbeat/cores/root
Jan 09 22:40:02 alamot80 stonith-ng: [3579]: info: G_main_add_SignalHandler:
Added signal handler for signal 17
Jan 09 22:40:02 alamot80 stonith-ng: [3579]: CRIT: get_cluster_type: This
installation of Pacemaker does not support the '(null)' cluster
infrastructure.  Terminating.
Jan 09 22:40:02 alamot80 heartbeat: [3558]: WARN: Managed
/usr/lib/heartbeat/stonithd process 3579 exited with return code 100.
Jan 09 22:40:02 alamot80 heartbeat: [3558]: ERROR: Client
/usr/lib/heartbeat/stonithd exited with return code 100.
Jan 09 22:40:02 alamot80 ccm: [3576]: info: Hostname: alamot80
Jan 09 22:40:02 alamot80 lrmd: [3578]: info: G_main_add_SignalHandler: Added
signal handler for signal 17
Jan 09 22:40:02 alamot80 lrmd: [3578]: info: enabling coredumps
Jan 09 22:40:02 alamot80 lrmd: [3578]: info: G_main_add_SignalHandler: Added
signal handler for signal 10
Jan 09 22:40:02 alamot80 lrmd: [3578]: info: G_main_add_SignalHandler: Added
signal handler for signal 12
Jan 09 22:40:02 alamot80 lrmd: [3578]: info: Started.
Jan 09 22:40:02 alamot80 cib: [3577]: info: Invoked: /usr/lib/heartbeat/cib
Jan 09 22:40:02 alamot80 cib: [3577]: info: crm_log_init_worker: Changed
active directory to /var/lib/heartbeat/cores/hacluster
Jan 09 22:40:02 alamot80 cib: [3577]: info: G_main_add_TriggerHandler: Added
signal manual handler
Jan 09 22:40:02 alamot80 cib: [3577]: info: G_main_add_SignalHandler: Added
signal handler for signal 17
Jan 09 22:40:02 alamot80 cib: [3577]: info: retrieveCib: Reading cluster
configuration from: /var/lib/heartbeat/crm/cib.xml (digest:
/var/lib/heartbeat/crm/cib.xml.sig)
Jan 09 22:40:02 alamot80 cib: [3577]: WARN: retrieveCib: Cluster
configuration not found: /var/lib/heartbeat/crm/cib.xml
Jan 09 22:40:02 alamot80 cib: [3577]: WARN: readCibXmlFile: Primary
configuration corrupt or unusable, trying backup...
Jan 09 22:40:02 alamot80 cib: [3577]: WARN: readCibXmlFile: Continuing with
an empty configuration.
Jan 09 22:40:02 alamot80 cib: [3577]: info: validate_with_relaxng: Creating
RNG parser context
Jan 09 22:40:03 alamot80 cib: [3577]: info: startCib: CIB Initialization
completed successfully
Jan 09 22:40:03 alamot80 cib: [3577]: CRIT: get_cluster_type: This
installation of Pacemaker does not support the '(null)' cluster
infrastructure.  Terminating.
Jan 09 22:40:03 alamot80 heartbeat: [3558]: WARN: Managed
/usr/lib/heartbeat/cib process 3577 exited with return code 100.
Jan 09 22:40:03 alamot80 heartbeat: [3558]: ERROR: Client
/usr/lib/heartbeat/cib exited with return code 100.
Jan 09 22:40:03 alamot80 crmd: [3581]: info: do_cib_control: Could not
connect to the CIB service: connection failed
Jan 09 22:40:03 alamot80 crmd: [3581]: WARN: do_cib_control: Couldn't
complete CIB registration 1 times... pause and retry
Jan 09 22:40:03 alamot80 crmd: [3581]: info: crmd_init: Starting crmd's
mainloop
Jan 09 22:40:05 alamot80 crmd: [3581]: info: crm_timer_popped: Wait Timer
(I_NULL) just popped!
Jan 09 22:40:06 alamot80 ccm: [3576]: info: G_main_add_SignalHandler: Added
signal handler for signal 15
Jan 09 22:40:06 alamot80 crmd: [3581]: info: do_cib_control: Could not
connect to the CIB service: connection failed
Jan 09 22:40:06 alamot80 crmd: [3581]: WARN: do_cib_control: Couldn't
complete CIB registration 2 times... pause and retry
Jan 09 22:40:08 alamot80 crmd: [3581]: info: crm_timer_popped: Wait Timer
(I_NULL) just popped!
Jan 09 22:40:09 alamot80 crmd: [3581]: info: do_cib_control: Could not
connect to the CIB service: connection failed
Jan 09 22:40:09 alamot80 crmd: [3581]: WARN: do_cib_control: Couldn't
complete CIB registration 3 times... pause and retry
Jan 09 22:40:10 alamot80 heartbeat: [3558]: info: Status update for node
damavand80: status active
Jan 09 22:40:11 alamot80 crmd: [3581]: info: crm_timer_popped: Wait Timer
(I_NULL) just popped!
Jan 09 22:40:12 alamot80 crmd: [3581]: info: do_cib_control: Could not
connect to the CIB service: connection failed
Jan 09 22:40:12 alamot80 crmd: [3581]: WARN: do_cib_control: Couldn't
complete CIB registration 4 times... pause and retry
Jan 09 22:40:14 alamot80 crmd: [3581]: info: crm_timer_popped: Wait Timer
(I_NULL) just popped!
Jan 09 22:40:15 alamot80 crmd: [3581]: info: do_cib_control: Could not
connect to the CIB service: connection failed
Jan 09 22:40:15 alamot80 crmd: [3581]: WARN: do_cib_control: Couldn't
complete CIB registration 5 times... pause and retry
Jan 09 22:40:17 alamot80 crmd: [3581]: info: crm_timer_popped: Wait Timer
(I_NULL) just popped!
Jan 09 22:40:18 alamot80 crmd: [3581]: info: do_cib_control: Could not
connect to the CIB service: connection failed
Jan 09 22:40:18 alamot80 crmd: [3581]: WARN: do_cib_control: Couldn't
complete CIB registration 6 times... pause and retry
Jan 09 22:40:20 alamot80 crmd: [3581]: info: crm_timer_popped: Wait Timer
(I_NULL) just popped!
Jan 09 22:40:21 alamot80 crmd: [3581]: info: do_cib_control: Could not
connect to the CIB service: connection failed
Jan 09 22:40:21 alamot80 crmd: [3581]: WARN: do_cib_control: Couldn't
complete CIB registration 7 times... pause and retry
Jan 09 22:40:23 alamot80 crmd: [3581]: info: crm_timer_popped: Wait Timer
(I_NULL) just popped!
Jan 09 22:40:24 alamot80 crmd: [3581]: info: do_cib_control: Could not
connect to the CIB service: connection failed
Jan 09 22:40:24 alamot80 crmd: [3581]: WARN: do_cib_control: Couldn't
complete CIB registration 8 times... pause and retry
Jan 09 22:40:26 alamot80 crmd: [3581]: info: crm_timer_popped: Wait Timer
(I_NULL) just popped!
Jan 09 22:40:27 alamot80 crmd: [3581]: info: do_cib_control: Could not
connect to the CIB service: connection failed
Jan 09 22:40:27 alamot80 crmd: [3581]: WARN: do_cib_control: Couldn't
complete CIB registration 9 times... pause and retry
Jan 09 22:40:29 alamot80 crmd: [3581]: info: crm_timer_popped: Wait Timer
(I_NULL) just popped!
Jan 09 22:40:30 alamot80 crmd: [3581]: info: do_cib_control: Could not
connect to the CIB service: connection failed
Jan 09 22:40:30 alamot80 crmd: [3581]: WARN: do_cib_control: Couldn't
complete CIB registration 10 times... pause and retry
Jan 09 22:40:32 alamot80 crmd: [3581]: info: crm_timer_popped: Wait Timer
(I_NULL) just popped!
Jan 09 22:40:33 alamot80 crmd: [3581]: info: do_cib_control: Could not
connect to the CIB service: connection failed
Jan 09 22:40:33 alamot80 crmd: [3581]: WARN: do_cib_control: Couldn't
complete CIB registration 11 times... pause and retry
Jan 09 22:40:35 alamot80 crmd: [3581]: info: crm_timer_popped: Wait Timer
(I_NULL) just popped!
Jan 09 22:40:36 alamot80 crmd: [3581]: info: do_cib_control: Could not
connect to the CIB service: connection failed
Jan 09 22:40:36 alamot80 crmd: [3581]: WARN: do_cib_control: Couldn't
complete CIB registration 12 times... pause and retry
Jan 09 22:40:38 alamot80 heartbeat: [3558]: info: killing
/usr/lib/heartbeat/crmd process group 3581 with signal 15
Jan 09 22:40:38 alamot80 crmd: [3581]: info: crm_signal_dispatch: Invoking
handler for signal 15: Terminated
Jan 09 22:40:38 alamot80 crmd: [3581]: info: crm_shutdown: Requesting
shutdown
Jan 09 22:40:38 alamot80 crmd: [3581]: info: crm_shutdown: Using default
shutdown escalation: 1200000ms
Jan 09 22:40:38 alamot80 crmd: [3581]: WARN: do_log: FSA: Input I_SHUTDOWN
from crm_shutdown() received in state S_STARTING
Jan 09 22:40:38 alamot80 crmd: [3581]: info: do_state_transition: State
transition S_STARTING -> S_STOPPING [ input=I_SHUTDOWN cause=C_SHUTDOWN
origin=crm_shutdown ]
Jan 09 22:40:38 alamot80 crmd: [3581]: CRIT: get_cluster_type: This
installation of Pacemaker does not support the '(null)' cluster
infrastructure.  Terminating.
Jan 09 22:40:38 alamot80 heartbeat: [3558]: info: client
[/usr/lib/heartbeat/attrd] is not running.
Jan 09 22:40:38 alamot80 heartbeat: [3558]: info: client
[/usr/lib/heartbeat/stonithd] is not running.
Jan 09 22:40:38 alamot80 heartbeat: [3558]: info: killing
/usr/lib/heartbeat/lrmd -r process group 3578 with signal 15
Jan 09 22:40:38 alamot80 lrmd: [3578]: info: lrmd is shutting down
Jan 09 22:40:38 alamot80 heartbeat: [3558]: info: client
[/usr/lib/heartbeat/cib] is not running.
Jan 09 22:40:38 alamot80 heartbeat: [3558]: info: killing
/usr/lib/heartbeat/ccm process group 3576 with signal 15
Jan 09 22:40:38 alamot80 ccm: [3576]: info: received SIGTERM, going to shut
down
Jan 09 22:40:39 alamot80 heartbeat: [3558]: info: killing HBFIFO process
3563 with signal 15
Jan 09 22:40:39 alamot80 heartbeat: [3558]: info: killing HBREAD process
3565 with signal 15
Jan 09 22:40:39 alamot80 heartbeat: [3558]: info: killing HBWRITE process
3566 with signal 15
Jan 09 22:40:39 alamot80 heartbeat: [3558]: info: killing HBREAD process
3567 with signal 15
Jan 09 22:40:39 alamot80 heartbeat: [3558]: info: killing HBWRITE process
3564 with signal 15
Jan 09 22:40:39 alamot80 heartbeat: [3558]: info: Core process 3567 exited.
5 remaining
Jan 09 22:40:39 alamot80 heartbeat: [3558]: info: Core process 3564 exited.
4 remaining
Jan 09 22:40:39 alamot80 heartbeat: [3558]: info: Core process 3563 exited.
3 remaining
Jan 09 22:40:39 alamot80 heartbeat: [3558]: info: Core process 3565 exited.
2 remaining
Jan 09 22:40:39 alamot80 heartbeat: [3558]: info: Core process 3566 exited.
1 remaining
Jan 09 22:40:39 alamot80 heartbeat: [3558]: info: alamot80 Heartbeat
shutdown complete.

Thank you in advance for your help.

Avestan :o)






Igor Chudov-3 wrote:
> 
> look for logfile.1.gz or something
> 
> On Sun, Jan 9, 2011 at 4:24 PM, Avestan <[email protected]>
> wrote:
> 
>>
>> Hello again,
>>
>> you may ask why I didn't copy/past what is in the log file. My humble
>> apology, the log file is empty with no message in it! %-|
>>
>> I also tried the heartbest with the same R1 setting that I have on my
>> production, and doing so results the both machine take control of the
>> resources! %-| and since I am using IPaddr in my "haresources" file, both
>> machine claims to have the floating IP address.
>>
>> Thanks,
>>
>> Avestan
>>
>>
>>
>> Avestan wrote:
>> >
>> > Hello,
>> >
>> > I have been using Heartbeat R1 for a long time and have been pretty
>> > satisfied with it.  Now, I am trying to move to Heartbeat and Pacemaker
>> as
>> > the CRM and I have followed the information
>> >
>> >  http://blog.foaa.de/2010/10/intro-to-pacemaker-on-heartbeat/ Here
>> >
>> > I said, I am trying since I am unable to get this going and the
>> following
>> > is the my setting and configuration:
>> >
>> > [r...@damavand80 ~]# rpm -qa|grep -i heartbeat
>> > heartbeat-libs-3.0.0-0.7.0daab7da36a8.hg.fc14.i686
>> > heartbeat-3.0.0-0.7.0daab7da36a8.hg.fc14.i686
>> > [r...@damavand80 ~]#
>> > [r...@damavand80 ~]# rpm -qa|grep -i pacemaker
>> > pacemaker-libs-1.1.4-4.fc14.i686
>> > pacemaker-1.1.4-4.fc14.i686
>> > [r...@damavand80 ~]#
>> >
>> > and the following is the configuration file "ha.cf":
>> >
>> > # enable pacemaker, without stonith
>> > crm             yes
>> >
>> > # Heartbeat logging configuration
>> > debugfile       /var/log/ha-debug
>> > logfile         /var/log/ha-log
>> > logfacility     local0
>> >
>> > # warning of soon be dead
>> > warntime        10
>> >
>> > # declare a host (the other node) dead after:
>> > deadtime        20
>> >
>> > # dead time on boot (could take some time until net is up)
>> > initdead        120
>> >
>> > # time between heartbeats
>> > keepalive       2
>> >
>> > # the nodes
>> > node            alamot80
>> > node            damavand80
>> >
>> > # heartbeats, over the serial cable!
>> > baud            19200
>> > serial          /dev/ttyS0
>> >
>> > # ping the switch to assure we are online
>> > ping            192.168.178.1
>> >
>> > The problem is when I start the heartbeat on both machines, the
>> machines
>> > become all of the sudden very busy and I lose ssh connection to them
>> and
>> > after a while I can connect to the machine via ssh and once again I
>> lose
>> > connection and heartbeat doesn't seem to be working.
>> >
>> > In advance I would like to thank you for your help.
>> >
>> > Avestan :drunk:
>> >
>>
>> --
>> View this message in context:
>> http://old.nabble.com/Problem-with-Heartbeat-3.0-%2B-Pacemaker-1.1-tp30629395p30629789.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-tp30629395p30631496.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