similar to: CTDB panics when vacuuming serverid.tdb

Hi, I am setting up a two node Samba cluster with CTDB in AWS in two different subnets. All IP ports are open between these two subnets. I am initially forming the Samba cluster with one node, then will add the second node after startup of CTDB. I am not using public_addresses for CTDB due to AWS not supporting VIP's. I am using 64bit Amazon Linux with two NICs defined, eth0 as the

Hello I find the following email form internet, and I have the same problem, can you share your information about this issue? [Samba] ctdb issue: existing header for db_id 0xf2a58948 has larger RSN 1 than new RSN 1 in ctdb_persistent_store Nate Hardt nate at scalecomputing.com

Hi, I?ve setup a simple ctdb cluster. Actually copied the config file from an existing system. Thats what happens: Node 1, alone Number of nodes:2 pnn:0 10.0.0.1 OK (THIS NODE) pnn:1 10.0.0.2 DISCONNECTED|UNHEALTHY|INACTIVE Generation:1369816268 Size:1 hash:0 lmaster:0 Recovery mode:NORMAL (0) Recovery master:0 Node1, after start of ctdb on Node 2 Number of nodes:2 pnn:0

Hi everyone; Have a Windows 2012 based workload that generates many (20K+ PPS) small reads (Wireshark tells me the individual packets are typically less than 200 bytes and are Read AndX Request) from eight or so hosts to a Samba server running on RHEL 6.5. Samba version is the latest Red Hat provided 3.6.9 version. Things are going quite a bit slower than expected (as compared to the same

Hi, last weekend I've updated samba and ctdb on my 2-node cluster. Samba is now on 3.5.6 (from 3.3.4), ctdb on 1.0.114 (from 1.0.84). Both installed from repo via yum and ctdb-packages. After restarting both nodes everything was fine, we could access files on the cluster. On monday I noticed that the nodes didn't had their initial adresses: Node 1: hostname dscln01, public IP

Hi Bob, On Thu, 26 Oct 2017 22:44:30 -0700, Computerisms Corporation via samba <samba at lists.samba.org> wrote: > I set up a ctdb cluster a couple months back. Things seemed pretty > solid for the first 2-3 weeks, but then I started getting reports of > people not being able to access files, or some times directories. It > has taken me a while to figure some stuff out,

** Low Priority ** Hi Volker, This is regarding your fix on recycled PIDs. I am an NCP developer from Novell and we use libsmbsharemodes library from Samba for Cross Protocols Locks between NCP, Samba and others. I have few queries regarding your fix. In your fix, you have added a new field called 'unique_id' in the server_id structure and we need to pass this in our call to samba

Hi List, I set up a ctdb cluster a couple months back. Things seemed pretty solid for the first 2-3 weeks, but then I started getting reports of people not being able to access files, or some times directories. It has taken me a while to figure some stuff out, but it seems the common denominator to this happening is vacuuming timeouts for locking.tdb in the ctdb log, which might go on

On Thu, 2 Nov 2017 11:17:27 -0700, Computerisms Corporation via samba <samba at lists.samba.org> wrote: > This occurred again this morning, when the user reported the problem, I > found in the ctdb logs that vacuuming has been going on since last > night. The need to fix it was urgent (when isn't it?) so I didn't have > time to poke around for clues, but immediately

Originally filed by Robert LeBlanc as Debian Bug # 652679 - <http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652679> <Quote> Package: winbind Version: 2:3.6.1-3 Severity: important Dear Maintainer, After upgrading to 3.6.1 I am no longer able to login to Debian using my Active Directory account. 'winbind -u', 'winbind -g', 'winbind -t' and many others work

Hello, I found a bug in ipconfig and I'm sending a proposed patch for it. I've only seen it happen in 2 dhcp-server environments. Scenario: ipconfig sends a DHCP_DISCOVER, server A answers with a DHCP_OFFER, server B answers with a DHCP_OFFER, ipconfig sends a DHCP_REQUEST for server A, ipconfig accepts the DHCP_OFFER from server B instead of DHCP_ACK from server A. <== BUG The reason

Release Announcements ===================== This is the second release candidate of Samba 4.8. 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.8 will be the next version of the Samba suite. UPGRADING ========= NEW FEATURES/CHANGES

Release Announcements ===================== This is the second release candidate of Samba 4.8. 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.8 will be the next version of the Samba suite. UPGRADING ========= NEW FEATURES/CHANGES

Release Announcements ===================== This is the first release candidate of Samba 4.8. 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.8 will be the next version of the Samba suite. UPGRADING ========= NEW FEATURES/CHANGES

Release Announcements ===================== This is the first release candidate of Samba 4.8. 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.8 will be the next version of the Samba suite. UPGRADING ========= NEW FEATURES/CHANGES

Release Announcements ===================== This is the third release candidate of Samba 4.8. 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.8 will be the next version of the Samba suite. UPGRADING ========= NEW FEATURES/CHANGES

Release Announcements ===================== This is the third release candidate of Samba 4.8. 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.8 will be the next version of the Samba suite. UPGRADING ========= NEW FEATURES/CHANGES

Hi, Some users are experiencing problems working with files in Windows and Samba shares within engineering applications. The sequence is as follows: A user opens a file, e.g. a drawing, inside an application. The user works fine for a while, but suddenly it cannot edit the file anymore. The only way to continue working is closing and opening the file again, like if the session had expired and a

Am 07.11.18 um 12:07 schrieb Rowland Penny via samba: > On Wed, 7 Nov 2018 11:44:28 +0100 > Reindl Harald via samba <samba at lists.samba.org> wrote: > >> >> Am 07.11.18 um 09:54 schrieb Rowland Penny via samba: >>> On Wed, 7 Nov 2018 05:45:45 +0300 >>> Albert Berger via samba <samba at lists.samba.org> wrote: >>> >>>>

Hi Martin, well, it has been over a week since my last hung process, but got another one today... >> So, not sure how to determine if this is a gluster problem, an lxc >> problem, or a ctdb/smbd problem. Thoughts/suggestions are welcome... > > You need a stack trace of the stuck smbd process. If it is wedged in a > system call on the cluster filesystem then you can blame