search for: ctdb_recovery_lock

Hello list, I compiled the CTDB version from samba.org::ftp/unpacked/ctdb with the parameter: " --prefix= " This I did on CentOS 5.5 Then I copy and edit ctdb.sysconfig from /usr/src/ctdb/config to /etc/sysconfig/ctdb I set CTDB_RECOVERY_LOCK="/share/ctdb_lock/lock_file" on all three nodes. Every node can read and write on /share. When I try to start ctdb it start successful with [OK]. But it print the message "No recovery lock specified. Starting CTBD without split brain prevention." When I start the ctdbd with th...

...clones, they don't behave identically : when shutting down node 1, node 0 takes over every part of ctdb setup (ip, recmaster, services). But when I stop ctdb daemon on node 1, though ctdb node 0 correctly stops its children daemons (nmbd, smbd and winbind) and kills itself, node 1 claims : ctdb_recovery_lock: Failed to get recovery lock on '/ctdb/.ctdb.lock' (This directory is clvm + gfs2 shared, writable and correctly accessible from both nodes) This leads node 1 to get banned. Then, (I guess), when being unbanned, reelection occurs, but I get : Recmaster node 1 no longer available. Force...

...68.11.20 192.168.11.24" dns_search="kl01.amtb-m.org.my" routes_enp2s0="default via 192.168.11.10" routes_enp2s2="default via 192.168.11.10" routes_enp2s3="default via 192.168.11.10" routes_enp2s4="default via 192.168.11.10" */etc/conf.d/ctdb* CTDB_RECOVERY_LOCK=/amtb/.ctdb.lock CTDB_PUBLIC_ADDRESSES=/etc/ctdb/public_addresses CTDB_MANAGES_SAMBA=yes CTDB_SAMBA_SKIP_SHARE_CHECK=yes CTDB_NFS_SKIP_SHARE_CHECK=yes CTDB_MANAGES_WINBIND=yes CTDB_MANAGES_VSFTPD=no CTDB_MANAGES_ISCSI=no CTDB_MANAGES_NFS=no CTDB_MANAGES_HTTPD=no CTDB_SYSLOG=yes CTDB_DEBUGLEVEL=NOTI...

...and openvz patch) Network: Guest has full control of eth1 node1 Guest: Ubuntu 10.04 x86 Host: VMWare ESXI 4 x86_64 Network: Guest adapter bridged to host node2 Guest: Ubuntu 10.04 x86_64 Host: VMWare Player (Windows 7) Network: Guest adapter bridged to host Our config: /etc/default/ctdb CTDB_RECOVERY_LOCK="mnt/data/lockfile" CTDB_PUBLIC_INTERFACE=eth1 # varies per server CTDB_PUBLIC_ADDRESSES=/etc/ctdb/public_addresses CTDB_MANAGES_SAMBA=yes CTDB_SAMBA_CHECK_PORTS="445" # work around grep error in log CTDB_MANAGES_WINBIND=yes CTDB_SERVICE_SMB=samba4 #name of our init script...

...n" agent="fence_manual"/> <!-- Define ilo fencing --> <fencedevice name="ilo" agent="fence_ilo" login="admin" password="foo"/> </fencedevices> </cluster> # Options to ctdbd. This is read by /etc/init.d/ctdb CTDB_RECOVERY_LOCK="/smb-ctdb/.ctdb_locking" CTDB_PUBLIC_INTERFACE=eth2 CTDB_PUBLIC_ADDRESSES=/etc/ctdb/public_addresses CTDB_MANAGES_SAMBA=yes CTDB_INIT_STYLE=ubuntu CTDB_NODES=/etc/ctdb/nodes CTDB_NOTIFY_SCRIPT=/etc/ctdb/notify.sh CTDB_DBDIR=/var/ctdb CTDB_DBDIR_PERSISTENT=/var/ctdb/persistent CTDB_SOCKET...

...is obviously not desirable. We're planning a redesign for this and were wondering what other people in similar environments are doing with the their CTDB shared files. Specifically, I'm referring to the locations supplied for <shared_dir> in these variables: /etc/sysconfig/ctdb: CTDB_RECOVERY_LOCK=<shared_dir> /etc/sysconfig/nfs: STATD_HOSTNAME=$NFS_HOSTNAME -P <shared_dir> -H /etc/ctdb/statd-callout /etc/sysconfig/nfs: NFS_TICKLE_SHARED_DIRECTORY=<shared_dir> /etc/sysconfig/nfs: STATD_SHARED_DIRECTORY=<shared_dir> Thanks! Stewart

Hi everyone I'm installing the CTDB and facing the following problem: When you start / etc / init.d / start ctdb returns error: You must the configuration of the CTDB_RECOVERY_LOCK To check the status of samba: smbstatus: the error message: "connect (/ tmp / ctdb.socket) failed: File or directory not found. messaging_ctdb_init failed: NT_STATUS_OBJECT_NAME_NOT_FOUND messaging_ctdb failed. I did the basic setup, with the configuration file ctdb in / etc / sysconfig / an...

