similar to: [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

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

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

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 Stefan, On Thu, 26 Jan 2023 16:35:59 +0100, Stefan Kania via samba <samba at lists.samba.org> wrote: > I'm having a CTDB-Cluster with two nodes (both Ubuntu wit > Sernet-packages 4.17.4). Now I want to replace one of the nodes. The > first step was to bring a new node to the CTDB-Cluster. This time a > Debian 11 but with the same sernet-packages (4.17.4). Adding the

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

Hi to all, I'm having a CTDB-Cluster with two nodes (both Ubuntu wit Sernet-packages 4.17.4). Now I want to replace one of the nodes. The first step was to bring a new node to the CTDB-Cluster. This time a Debian 11 but with the same sernet-packages (4.17.4). Adding the new node to /etc/ctdb/nodes at the end of the list. And the virtual IP to /etc/ctdb/public_addresses, also at the end

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

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

Hi Bob, On Tue, 29 Sep 2020 18:27:00 -0400, Robert Buck via samba <samba at lists.samba.org> wrote: > When I try to enable CTDB to manage (legacy) SMB and Winbind, I get startup > errors. > > Sep 29 22:23:06 euw2-samba-server-c21-01 ctdb-eventd[1509]: *49.winbind: > Failed to start winbind* > > Sep 29 22:23:06 euw2-samba-server-c21-01 ctdb-eventd[1509]: *startup

Hi Micha, On Mon, 7 May 2018 15:46:50 +0200, Micha Ballmann <ballmann at uni-landau.de> wrote: > 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

Ok, thanks. [root at euw2-samba-server-c21-01 ec2-user]# systemctl status winbind.service *?* winbind.service - Samba Winbind Daemon Loaded: loaded (/usr/lib/systemd/system/winbind.service; enabled; vendor preset: disabled) Active: *failed* (Result: exit-code) since Wed 2020-09-30 12:58:25 UTC; 1s ago Docs: man:winbindd(8) man:samba(7) man:smb.conf(5)

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

Thanks, i added "Environment=PATH=$PATH:/usr/local/samba/bin:/bin". Needed also to add "/bin" because couldnt find "sleep". Thats the script now: ---- [Unit] Description=CTDB Documentation=man:ctdbd(1) man:ctdb(7) After=network-online.target time-sync.target ConditionFileNotEmpty=/usr/local/samba/etc/ctdb/nodes [Service]

------------------原始邮件------------------ 发件人：朱尚忠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

On 03/03/2020 09:13, Ralph Boehme via samba wrote: > Am 3/3/20 um 10:05 AM schrieb Micha Ballmann via samba: >> Mar? 3 09:50:50 ctdb1 systemd[1]: Starting CTDB... >> Mar? 3 09:50:50 ctdb1 ctdbd[24663]: CTDB starting on node >> Mar? 3 09:50:50 ctdb1 ctdbd[24667]: Starting CTDBD (Version 4.11.6) as >> PID: 24667 >> Mar? 3 09:50:50 ctdb1 ctdbd[24667]: Created PID file

Hai, Hmm, about .. > "Environment=PATH=$PATH:/usr/local/samba/bin:/bin". > Needed also > to add "/bin" because couldnt find "sleep". /bin should be found in $PATH.. In since it looks like it does not. Then i suggest this: Environment="PATH=$PATH:/usr/local/samba/bin:/usr/local/samba/sbin:/bin:/sbin:/usr/bin:/usr/sbin" # to make sure you

Ah, yes, thats it Ralph.. Good one. Then in the systemd.service file you need to add. [Service] Environment=PATH=$PATH:/usr/local/samba/bin > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Ralph Boehme via samba > Verzonden: dinsdag 3 maart 2020 10:13 > Aan: Micha Ballmann; Anoop C S > CC: samba at lists.samba.org >

Hi all We did some failover/failback tests on 2 nodes��A and B�� with architecture 'glusterfs + ctdb(public address) + nfs-ganesha'�� 1st: During write, unplug the network cable of serving node A ->NFS Client took a few seconds to recover to conitinue writing. After some minutes, plug the network cable of serving node A ->NFS Client also took a few seconds to recover

When I try to enable CTDB to manage (legacy) SMB and Winbind, I get startup errors. Sep 29 22:23:06 euw2-samba-server-c21-01 ctdb-eventd[1509]: *49.winbind: Failed to start winbind* Sep 29 22:23:06 euw2-samba-server-c21-01 ctdb-eventd[1509]: *startup event failed* Sep 29 22:23:06 euw2-samba-server-c21-01 ctdbd[1507]: *startup event failed* Sep 29 22:23:11 euw2-samba-server-c21-01 ctdbd[1507]: