Displaying 9 results from an estimated 9 matches for "ctdb_recover".
Did you mean:
ctdb_recoverd
2014 Oct 07
1
CDTB On Samba 4.1.12 As Member files server.
...68.11.20 192.168.11.24"
dns_search="kl01.amtb-m.org.my"
routes_enp2s0="default via 192.168.11.10"
routes_enp2s2="default via 192.168.11.10"
routes_enp2s3="default via 192.168.11.10"
routes_enp2s4="default via 192.168.11.10"
*/etc/conf.d/ctdb*
CTDB_RECOVERY_LOCK=/amtb/.ctdb.lock
CTDB_PUBLIC_ADDRESSES=/etc/ctdb/public_addresses
CTDB_MANAGES_SAMBA=yes
CTDB_SAMBA_SKIP_SHARE_CHECK=yes
CTDB_NFS_SKIP_SHARE_CHECK=yes
CTDB_MANAGES_WINBIND=yes
CTDB_MANAGES_VSFTPD=no
CTDB_MANAGES_ISCSI=no
CTDB_MANAGES_NFS=no
CTDB_MANAGES_HTTPD=no
CTDB_SYSLOG=yes
CTDB_DEBUGLEVE...
2014 Feb 26
0
CTDB Debug Help
...eeze priority 1
2014/02/26 12:10:30.173525 [10027232]: Freeze priority 2
2014/02/26 12:10:30.173710 [10027232]: Freeze priority 3
2014/02/26 12:10:33.500359 [10027232]: Freeze priority 1
2014/02/26 12:10:33.639712 [10027232]: Freeze priority 2
2014/02/26 12:10:33.677081 [recoverd:11272374]:
server/ctdb_recoverd.c:3699 Current recmaster node 0 does not have
CAP_RECMASTER, but we (node 1) have - force an election
2014/02/26 12:10:33.677186 [10027232]: Freeze priority 1
2014/02/26 12:10:33.677336 [10027232]: Freeze priority 2
2014/02/26 12:10:33.677491 [10027232]: Freeze priority 3
2014/02/26 12:10:33.7896...
2016 Jun 22
2
CTDB/Kernel BUG
...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_...
2023 Nov 26
1
CTDB: some problems about disconnecting the private network of ctdb leader nodes
...t 19:18:59.822903, this node timed out obtaining a lock, and the log shows ?Time out getting recovery lock, allowing recovery mode set any way??and then host-192-168-34-164 takeover all the virtual ip.
I checked the source code of ctdb and found that lines 578 to 582 of the file samba/ctdb/server/ctdb_recover. c state: Timeout. Consider this a success, not a failure, as we failed to set the recovery lock which is what we wanted. This can be caused by the cluster filesystem being very slow to arbitrate locks immediately after a node failure.
I am puzzled why get the recloc...
2016 Jun 22
0
CTDB/Kernel BUG
...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 dumpe...
2013 Apr 09
0
Failed to start CTDB first time after install
...ed, eth0 as the primary NIC, eth1 as the private IP NIC. With clustering off and no CTDB, Samba works. I need to get this running for a needed project. Only errors are reported in /var/log/log.ctdb. Please help.
CTDB Configs:
Edit /etc/sysconfig/ctdb for the following to change from default.
CTDB_RECOVERY_LOCK="/samba/samba_lock"
CTDB_NODES=/etc/ctdb/nodes
CTDB_DEBUGLEVEL=3
Edited /etc/ctdb/nodes to add internal Ip address for eth1 for private IP.
The complete /var/log/log.ctdb:
2013/04/09 16:09:59.881679 [30574]: CTDB starting on node
2013/04/09 16:09:59.886133 [30575]: Starting...
2012 Jan 13
0
CTDB crash - trying to allocate > 256kB of memory
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 ctdbd:
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Jan 13 15:27:13 nasfe03 ctdbd: INTERNAL ERROR: Sig...
2018 Sep 05
1
[ctdb]Unable to run startrecovery event(if mail content is encrypted, please see the attached file)
...eat 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 ctdb-recoverd[9437]: ../ctdb/server/ctdb_recoverd.c:1267 Starting do_recovery
2018/09/04 04:35:09.412689 ctdb-recoverd[9437]: Already holding recovery lock
2018/09/04 04:35:09.412700 ctdb-recoverd[9437]: ../ctdb/server/ctdb_recoverd.c:1326 Recovery initiated due to problem with node 1
2018/09/04 04:35:09.412974 ctdb-recoverd[9437]: ../ctdb/server...
2015 May 19
0
ctdb_client.c control timed out - banning nodes
...nnected'
2015/05/18 14:24:39.235572 [13021]: ctdb_control error: 'node is disconnected'
2015/05/18 14:24:39.235583 [13021]: Async operation failed with ret=-1 res=-1 opcode=80
2015/05/18 14:24:39.235590 [13021]: Async wait failed - fail_count=1
2015/05/18 14:24:39.235598 [13021]: server/ctdb_recoverd.c:251 Failed to read node capabilities.
2015/05/18 14:24:39.235605 [13021]: server/ctdb_recoverd.c:3025 Unable to update node capabilities.
2015/05/18 14:24:59.405500 [12968]: Freeze priority 1
2015/05/18 14:25:03.257579 [12968]: Could not add client IP 155.198.17.133. This is not a public address...