search for: eventscript

...:59.881679 [30574]: CTDB starting on node 2013/04/09 16:09:59.886133 [30575]: Starting CTDBD as pid : 30575 2013/04/09 16:09:59.886305 [30575]: Set scheduler to SCHED_FIFO 2013/04/09 16:09:59.886637 [30575]: ctdb chose network address 10.22.1.20:4379 pnn 0 2013/04/09 16:09:59.887035 [30575]: server/eventscript.c:800 Starting eventscript init 2013/04/09 16:09:59.969022 [30575]: 10.interface: No public addresses file found. Nothing to do for 10.interfaces 2013/04/09 16:10:00.246654 [30575]: server/eventscript.c:486 Eventscript init finished with state 0 2013/04/09 16:10:00.248978 [30575]: Keepalive monit...

...:NORMAL (0) > Recovery master:0 I could not find out why the nodes are both disabled. So then I issue # ctdb enable on each node. After that ctdb will not be able to assign the public ip addresses. On the first node I get repeatedly: > 2012/05/24 14:32:09.408217 [ 6773]: Forced running of eventscripts with argument > s ipreallocated > 2012/05/24 14:32:09.442628 [recoverd: 6800]: Public address '10.94.43.67' is not > assigned and we could serve this ip > 2012/05/24 14:32:09.442643 [recoverd: 6800]: Public address '10.94.43.66' is not > assigned and we could serve...

...33 [31866]: server/ctdb_takeover.c:162 public address '192.168.134.100' now unassigned (old iface '__none__' refs[0]) 2010/05/20 09:35:40.092451 [31866]: Recovery has finished 2010/05/20 09:35:40.092492 [31866]: Monitoring has been disabled 2010/05/20 09:35:40.092516 [31866]: server/eventscript.c:715 Starting eventscript recovered 2010/05/20 09:35:40.378186 [31866]: server/eventscript.c:466 Eventscript recovered finished with state 0 2010/05/20 09:35:40.378264 [31866]: Monitoring has been enabled 2010/05/20 09:35:40.534741 [31866]: CTDB_WAIT_UNTIL_RECOVERED 2010/05/20 09:35:40.534809 [31...

...: server/ctdb_monitor.c:293 in recovery. Wait one more second 2014/08/27 03:00:14.583565 [ 4411]: Freeze priority 1 2014/08/27 03:00:14.585431 [ 4411]: Freeze priority 2 2014/08/27 03:00:14.587089 [ 4411]: Freeze priority 3 2014/08/27 03:00:14.589524 [ 4411]: server/ctdb_recover.c:988 startrecovery eventscript has been invoked 2014/08/27 03:00:14.845167 [ 4411]: server/ctdb_recover.c:612 Recovery mode set to NORMAL 2014/08/27 03:00:14.845236 [ 4411]: Thawing priority 1 2014/08/27 03:00:14.845254 [ 4411]: Release freeze handler for prio 1 2014/08/27 03:00:14.845295 [ 4411]: Thawing priority 2 2014/08/27 0...

...ld not cause problems with simple failover. Hmm, that node where above output was seen hat released and taken that very ip shortly before. And then released it again. The last point in time is the one where I saw the remaining connections: Feb 13 12:08:11 serverpnn1 ctdbd[85617]: ../../ctdb/server/eventscript.c:655 Running event releaseip with arguments team1 x.x.253.252 24 Feb 13 12:16:26 serverpnn1 ctdbd[85617]: ../../ctdb/server/eventscript.c:655 Running event takeip with arguments team1 x.x.253.252 24 Feb 13 12:27:50 serverpnn1 ctdbd[85617]: ../../ctdb/server/eventscript.c:655 Running event releasei...

...s I'm missing. Versions are a bit out of date (running in CentOS 6.5): [root at gp-1-0 ctdb]# rpm -qa ctdb samba samba-3.6.9-151.el6_4.1.x86_64 ctdb-1.0.114.5-3.el6.x86_64 I've done this heaps of times with Ethernet public addresses but not with the IB interface. Maybe something in the eventscript? Pointers, advice welcomed. Regards, Malcolm.

...config * : backend = tdb2 ea support = Yes map acl inherit = Yes cups options = raw store dos attributes = Yes --------- End of smb.conf --------------- ----------- log.ctdb (debug level 10 )------------------------- 2012/04/17 14:57:33.045989 [18864]: server/eventscript.c:762 Starting eventscript startup 2012/04/17 14:57:33.081299 [18864]: iface[eth0] has changed it's link status down => up 2012/04/17 14:57:33.253713 [18864]: server/ctdb_daemon.c:188 Registered message handler for srvid=544851151346827329 2012/04/17 14:57:33.253776 [18864]: server/ctdb_daem...

...) showed 405 of > > Hmm, that node where above output was seen hat released and taken > that very ip shortly before. And then released it again. The last > point in time is the one where I saw the remaining connections: > Feb 13 12:08:11 serverpnn1 ctdbd[85617]: ../../ctdb/server/eventscript.c:655 Running event releaseip with arguments team1 x.x.253.252 24 > Feb 13 12:16:26 serverpnn1 ctdbd[85617]: ../../ctdb/server/eventscript.c:655 Running event takeip with arguments team1 x.x.253.252 24 > Feb 13 12:27:50 serverpnn1 ctdbd[85617]: ../../ctdb/server/eventscript.c:655 Running even...

