search for: ctdb_logfile

...cket CTDB_TRANSPORT="tcp" CTDB_MONITOR_FREE_MEMORY=100 CTDB_START_AS_DISABLED="yes" CTDB_CAPABILITY_RECMASTER=yes CTDB_CAPABILITY_LMASTER=yes NATGW_PUBLIC_IP= NATGW_PUBLIC_IFACE= NATGW_DEFAULT_GATEWAY= NATGW_PRIVATE_IFACE= NATGW_PRIVATE_NETWORK= NATGW_NODES=/etc/ctdb/natgw_nodes CTDB_LOGFILE=/var/log/ctdb/log.ctdb CTDB_DEBUGLEVEL=2 CTDB_OPTIONS=

...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_DEBUGLEVEL=2 Yauheni Labko (Eugene Lobko) Junior System Administrator Chapdelaine & Co. (212)208-9150

...ND=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_PERSISTENT=/EDAPT/ctdb/persistent CTDB_EVENT_SCRIPT_DIR=/etc/ctdb/events.d CTDB_SOCKET=/tmp/ctdb.socket CTDB_TRANSPORT="tcp" CTDB_LOGFILE=/var/log/log.ctdb CTDB_DEBUGLEVEL=2

...cket CTDB_TRANSPORT="tcp" CTDB_MONITOR_FREE_MEMORY=100 CTDB_START_AS_DISABLED="yes" CTDB_CAPABILITY_RECMASTER=yes CTDB_CAPABILITY_LMASTER=yes NATGW_PUBLIC_IP= NATGW_PUBLIC_IFACE= NATGW_DEFAULT_GATEWAY= NATGW_PRIVATE_IFACE= NATGW_PRIVATE_NETWORK= NATGW_NODES=/etc/ctdb/natgw_nodes CTDB_LOGFILE=/var/log/messages CTDB_DEBUGLEVEL=2 CTDB_OPTIONS= */etc/ctdb/nodes* 192.168.12.30 192.168.12.34 */etc/ctdb/public_addresses* 192.168.11.29/24 enp2s2 192.168.11.33/24 enp2s2 192.168.11.30/24 enp2s3 192.168.11.34/24 enp2s3 192.168.11.31/24 enp2s4 192.168.11.35/24...

...es 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 = yes idmap backend = tdb2 vf...

...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_LOGFILE=/var/log/log.ctdb CTDB_DEBUGLEVEL=2

...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

...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_LOGFILE=/var/log/log.ctdb CTDB_DEBUGLEVEL=2

...=/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 CTDB_TRANSPORT="tcp" CTDB_MONITOR_FREE_MEMORY=100 CTDB_LOGFILE=/var/log/log.ctdbq My /etc/ctdb/nodes 192.168.134.28 192.168.134.27 My /etc/ctdb/public_addresses 192.168.134.100/24 eth0 192.168.134.101/24 eth0 My /etc/samba/smb.conf [global] workgroup = domain-cluster security=user clustering=yes private dir=/cluster/recovery...

...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.182/16 10.200.180.183/16 oss02:/ # cat /etc/ctdb/nodes 10.200.20.55 10.200.20.56 10.200.20.58 Thanks for any help, JR

...ESSES=/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 CTDB_DBDIR_PERSISTENT=/var/ctdb/persistent CTDB_LOGFILE=/var/log/log.ctdb CTDB_DEBUGLEVEL=3 /etc/ctdb/public_addresses 192.168.2.119/24 eth1 192.168.2.120/24 eth1 192.168.2.121/24 eth1 (network adapter varies) /etc/ctdb/nodes 10.0.0.1 10.0.0.2 10.0.0.3 excerpt from /etc/network/interfaces auto eth1 iface eth1 inet static address 192.16...

...B_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 during CTDB startup? # CTDB_SET_TraverseTimeout=60 CTDB_SAMBA_SKIP_SHARE_CHECK=yes -- This message is intended only for the addressee and may...

