search for: recoveries

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

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

...9437]: Takeover run unsuccessful 2018/09/04 04:34:56.313675 ctdb-recoverd[9437]: ../ctdb/server/ctdb_recoverd.c:1398 Recovery complete 2018/09/04 04:34:56.313684 ctdb-recoverd[9437]: Resetting ban count to 0 for all nodes 2018/09/04 04:34:56.313694 ctdb-recoverd[9437]: Just finished a recovery. New recoveries will now be supressed for the rerecovery timeout (10 seconds) 2018/09/04 04:34:56.313703 ctdb-recoverd[9437]: Disabling recoveries for 10 seconds 2018/09/04 04:34:56.394112 ctdb-recoverd[9437]: Unassigned IP 10.231.8.69 can be served by this node 2018/09/04 04:34:56.394234 ctdb-recoverd[9437]: Trig...

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

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, 27 Oct 2020 15:09:34 +1100, Martin Schwenke via samba <samba at lists.samba.org> wrote: > On Sun, 25 Oct 2020 20:44:07 -0400, Robert Buck <robert.buck at som.com> > wrote: > > > 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 > >

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

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

Hi I have a question regarding CTDB RecLockLatencyMs tunable parameter. Is 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

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...

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

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/04/09 16:10:03.972067 [30575]: Monitoring has been disabled 2013/04/09 16:10:03.972083 [30575]: server/eventscript.c:800 Starting eventscript recovered 2013/04/09 16:10:04.250561 [30575]: CTDB_WAIT_UNTIL_RECOVERED 2013/04/09 16:10:04.250613 [30575]: server/ctdb_monitor.c:261 wait for pending recoveries to end. Wait one more second. 2013/04/09 16:10:04.322804 [30575]: server/eventscript.c:486 Eventscript recovered finished with state 0 2013/04/09 16:10:04.322870 [30575]: Monitoring has been enabled 2013/04/09 16:10:04.322983 [recoverd:30648]: server/ctdb_recoverd.c:1841 Recovery - finished the re...

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.

...r run completed successfully 2018/05/07 15:31:44.407040 ctdb-recoverd[2160]: ../ctdb/server/ctdb_recoverd.c:1399 Recovery complete 2018/05/07 15:31:44.407066 ctdb-recoverd[2160]: Resetting ban count to 0 for all nodes 2018/05/07 15:31:44.407089 ctdb-recoverd[2160]: Just finished a recovery. New recoveries will now be suppressed for the rerecovery timeout (10 seconds) 2018/05/07 15:31:44.407108 ctdb-recoverd[2160]: Disabling recoveries for 10 seconds 2018/05/07 15:31:44.826298 ctdbd[2093]: Recovery mode set to ACTIVE 2018/05/07 15:31:44.827914 ctdbd[2093]: Remote node (0) is now the recovery maste...

Hello list, I try to repack(tdbtool repack) my "dc=domain,dc=com.ldb" file: tdb> info Size of file/data: 3388084000/1050098055 Header offset/logical size: 0/3388084000 Number of records: 669737 Incompatible hash: no Active/supported feature flags: 0x00000000/0x00000001 Robust mutexes locking: no Smallest/average/largest keys: 12/57/242 Smallest/average/largest data: 72/1510/1235987

I am unable to boot Dom0 on a machine with Reiser file systems. Reiser support is built into the xen0 kernel. I have similar setup with ext3 file systems working just fine, so I don''t think it is a setup problem. I have tried booting with and without and initrd file, booting with the original Linux distro initrd file, etc, but nothing seems to work. I recall seeing a thread about ReiserFS

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

Hi Bob, On Tue, 30 Jun 2020 17:00:11 -0400, Robert Buck via samba <samba at lists.samba.org> wrote: > I have a question regarding CTDB RecLockLatencyMs tunable parameter. Is > 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

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