Displaying 7 results from an estimated 7 matches for "ctdb_client".
2015 May 19
0
ctdb_client.c control timed out - banning nodes
...om a problem. On some occasions, all other nodes get banned if a node is stopped; sometimes it's just 1 or 2 of the other nodes but it always happens to at least 1.
In the logs the problems always start with "control timed out". See below:
2015/05/18 14:24:23.375195 [ 6031]: client/ctdb_client.c:759 control timed out. reqid:129 opcode:43 dstnode:0
2015/05/18 14:24:23.375232 [ 6031]: client/ctdb_client.c:870 ctdb_control_recv failed
2015/05/18 14:24:23.375240 [ 6031]: Async operation failed with state 3, opcode:0
2015/05/18 14:24:23.375257 [ 6031]: Async wait failed - fail_count=1
2015/05...
2019 May 16
2
CTDB node stucks in " ctdb-eventd[13184]: 50.samba: samba not listening on TCP port 445"
...P port 445
May 16 11:25:42 ctdb-lbn1 ctdb-eventd[13184]: monitor event failed
May 16 11:25:46 ctdb-lbn1 ctdb-eventd[13184]: 50.samba: samba not
listening on TCP port 445
May 16 11:25:46 ctdb-lbn1 ctdb-eventd[13184]: monitor event failed
May 16 11:25:50 ctdb-lbn1 ctdb-recoverd[13293]:
../ctdb/server/ctdb_client.c:678 control timed out. reqid:2147483471
opcode:80 dstnode:1
May 16 11:25:50 ctdb-lbn1 ctdb-recoverd[13293]:
../ctdb/server/ctdb_client.c:791 ctdb_control_recv failed
May 16 11:25:50 ctdb-lbn1 ctdb-recoverd[13293]: Async operation failed
with state 3, opcode:80
May 16 11:25:50 ctdb-lbn1 ctdb-recov...
2014 Jul 03
0
ctdb split brain nodes doesn't see each other
...18302628885633695744 for client 65746
2014/07/03 16:08:18.936008 [33287]: Trigger takeoverrun
2014/07/03 16:08:20.288537 [33287]: Trigger takeoverrun
2014/07/03 16:08:23.891691 [33243]: Node became HEALTHY. Ask recovery master 0 to perform ip reallocation
2014/07/03 16:10:39.962127 [33287]: client/ctdb_client.c:759 control timed out. reqid:67831 opcode:80 dstnode:1
2014/07/03 16:10:39.962203 [33287]: client/ctdb_client.c:870 ctdb_control_recv failed
2014/07/03 16:10:39.962219 [33287]: Async operation failed with state 3, opcode:80
2014/07/03 16:10:39.962235 [33287]: Async wait failed - fail_count=1
2014...
2019 May 16
0
CTDB node stucks in " ctdb-eventd[13184]: 50.samba: samba not listening on TCP port 445"
...2 ctdb-lbn1 ctdb-eventd[13184]: monitor event failed
> May 16 11:25:46 ctdb-lbn1 ctdb-eventd[13184]: 50.samba: samba not
> listening on TCP port 445
> May 16 11:25:46 ctdb-lbn1 ctdb-eventd[13184]: monitor event failed
> May 16 11:25:50 ctdb-lbn1 ctdb-recoverd[13293]:
> ../ctdb/server/ctdb_client.c:678 control timed out. reqid:2147483471
> opcode:80 dstnode:1
> May 16 11:25:50 ctdb-lbn1 ctdb-recoverd[13293]:
> ../ctdb/server/ctdb_client.c:791 ctdb_control_recv failed
> May 16 11:25:50 ctdb-lbn1 ctdb-recoverd[13293]: Async operation failed
> with state 3, opcode:80
> May 16...
2018 Sep 05
1
[ctdb]Unable to run startrecovery event(if mail content is encrypted, please see the attached file)
...29:33.414817 ctdbd[10129]: Tearing down connection to dead node :0
2018/09/04 04:29:33.420483 ctdbd[10129]: Recovery mode set to ACTIVE
2018/09/04 04:29:33.422946 ctdb-recoverd[11302]: ctdb_control error: 'node is disconnected'
2018/09/04 04:29:33.438802 ctdb-recoverd[11302]: ../ctdb/client/ctdb_client.c:1584 ctdb_control for getnodes failed ret:-1 res:-1
2018/09/04 04:29:33.438814 ctdb-recoverd[11302]: ../ctdb/server/ctdb_recoverd.c:2515 Unable to get nodemap from recovery master 0
2018/09/04 04:29:36.440112 ctdb-recoverd[11302]: Election period ended
2018/09/04 04:29:52.465429 ctdb-recoverd[113...
2014 Aug 16
1
CTDB: Failed to connect client socket to daemon.
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 Failed to connect to daemon
2014/08/16 15:32:03.261221 [23255]: Failed to init ctdb
/etc/default/ctdb
CTDB_NODES=/etc/ctdb/nodes
CTDB_PUBLIC_ADDRESSES=/etc/ctdb/public_addresses
CTDB_MANAGES_SAMBA=...
2014 May 20
1
CTDB + InfiniBand Public IP Addresses
...add a public address as follows:
[root at gp-1-0 ctdb]# ctdb ip
Public IPs on node 0
[root at gp-1-0 ctdb]# ctdb ip -Y
:Public IP:Node:ActiveInterface:AvailableInterfaces:ConfiguredInterfaces:
[root at gp-1-0 ctdb]# ctdb addip 192.168.5.151/24 ib0
2014/05/20 06:44:31.202611 [180506]: client/ctdb_client.c:2184 ctdb_control
for takeover_ip failed
2014/05/20 06:44:31.202746 [180506]: Failed to take over IP on node 0
2014/05/20 06:44:31.202762 [180506]: Failed to move ip to node 0
[root at gp-1-0 ctdb]# ctdb ip -Y
:Public IP:Node:ActiveInterface:AvailableInterfaces:ConfiguredInterfaces:
:192.168...