search for: ctdb_manages_nfs

...ist 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. # CTDB_MANAGES_SAMBA=yes # CTDB_MANAGES_WINBIND=yes CTDB_MANAGES_NFS=yes # Raise the file descriptor limit for CTDB? # CTDB_MAX_OPEN_FILES=10000 # Default is to use the log file below instead of syslog. CTDB_LOGGING=file:/var/log/log.ctdb # Default log level is NOTICE. Want less logging? CTDB_DEBUGLEVEL=DEBUG # Set some CTDB tunable variables during CTDB startu...

...re allow guests = yes map to guest = Bad User hide dot files = Yes hide files = /$*/ hide special files = yes strict sync = No /etc/ctdb/ctdbd.conf: CTDB_PUBLIC_ADDRESSES=/etc/ctdb/public_addresses CTDB_MANAGES_SAMBA=yes CTDB_SAMBA_SKIP_SHARE_CHECK=yes CTDB_MANAGES_WINBIND=yes CTDB_MANAGES_NFS=yes CTDB_NFS_CALLOUT=/etc/ctdb/nfs-ganesha-callout CTDB_NFS_CHECKS_DIR=/etc/ctdb/nfs-checks-ganesha.d CTDB_NFS_SKIP_SHARE_CHECK=yes CTDB_DEBUGLEVEL=NOTICE

...4="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=NOTICE CTDB_INIT_STYLE= CTDB_SERVICE_SMB=samba CTDB_SERVICE_WINBIND=winbind 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_SCRIPT_DIR=/etc/c...

...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 192.168.10.232 192.168.10.233 I do not use /etc/ctdb/public_addresses because I do not want HA or ip takeover to happen. My samba config looks like this: In [global] I have clustering = ye...

...First and foremost, thanks *very* much for ctdb. It's a joy to use after banging around with other HA solutions. We're planning to use it to export Samba and NFS shares throughout campus. I'm having one problem with the NFS part though. When ctdbd first starts statd (we're using CTDB_MANAGES_NFS=yes), it does so without appending the stuff in the STATD_HOSTNAME variable in /etc/sysconfig/nfs, which is where the statd-callout script is passed to statd. In our case, this means that statd is running as rpc.statd -p 662 -o 2020 instead of rpc.statd -n gfs -H /etc/ctdb/statd-callout -p 662...

...> hide dot files = Yes > hide files = /$*/ > hide special files = yes > strict sync = No > >/etc/ctdb/ctdbd.conf: > > CTDB_PUBLIC_ADDRESSES=/etc/ctdb/public_addresses > CTDB_MANAGES_SAMBA=yes > CTDB_SAMBA_SKIP_SHARE_CHECK=yes > CTDB_MANAGES_WINBIND=yes > CTDB_MANAGES_NFS=yes > CTDB_NFS_CALLOUT=/etc/ctdb/nfs-ganesha-callout > CTDB_NFS_CHECKS_DIR=/etc/ctdb/nfs-checks-ganesha.d > CTDB_NFS_SKIP_SHARE_CHECK=yes > CTDB_DEBUGLEVEL=NOTICE >-- >To unsubscribe from this list go to the following URL and read the >instructions: https://lists.samba.org/ma...

...t. > CTDB_PUBLIC_ADDRESSES=/etc/ctdb/public_addresses These are no longer used. The above defaults in /etc/ctdb/ are now hardwired. Symlinks can be used if necessary. > # What services should CTDB manage? Default is none. > # CTDB_MANAGES_SAMBA=yes > # CTDB_MANAGES_WINBIND=yes > CTDB_MANAGES_NFS=yes Gone. Now just enable the event scripts. > # Raise the file descriptor limit for CTDB? > # CTDB_MAX_OPEN_FILES=10000 Gone. Either do the right thing in the systemd unit file or put a ulimit command in /etc/sysconfig/ctdb or /etc/default/ctdb (depending on distro). > # Default is...

...tc/ctdb/public_addresses These are no longer used. The above defaults in /etc/ctdb/ are now hardwired. Symlinks can be used if necessary. > # What services should CTDB manage? Default is none. > # CTDB_MANAGES_SAMBA=yes > # CTDB_MANAGES_WINBIND=yes > CTDB_MANAGES_NFS=yes Gone. Now just enable the event scripts. > # Raise the file descriptor limit for CTDB? > # CTDB_MAX_OPEN_FILES=10000 Gone. Either do the right thing in the systemd unit file or put a ulimit command in /etc/sysconfig/ctdb or /etc/default/ctdb (depending...

...t of nodes in the cluster. Default is below. CTDB_NODES=/mfs/ctdb/nodes # List of public addresses for providing NAS services. No default. CTDB_PUBLIC_ADDRESSES=/mfs/ctdb/public_addresses_cl # What services should CTDB manage? Default is none. CTDB_MANAGES_SAMBA=yes CTDB_MANAGES_WINBIND=yes # CTDB_MANAGES_NFS=yes # Raise the file descriptor limit for CTDB? # ulimit -n 10000 # Default is to use the log file below instead of syslog. # CTDB_LOGFILE=/var/log/log.ctdb # CTDB_SYSLOG=no # Default log level is ERR. NOTICE is a little more verbose. CTDB_DEBUGLEVEL=NOTICE # Set some CTDB tunable variables du...

...These are no longer used. The above defaults in /etc/ctdb/ are now hardwired. Symlinks can be used if necessary. > # What services should CTDB manage? Default is none. > # CTDB_MANAGES_SAMBA=yes > # CTDB_MANAGES_WINBIND=yes > CTDB_MANAGES_NFS=yes Gone. Now just enable the event scripts. > # Raise the file descriptor limit for CTDB? > # CTDB_MAX_OPEN_FILES=10000 Gone. Either do the right thing in the systemd unit file or put a ulimit command in /etc/sysconfig/ctdb or /etc/def...

