search for: eventscripts

...2013/04/09 16:10:03.619164 [30575]: Release freeze handler for prio 3 2013/04/09 16:10:03.622723 [recoverd:30648]: server/ctdb_recoverd.c:1815 Recovery - disabled recovery mode 2013/04/09 16:10:03.623218 [recoverd:30648]: Disabling ip check for 9 seconds 2013/04/09 16:10:03.623228 [30575]: Running eventscripts with arguments ipreallocated 2013/04/09 16:10:03.623260 [30575]: Monitoring has been disabled 2013/04/09 16:10:03.623283 [30575]: server/eventscript.c:800 Starting eventscript ipreallocated 2013/04/09 16:10:03.971720 [30575]: server/eventscript.c:486 Eventscript ipreallocated finished with state...

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

I did a new rsync and compiled ctdb new. This version did not establish a new config file!!!: /etc/sysconfig/ctdb. I had to use my old one. After starting ctdb recognizing that ctdb wants his state directory in /usr/local/var/ctdb/state I could not fix that in /etc/sysconfig/ctdb file. So I had do mkdir /usr/local/var/ctdb manually. After starting ctdb on both nodes all nodes rest unhealthy. And

Hello all, I've some CTDB issue which I'm not sure where to start... I follow this guide by steve which is nice. The different on what have is that I don't have drbd running... Also I've 4 x GE which is all Connected to a switch with different ip but same subnet This is suppose to load balance the traffic as under samba dns, they all have the same name. I'm only planing 3

Martin Schwenke schrieb am 15.02.2023 23:23: > Hi Uli, > > [Sorry for slow response, life is busy...] Thanks for answering anyway! > On Mon, 13 Feb 2023 15:06:26 +0000, Ulrich Sibiller via samba > OK, this part looks kind-of good. It would be interesting to know how > long the entire failover process is taking. What exactly would you define as the begin and end of the

Hi, I'm trying to set up a small CTDB cluster running in an IPoIB InfiniBand network. When I try to start up a cluster with a set of public IP addresses, the public addresses do not come online. So, I removed the public address configuration and started a single node up by hand, then tried to add a public address as follows: [root at gp-1-0 ctdb]# ctdb ip Public IPs on node 0 [root at

CTDB Samba Team, I have a two-node cluster successfully running a GFS2 filesystem. I compiled ctdb ver 1.12 with Samba 3.6.3 for 64-bit systems. Running on RHEL 5.7. I was able to add the cluster to the domain but after I restarted CTDB, it panics right after doing a vacuum of the serverid.tdb database. The lock file is on the GFS FS so both nodes can access it. Any ideas as to what

On Thu, 16 Feb 2023 17:30:37 +0000, Ulrich Sibiller <ulrich.sibiller at atos.net> wrote: > Martin Schwenke schrieb am 15.02.2023 23:23: > > OK, this part looks kind-of good. It would be interesting to know how > > long the entire failover process is taking. > > What exactly would you define as the begin and end of the failover? From "Takeover run

Hi, I use shorewall-4.5.4 + lsm-0.143 and it does not seem to work as expected... When all providers are up, everything seems fine. When one goes down, lsm says "link <provider> down event"... and it seems ok but we then experience some problems such as a few unreachable sites, DNS problems... If I remove the downed provider from all confs and restart, everything works again.

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

This will be the last stable release of CTDB 2.5.x. CTDB 2.5.6 should only be used with Samba releases prior to Samba 4.2.x (i.e. Samba releases 3.6.x, 4.0.x and 4.1.x). Please note that Samba releases 3.6.x, 4.0.x and 4.1.x are out of support. If you are still using any of these releases for clustered samba with CTDB 2.5.x, please switch to latest Samba 4.3.x or 4.4.0 (Since Samba 4.2.0 release

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

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

Changes in CTDB 2.2 =================== 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

====================================================== "Cheers to a new year and another chance for us to get it right." Oprah Winfrey ====================================================== Release Announcements --------------------- This is the latest stable release of Samba 4.4. Changes since 4.4.8: -------------------- o Michael Adam <obnox at samba.org>

====================================================== "Cheers to a new year and another chance for us to get it right." Oprah Winfrey ====================================================== Release Announcements --------------------- This is the latest stable release of Samba 4.4. Changes since 4.4.8: -------------------- o Michael Adam <obnox at samba.org>

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

====================================================== "Some people die at 25 and aren't buried until 75." Benjamin Franklin ====================================================== Release Announcements --------------------- This is the latest stable release of the Samba 4.5 release series. Changes since 4.5.1: -------------------- o Michael Adam <obnox at