...nf file I have: # Options to ctdbd, read by ctdbd_wrapper(1) # # See ctdbd.conf(5) for more information about CTDB configuration variables. # Shared recovery lock file to avoid split brain. No default. # # Do NOT run CTDB without a recovery lock file unless you know exactly # what you are doing. CTDB_RECOVERY_LOCK=/run/gluster/shared_storage/.CTDB-lockfile # List of nodes in the cluster. Default is below. CTDB_NODES=/etc/ctdb/nodes # List of public addresses for providing NAS services. No default. CTDB_PUBLIC_ADDRESSES=/etc/ctdb/public_addresses # What services should CTDB manage? Default is none. # CT...

...ing = Yes private dir = /cluster/ctdb [users] path = /cluster/users read only = No The nodes are mounted at both ends: /dev/drbd1 on /cluster type ocfs2 (rw,relatime,_netdev,heartbeat=local,nointr,data=ordered,errors=remount-ro,atime_quantum=60,coherency=full,user_xattr,acl) /etc/sysconfig/ctdb CTDB_RECOVERY_LOCK="/cluster/ctdb/lockfile" CTDB_PUBLIC_INTERFACE=enp0s3 CTDB_PUBLIC_ADDRESSES=/etc/ctdb/public_addresses CTDB_LVS_PUBLIC_IP= CTDB_SAMBA_SKIP_SHARE_CHECK=yes CTDB_MANAGES_ISCSI=yes CTDB_INIT_STYLE= CTDB_NODES=/etc/ctdb/nodes CTDB_NOTIFY_SCRIPT=/etc/ctdb/notify.sh CTDB_DBDIR=/var/lib/ctdb CTD...

...ed, eth0 as the primary NIC, eth1 as the private IP NIC. With clustering off and no CTDB, Samba works. I need to get this running for a needed project. Only errors are reported in /var/log/log.ctdb. Please help. CTDB Configs: Edit /etc/sysconfig/ctdb for the following to change from default. CTDB_RECOVERY_LOCK="/samba/samba_lock" CTDB_NODES=/etc/ctdb/nodes CTDB_DEBUGLEVEL=3 Edited /etc/ctdb/nodes to add internal Ip address for eth1 for private IP. The complete /var/log/log.ctdb: 2013/04/09 16:09:59.881679 [30574]: CTDB starting on node 2013/04/09 16:09:59.886133 [30575]: Starting CTDBD...

...roup: files winbind hosts: files dns bootparams: nisplus [NOTFOUND=return] files ethers: files netmasks: files networks: files protocols: files rpc: files services: files netgroup: files publickey: nisplus automount: files aliases: files nisplus ctdb.conf: CTDB_RECOVERY_LOCK="/EDAPT/ctdb/CTDB_lock" CTDB_PUBLIC_INTERFACE=eth0 CTDB_PUBLIC_ADDRESSES=/etc/ctdb/public_addresses CTDB_MANAGES_SAMBA=no CTDB_SAMBA_CHECK_PORTS="445" CTDB_MANAGES_WINBIND=no CTDB_INIT_STYLE=redhat CTDB_SERVICE_SMB=smb CTDB_SERVICE_WINBIND=winbind ulimit -n 10000 CTDB...

...ross CTDB managed servers authenticating via Active Directory(AD)? An example would be Samba's IDMAP backend for Winbind: RID vs. AD or tag Winbind to a primary CTDB node and point other nodes to authenticate from AD via proxy primary CTDB node? /etc/sysconfig/ctdb on all nodes is as follows: CTDB_RECOVERY_LOCK=/mnt/gpfs/CTDB/recovery.lck CTDB_PUBLIC_INTERFACE=eth2 CTDB_PUBLIC_ADDRESSES=/etc/ctdb/public_addresses CTDB_MANAGES_SAMBA=yes CTDB_MANAGES_WINBIND=yes CTDB_NODES=/etc/ctdb/nodes I had asked this before, but I have a strange scenario where Windows node is able to mount only from one of the CTDB-ma...

...2 records As you see the same file is mentioned twice because two clients have it open on two servers. gluster volume info <- is OK on both machines ctdb status <- is OK on both machines wbinfo -t <- is OK on both machines net ads info <- is OK on both machines /etc/sysconfig/ctdb CTDB_RECOVERY_LOCK=/media/gluster/system/ctdblockfile CTDB_NODES=/media/gluster/system/nodes #CTDB_PUBLIC_ADDRESSES=/etc/ctdb/public_addresses #CTDB_MANAGES_SAMBA=yes #CTDB_MANAGES_WINBIND=yes # CTDB_MANAGES_NFS=yes ulimit -n 10000 CTDB_LOGFILE=/var/log/log.ctdb CTDB_SYSLOG=no CTDB_DEBUGLEVEL=NOTICE /etc/ctdb/nodes 1...