...th = /mnt/global/nfsexport read only = No inherit permissions = Yes inherit acls = Yes /etc/sysconfig/ctdb ------------------- CTDB_RECOVERY_LOCK=/mnt/global/CTDB/recovery.lck CTDB_PUBLIC_ADDRESSES=/etc/ctdb/public_addresses CTDB_MANAGES_SAMBA=yes CTDB_MANAGES_WINBIND=yes CTDB_MANAGES_NFS=yes CTDB_NODES=/etc/ctdb/nodes

...tc/ctdb/public_addresses These are no longer used. The above defaults in /etc/ctdb/ are now hardwired. Symlinks can be used if necessary. > # What services should CTDB manage? Default is none. > # CTDB_MANAGES_SAMBA=yes > # CTDB_MANAGES_WINBIND=yes > CTDB_MANAGES_NFS=yes Gone. Now just enable the event scripts. > # Raise the file descriptor limit for CTDB? > # CTDB_MAX_OPEN_FILES=10000 Gone. Either do the right thing in the systemd unit file or put a ulimit command in /etc/sysconfig/ctdb or /etc/default/ctdb (depending...

On 03/07/16 13:06, Volker Lendecke wrote: > On Fri, Jul 01, 2016 at 10:00:21AM +0100, Alex Crow wrote: >> We've had a strange issue after following the recommendations at >> https://wiki.samba.org/index.php/Ping_pong, particularly the part >> about mmap coherence. We are running CTDB/Samba over a MooseFS >> clustered FS, and we'd not done the ping-pong before.

...ds 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=glusterfs CTDB_NFS_CHECKS_DIR=/etc/ctdb/nfs-checks-ganesha.d/ CTDB_NFS_STATE_MNT=/mnt/mgt_vol/grp45/nfs_state CTDB_NFS_SKIP_SHARE_CHECK=yes CTDB_SET_KeepaliveLimit=1 cat /mnt/mgt_vol/grp45/nodes 192.168.100.15 #inner network...

...providing NAS services. No default. CTDB_PUBLIC_ADDRESSES=/var/run/gluster/shared_storage/ctdb/public_addresses # List of nodes in the cluster. CTDB_NODES=/var/run/gluster/shared_storage/ctdb/nodes # What services should CTDB manage?  Default is none. CTDB_MANAGES_SAMBA=yes CTDB_MANAGES_WINBIND=yes CTDB_MANAGES_NFS=no CTDB_SAMBA_SKIP_SHARE_CHECK=yes CTDB_SERVICE_NMB=nmb # Default is to use the log file below instead of syslog. CTDB_LOGGING=file:/var/log/ctdb.log CTDB_DEBUGLEVEL=NOTICE testparm output excluding the shared folders: netbios name = FILE realm = PI5.MYDOMAIN workgroup = PI5 log file = /var/log/...

...tor" event is now done via: ctdb event status legacy monitor See ctdb(1) for details. * The following service-related event script options have been removed: CTDB_MANAGES_SAMBA CTDB_MANAGES_WINBIND CTDB_MANAGES_CLAMD CTDB_MANAGES_HTTPD CTDB_MANAGES_ISCSI CTDB_MANAGES_NFS CTDB_MANAGES_VSFTPD CTDB_MANAGED_SERVICES Event scripts for services are now disabled by default. To enable an event script and, therefore, manage a service use a command like the following: ctdb event script enable legacy 50.samba * Notification scripts have moved to the scr...

...tor" event is now done via: ctdb event status legacy monitor See ctdb(1) for details. * The following service-related event script options have been removed: CTDB_MANAGES_SAMBA CTDB_MANAGES_WINBIND CTDB_MANAGES_CLAMD CTDB_MANAGES_HTTPD CTDB_MANAGES_ISCSI CTDB_MANAGES_NFS CTDB_MANAGES_VSFTPD CTDB_MANAGED_SERVICES Event scripts for services are now disabled by default. To enable an event script and, therefore, manage a service use a command like the following: ctdb event script enable legacy 50.samba * Notification scripts have moved to the scr...

...| 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 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_SCRIPT_DIR=/etc/ctdb/events.d CTDB_SOCKET=/tmp/ctdb.socket CTDB_TRANSPORT="tcp&qu...

...tor" event is now done via: ctdb event status legacy monitor See ctdb(1) for details. * The following service-related event script options have been removed: CTDB_MANAGES_SAMBA CTDB_MANAGES_WINBIND CTDB_MANAGES_CLAMD CTDB_MANAGES_HTTPD CTDB_MANAGES_ISCSI CTDB_MANAGES_NFS CTDB_MANAGES_VSFTPD CTDB_MANAGED_SERVICES Event scripts for services are now disabled by default. To enable an event script and, therefore, manage a service use a command like the following: ctdb event script enable legacy 50.samba * Notification scripts have moved to the scr...

...tor" event is now done via: ctdb event status legacy monitor See ctdb(1) for details. * The following service-related event script options have been removed: CTDB_MANAGES_SAMBA CTDB_MANAGES_WINBIND CTDB_MANAGES_CLAMD CTDB_MANAGES_HTTPD CTDB_MANAGES_ISCSI CTDB_MANAGES_NFS CTDB_MANAGES_VSFTPD CTDB_MANAGED_SERVICES Event scripts for services are now disabled by default. To enable an event script and, therefore, manage a service use a command like the following: ctdb event script enable legacy 50.samba * Notification scripts have moved to the scr...