similar to: Winbind issues with CTDB

I am attempting to configure a Samba cluster using DRBD and CTDB. I am currently having some issues with winbind. Everytime I start winbind or attempt to join my server to the domain the machine stalls and the ctdb error log is filled with the following: 2010/04/30 14:49:59.367076 [ 8394]: server/ctdb_control.c:445 Unknown CTDB control opcode 119 I have not been able to find a description of

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

I am currently setting up a cluster of Samba servers using DRBD and CTDB. I have gotten the DRBD and CTDB configured on my cluster. I have configured Samba and Winbind to join my active directory domain. Right now I am struggling to get authentication through Winbind to work. My /var/log/secure file looks like my system is not even trying to authenticate against AD. wbinfo -u work great as does

I have been working on a CTDB cluster on and off for a while now. I had it working great for a while. THen I decide dthat I wanted to change the configuration of my replicated volumes. I changed my DRBD configuration to match my desired configuration. Now I can get the CTDB to work quite right. I am able to join the cluster to the domain without issues. I can also list my ad users and groups using

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

We've only seen this error once, just occurred. We were having domain join issues. Enter ******@*******.local's password: ../../source3/lib/dbwrap/dbwrap_ctdb.c:855 ERROR: new_seqnum[10] != old_seqnum[8] + (0 or 1) after failed TRANS3_COMMIT - this should not happen! secrets_store_JoinCtx: dbwrap_transaction_commit() failed for SOMDEV libnet_join_joindomain_store_secrets:

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

Hello list, I compiled the CTDB version from samba.org::ftp/unpacked/ctdb with the parameter: " --prefix= " This I did on CentOS 5.5 Then I copy and edit ctdb.sysconfig from /usr/src/ctdb/config to /etc/sysconfig/ctdb I set CTDB_RECOVERY_LOCK="/share/ctdb_lock/lock_file" on all three nodes. Every node can read and write on /share. When I try to start ctdb it start successful

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

Dear all, after downloading ctdb with rsync -avz samba.org::ftp/unpacked/ctdb and compiling well. I installed on my Centos 5.3 sernet package samba 3.5.2. Also working well. But after setting up ctdb and samba und running it my two nodes freezing for a while And ctdb and samba are down again. On Both nodes My /etc/sysconfig/ctdb: CTDB_RECOVERY_LOCK="/cluster/recovery/recovery"

I don't know if I can ask here, but I don't have any answer in official forum[1]. I really need to implement this, please help me. I did all steps of INSTALL documentation and I got this error: [2010/12/10 11:58:33.911661, 0] lib/module.c:59(do_smb_load_module) Error trying to resolve symbol 'init_samba_module' in /usr/lib64/samba/vfs/mysql_audit.so:

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 2.5.3 dual node file server with 4.1.9 serving AD domain Hi We have enabled the script at: /etc/cdb/events.d/50.samba but when we are the enabled node, it starts not only smbd but also nmbd. This doesn't make sense in an AD domain. I've tried disabling nmbd starting under openSUSE's systemd but ctdb overrides that, I've had a look at the script but can't decipher the bit

Ubuntu 14.04, ctdb 2.5.1 from the ubuntu package. samba 4.1.11 with cluster support from source. Error upon startup only. Restarting ctdb on that node clears the error. The other node with the same config is OK. Any ideas? Cheers, Steve smb.conf [global] workgroup = ALTEA realm = ALTEA.SITE security = ADS kerberos method = secrets and keytab netbios name = SMBCLUSTER disable netbios = Yes

Ubuntu 14.04, ctdb 2.5.3, samba 4.1.11. CTDB is working with IP takeover between the 2 nodes. The machine is joined to the domain. Any help with the following errors would be most gratefully received. 1. connect to socket error: ctdb status 2014/08/16 15:32:03.248034 [23255]: client/ctdb_client.c:267 Failed to connect client socket to daemon. Errno:Connection refused(111) common/cmdline.c:156

Hello, We are using CTDB / Samba to serve a number of windows users, at this point around 1200. We have a 4 node CTDB setup. CTDB version - ctdb-1.0.114.7-1 Samba Version - sernet-samba-4.1.16-10 In recent months we've seen a big problem when 1 of the CTDB nodes is stopped or disconnected either manually or resulting from a problem. On some occasions, all other nodes get banned if a node

Ubuntu 14.04. 2 node ctdb in an 4.1.11 AD domain with 4.1.11 member servers on each node. winbindd is present but nss and pam are controlled by sssd. All OK, except that the event script which starts samba is not working. smb.conf [global] workgroup = ALTEA realm = ALTEA.SITE security = ADS kerberos method = secrets and keytab netbios name = SMBCLUSTER clustering = Yes ctdbd socket =

hello i m using asterisk-1.0.9. i want to connect to db through odbc. isql is working. but asterisk is not getting user information from this table. can any one pls check this /etc/asterisk/extconfig.conf [settings] sipusers => odbc,mysql1,sip_buddies sippeers => odbc,mysql1,sip_buddies sip.conf => odbc,mysql1,sip_buddies sipfriends => odbc,mysql1,sip_buddies

hello i m using asterisk-1.0.9. i want to connect to db through odbc. isql is working. but asterisk is not getting user information from this table. can any one pls check this odbc connection is working properly is there some thing required /etc/asterisk/extconfig.conf [settings] sipusers => odbc,mysql1,sip_buddies sippeers => odbc,mysql1,sip_buddies sip.conf =>