...SAMBA=yes CTDB_SAMBA_SKIP_SHARE_CHECK="yes" CTDB_MANAGES_WINBIND=yes CTDB_NODES=/etc/ctdb/nodes CTDB_DBDIR=/var/ctdb CTDB_DBDIR_PERSISTENT=/var/ctdb/persistent CTDB_EVENT_SCRIPT_DIR=/etc/ctdb/events.d CTDB_SOCKET=/tmp/ctdb.socket CTDB_TRANSPORT="tcp" CTDB_MONITOR_FREE_MEMORY=100 CTDB_LOGFILE=/var/log/log.ctdb /etc/ctdb/nodes 10.2.3.1 10.2.3.2 /etc/ctdb/public_addresses 172.16.100.115/24 eth0 172.16.100.114/24 eth0 i'm running: ./smbtorture //cifscluster/users/eneal -Ueneal%password RAW-BENCH-LOCK --unclist=unclist.txt --num-progs=32 -t60 -d 99 when the contents of unclis...

...=/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 CTDB_TRANSPORT="tcp" CTDB_MONITOR_FREE_MEMORY=100 CTDB_LOGFILE=/var/log/log.ctdbq My /etc/ctdb/nodes 192.168.134.28 192.168.134.27 My /etc/ctdb/public_addresses 192.168.134.100/24 eth0 192.168.134.101/24 eth0 My /etc/samba/smb.conf [global] workgroup = domain-cluster security=user clustering=yes private dir=/cluster/recovery...

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.

...an now also show, transfer or seize the DNS infrastructure roles: DomainDnsZones Infrastructure Master ForestDnsZones Infrastructure Master CTDB logging changes -------------------- The destination for CTDB logging is now set via a single new configuration variable CTDB_LOGGING. This replaces CTDB_LOGFILE and CTDB_SYSLOG, which have both been removed. See ctdbd.conf(5) for details of CTDB_LOGGING. CTDB no longer runs a separate logging daemon. CTDB NFS support changes ------------------------ CTDB's NFS service management has been combined into a single 60.nfs event script. This updated 60....

...an now also show, transfer or seize the DNS infrastructure roles: DomainDnsZones Infrastructure Master ForestDnsZones Infrastructure Master CTDB logging changes -------------------- The destination for CTDB logging is now set via a single new configuration variable CTDB_LOGGING. This replaces CTDB_LOGFILE and CTDB_SYSLOG, which have both been removed. See ctdbd.conf(5) for details of CTDB_LOGGING. CTDB no longer runs a separate logging daemon. CTDB NFS support changes ------------------------ CTDB's NFS service management has been combined into a single 60.nfs event script. This updated 60....

...an now also show, transfer or seize the DNS infrastructure roles: DomainDnsZones Infrastructure Master ForestDnsZones Infrastructure Master CTDB logging changes -------------------- The destination for CTDB logging is now set via a single new configuration variable CTDB_LOGGING. This replaces CTDB_LOGFILE and CTDB_SYSLOG, which have both been removed. See ctdbd.conf(5) for details of CTDB_LOGGING. CTDB no longer runs a separate logging daemon. CTDB NFS support changes ------------------------ CTDB's NFS service management has been combined into a single 60.nfs event script. This updated 60....

...an now also show, transfer or seize the DNS infrastructure roles: DomainDnsZones Infrastructure Master ForestDnsZones Infrastructure Master CTDB logging changes -------------------- The destination for CTDB logging is now set via a single new configuration variable CTDB_LOGGING. This replaces CTDB_LOGFILE and CTDB_SYSLOG, which have both been removed. See ctdbd.conf(5) for details of CTDB_LOGGING. CTDB no longer runs a separate logging daemon. CTDB NFS support changes ------------------------ CTDB's NFS service management has been combined into a single 60.nfs event script. This updated 60....

...an now also show, transfer or seize the DNS infrastructure roles: DomainDnsZones Infrastructure Master ForestDnsZones Infrastructure Master CTDB logging changes -------------------- The destination for CTDB logging is now set via a single new configuration variable CTDB_LOGGING. This replaces CTDB_LOGFILE and CTDB_SYSLOG, which have both been removed. See ctdbd.conf(5) for details of CTDB_LOGGING. CTDB no longer runs a separate logging daemon. CTDB NFS support changes ------------------------ CTDB's NFS service management has been combined into a single 60.nfs event script. This updated 60....