search for: ctdb_public_interfac

...tive 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-managed SMB servers. The NetBIOS name is same on al...

...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 CTDB_DBDIR_PERSISTENT=/var/lib/ctdb/persistent CTDB_EVENT_S...

...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=/tmp/ctdb.socket CTDB_LOGFILE=/var/log/ctdb.log CTDB_DEB...

...arams: 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_NODES=/etc/ctdb/nodes CTDB_DBDIR=/var/ctdb CTDB_DBDIR...

...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_SOCKET=/tmp/ctdb.socket CTDB_TRANSPORT="tcp" CTDB_LOG...

...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_SOCKET=/tmp/ctdb.socket CTDB_TRANSPORT="tcp" CTDB_LOG...

...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:/ # cat /etc/ctdb/public_addresses 10.200.180.181/16 10.200.180...

...l 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 CTDB_NODES=/etc/ctdb/nodes CTDB_DBDIR=/var/ctdb...

...07/03 16:10:15.788078 [17182]: Freeze priority 2 2014/07/03 16:10:15.788162 [17182]: Freeze priority 3 System Details: Redhat 6.5 Nodes: 10.0.0.1 10.0.0.2 public_addresses: 10.98.81.2/24 bond0 Ctdb: CTDB_RECOVERY_LOCK=/mnt/media23/.ctdb_lock/lock.file CTDB_DEBUGLEVEL=ERR CTDB_MANAGES_SAMBA=yes CTDB_PUBLIC_INTERFACE=bond0 CTDB_PUBLIC_ADDRESSES=/etc/ctdb/public_addresses CTDB_SET_NoIpFailback=1 CTDB_SET_DeterministicIPs=0 The lock Filesystem is a Stornext Filesystem Any help would be apreciated. Cheers Axel -- View this message in context: http://samba.2283325.n4.nabble.com/ctdb-split-brain-nodes-do...

...iled to send tcp tickle ack for ::ffff:10.10.11.18 2019/02/22 18:01:05.389656 ctdbd[29541]: Starting traverse on DB ctdb.tdb (id 6238) 2019/02/22 18:01:05.392182 ctdbd[29541]: Ending traverse on DB ctdb.tdb (id 6238), records 1 cat /etc/sysconfig/ctdb CTDB_RECOVERY_LOCK=/mnt/mgt_vol/grp45/lockfile CTDB_PUBLIC_INTERFACE=eth3 CTDB_NODES=/mnt/mgt_vol/grp45/nodes CTDB_PUBLIC_ADDRESSES=/mnt/mgt_vol/grp45/public_addresses CTDB_MANAGES_SAMBA=yes CTDB_MANAGES_WINBIND=no CTDB_MANAGES_VSFTP=yes CTDB_SAMBA_SKIP_SHARE_CHECK=yes CTDB_MANAGES_NFS=yes CTDB_NFS_CALLOUT=/etc/ctdb/nfs-ganesha-callout CTDB_NFS_STATE_FS_TYPE=gluste...

