similar to: Using --files-from with a pipe

Martin, Here you go, # echo "mypassword" | net --no-dns-updates -U service-account-name ads testjoin domain.local kerberos_kinit_password NETBIOS_NAME$@DOMAIN.LOCAL failed: Client not found in Kerberos database Join to domain is not valid: The name provided is not a properly formed account name. On Wed, Sep 30, 2020 at 9:34 PM Martin Schwenke <martin at meltin.net> wrote:

If eth0 holds virtual IP as its secondary IP and I bring down eth0 by command "ifdown eth0", CTDB will automatically pull eth0 up. Sometime it goes wrong. The virtual IP becomes primary IP, and origin primary IP turns into a secondary IP or just missing. If the origin primary IP is missing, I have to run "ifup eth0" though CTDB has pulled eth0 up. CTDB uses “ip link set eth0

On Sat, Aug 8, 2020 at 2:52 AM Martin Schwenke <martin at meltin.net> wrote: > Hi Bob, > > On Thu, 6 Aug 2020 06:55:31 -0400, Robert Buck <robert.buck at som.com> > wrote: > > > And so we've been rereading the doc on the public addresses file. So it > may > > be we have gravely misunderstood the *public_addresses* file, we never > read > >

Hi Bob, On Thu, 15 Oct 2020 16:37:18 -0400, Robert Buck <robert.buck at som.com> wrote: > Digging in the code I think I figured it out (though untested). Here is my > Ansible fragment. Is this correct for the property names? > > ... > [legacy] > realtime scheduling = false > {% if ctdb_lmaster_capability is defined %} > lmaster capability = {{

Hi Martin, Thanks very much for the information. I guess the part: * Coherency of the file data you serve with Samba You need to make sure that updates to the data that you are serving are seen coherently across the cluster. Is the tough one. Is there a way to do this that you know of when using NFS? I see version 4.5 RC2 was just released. Do you know when it will be fully released?

Thank you very much for reply. Our test team insists on simulating network failure by using ifdown instead of just unpluging the cable. I have to modify the event script 10.interface. When noticing a NIC failure, CTDB just marks the NIC down and do not try to pull it up. It seems to work fine. -----邮件原件----- 发件人: Martin Schwenke [mailto:martin at meltin.net] 发送时间: 2016年9月18日 18:49 收件人: Weidong

Hello all, Thanks for the input. I opened up the firewall ports and testing connectivity by ctdb's ping to no avail. I did however fix the problem. I must have missed the section of the guide outlining the importance of the nodes file, but it seems the issue was that machine A's nodes file was in reverse order compared to B's. After rectifying that the cluster came up without issue,

Ok, thanks. [root at euw2-samba-server-c21-01 ec2-user]# systemctl status winbind.service *?* winbind.service - Samba Winbind Daemon Loaded: loaded (/usr/lib/systemd/system/winbind.service; enabled; vendor preset: disabled) Active: *failed* (Result: exit-code) since Wed 2020-09-30 12:58:25 UTC; 1s ago Docs: man:winbindd(8) man:samba(7) man:smb.conf(5)

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,

And more information, wondering about DNS issues or DC issues... # wbinfo --ping-dc checking the NETLOGON for domain[MYDOMAINNAME] dc connection to "" failed failed to call wbcPingDc: WBC_ERR_DOMAIN_NOT_FOUND On Thu, Oct 1, 2020 at 9:21 AM Robert Buck <robert.buck at som.com> wrote: > Martin, > > Here you go, > > # echo "mypassword" | net

Am Fr 02.02.2018 um 10:27 schrieb Martin Schwenke: > On Thu, 1 Feb 2018 13:11:58 +0100, Nicolas Zuber via samba > <samba at lists.samba.org> wrote: > >> after starting the ctdb process and setting the log level to 5. If I set >> the log level to 2 it shows that winbind and nmbd starts successfully >> and no complains about a failed smbd process (see log below).

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

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

On 09/11/16 23:28, Martin Schwenke via samba wrote: > On Wed, 9 Nov 2016 16:05:32 +0000, lejeczek via samba > <samba at lists.samba.org> wrote: > >> an attempt to set up a cluster, I'm reading around and see >> some howto writers would say to put "private dir on the FS >> cluster" - one question I have: is this correct? necessary? > No, this is not

Hi Martin Many thanks for the detailed response. A few follow-ups inline: On Wed, Sep 19, 2018 at 5:19 AM Martin Schwenke <martin at meltin.net> wrote: > Hi David, > > On Tue, 18 Sep 2018 19:34:25 +0100, David C via samba > <samba at lists.samba.org> wrote: > > > I have a newly implemented two node CTDB cluster running on CentOS 7, > Samba > > 4.7.1

Thanks, I'll do that. It might be a week or two. But I have solid C skills going back 25 years, and spent a decade doing C++. Let me know if there's a "getting started guide" for developers on the Samba project. Key tools to install, etc. I will need to spin up a VM to work in. Also, should chat with the CTO so he's aware. On Thu, Nov 12, 2020 at 4:46 AM Martin Schwenke

Martin - thank you for this. I don't know why I couldn't find any of this information anywhere. How long has this change been in place, every website I see about configuring nfs-ganesha with ctdb shows the old information, not the new. Do I need to enable the legacy 06.nfs 60.nfs files when using ganesha? I assume no. ?On 10/1/19, 5:46 PM, "Martin Schwenke" <martin at

Very helpful. Thank you, Martin. I'd like to share the information below with you and solicit your fine feedback :-) I provide additional detail in case there is something else you feel strongly we should consider. We made some changes last night, let me share those with you. The error that is repeating itself and causing these failures is: Takeover run starting RELEASE_IP 10.200.1.230

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

Hi Marin - again thank you for the help. I can't believe I coundn't find any info about this big configuration change. Even the Samba WIKI doesn't really spell this out at all in instructs you to use ctdbd.conf. Do I need to enable the 20.nfs_ganesha.check script file at all, or will the config itself take care of that? Also, are there any recommendations on which nfs-checks.d