similar to: ctdb_client.c control timed out - banning nodes

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

There is a 3 nodes ctdb cluster is running. When one of 3 nodes is powered down, lots of logs will be wrote to log.ctdb. node1: repeat logs: 2018/09/04 04:35:06.414369 ctdbd[10129]: Recovery has started 2018/09/04 04:35:06.414944 ctdbd[10129]: connect() failed, errno=111 2018/09/04 04:35:06.415076 ctdbd[10129]: Unable to run startrecovery event node2: repeat logs: 2018/09/04 04:35:09.412368

Hi Benedikt, On Thu, 16 May 2019 10:32:51 +0200, Benedikt Kaleß via samba <samba at lists.samba.org> wrote: > Hi everybody, > > I just updated my ctdb node from Samba version > 4.9.4-SerNet-Debian-11.stretch to Samba version > 4.9.8-SerNet-Debian-13.stretch. > > After restarting the sernet-samba-ctdbd service the node doesn't come > back and remains in state

Hi everybody, I just updated my ctdb node from Samba version 4.9.4-SerNet-Debian-11.stretch to Samba version 4.9.8-SerNet-Debian-13.stretch. After restarting the sernet-samba-ctdbd service the node doesn't come back and remains in state "UNHEALTHY". I can find that in the syslog: May 16 11:25:40 ctdb-lbn1 ctdb-eventd[13184]: 50.samba: samba not listening on TCP port 445 May 16

I am attempting to enable IPv6 on our CTDB setup. I have placed the IPv6 address in the public_addresses file with the correct prefix. The addresses never come up and I recieve these messages in the log 2012/06/28 10:54:43.313227 [ 1820]: Async operation failed with ret=0 res=1 opcode=0 2012/06/28 10:54:43.313918 [ 1820]: Async operation failed with ret=0 res=1 opcode=0 2012/06/28

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

Can anyone help with some pointers to debug a problem with Samba and CTDB with smbstatus traversing the connections tdb? I've got a new two node cluster with Samba and CTDB on AIX. If I run smbstatus when the server has much user activity it hangs and the node it was run on gets banned. I see the following in the ctdb log: 2014/10/29 11:12:45.374580 [3932342]:

Hi, we run ctdb with samba on SLES11. It was running for some month ok but after an update of the system and ctdb it fails to run. I tried to setup a new ctdb setup on two other nodes and it still fails with the same error. After startup the status is: > ctdb status > Number of nodes:2 > pnn:0 10.94.43.7 DISABLED > pnn:1 10.94.43.8 DISABLED (THIS NODE) >

Hello, Submitting a bug report for Samba crashing on occasion when copying files (also submitted a bug report w/Debian). Package: samba Version: 4.0.13+dfsg-1 While copying files from Linux(SAMBA) -> to a Windows 7 host using Debian Testing (x86_64) w/ distribution's Samba version (4.0.13+dfsg-1): Cores: # ls -ltr *smb* -rw------- 1 root root 2764800 Nov 10 12:30

Hi, I have successfully compiled and installed Samba 4.0.0rc2 on Debian Squeeze as described in the Wiki. In order to support Win XP and Win 7 clients, I have created GPOs for folders redirection. The problem I am facing is with random PANIC messages in the logs and logon/logoff/file access process gets hung on the client. Here are the logs: Oct 18 13:42:32 pdc smbd[27384]: [2012/10/18

Hi! We're running Samba4 (Version 4.0.0beta4) and are experiencing problems with smb_panic actions which result in loads of sleep processes in the end taking down the entire machine. This problem did not exist in prior builds for us (upgraded from alpha17 to beta3 and then beta4). Are there any specific log extracts I can supply that can help someone pinpoint the problem? log.smbd seems to

Hello, My envirronement: Debian 7.5 Samba version 4.1.7 from backport Cups 1.5.3-5 I have upgrade from samba 3 to samba4 this morning. Since, I have some very strange error when I try to print or list the shared printer from a windows Server: Here is my syslog log file when I try to refresh the printers list from a Windws 2008 server. Jun 4 17:00:24 daisy2k11 smbd[22133]: [2014/06/04

I will probably file a bug about this, but perhaps someone here will have some ideas. We have a problem with files being deleted instead of being saved when making changes in Microsoft Excel. The log shows an error of: 'Lock order violation'. This is with Samba 4.1.6 and happens on both Linux (2.6.25-14.fc9.i686) and Solaris 10. No such problem when running Samba 3.6.22. We have a setup

Hi, I thought I should share this unusual behaiviour of samba 4.1.11. All of a sudden while I tried to delete a Folder via samba on a share it crashed. I was using Mac OSx's V 10.9.4 internal samba client (regular "CMD+K" mount via Finder). Server: [...] FreeBSD 10.0-RELEASE-p7 #0: Tue Jul 8 06:37:44 UTC 2014 root at amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC

Hi, I'm using a fresh install of samba 4.1.11 compiled from source on a fully patched Ubuntu 12.04 Server. Most Clients are Windows 7 and some are Windows XP. My logs get flooded (happend over 100 times in the last 12 hours) with internal errors and smbd dumps core. Has anyone else such a problem or knows how to fix it? 2014/08/12 07:27:50.280149, 0]

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

I have Samba 4.0.9 installed on three Centos servers. On my primary DC I am getting faults and core dumps. Oct 2 06:10:37 dc1 smbd[1195]: [2013/10/02 06:10:37.083800, 0] ../lib/util/fault.c:72(fault_report) Oct 2 06:10:37 dc1 smbd[1195]: =============================================================== Oct 2 06:10:37 dc1 smbd[1195]: [2013/10/02 06:10:37.084493, 0]

Dear list, I keep getting strange "internal error"s from smbd. I increased the log level to 3 and pasted the relevant log snippet. Does anyone know (or guess) what's going on? What should I check? Any direction to investigate? Thanks a lot, Sascha ? =============================================================== [2014/03/24 13:28:49.787910, ?0, pid=13041, effective(3000026, 20),

Hello, A few months ago the distribution I use (Debian Testing) moved from Samba 3 to Samba 4 - I started seeing a lot of problems. Since then there are two bugs I find occurring on a regular basis: 1. Consistent dumping core on a regular basis (very rarely, if ever occurred with Samba 3) a. $ ls -ltr *core*smbd* |wc -l b. 1297 c. $ du -ach *core*smbd*|tail -n 1

Server: Debian Wheezy 7.3, ECC RAM, updated via cron-apt Version: 4.1.4 Clients: Windows 8.1 Pro Environment: Active Directory, installed from scratch (no migration), roaming profiles, group policies for printers, network mappings, ... Hello everyone, I've upgraded my Samba installation from 4.0.14 (which was working more or less fine) to 4.1.4 yesterday - via Sernet packages, i. e. just