similar to: [Announce] CTDB release 2.5.6 is available for download

Changes in CTDB 2.5 =================== User-visible changes -------------------- * The default location of the ctdbd socket is now: /var/run/ctdb/ctdbd.socket If you currently set CTDB_SOCKET in configuration then unsetting it will probably do what you want. * The default location of CTDB TDB databases is now: /var/lib/ctdb If you only set CTDB_DBDIR (to the old default of

Release Announcements ===================== This is the first release candidate of Samba 4.4. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.4 will be the next version of the Samba suite. UPGRADING ========= Nothing special. NEW

Release Announcements ===================== This is the first release candidate of Samba 4.4. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.4 will be the next version of the Samba suite. UPGRADING ========= Nothing special. NEW

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

Release Announcements ===================== This is the second release candidate of Samba 4.4. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.4 will be the next version of the Samba suite. UPGRADING ========= Nothing special. NEW

Release Announcements ===================== This is the second release candidate of Samba 4.4. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.4 will be the next version of the Samba suite. UPGRADING ========= Nothing special. NEW

Changes in CTDB 2.4 =================== User-visible changes -------------------- * A missing network interface now causes monitoring to fail and the node to become unhealthy. * Changed ctdb command's default control timeout from 3s to 10s. * debug-hung-script.sh now includes the output of "ctdb scriptstatus" to provide more information. Important bug fixes

Release Announcements ===================== This is the third release candidate of Samba 4.4. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.4 will be the next version of the Samba suite. UPGRADING ========= Nothing special. NEW

Release Announcements ===================== This is the third release candidate of Samba 4.4. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.4 will be the next version of the Samba suite. UPGRADING ========= Nothing special. NEW

Hi folks, We're building a new CTDB cluster - any recommendation on what version of CTDB is the most "production" at the moment? We're currently on 1.2.66 on our currently in-service clusters. Cheers, Orlando > -------- Original Message -------- > Subject: [Samba] [Announce] CTDB 2.4 available for download > Date: Fri, 23 Aug 2013 14:11:29 +1000 > From:

Is there a place I can read about the improvements to the DNS service? Thanks. On 3/16/2016 6:03 AM, Karolin Seeger wrote: > Release Announcements > ===================== > > This is the fifth release candidate of Samba 4.4. This is *not* > intended for production environments and is designed for testing > purposes only. Please report any defects via the Samba bug reporting

Hi everybody, I have tested CTDB+GFS2+CMAN under Debian. It works good but I do not understand some points. It is possible to run the CTDB defining it under services section in cluster.conf but running it on the second node shuts down the process at the first one. My CTDB configuration implies 2 active-active nodes. Does CTDB care if the node starts with clean_start="0" or

Hi 2 node drbd cluster with ocfs2. both nodes: openSUSE 4.1.9 with drbd 8.4 and ctdbd 2.3 All seems OK with ctdb: n1: ctdb status Number of nodes:2 pnn:0 192.168.0.10 OK (THIS NODE) pnn:1 192.168.0.11 OK Generation:1187222392 Size:2 hash:0 lmaster:0 hash:1 lmaster:1 Recovery mode:NORMAL (0) Recovery master:0 n2: ctdb status Number of nodes:2 pnn:0 192.168.0.10 OK pnn:1 192.168.0.11

====================================================== "In politics stupidity is not a handicap." Napoleon Bonaparte ====================================================== Release Announcements ===================== This is the first stable release of the Samba 4.4 release series. UPGRADING ========= Nothing special. NEW FEATURES/CHANGES ====================

====================================================== "In politics stupidity is not a handicap." Napoleon Bonaparte ====================================================== Release Announcements ===================== This is the first stable release of the Samba 4.4 release series. UPGRADING ========= Nothing special. NEW FEATURES/CHANGES ====================

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.

Release Announcements ===================== This is the fifth release candidate of Samba 4.4. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.4 will be the next version of the Samba suite. UPGRADING ========= Nothing special. NEW

Release Announcements ===================== This is the fifth release candidate of Samba 4.4. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.4 will be the next version of the Samba suite. UPGRADING ========= Nothing special. NEW

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 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. After finding > that the mmap coherence test did not pass, we