search for: ctdb_recovered

Hello all, I've some CTDB issue which I'm not sure where to start... I follow this guide by steve which is nice. The different on what have is that I don't have drbd running... Also I've 4 x GE which is all Connected to a switch with different ip but same subnet This is suppose to load balance the traffic as under samba dns, they all have the same name. I'm only planing 3

Hello, I've got a two node CTDB/Samba cluster that I'm having trouble with trying to add back a node after having to do an OS reload on it. The servers are running CTDB 2.5.1 and Samba 4.1.4 on AIX 7.1 TL2. The Samba CTDB databases and Samba service work fine from the node that was not reloaded. The rebuilt node is failing to re-add itself to the cluster. I'm looking for

...ning latest Centos 7.2 with Samba/CTDB from standard repos. Underlying FS is MooseFS backed by ZFS. Every so often, especially when CIFS activity is high (eg 100+ users loading or saving Windows profiles, we see a BUG in our logs: Jun 20 16:31:13 metamora kernel: BUG: Bad page state in process ctdb_recovered pfn:8c8e00 Jun 20 16:31:13 metamora kernel: page:ffffea0023238000 count:0 mapcount:0 mapping: (null) index:0x7ff509800 Jun 20 16:31:13 metamora kernel: page flags: 0x2fffff00184008(uptodate|head|swapbacked|unevictable) Jun 20 16:31:13 metamora kernel: page dumped because: PAGE_FLAGS_CH...

My ctdb version is 4.17.7 Hello, everyone. My ctdb cluster configuration is correct and the cluster is healthy before operation. My cluster has three nodes, namely host-192-168-34-164, host-192-168-34-165, and host-192-168-34-166. And the node host-192-168-34-164 is the leader before operation. I conducted network oscillation testing on node host-192-168-34-164?I down the interface of private

...h Samba/CTDB from standard > repos. Underlying FS is MooseFS backed by ZFS. Every so often, especially > when CIFS activity is high (eg 100+ users loading or saving Windows > profiles, we see a BUG in our logs: > > Jun 20 16:31:13 metamora kernel: BUG: Bad page state in process > ctdb_recovered pfn:8c8e00 > Jun 20 16:31:13 metamora kernel: page:ffffea0023238000 count:0 mapcount:0 > mapping: (null) index:0x7ff509800 > Jun 20 16:31:13 metamora kernel: page flags: > 0x2fffff00184008(uptodate|head|swapbacked|unevictable) > Jun 20 16:31:13 metamora kernel: page dumped...

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

We've had a few crashes of CTDB where it tries to allocate > 256kB of memory to "pulldb_data" (assuming that the big number given below is in bytes). Jan 13 15:27:13 nasfe03 ctdbd: server/ctdb_recover.c:352 Failed to expand pulldb_data to 268435485 Jan 13 15:27:13 nasfe03 ctdbd: ctdb fatal error: failed to allocate memory for recovery. shutting down Jan 13 15:27:13 nasfe03

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