....16.22   eth3 COUNT   client1_ovh    eth3                 eth0:192.168.16.22 ... ---------------------------------------------------------------------- /etc/lsm/lsm.conf ---------------------------------------------------------------------- debug=8 defaults {   name=defaults   checkip=127.0.0.1   eventscript=/etc/lsm/script   notifyscript=/usr/share/lsm/default_script   max_packet_loss=15   max_successive_pkts_lost=7   min_packet_loss=5   min_successive_pkts_rcvd=10   interval_ms=1000   timeout_ms=1000   warn_email=alert@ipernity.com   check_arp=0   sourceip=   ttl=0 } include /etc/lsm/shorewall.conf...

Hi Uli, [Sorry for slow response, life is busy...] On Mon, 13 Feb 2023 15:06:26 +0000, Ulrich Sibiller via samba <samba at lists.samba.org> wrote: > 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

...ropriate... * Numerous resource leak fixes, many of which were found by Coverity Important internal changes -------------------------- * TDB checking is now done under a timeout This avoid cases where tdbtool/tdbdump can hang indefinitely if the database size grows to over 4GB. * The Samba eventscript now logs errors from testparm * Cleaned up route flushing code to avoid noise in logs Reporting bugs & Development Discussion =============================== Please discuss this release on the samba-technical mailing list or by joining the #ctdb IRC channel on irc.freenode.net. All bug re...

Highlights ======= * Support for Samba 4.0.0 To use CTDB 2.1 with Samba 3.x, enable Samba3AvoidDeadlocks tunable * Set CTDB_BASE in eventscripts, so they can be run easily * Clean up orphaned interfaces * Do not restart NFS on reconfigure event * Fix RSN based recovery of persistent databases to avoid corruption * Re-factor and separate IP allocation algorithms Reporting bugs & Development Discussion =============================...

Changes in CTDB 2.3 =================== User-visible changes -------------------- * 2 new configuration variables for 60.nfs eventscript: - CTDB_MONITOR_NFS_THREAD_COUNT - CTDB_NFS_DUMP_STUCK_THREADS See ctdb.sysconfig for details. * Removed DeadlockTimeout tunable. To enable debug of locking issues set CTDB_DEBUG_LOCKS=/etc/ctdb/debug_locks.sh * In overall statistics and database statistics, lock buckets have been...

