search for: ctdb_log

...IC_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 startup? # CTDB_SET_TDBMutexEnabled=0 CTDB_NFS_CALLOUT=/etc/ctdb/nfs-ganesha-callout CTDB_NFS_CHECKS_DIR=/etc/ctdb/nfs-checks-ganesha.d CTBS_NFS_STATE...

...Infrastructure Master It can 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.nf...

...Infrastructure Master It can 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.nf...

...Infrastructure Master It can 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.nf...

...Infrastructure Master It can 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.nf...

...gt; # 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 to use the log file below instead of syslog. > CTDB_LOGGING=file:/var/log/log.ctdb ctdb.conf: [logging] location = file:/var/log/log.ctdb However, this is the default so you can just omit it. If you can use syslog instead, then I strongly suggest you do that (see ctdb.conf(5) manpage). CTDB's file logging has no useful way of rotating the log...

...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 to use the log file below instead of syslog. > CTDB_LOGGING=file:/var/log/log.ctdb ctdb.conf: [logging] location = file:/var/log/log.ctdb However, this is the default so you can just omit it. If you can use syslog instead, then I strongly suggest you do that (see ctdb.conf(5) manpage). CTDB's file loggi...

...Infrastructure Master It can 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.nf...

...Infrastructure Master It can 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.nf...

...how, 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 manage...

...> # 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 to use the log file below instead of syslog. > CTDB_LOGGING=file:/var/log/log.ctdb ctdb.conf: [logging] location = file:/var/log/log.ctdb However, this is the default so you can just omit it. If you can use syslog instead, then I strongly suggest you do that (see ctdb.conf(5) manpage)...

...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 to use the log file below instead of syslog. > CTDB_LOGGING=file:/var/log/log.ctdb ctdb.conf: [logging] location = file:/var/log/log.ctdb However, this is the default so you can just omit it. If you can use syslog instead, then I strongly suggest you do that (see ctdb.conf(5) manpage). CTDB's file loggi...

...Infrastructure Master It can 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.nf...

...Infrastructure Master It can 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.nf...

...ns but it didn't help: posix locking = no kernel oplocks = no kernel share modes = no The ctdb configuration: /etc/default/ctdb CTDB_RECOVERY_LOCK=/mnt/common/ctdb.lock CTDB_NODES=/etc/ctdb/nodes CTDB_PUBLIC_ADDRESSES=/etc/ctdb/public_addresses CTDB_MANAGES_SAMBA=yes CTDB_MANAGES_WINBIND=yes CTDB_LOGGING=file:/var/log/log.ctdb CTDB_SET_TraverseTimeout=60 CTDB_SET_EventScriptTimeout=120 /etc/ctdb/nodes 192.168.176.11 192.168.176.14 /etc/ctdb/public_addresses 123.123.123.155/24 eth0 Does this lock should be preserved after moving the IP or do I have something wrong in my configuration? Thank...

...Infrastructure Master It can 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.nf...

...Infrastructure Master It can 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.nf...

...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/samba/tmp/samba_%I.log clustering = Yes registry shares = Yes load printers = No security = ADS deadtime = 10 template home...

...ket command-line option - The ctdb command's CTDB_NODES environment variable When writing tests there are still mechanisms available to change the locations of certain directories and files. * The following ctdbd.conf and ctdbd options have been replaced by new ctdb.conf options: CTDB_LOGGING/--logging logging -> location CTDB_DEBUGLEVEL/-d logging -> log level CTDB_TRANSPORT/--transport cluster -> transport CTDB_NODE_ADDRESS/--listen cluster -> node address CTDB_RECOVERY_LOCK...

...ket command-line option - The ctdb command's CTDB_NODES environment variable When writing tests there are still mechanisms available to change the locations of certain directories and files. * The following ctdbd.conf and ctdbd options have been replaced by new ctdb.conf options: CTDB_LOGGING/--logging logging -> location CTDB_DEBUGLEVEL/-d logging -> log level CTDB_TRANSPORT/--transport cluster -> transport CTDB_NODE_ADDRESS/--listen cluster -> node address CTDB_RECOVERY_LOCK...