search for: o2cb_enabled

....1.35 number = 0 name = x1 cluster = xx node: ip_port = 7777 ip_address = 192.168.1.36 number = 1 name = x2 cluster = xx cluster: node_count = 2 name = xx o2cb: # 'dpkg-reconfigure ocfs2-tools'. # # O2CB_ENABLED: 'true' means to load the driver on boot. O2CB_ENABLED=true # O2CB_STACK: The name of the cluster stack backing O2CB. O2CB_STACK=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....

Hi I have: SLES 10 SP2 (2.6.16.60-0.21-smp) ocfs2-tools-1.4.0-0.3 ocfs2console-1.4.0-0.3 and I can't change "heartbeat dead threshold" value. Content of /etc/sysconfig/o2cb: # O2CB_ENABLED: 'true' means to load the driver on boot. O2CB_ENABLED=true # O2CB_BOOTCLUSTER: 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 be...

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

...Thanks -Bret [root at pbx_1 ~]# cat /etc/sysconfig/o2cb # # This is a configuration file for automatic startup of the O2CB # driver. It is generated by running /etc/init.d/o2cb configure. # On Debian based systems the preferred method is running # 'dpkg-reconfigure ocfs2-tools'. # # O2CB_ENABLED: 'true' means to load the driver on boot. O2CB_ENABLED=true # O2CB_STACK: The name of the cluster stack backing O2CB. O2CB_STACK=o2cb # O2CB_BOOTCLUSTER: If not empty, the name of a cluster to start. O2CB_BOOTCLUSTER=pbx # O2CB_HEARTBEAT_THRESHOLD: Iterations before a node is considered...

...onfiguration file for automatic startup of the O2CB >>> # driver. ?It is generated by running /etc/init.d/o2cb configure. >>> # On Debian based systems the preferred method is running >>> # 'dpkg-reconfigure ocfs2-tools'. >>> # >>> >>> # O2CB_ENABLED: 'true' means to load the driver on boot. >>> O2CB_ENABLED=true >>> >>> # O2CB_BOOTCLUSTER: If not empty, the name of a cluster to start. >>> O2CB_BOOTCLUSTER=ocfs2 >>> >>> # O2CB_HEARTBEAT_THRESHOLD: Iterations before a node is consider...

...mkfs.ocfs2 successful 6)this is the /etc/sysconfig/o2cb file # # This is a configuration file for automatic startup of the O2CB # driver. It is generated by running /etc/init.d/o2cb configure. # On Debian based systems the preferred method is running # 'dpkg-reconfigure ocfs2-tools'. # # O2CB_ENABLED: 'true' means to load the driver on boot. O2CB_ENABLED=true # O2CB_STACK: The name of the cluster stack backing O2CB. O2CB_STACK=pcmk # O2CB_BOOTCLUSTER: If not empty, the name of a cluster to start. O2CB_BOOTCLUSTER=pacemaker # O2CB_HEARTBEAT_THRESHOLD: Iterations before a node is consi...

...itrd-2.6.9-34.ELsmp.img title Red Hat Enterprise Linux AS-up (2.6.9-34.EL) root (hd0,0) kernel /vmlinuz-2.6.9-34.EL ro root=/dev/VolGroup00/LogVol00 elevator=deadline vga=0xf05 initrd /initrd-2.6.9-34.EL.img [root at rac1 ~]# --- [root at rac1 ~]# cat /etc/sysconfig/o2cb O2CB_ENABLED=true O2CB_BOOTCLUSTER=ocfs2 O2CB_HEARTBEAT_THRESHOLD=16 [root at rac1 ~]# --- Crash message: --- Apr 18 15:54:43 rac1/rac1 (2858,1):o2net_set_nn_state:426 accepted connection from node rac2 (num 1) at 10.0.1.2:7777 Apr 18 15:54:47 rac1/rac1 (2858,1):__dlm_print_nodes:384 Nodes in my domain (&qu...

...logs on the bottom of this message. I saw some other people is getting on a similar trouble (http://www.mail-archive.com/ocfs2-users@oss.oracle.com/msg01135.html) but the thread don't gave me help... Anyone has any idea? Thanks you in advance. Maurizio web-ha1:~ # cat /etc/sysconfig/o2cb O2CB_ENABLED=true O2CB_BOOTCLUSTER=ocfs2 O2CB_HEARTBEAT_THRESHOLD=451 web-ha1:~ # web-ha1:~ # cat /etc/ocfs2/cluster.conf node: ip_port = 7777 ip_address = 192.168.255.1 number = 0 name = web-ha1 cluster = ocfs2 node: ip_port = 7777 ip_address = 192.168....

...set the active controller to offline, the client should initiate an failover to the second controller. this 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...