similar to: [Announce] Samba 4.14.0rc1 Available for Download

Release Announcements ===================== This is the fourth release candidate of Samba 4.14. 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.14 will be the next version of the Samba suite. UPGRADING ========= New GPG key ----------- The GPG

Release Announcements ===================== This is the fourth release candidate of Samba 4.14. 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.14 will be the next version of the Samba suite. UPGRADING ========= New GPG key ----------- The GPG

Release Announcements --------------------- This is the first stable release of the Samba 4.14 release series. Please read the release notes carefully before upgrading. New GPG key =========== The GPG release key for Samba releases changed from: pub dsa1024/6F33915B6568B7EA 2007-02-04 [SC] [expires: 2021-02-05] Key fingerprint = 52FB C0B8 6D95 4B08 4332 4CDC 6F33 915B 6568 B7EA uid

Release Announcements --------------------- This is the first stable release of the Samba 4.14 release series. Please read the release notes carefully before upgrading. New GPG key =========== The GPG release key for Samba releases changed from: pub dsa1024/6F33915B6568B7EA 2007-02-04 [SC] [expires: 2021-02-05] Key fingerprint = 52FB C0B8 6D95 4B08 4332 4CDC 6F33 915B 6568 B7EA uid

Hi! I'm evaluating how various binaries and components are split into different binary packages in Debian. And am having issues classifying these. Initially there has been request to remove dependency on python3-samba package (this is AD-related stuff) from samba-the-file-server package, to be able to use it on smaller devices. And at the same time, there has been another request to move

Looks like this is the actual error: 2019/10/04 09:51:29.174870 ctdbd[17244]: Recovery has started 2019/10/04 09:51:29.174982 ctdbd[17244]: ../ctdb/server/ctdb_server.c:188 ctdb request 2147483554 of type 8 length 48 from node 1 to 0 2019/10/04 09:51:29.175021 ctdbd[17244]: Recovery lock configuration inconsistent: recmaster has NULL, this node has /run/gluster/shared_storage/.CTDB-lockfile,

I?ll have to check out the script issue on Monday. You said the lock needs to be the same on all nodes. I can do that but this is now in production and restarting the ctdb service forces a failover of the ip, which actually causes a failure of a few of our Kubernetes sql database pods - they freak out and don?t recovery if storage is ripped out from under them. Is there a way to do this

Ok that looks good. Ont to try on the pc your testing. Disable ipv6 ( just remove the checkmark dont remove it. ) from the network adapter. *( optional : http://www.bvanleeuwen.nl/faq/?p=1142 ipv6 admx template. ) I have a setup with this admx, i completely disabled ipv6 in my lan. And as Rowland also is telling.. Dns domain = foo Realm = FOO Workgroup = FOO

Hi Max, On Fri, 4 Oct 2019 14:01:22 +0000, Max DiOrio <Max.DiOrio at ieeeglobalspec.com> wrote: > Looks like this is the actual error: > > 2019/10/04 09:51:29.174870 ctdbd[17244]: Recovery has started > 2019/10/04 09:51:29.174982 ctdbd[17244]: ../ctdb/server/ctdb_server.c:188 ctdb request 2147483554 of type 8 length 48 from node 1 to 0 > 2019/10/04 09:51:29.175021

Release Announcements ===================== This is the first preview release of Samba 4.5. 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.5 will be the next version of the Samba suite. UPGRADING ========= NTLMv1 authentication disabled by

Release Announcements ===================== This is the first preview release of Samba 4.5. 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.5 will be the next version of the Samba suite. UPGRADING ========= NTLMv1 authentication disabled by

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I just set up a CTDB-Cluster with two nodes. In /var/log/log.ctdb I saw the following error many times: - ---------- ERROR: samba tcp port 445, is not responding - ---------- the command "ctdb scriptstatus" is showing: - ---------- root at fs1:~# ctdb scriptstatus 11 scripts were executed last monitor cycle 00.ctdb

Release Announcements ===================== This is the second release candidate of Samba 4.5. 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.5 will be the next version of the Samba suite. UPGRADING ========= NTLMv1 authentication disabled by

Release Announcements ===================== This is the second release candidate of Samba 4.5. 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.5 will be the next version of the Samba suite. UPGRADING ========= NTLMv1 authentication disabled by

Hey all, I am trying to figure out a weird problem. I have a two node ctdb samba setup where the first node acts as expected setting the default gateway (startup shutdown takeip recoveryip) if there is a network blip / link down, but the second node does not set the default gateway properly on the initial recovery of the link after the blip has occurred. If I restart the machine or restart the

Release Announcements ===================== This is the third release candidate of Samba 4.5. 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.5 will be the next version of the Samba suite. UPGRADING ========= NTLMv1 authentication disabled by

Release Announcements ===================== This is the third release candidate of Samba 4.5. 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.5 will be the next version of the Samba suite. UPGRADING ========= NTLMv1 authentication disabled by

Does this push 4.2.x to discontinued? On Wed, Sep 7, 2016 at 9:06 AM, Stefan Metzmacher <metze at samba.org> wrote: > ====================================================== > "It does not matter how slowly you go > as long as you do not stop." > > Confucius >

====================================================== "It does not matter how slowly you go as long as you do not stop." Confucius ====================================================== Release Announcements --------------------- This is the first stable release of the Samba 4.5 release series. UPGRADING ========= NTLMv1

====================================================== "It does not matter how slowly you go as long as you do not stop." Confucius ====================================================== Release Announcements --------------------- This is the first stable release of the Samba 4.5 release series. UPGRADING ========= NTLMv1