...s in the new configuration scheme: CTDB_PIDFILE --pidfile CTDB_SOCKET --socket CTDB_NODES --nlist CTDB_PUBLIC_ADDRESSES --public-addresses CTDB_EVENT_SCRIPT_DIR --event-script-dir CTDB_NOTIFY_SCRIPT --notification-script CTDB_PUBLIC_INTERFACE --public-interface CTDB_MAX_PERSISTENT_CHECK_ERRORS --max-persistent-check-errors - The compile-time defaults should be used for the first 6 of these. - Use a symbolic link from the configuration directory to specify a different location for nodes or public_addresses (e.g. in the...

...s in the new configuration scheme: CTDB_PIDFILE --pidfile CTDB_SOCKET --socket CTDB_NODES --nlist CTDB_PUBLIC_ADDRESSES --public-addresses CTDB_EVENT_SCRIPT_DIR --event-script-dir CTDB_NOTIFY_SCRIPT --notification-script CTDB_PUBLIC_INTERFACE --public-interface CTDB_MAX_PERSISTENT_CHECK_ERRORS --max-persistent-check-errors - The compile-time defaults should be used for the first 6 of these. - Use a symbolic link from the configuration directory to specify a different location for nodes or public_addresses (e.g. in the...

...10.2/24 root at smb-cluster-1:~# cat /etc/ctdb/public_addresses 192.168.100.144/24 192.168.100.145/24 root at smb-cluster-1:~# cat /etc/ctdb/static-routes eth0 0.0.0.0/0 192.168.100.2 root at smb-cluster-1:~# grep -v ^\# /etc/default/ctdb | grep -v ^$ CTDB_RECOVERY_LOCK="/samba/ctdb/ctdb" CTDB_PUBLIC_INTERFACE=eth0 CTDB_PUBLIC_ADDRESSES=/etc/ctdb/public_addresses CTDB_MANAGES_SAMBA=yes CTDB_SAMBA_SKIP_SHARE_CHECK=no CTDB_SAMBA_CHECK_PORTS="445" CTDB_MANAGES_WINBIND=yes CTDB_MANAGES_VSFTPD=no CTDB_MANAGES_ISCSI=no CTDB_MANAGES_NFS=no CTDB_MANAGES_HTTPD=no CTDB_INIT_STYLE=debian ulimit -n 30000...

...s in the new configuration scheme: CTDB_PIDFILE --pidfile CTDB_SOCKET --socket CTDB_NODES --nlist CTDB_PUBLIC_ADDRESSES --public-addresses CTDB_EVENT_SCRIPT_DIR --event-script-dir CTDB_NOTIFY_SCRIPT --notification-script CTDB_PUBLIC_INTERFACE --public-interface CTDB_MAX_PERSISTENT_CHECK_ERRORS --max-persistent-check-errors - The compile-time defaults should be used for the first 6 of these. - Use a symbolic link from the configuration directory to specify a different location for nodes or public_addresses (e.g. in the...

...s in the new configuration scheme: CTDB_PIDFILE --pidfile CTDB_SOCKET --socket CTDB_NODES --nlist CTDB_PUBLIC_ADDRESSES --public-addresses CTDB_EVENT_SCRIPT_DIR --event-script-dir CTDB_NOTIFY_SCRIPT --notification-script CTDB_PUBLIC_INTERFACE --public-interface CTDB_MAX_PERSISTENT_CHECK_ERRORS --max-persistent-check-errors - The compile-time defaults should be used for the first 6 of these. - Use a symbolic link from the configuration directory to specify a different location for nodes or public_addresses (e.g. in the...

...s in the new configuration scheme: CTDB_PIDFILE --pidfile CTDB_SOCKET --socket CTDB_NODES --nlist CTDB_PUBLIC_ADDRESSES --public-addresses CTDB_EVENT_SCRIPT_DIR --event-script-dir CTDB_NOTIFY_SCRIPT --notification-script CTDB_PUBLIC_INTERFACE --public-interface CTDB_MAX_PERSISTENT_CHECK_ERRORS --max-persistent-check-errors - The compile-time defaults should be used for the first 6 of these. - Use a symbolic link from the configuration directory to specify a different location for nodes or public_addresses (e.g. in the...

...s in the new configuration scheme: CTDB_PIDFILE --pidfile CTDB_SOCKET --socket CTDB_NODES --nlist CTDB_PUBLIC_ADDRESSES --public-addresses CTDB_EVENT_SCRIPT_DIR --event-script-dir CTDB_NOTIFY_SCRIPT --notification-script CTDB_PUBLIC_INTERFACE --public-interface CTDB_MAX_PERSISTENT_CHECK_ERRORS --max-persistent-check-errors - The compile-time defaults should be used for the first 6 of these. - Use a symbolic link from the configuration directory to specify a different location for nodes or public_addresses (e.g. in the...

...s in the new configuration scheme: CTDB_PIDFILE --pidfile CTDB_SOCKET --socket CTDB_NODES --nlist CTDB_PUBLIC_ADDRESSES --public-addresses CTDB_EVENT_SCRIPT_DIR --event-script-dir CTDB_NOTIFY_SCRIPT --notification-script CTDB_PUBLIC_INTERFACE --public-interface CTDB_MAX_PERSISTENT_CHECK_ERRORS --max-persistent-check-errors - The compile-time defaults should be used for the first 6 of these. - Use a symbolic link from the configuration directory to specify a different location for nodes or public_addresses (e.g. in the...

...s in the new configuration scheme: CTDB_PIDFILE --pidfile CTDB_SOCKET --socket CTDB_NODES --nlist CTDB_PUBLIC_ADDRESSES --public-addresses CTDB_EVENT_SCRIPT_DIR --event-script-dir CTDB_NOTIFY_SCRIPT --notification-script CTDB_PUBLIC_INTERFACE --public-interface CTDB_MAX_PERSISTENT_CHECK_ERRORS --max-persistent-check-errors - The compile-time defaults should be used for the first 6 of these. - Use a symbolic link from the configuration directory to specify a different location for nodes or public_addresses (e.g. in the...

...s in the new configuration scheme: CTDB_PIDFILE --pidfile CTDB_SOCKET --socket CTDB_NODES --nlist CTDB_PUBLIC_ADDRESSES --public-addresses CTDB_EVENT_SCRIPT_DIR --event-script-dir CTDB_NOTIFY_SCRIPT --notification-script CTDB_PUBLIC_INTERFACE --public-interface CTDB_MAX_PERSISTENT_CHECK_ERRORS --max-persistent-check-errors - The compile-time defaults should be used for the first 6 of these. - Use a symbolic link from the configuration directory to specify a different location for nodes or public_addresses (e.g. in the...