...ctdb-statistics.7. Important bug fixes ------------------- * Verify policy routing configuration when starting up to make sure that policy routing tables do not override default routing tables. * "ctdb scriptstatus" should correctly list the number of scripts executed. * Do not run eventscripts at real-time priority. * Make sure "ctdb restoredb" and "ctdb wipedb" cannot affect an ongoing recovery. * If a readonly record revokation fails, CTDB does not abort anymore. It will retry revoke. * pending_calls statistic now gets updated correctly. Important internal...

...=================== User-visible changes -------------------- * The "stopped" event has been removed. The "ipreallocated" event is now run when a node is stopped. Use this instead of "stopped". * New --pidfile option for ctdbd, used by initscript * The 60.nfs eventscript now uses configuration files in /etc/ctdb/nfs-rpc-checks.d/ for timeouts and actions instead of hardcoding them into the script. * Notification handler scripts can now be dropped into /etc/ctdb/notify.d/. * The NoIPTakeoverOnDisabled tunable has been renamed to NoIPHostOnAllDisabled and now...

...etzmacher <metze at samba.org> * BUG 10297: s3:smbd: Only pass UCF_PREP_CREATEFILE to filename_convert() if we may create a new file. * BUG 12471: Fix build with MIT Kerberos. o Mathieu Parent <math.parent at gmail.com> * BUG 12371: ctdb-scripts: Fix Debian init in Samba eventscript. o Andreas Schneider <asn at samba.org> * BUG 12183: s3-printing: Correctly encode CUPS printer URIs. * BUG 12195: s3-printing: Allow printer names longer than 16 chars. * BUG 12269: nss_wins: Fix errno values for HOST_NOT_FOUND. * BUG 12405: s3-winbind: Do not return NO_MEMORY...

...etzmacher <metze at samba.org> * BUG 10297: s3:smbd: Only pass UCF_PREP_CREATEFILE to filename_convert() if we may create a new file. * BUG 12471: Fix build with MIT Kerberos. o Mathieu Parent <math.parent at gmail.com> * BUG 12371: ctdb-scripts: Fix Debian init in Samba eventscript. o Andreas Schneider <asn at samba.org> * BUG 12183: s3-printing: Correctly encode CUPS printer URIs. * BUG 12195: s3-printing: Allow printer names longer than 16 chars. * BUG 12269: nss_wins: Fix errno values for HOST_NOT_FOUND. * BUG 12405: s3-winbind: Do not return NO_MEMORY...

...itionally. * ctdbd once again successfully kills client processes on releasing public IPs. It was checking for them as tracked child processes and not finding them, so wasn't killing them. * ctdbd_wrapper now exports CTDB_SOCKET so that child processes of ctdbd (such as uses of ctdb in eventscripts) use the correct socket. * Always use Jenkins hash when creating volatile databases. There were a few places where TDBs would be attached with the wrong flags. * Vacuuming code fixes in CTDB 2.2 introduced bugs in the new code which led to header corruption for empty records. This resulted...

...uccessfully kills client processes on releasing > public IPs. It was checking for them as tracked child processes > and not finding them, so wasn't killing them. > > * ctdbd_wrapper now exports CTDB_SOCKET so that child processes of > ctdbd (such as uses of ctdb in eventscripts) use the correct socket. > > * Always use Jenkins hash when creating volatile databases. There > were a few places where TDBs would be attached with the wrong flags. > > * Vacuuming code fixes in CTDB 2.2 introduced bugs in the new code > which led to header corrupti...

...ULL dereference in failure case. o Stefan Metzmacher <metze at samba.org> * BUG 10297: s3:smbd: Only pass UCF_PREP_CREATEFILE to filename_convert() if we may create a new file. o Mathieu Parent <math.parent at gmail.com> * BUG 12371: ctdb-scripts: Fix Debian init in samba eventscript. o Garming Sam <garming at catalyst.net.nz> * BUG 9954: samba_tool/fsmo: Allocate RID Set when seizing RID manager. * BUG 10882: s4-auth: Don't check for NULL saltPrincipal if it doesn't need it. * BUG 12297: upgradeprovision: Remove objectCategory from constructed att...