search for: startrecoveri

Displaying 7 results from an estimated 7 matches for "startrecoveri".

Did you mean: startrecovery
2018 Sep 05
0
[ctdb]Unable to run startrecovery event(if mail contentis encrypted, please see the attached file)
Thanks Martin! We are using the ctdb 4.6.10. Are you able to recreate this every time? Sometimes? Rarely? Rarely. Note that you're referring to nodes 1, 2, 3 while CTDB numbers the nodes 0, 1, 2. In fact, the situation is a little more confused than this: This is my wrong. The CTDB numbers the nodes is 0,1,2. # ctdb status Number of nodes:3 pnn:0 10.231.8.70 OK pnn:1 10.231.8.68 OK
2018 Sep 05
0
[ctdb]Unable to run startrecovery event(if mail contentis encrypted, please see the attached file)
Thanks Martin! We are using the ctdb 4.6.10. Are you able to recreate this every time? Sometimes? Rarely? Rarely. Note that you're referring to nodes 1, 2, 3 while CTDB numbers the nodes 0, 1, 2. In fact, the situation is a little more confused than this: This is my wrong. The CTDB numbers the nodes is 0,1,2. # ctdb status Number of nodes:3 pnn:0 10.231.8.67 OK pnn:1 10.231.8.65 OK
2018 Sep 06
0
[ctdb]Unable to run startrecovery event
Thanks Martin. --------------------------------------------------- Re: [Samba] [ctdb]Unable to run startrecovery event On Thu, 6 Sep 2018 14:24:12 +0800 (CST), "zhu.shangzhong--- via samba" <samba at lists.samba.org> wrote: > I have checked more logs. > Before ctdb-eventd went away, system memory utilization is very high, almost 100%. > Is it related to "Bad talloc
2018 Sep 06
1
[ctdb]Unable to run startrecovery event
Martin, I have checked more logs. Before ctdb-eventd went away, system memory utilization is very high, almost 100%. Is it related to "Bad talloc magic value - wrong talloc version used/mixed"? 2018/08/14 15:22:57.818762 ctdb-eventd[10131]: 05.system: WARNING: System memory utilization 95% >= threshold 80% 2018/08/14 15:22:57.818800 ctdb-eventd[10131]: 05.system: WARNING: System
2018 Sep 05
1
[ctdb]Unable to run startrecovery event(if mail content is encrypted, please see the attached file)
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
2014 Oct 07
1
CDTB On Samba 4.1.12 As Member files server.
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
2013 Apr 09
0
Failed to start CTDB first time after install
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