search for: recovery

Displaying 20 results from an estimated 2594 matches for "recovery".

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 following the ctdb logs: 2018/02/12 19:38:51.147959 ctdbd[5615]: CTDB starting...
2018 Feb 26
0
答复: [ctdb] Unable to take recovery lock - contention
...g, 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 - 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...
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 ctdb-recoverd[9437]: ../ctdb/server/ctdb_recoverd.c:1267 Starting do_recovery 2018/09/04 04:35:...
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)...
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)...
2020 Oct 29
1
CTDB Question: external locking tool
...io where we have a set of processes that > > have it set to false, then others that have it set to true, does the > > locking tool get called when they're set to false? > > Indeed it does. There are 2 current things conspiring against you: > > * At the start of each recovery a recovery lock consistency check is > done. Unfortunately, this means the recovery lock can't be left unset > on nodes that do not have the recmaster capability because then the > consistency check would fail. > > * At the end of recovery, if the recovery lock is set, all...
2020 Oct 26
2
CTDB Question: external locking tool
Folks, We use a Golang-based lock tool that we wrote for CTDB. That tool interacts with our 3.4 etcd cluster, and follows the requirements specified in the project. Question, does the external command line tool get called when LMASTER and RECMASTER are false? Given a scenario where we have a set of processes that have it set to false, then others that have it set to true, does the locking tool
2011 Feb 08
4
mount the wrong device after system recovery
Hi, I am recovering a CentOS 5.4 system. I've copied all partitions into the recovery system. I've installed grub boot loader. However, the original system is using /dev/sdb1 for root (/), while the recovery system is using LVM (/dev/vg0/lv1) for root (/). When recovery system boots, I got the panic error: * Mounting /dev/sdb1 on /sysroot * Mount: mounting /...
2020 Jun 30
2
CTDB RecLockLatencyMs vs RecoverInterval
...there any relationship between the RecLockLatencyMs property and the RecoverInterval property? Does one need to be larger than the other? Or if RecLockLatencyMs were increased to 5000ms, should some other setting be changed in proportion? We're using a geo-distributed etcd cluster for the CTDB recovery lock and I noticed a "*High RECLOCK latency"* (of 4s) message in syslog, and just wanted to see if we could safely squelch the warning, and if so, how? Thank you, -- BOB BUCK SENIOR PLATFORM SOFTWARE ENGINEER SKIDMORE, OWINGS & MERRILL 7 WORLD TRADE CENTER 250 GREENWICH STREET NE...
2001 Mar 20
3
Interesting interaction between journal recovery and slow boots
For some time now I have been puzzled as to why certain portions of my system boot were quite slow -- but only after journal recoveries. I was fearing that there was some ugly interaction between the recovery and the use of the journal shortly afterward but alas that is not the case. So just in case anybody else is seeing this problem and decides to try to hunt it down, let me save you some time. I am using an 0.0.6b ext3 kernel on a Red Hat 7.0 system. I was finding that if my system did not get shu...
2010 Aug 20
4
Windows Recovery console FAILS to boot withSyslinux-4.02
Hello Sir, on Friday, August 20, 2010 11:32 AM Gert Hulselmans wrote > loading the boot file ... > Boting ... > "-" cursor keeps on blincking Are you quite sure that booting the Windows Recovery Console under syslinux can work and that "cursor keeps blinking" is only a problem of your special menu? YES I am 100% sure that booting the Windows Recovery Console under Syslinux had worked and that cursor goes on blinking. What next please, Thanks in advance with regards,...
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
2013 Apr 09
0
Failed to start CTDB first time after install
...th0 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 C...
2010 Dec 16
0
Data Recovery tools Mac
Many people have deleted the wrong file when the file has been accidentally lost, a lot of computer companies now have a data recovery business, but also set the price very high, not the individual can accept, in fact, data recovery is also dependent on A variety of data recovery software, as long as the master of the use of these software, we can get back some of their own deleted files. Data recovery software is also there...
2018 May 07
2
CTDB Path
...n/ctdbd First I thought it works, but CTDB ignored my ctdbd.conf and public_addresses files. logfile shows: #################################################################################### 2018/05/07 15:31:39.654278 ctdbd[2092]: CTDB starting on node 2018/05/07 15:31:39.654461 ctdbd[2092]: Recovery lock not set 2018/05/07 15:31:39.658143 ctdbd[2093]: Starting CTDBD (Version 4.7.7) as PID: 2093 2018/05/07 15:31:39.659359 ctdbd[2093]: Removed stale socket /usr/local/samba/var/run/ctdb/ctdbd.socket 2018/05/07 15:31:39.659502 ctdbd[2093]: Listening to ctdb socket /usr/local/samba/var/run/ctdb/...
2018 Aug 02
3
tdbtool repack fails
...s: 12/18485/715170720 Number of hash chains: 10000 Smallest/average/largest hash chains: 26/66/116 Number of uncoalesced records: 253 Smallest/average/largest uncoalesced runs: 1/1/2 Percentage keys/data/padding/free/dead/rechdrs&tailers/hashes: 1/30/8/21/39/1/0 it ends with this error: tdb_recovery_allocate: overflow recovery area tdb_transaction_prepare_commit: failed to setup recovery data ../lib/tdb/common/tdb.c:1055 Failed to commit I follow the code and found this line: transaction.c:783         /* New head will be at end of file. */         recovery_head = tdb->map_size; In my...
2005 Jun 09
8
Xen and ReiserFS
...revisioRed Hat/Adaptec aacraid driver (1.1.2-lk2 Jun 9 2005) 3ware Storage Controller device driver for Linux v1.26.02.000. Fusion MPT base driver 3.01.18 Copyright (c) 1999-2004 LSI Logic Corporation mptbase: Initiating ioc0 bringup ioc0: 53C1030: Capabilities={Initiator} mptbase: Initiating ioc0 recovery mptbase: Initiating ioc0 recovery mptbase: Initiating ioc0 recovery mptbase: Initiating ioc0 recovery mptbase: Initiating ioc0 recovery mptbase: Initiating ioc0 recovery Fusion MPT SCSI Host driver 3.01.18 scsi0 : ioc0: LSI53C1030, FwRev=01032700h, Ports=1, MaxQ=222, IRQ=10 mptscsih: ioc0: >>...
2011 Mar 11
1
Samba in Pacemaker-Cluster: CTDB fails to get recovery lock
I'm currently testing fail-over with a two-node active-active cluster (with node dig and node dag): Both nodes are up, one is manually killed. CTDB on the node that's still alive should perform a recovery and everything should working again. What's infrequently happening is: After killing the pacemaker-process on dag (and dag consequently being fenced), dig's CTDB tries to get the recovery lock and fails. As there is no other node online to get the recovery lock and thus finishing CTDB...
2020 Jun 30
0
CTDB RecLockLatencyMs vs RecoverInterval
...tween the RecLockLatencyMs property and > the RecoverInterval property? Does one need to be larger than the other? Or > if RecLockLatencyMs were increased to 5000ms, should some other setting be > changed in proportion? > > We're using a geo-distributed etcd cluster for the CTDB recovery lock and I > noticed a "*High RECLOCK latency"* (of 4s) message in syslog, and just > wanted to see if we could safely squelch the warning, and if so, how? RecoverInterval indicates how often nodes should monitor conditions that indicate that a database recovery is needed. I would...
2020 Aug 05
2
CTDB question about "shared file system"
Could I impose upon someone to provide some guidance? Some hint? Thank you Is a shared file system actually required? If etcd is used to manage the global recovery lock, is there any need at that point for a shared file system? In other words, are there samba or CTDB files (state) that must be on a shared file system, or can each clustered host simply have these files locally? What must be shared? What can be optionally shared? The doc is not clear on this...