Displaying 20 results from an estimated 700 matches similar to: "Failed to start CTDB first time after install"
2018 May 07
2
CTDB Path
Hello,
i'm still trying to find out what is the right path for ctdb.conf
(ubuntu 18.04, samba was compiled from source!!).
When im trying to start CTDB without any config file, my log in
/usr/local/samba/var/log/log.ctdb shows me:
2018/05/07 12:56:44.363513 ctdbd[4503]: Failed to read nodes file
"/usr/local/samba/etc/ctdb/nodes"
2018/05/07 12:56:44.363546 ctdbd[4503]: Failed to
2012 Apr 17
0
CTDB panics when vacuuming serverid.tdb
CTDB Samba Team,
I have a two-node cluster successfully running a GFS2 filesystem. I
compiled ctdb ver 1.12 with Samba 3.6.3 for 64-bit systems. Running on
RHEL 5.7. I was able to add the cluster to the domain but after I
restarted CTDB, it panics right after doing a vacuum of the serverid.tdb
database.
The lock file is on the GFS FS so both nodes can access it. Any
ideas as to what
2010 May 20
0
WG: Which version of CTDB
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
2018 Feb 26
0
答复: [ctdb] Unable to take recovery lock - contention
Am Montag, 26. Februar 2018, 17:26:06 CET schrieb zhu.shangzhong--- via samba:
Decoded base64 encoded body with some chinese characters:
------------------原始邮件------------------
发件人:朱尚忠10137461
收件人:samba at lists.samba.org <samba at lists.samba.org>
日 期 :2018年02月26日 17:10
主 题 :[ctdb] Unable to take recovery lock - contention
When the ctdb is starting, the "Unable to take recovery lock
2018 Feb 26
0
[ctdb] Unable to take recovery lock - contention
When the ctdb is starting, the "Unable to take recovery lock - contention" log will be output all the time.
Which cases will the "unable to take lock" errror be output?
Thanks!
The following the ctdb logs:
2018/02/12 19:38:51.147959 ctdbd[5615]: CTDB starting on node
2018/02/12 19:38:51.528921 ctdbd[6602]: Starting CTDBD (Version 4.6.10) as PID: 6602
2018/02/12 19:38:51.529060
2018 Feb 26
2
[ctdb] Unable to take recovery lock - contention
When the ctdb is starting, the "Unable to take recovery lock - contention" log will be output all the time.
Which cases will the "unable to take lock" errror be output?
Thanks!
The following the ctdb logs:
2018/02/12 19:38:51.147959 ctdbd[5615]: CTDB starting on node
2018/02/12 19:38:51.528921 ctdbd[6602]: Starting CTDBD (Version 4.6.10) as PID: 6602
2018/02/12 19:38:51.529060
2014 Feb 26
0
CTDB Debug Help
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
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
2018 Feb 26
2
答复: [ctdb] Unable to take recovery lock - contention
------------------原始邮件------------------
发件人:朱尚忠10137461
收件人:samba@lists.samba.org <samba@lists.samba.org>
日 期 :2018年02月26日 17:10
主 题 :[ctdb] Unable to take recovery lock - contention
When the ctdb is starting, the "Unable to take recovery lock - contention" log will be output all the time.
Which cases will the "unable to take lock" errror be output?
Thanks!
The
2012 May 24
0
Could not find node to take over public address
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)
>
2011 Apr 27
1
CTDB / Samba4. Nodes don't become healthy on first startup
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I'm trying to bring up a three node cluster using CTDB and SAMBA4 on a
GlusterFS clustered file system.
The filesystem itself seems to be working just fine, but CTDB doesn't
seem happy.
If I start a single node up:
service ctdb start
After about 10 seconds it becomes healthy, starts SAMBA and takes over
all 3 IP addresses. However,
2018 May 04
2
CTDB Path
Hello,
at this time i want to install a CTDB Cluster with SAMBA 4.7.7 from SOURCE!
I compiled samba as follow:
|./configure| |--with-cluster-support
||--with-shared-modules=idmap_rid,idmap_tdb2,idmap_ad|
The whole SAMBA enviroment is located in /usr/local/samba/.
CTDB is located in /usr/local/samba/etc/ctdb.
I guess right that the correct path of ctdbd.conf (node file, public
address file
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
2020 Aug 08
1
CTDB question about "shared file system"
On Sat, Aug 8, 2020 at 2:52 AM Martin Schwenke <martin at meltin.net> wrote:
> Hi Bob,
>
> On Thu, 6 Aug 2020 06:55:31 -0400, Robert Buck <robert.buck at som.com>
> wrote:
>
> > And so we've been rereading the doc on the public addresses file. So it
> may
> > be we have gravely misunderstood the *public_addresses* file, we never
> read
> >
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
2014 Jul 03
0
ctdb split brain nodes doesn't see each other
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
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
2014 Oct 29
1
smbstatus hang with CTDB 2.5.4 and Samba 4.1.13
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]:
2019 May 16
0
CTDB node stucks in " ctdb-eventd[13184]: 50.samba: samba not listening on TCP port 445"
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