similar to: CTDB port 445 ERROR

Looks like this is the actual error: 2019/10/04 09:51:29.174870 ctdbd[17244]: Recovery has started 2019/10/04 09:51:29.174982 ctdbd[17244]: ../ctdb/server/ctdb_server.c:188 ctdb request 2147483554 of type 8 length 48 from node 1 to 0 2019/10/04 09:51:29.175021 ctdbd[17244]: Recovery lock configuration inconsistent: recmaster has NULL, this node has /run/gluster/shared_storage/.CTDB-lockfile,

I?ll have to check out the script issue on Monday. You said the lock needs to be the same on all nodes. I can do that but this is now in production and restarting the ctdb service forces a failover of the ip, which actually causes a failure of a few of our Kubernetes sql database pods - they freak out and don?t recovery if storage is ripped out from under them. Is there a way to do this

Hi Max, On Fri, 4 Oct 2019 14:01:22 +0000, Max DiOrio <Max.DiOrio at ieeeglobalspec.com> wrote: > Looks like this is the actual error: > > 2019/10/04 09:51:29.174870 ctdbd[17244]: Recovery has started > 2019/10/04 09:51:29.174982 ctdbd[17244]: ../ctdb/server/ctdb_server.c:188 ctdb request 2147483554 of type 8 length 48 from node 1 to 0 > 2019/10/04 09:51:29.175021

This is the latest stable release of CTDB. CTDB 2.5.4 can be used with Samba releases 3.6.x, 4.0.x and 4.1.x. Changes in CTDB 2.5.4 ===================== User-visible changes -------------------- * New command "ctdb detach" to detach a database. * Support for TDB robust mutexes. To enable set TDBMutexEnabled=1. The setting is per node. * New manual page ctdb-statistics.7.

Hi there, I use Samba 4.9 since its releaseday and also had some troubles first due to the lack of informations in the wiki. Anyways... after some try & error i got it working and since i run the Cluster (non-production environment) had no errors except CTDBs monitoring of the Samba process did'nt work as i would expect it (RPC-Server was dead but CTDB did'nt complain and "ctdb

Changes in CTDB 2.4 =================== User-visible changes -------------------- * A missing network interface now causes monitoring to fail and the node to become unhealthy. * Changed ctdb command's default control timeout from 3s to 10s. * debug-hung-script.sh now includes the output of "ctdb scriptstatus" to provide more information. Important bug fixes

Hi folks, We're building a new CTDB cluster - any recommendation on what version of CTDB is the most "production" at the moment? We're currently on 1.2.66 on our currently in-service clusters. Cheers, Orlando > -------- Original Message -------- > Subject: [Samba] [Announce] CTDB 2.4 available for download > Date: Fri, 23 Aug 2013 14:11:29 +1000 > From:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello everybody, I try to set up a GlusterFS together with CTDB. The OS on all systems is Debian wheezy. No backports aktiv. All Samba-packages are from Sernet (samba 4.14) My setup is the following: - ------------ GlusterFS: - ------------ Node1: 192.168.57.101 Node2: 192.168.57.102 Two nodes each with one disk. The disks are formated. The disks

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Davor, Am 12.01.2015 um 19:44 schrieb Davor Vusir: > 2015-01-12 17:47 GMT+01:00 Stefan Kania <stefan at kania-online.de>: > Am 11.01.2015 um 19:10 schrieb Davor Vusir: >>>> Hi Stefan! >>>> >>>> 2015-01-09 17:27 GMT+01:00 Stefan Kania >>>> <stefan at kania-online.de>: Hello

Hi Max, On Wed, 2 Oct 2019 15:08:43 +0000, Max DiOrio <Max.DiOrio at ieeeglobalspec.com> wrote: > As soon as I made the configuration change and restarted CTDB, it crashes. > > Oct 2 11:05:14 hq-6pgluster01 systemd: Started CTDB. > Oct 2 11:05:21 hq-6pgluster01 systemd: ctdb.service: main process exited, code=exited, status=1/FAILURE > Oct 2 11:05:21 hq-6pgluster01