...= True map acl inherit = yes inherit acls = yes vfs object = mysql_audit mysql_audit:host=mysql1.[DOMAIN].local mysql_audit:user=smbd mysql_audit:pass=TpwqOnYz mysql_audit:name=smbd mysql_audit:port=3306 Here is a copy of my ctdb configuration: CTDB_RECOVERY_LOCK="/[DOMAIN]/ctdb/CTDB_lock" CTDB_PUBLIC_INTERFACE=eth0 CTDB_PUBLIC_ADDRESSES=/etc/ctdb/public_addresses CTDB_INIT_STYLE=redhat ulimit -n 10000 CTDB_NODES=/etc/ctdb/nodes CTDB_DBDIR=/var/ctdb CTDB_DBDIR_PERSISTENT=/[DOMAIN]/ctdb/persistent CTDB_EVENT_SCRIPT_DIR=/etc/ctdb/events.d CTDB_SOCKE...

...vfs objects = fileid security = user workgroup = panastor [share] comment = None path = /gluster/data browseable = yes read only = no hosts allow = hosts deny = guest ok = yes ----------------------------------- ctdb ----------------------------------- CTDB_RECOVERY_LOCK=/gluster/lock/lockfile CTDB_PUBLIC_ADDRESSES=/gluster/lock/public_addresses CTDB_MANAGES_SAMBA=yes ulimit -n 10000 CTDB_NODES=/gluster/lock/nodes CTDB_LOGFILE=/var/log/log.ctdb CTDB_DEBUGLEVEL=3 ----------------------------------- thanks a lot nuaa_liuben

...= True map acl inherit = yes inherit acls = yes vfs object = mysql_audit mysql_audit:host=mysql1.[ DOMAIN].local mysql_audit:user=smbd mysql_audit:pass=TpwqOnYz mysql_audit:name=smbd mysql_audit:port=3306 Here is a copy of my ctdb configuration: CTDB_RECOVERY_LOCK="/[DOMAIN]/ctdb/CTDB_lock" CTDB_PUBLIC_INTERFACE=eth0 CTDB_PUBLIC_ADDRESSES=/etc/ctdb/public_addresses CTDB_INIT_STYLE=redhat ulimit -n 10000 CTDB_NODES=/etc/ctdb/nodes CTDB_DBDIR=/var/ctdb CTDB_DBDIR_PERSISTENT=/[DOMAIN]/ctdb/persistent CTDB_EVENT_SCRIPT_DIR=/etc/ctdb/events.d CTDB_SOCKE...

...ith rsync -avz samba.org::ftp/unpacked/ctdb and compiling well. I installed on my Centos 5.3 sernet package samba 3.5.2. Also working well. But after setting up ctdb and samba und running it my two nodes freezing for a while And ctdb and samba are down again. On Both nodes My /etc/sysconfig/ctdb: CTDB_RECOVERY_LOCK="/cluster/recovery/recovery" CTDB_PUBLIC_ADDRESSES=/etc/ctdb/public_addresses CTDB_MANAGES_SAMBA=yes ulimit -n 10000 CTDB_NOTIFY_SCRIPT=/etc/ctdb/notify.sh CTDB_DBDIR=/var/ctdb CTDB_DBDIR_PERSISTENT=/var/ctdb/persistent CTDB_EVENT_SCRIPT_DIR=/etc/ctdb/events.d CTDB_SOCKET=/tmp/ctdb.socket...

...path If I reenable the node, the private interface comes up and the files start copying again oss02:~ # ctdb enable -n 1 `/bin/ls.exe' -> `ls.4539.exe' `/bin/ls.exe' -> `ls.4540.exe' My config is: oss02:/ # perl -ne '/^#|^\s*$/ and next;print' /etc/sysconfig/ctdb CTDB_RECOVERY_LOCK="/net/lmd01/space/ctdb.lock" CTDB_PUBLIC_INTERFACE=eth3 CTDB_PUBLIC_ADDRESSES=/etc/ctdb/public_addresses CTDB_LVS_PUBLIC_IP=10.200.180.180 CTDB_NODES=/etc/ctdb/nodes CTDB_DBDIR=/var/ctdb CTDB_DBDIR_PERSISTENT=/var/ctdb/persistent CTDB_LOGFILE=/var/log/ctdb.log CTDB_DEBUGLEVEL=1 oss02:/ #...

...d by ctdbd_wrapper(1) > # > # See ctdbd.conf(5) for more information about CTDB configuration variables. > > # Shared recovery lock file to avoid split brain. No default. > # > # Do NOT run CTDB without a recovery lock file unless you know exactly > # what you are doing. > CTDB_RECOVERY_LOCK=/run/gluster/shared_storage/.CTDB-lockfile This should be in ctdb.conf: [cluster] recovery lock = /run/gluster/shared_storage/.CTDB-lockfile > # List of nodes in the cluster. Default is below. > CTDB_NODES=/etc/ctdb/nodes > > # List of public addresses for providing NAS services...

...# > # See ctdbd.conf(5) for more information about CTDB configuration variables. > > # Shared recovery lock file to avoid split brain. No default. > # > # Do NOT run CTDB without a recovery lock file unless you know exactly > # what you are doing. > CTDB_RECOVERY_LOCK=/run/gluster/shared_storage/.CTDB-lockfile This should be in ctdb.conf: [cluster] recovery lock = /run/gluster/shared_storage/.CTDB-lockfile > # List of nodes in the cluster. Default is below. > CTDB_NODES=/etc/ctdb/nodes > > # List of...