search for: ctdb_debuglevel

...* 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/ctdb/events.d CTDB_SOCKET=/var/lib/ctdb/ctdb.socket CTDB_T...

...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_FS_TYPE=glusterfs CTDB_NFS_STATE_MNT=/run/gluster/shared_storage CTDB_NFS_SKIP_SHARE_CHECK=yes...

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

...; interested to know if the public address is on an ordinary ethernet > interface. We are using two teaming-Interfaces (one for each LAN). Each team-Interface has 2x10Gbit LACP. > ctdb_killtcp has been very well tested. In the function that calls > ctdb_killtcp, you could add CTDB_DEBUGLEVEL=DEBUG to the ctdb_killtcp > call, like this: > CTDB_DEBUGLEVEL=DEBUG "${CTDB_HELPER_BINDIR}/ctdb_killtcp" "$_iface" > || { I have done that already. It is not really helpful as it floods the log with messages about packages it is ignoring. Within one minute of lo...

...rom iptables) because they are new connections. * If there has been an attempt to RST the connections then I'm interested to know if the public address is on an ordinary ethernet interface. ctdb_killtcp has been very well tested. In the function that calls ctdb_killtcp, you could add CTDB_DEBUGLEVEL=DEBUG to the ctdb_killtcp call, like this: CTDB_DEBUGLEVEL=DEBUG "${CTDB_HELPER_BINDIR}/ctdb_killtcp" "$_iface" || { For Samba 4.18, a new script variable CTDB_KILLTCP_DEBUGLEVEL has been added for this purpose. > I am wondering about possible reasons for ctdb no...

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

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

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

...nect client socket to daemon. Errno:Connection refused(111) common/cmdline.c:156 Failed to connect to daemon 2014/08/16 15:32:03.261221 [23255]: Failed to init ctdb /etc/default/ctdb CTDB_NODES=/etc/ctdb/nodes CTDB_PUBLIC_ADDRESSES=/etc/ctdb/public_addresses CTDB_MANAGES_SAMBA=yes CTDB_SYSLOG=yes CTDB_DEBUGLEVEL=NOTICE CTDB_SOCKET=/usr/local/var/run/ctdb/ctdbd.socket /usr/local/samba/etc/smb.conf [global] workgroup = ALTEA realm = ALTEA.SITE security = ADS kerberos method = secrets and keytab netbios name = SMBCLUSTER disable netbios = Yes clustering = Yes ctdbd socket = /usr/local/var/run/ctdb/ctdbd.soc...

.../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 vfs objects = fileid fileid:mapping = fsname I...

...ESSES=/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

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

...ESSES=/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

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

...SES=/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/mailman/options/samba -- Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.

Hello, we are using ctdb 4.15.5 on RHEL8 (Kernel 4.18.0-372.32.1.el8_6.x86_64) to provide NFS v3 (via tcp) to RHEL7/8 clients. Whenever an ip takeover happens most clients report something like this: [Mon Feb 13 12:21:22 2023] nfs: server x.x.253.252 not responding, still trying [Mon Feb 13 12:21:28 2023] nfs: server x.x.253.252 not responding, still trying [Mon Feb 13 12:22:31 2023] nfs: server

...st 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 logs. There's an open bug, there are plans, but it is complicated. > # Default log level is NOTICE. Want less logging? > CTDB_DEBUGLEVEL=DEBUG ctdb.conf: [logging] log level = DEBUG > CTDB_NFS_CALLOUT=/etc/ctdb/nfs-ganesha-callout > CTDB_NFS_CHECKS_DIR=/etc/ctdb/nfs-checks-ganesha.d > CTBS_NFS_STATE_FS_TYPE=glusterfs > CTDB_NFS_STATE_MNT=/run/gluster/shared_storage > CTDB_NFS_SKIP_SHARE_CHECK=yes > NFS_HOSTNAM...

...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 logs. There's an open bug, there are plans, but it is complicated. > # Default log level is NOTICE. Want less logging? > CTDB_DEBUGLEVEL=DEBUG ctdb.conf: [logging] log level = DEBUG > CTDB_NFS_CALLOUT=/etc/ctdb/nfs-ganesha-callout > CTDB_NFS_CHECKS_DIR=/etc/ctdb/nfs-checks-ganesha.d > CTBS_NFS_STATE_FS_TYPE=glusterfs > CTDB_NFS_STATE_MNT=/run/gluster/shared_storage > CT...

...rface has 2x10Gbit LACP. I'm not sure how this would affect the packet capture. I would guess that the frame format would be one of the ones that is now supported. > > > ctdb_killtcp has been very well tested. In the function that calls > > ctdb_killtcp, you could add CTDB_DEBUGLEVEL=DEBUG to the ctdb_killtcp > > call, like this: > > CTDB_DEBUGLEVEL=DEBUG "${CTDB_HELPER_BINDIR}/ctdb_killtcp" "$_iface" > > || { > > I have done that already. It is not really helpful as it floods the log with messages about packages it is ignori...

...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.168.2.164 netmask 255.255.255...