results from 'netstat -tlpn' gives me a line... tcp 0 0 0.0.0.0:46929 0.0.0.0:* LISTEN - googling for port 46929 doesn't turn up anything and so I don't have a clue what process this belongs to. Do I have to start capturing activity on this port or is there a better way to find out what this port is about? -- Craig White <craig at

Hi, in the following scenario I've got the Problem of "STATUS_SHARE_VIOLATION". Client A (with User 1) copies a file to share X. (with: DENY_NONE 0x120196 WRONLY NONE) Client B (with User 1) reads this file from share X (with: DENY_NONE 0x120089 RDONLY NONE) Now Client C (with User 1) wants also to read this file from share X and gets the STATUS_SHARE_VIOLATION.

Hi r-users,   I would like to extract the data that match.  Attached is my data: I'm interested in matchind the value in column 'intg' with value in column 'rand_no' > cbind(z=z,intg=dd,rand_no = rr)             z  intg rand_no    [1,]  0.00 0.000   0.001    [2,]  0.01 0.000   0.002    [3,]  0.02 0.000   0.002    [4,]  0.03 0.000   0.003    [5,]  0.04 0.000   0.003    [6,] 

Hi there, I am doing multiple comparisons for data that is not normally distributed. For this purpose I tried both functions kruskal{agricolae} and kruskalmc{pgirmess}. It confuses me that these functions do not yield the same results although they are doing the same thing, don't they? Can anyone tell my why this happens and which function I can trust? kruskalmc() tells me that there are no

Hello, Today I tried to upgrade to samba 4.8.0, the upgrade seems to have failed, and I can't seem to fix it or back out. The issue seems to be I've lost the some KRB tickets. Here's and example of the errors i get: samba-tool domain exportkeytab /tmp/test2 samba_kdc_fetch: could not find own KRBTGT in DB: dsdb_search at ../source4/dsdb/common/util.c:4641 ERROR(runtime): uncaught

On Thu, 24 May 2018 11:30:40 +0200 (CEST) Gaetan SLONGO via samba <samba at lists.samba.org> wrote: > Hi, > > > > > It's my first try to setup RODC using Samba 4.8. We have latest Samba > 4.7 environnement with 2 DC and some file servers. Joining the DC to > the domain is OK using samba-tool domain join command. The domain > controller appears in the DC

On Thu, 2018-04-12 at 13:02 -0400, Andrew Dumaresq via samba wrote: > Hello, > > Today I tried to upgrade to samba 4.8.0, the upgrade seems to have failed, > and I can't seem to fix it or back out. The issue seems to be I've lost > the some KRB tickets. Here's and example of the errors i get: > > samba-tool domain exportkeytab /tmp/test2 > samba_kdc_fetch:

Thanks for getting back to me. I managed to restore my domain from a backup that I forgot I had. Glad you know about the bug! On Fri, Apr 13, 2018 at 4:04 AM, Andrew Bartlett <abartlet at samba.org> wrote: > On Thu, 2018-04-12 at 13:02 -0400, Andrew Dumaresq via samba wrote: > > Hello, > > > > Today I tried to upgrade to samba 4.8.0, the upgrade seems to have >

This may be a dumb question, but will the upgrade work in 4.8.1 now? when I follow the bug, it looks like it wasn't included... On Fri, Apr 13, 2018 at 11:01 AM, Andrew Dumaresq <dumaresq at gmail.com> wrote: > Thanks for getting back to me. I managed to restore my domain from a > backup that I forgot I had. > > Glad you know about the bug! > > On Fri, Apr 13, 2018

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, here is a nother howto to set up a CTDB-Cluster together with GlusterFS. https://www.kania-online.de/wp-content/uploads/2016/10/ubuntu-cluster.tx t Stefan -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlf7ttYACgkQ2JOGcNAHDTYdWQCgsjoQa0W1G/SMYM0PeoAC6Ly0 I7gAnAzSHI+PtTEMmcdVdfV6CkFDNqCi =jsDs -----END PGP