search for: o2cb_keepalive_delay_m

...ACK=o2cb # O2CB_BOOTCLUSTER: If not empty, the name of a cluster to start. O2CB_BOOTCLUSTER=xx #O2CB_HEARTBEAT_THRESHOLD: Iterations before a node is considered dead. O2CB_HEARTBEAT_THRESHOLD= # O2CB_IDLE_TIMEOUT_MS: Time in ms before a network connection is considered dead. O2CB_IDLE_TIMEOUT_MS= # O2CB_KEEPALIVE_DELAY_MS: Max time in ms before a keepalive packet is sent O2CB_KEEPALIVE_DELAY_MS= # O2CB_RECONNECT_DELAY_MS: Min time in ms between connection attempts O2CB_RECONNECT_DELAY_MS= kernel version: 2.6.18-92.1.22.el5xen ocfs version: ocfs2-tools-1.4.2-1.el5 ocfs2-2.6.18-92.1.22.el5xen-1.4.2-1.el5 Thanks. -...

...OOTCLUSTER: If not empty, the name of a cluster to start. O2CB_BOOTCLUSTER=ocfs2 # O2CB_HEARTBEAT_THRESHOLD: Iterations before a node is considered dead. O2CB_HEARTBEAT_THRESHOLD=151 # O2CB_IDLE_TIMEOUT_MS: Time in ms before a network connection is considered dead. O2CB_IDLE_TIMEOUT_MS=10000 # O2CB_KEEPALIVE_DELAY_MS: Max time in ms before a keepalive packet is sent O2CB_KEEPALIVE_DELAY_MS=5000 # O2CB_RECONNECT_DELAY_MS: Min time in ms between connection attempts O2CB_RECONNECT_DELAY_MS=2000 # O2CB_HEARTBEAT_MODE: Whether to use the native "kernel" or the "user" # driven heartbeat (for ex...

Hi to all, this is My first time on this mailinglist. I have a problem with Ocfs2 on Debian etch 4.0 I'd like when a node go down or freeze without unmount the ocfs2 partition the heartbeat not fence the server that work well ( kernel panic ). I'd like disable or heartbeat or fencing. So we can work also with only 1 node. Thanks

...# O2CB_BOOTCLUSTER: If not empty, the name of a cluster to start. O2CB_BOOTCLUSTER=pbx # O2CB_HEARTBEAT_THRESHOLD: Iterations before a node is considered dead. O2CB_HEARTBEAT_THRESHOLD= # O2CB_IDLE_TIMEOUT_MS: Time in ms before a network connection is considered dead. O2CB_IDLE_TIMEOUT_MS= # O2CB_KEEPALIVE_DELAY_MS: Max time in ms before a keepalive packet is sent O2CB_KEEPALIVE_DELAY_MS= # O2CB_RECONNECT_DELAY_MS: Min time in ms between connection attempts O2CB_RECONNECT_DELAY_MS= [root at pbx_1 ~]# tail /etc/ocfs2/cluster.conf ip_port = 7777 ip_address = 10.128.7.255 number = 254 name = pbx_255.c1...

...t; # O2CB_HEARTBEAT_THRESHOLD: Iterations before a node is considered dead. >>> O2CB_HEARTBEAT_THRESHOLD= >>> >>> # O2CB_IDLE_TIMEOUT_MS: Time in ms before a network connection is >>> considered dead. >>> O2CB_IDLE_TIMEOUT_MS= >>> >>> # O2CB_KEEPALIVE_DELAY_MS: Max time in ms before a keepalive packet is >>> sent >>> O2CB_KEEPALIVE_DELAY_MS= >>> >>> # O2CB_RECONNECT_DELAY_MS: Min time in ms between connection attempts >>> O2CB_RECONNECT_DELAY_MS= >>> >>> # O2CB_HEARTBEAT_MODE: Whether to use...

...2CB_BOOTCLUSTER: If not empty, the name of a cluster to start. O2CB_BOOTCLUSTER=pacemaker # O2CB_HEARTBEAT_THRESHOLD: Iterations before a node is considered dead. O2CB_HEARTBEAT_THRESHOLD= # O2CB_IDLE_TIMEOUT_MS: Time in ms before a network connection is considered dead. O2CB_IDLE_TIMEOUT_MS= # O2CB_KEEPALIVE_DELAY_MS: Max time in ms before a keepalive packet is sent O2CB_KEEPALIVE_DELAY_MS= # O2CB_RECONNECT_DELAY_MS: Min time in ms between connection attempts O2CB_RECONNECT_DELAY_MS= 7)nodo5:~ # mount /dev/mapper/xenconfig_part1 /etc/xen/vm/ mount.ocfs2: Invalid argument while mounting /dev/mapper/xenconfig...

...his works, of only one clustermember is active for ocfs. At the moment there are two clustermembers, at least one crashes often both clients does a reboot. The the timeouts are the following O2CB_ENABLED=true O2CB_BOOTCLUSTER=debianocfs O2CB_HEARTBEAT_THRESHOLD=61 O2CB_IDLE_TIMEOUT_MS=90000 O2CB_KEEPALIVE_DELAY_MS=2000 O2CB_RECONNECT_DELAY_MS=2000 in the attachment i have the Dell multipath.conf. failback is already to manual, so it does least controller switches. what could be the reason for the crashes? best regards thomas -------------- next part -------------- An HTML attachment was scrubbed.....

I am trying to mount the same partition from a KVM ubuntu 8.04.1 virtual machine and on an ubuntu 8.04.1 host server. I am able to mount the partition just on fine on two ubuntu host servers, they both talk to each other. The logs on both servers show the other machine mounting and unmounting the drive. However, when I mount the drive in the KVM VM I get no communication to the host

...unmount the file system, so we hard-panic'd (insmod panic.ko). Vitals: - Linux mgr01 2.6.18-164.2.1.el5 #1 SMP Wed Sep 30 12:52:46 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux - ocfs2-2.6.18-164.2.1.el5-1.4.4-1.el5 - MD3000i iSCSI - O2CB_HEARTBEAT_THRESHOLD=61 - O2CB_IDLE_TIMEOUT_MS=30000 - O2CB_KEEPALIVE_DELAY_MS=2000 - O2CB_RECONNECT_DELAY_MS=2000 - iSCSI node.session.timeo.replacement_timeout = 120 - iSCSI node.conn[0].timeo.noop_out_interval = 5 - node.conn[0].timeo.noop_out_timeout = 5 Logs at the time of failure on mgr01: Nov 6 01:00:12 mgr01 kernel: connection1:0: ping timeout of 5 secs expi...

Hi, everyone I have some questions with the OCFS2 when using it as vm-store. With Ubuntu 1204, kernel version is 3.2.40, and ocfs2-tools version is 1.6.4. As the network configure change, there are some issues as the log below. Why is there the information of "Node 255 (he) is the Recovery Master for the dead node 255" in the syslog? Why the host ZHJD-VM6 is blocked until it reboot

Hi, everyone I have some questions with the OCFS2 when using it as vm-store. With Ubuntu 1204, kernel version is 3.2.40, and ocfs2-tools version is 1.6.4. As the network configure change, there are some issues as the log below. Why is there the information of "Node 255 (he) is the Recovery Master for the dead node 255" in the syslog? Why the host ZHJD-VM6 is blocked until it reboot