>> You don't have smbd/smbstatus installed from a package in /usr/ and the >> other left over in /usr/local/, or similar? In that case, they could >> be getting their configurations from different places... >> >> peace & happiness, >> martin > Hi Martin, > > No, nothing like that. Installing the Sernet packages obsoletes the > distro ones. > > FYI: > > # smbstatus -V > Version 4.4.6-SerNet-RedHat-31.el7 > # smbd -V > Version 4.4.6-SerNet-RedHat-31.el7 > > # find /usr -name smbd > /usr/sbin/smbd > # find /usr -name smbstatus > /usr/bin/smbstatus > > Thanks very much, > > Alex > --Interestingly I have a setup here for testing for rollout of S4 AD. The file servers are in an AD domain and are running Sernet 4.4.5, so one version older than production. I have tested the locking on these and it works. The only difference I can find that in prod, /etc/default/sernet-samba-ctdb contains these lines: CTDB_MANAGES_SAMBA=yes CTDB_MANAGES_WINBIND=yes Whereas in the test environment they are: CTDB_SERVICE_WINBIND="sernet-samba-winbindd" CTDB_SERVICE_SMB="sernet-samba-smbd" I'm wondering if this is what's making the difference? Cheers, Alex -- This message is intended only for the addressee and may contain confidential information. Unless you are that person, you may not disclose its contents or use it in any way and are requested to delete the message along with any attachments and notify us immediately. This email is not intended to, nor should it be taken to, constitute advice. The information provided is correct to our knowledge & belief and must not be used as a substitute for obtaining tax, regulatory, investment, legal or any other appropriate advice. "Transact" is operated by Integrated Financial Arrangements Ltd. 29 Clement's Lane, London EC4N 7AE. Tel: (020) 7608 4900 Fax: (020) 7608 5300. (Registered office: as above; Registered in England and Wales under number: 3727592). Authorised and regulated by the Financial Conduct Authority (entered on the Financial Services Register; no. 190856).
> Interestingly I have a setup here for testing for rollout of S4 AD. > The file servers are in an AD domain and are running Sernet 4.4.5, so > one version older than production. I have tested the locking on these > and it works. The only difference I can find that in prod, > /etc/default/sernet-samba-ctdb contains these lines: > > CTDB_MANAGES_SAMBA=yes > CTDB_MANAGES_WINBIND=yes > > Whereas in the test environment they are: > CTDB_SERVICE_WINBIND="sernet-samba-winbindd" > CTDB_SERVICE_SMB="sernet-samba-smbd" > > I'm wondering if this is what's making the difference? > > Cheers, > > Alex > >The above is not what I meant, apologies. In the prod cluster, these lines: CTDB_SERVICE_WINBIND="sernet-samba-winbindd" CTDB_SERVICE_SMB="sernet-samba-smbd" are actually absent. The CTDB_MANAGES_... ones are the same on both setups. Alex -- This message is intended only for the addressee and may contain confidential information. Unless you are that person, you may not disclose its contents or use it in any way and are requested to delete the message along with any attachments and notify us immediately. This email is not intended to, nor should it be taken to, constitute advice. The information provided is correct to our knowledge & belief and must not be used as a substitute for obtaining tax, regulatory, investment, legal or any other appropriate advice. "Transact" is operated by Integrated Financial Arrangements Ltd. 29 Clement's Lane, London EC4N 7AE. Tel: (020) 7608 4900 Fax: (020) 7608 5300. (Registered office: as above; Registered in England and Wales under number: 3727592). Authorised and regulated by the Financial Conduct Authority (entered on the Financial Services Register; no. 190856).
Martin Schwenke
2016-Oct-21 09:45 UTC
[Samba] CTDB and locking issues in 4.4.6 (Classic domain)
On Fri, 21 Oct 2016 10:34:07 +0100, Alex Crow via samba <samba at lists.samba.org> wrote:> > Interestingly I have a setup here for testing for rollout of S4 AD. > > The file servers are in an AD domain and are running Sernet 4.4.5, so > > one version older than production. I have tested the locking on these > > and it works. The only difference I can find that in prod, > > /etc/default/sernet-samba-ctdb contains these lines: > > > > CTDB_MANAGES_SAMBA=yes > > CTDB_MANAGES_WINBIND=yes > > > > Whereas in the test environment they are: > > CTDB_SERVICE_WINBIND="sernet-samba-winbindd" > > CTDB_SERVICE_SMB="sernet-samba-smbd" > > > > I'm wondering if this is what's making the difference?> The above is not what I meant, apologies. In the prod cluster, these lines: > > CTDB_SERVICE_WINBIND="sernet-samba-winbindd" > CTDB_SERVICE_SMB="sernet-samba-smbd" > > are actually absent. The CTDB_MANAGES_... ones are the same on both setups.I'm guessing that's it. Instead of running the Sernet initscripts (or systemd thingies), some other initscript is being run and it is probably not making smbd use the correct configuration, so smbd is probably running without clustering configured... ... but that's obviously just speculation! I don't know anything about the Sernet packages... Possibly time to talk to someone at Sernet? peace & happiness, martin
Ralph Böhme
2016-Oct-21 09:52 UTC
[Samba] CTDB and locking issues in 4.4.6 (Classic domain)
On Fri, Oct 21, 2016 at 10:30:46AM +0100, Alex Crow via samba wrote:> Interestingly I have a setup here for testing for rollout of S4 AD. The file > servers are in an AD domain and are running Sernet 4.4.5, so one version > older than production.maybe it's related to bug 12005 that was fixed in 4.4.6? Can you test with attached patch that reverts the change? Cheerio! -slow -------------- next part --------------
L.P.H. van Belle
2016-Oct-21 09:58 UTC
[Samba] CTDB and locking issues in 4.4.6 (Classic domain)
I suggest have a look in : https://bugzilla.samba.org/show_bug.cgi?id=12371 i think that wil help you. Greetz, Louis> -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens Martin Schwenke > via samba > Verzonden: vrijdag 21 oktober 2016 11:46 > Aan: samba at lists.samba.org > Onderwerp: Re: [Samba] CTDB and locking issues in 4.4.6 (Classic domain) > > On Fri, 21 Oct 2016 10:34:07 +0100, Alex Crow via samba > <samba at lists.samba.org> wrote: > > > > Interestingly I have a setup here for testing for rollout of S4 AD. > > > The file servers are in an AD domain and are running Sernet 4.4.5, so > > > one version older than production. I have tested the locking on these > > > and it works. The only difference I can find that in prod, > > > /etc/default/sernet-samba-ctdb contains these lines: > > > > > > CTDB_MANAGES_SAMBA=yes > > > CTDB_MANAGES_WINBIND=yes > > > > > > Whereas in the test environment they are: > > > CTDB_SERVICE_WINBIND="sernet-samba-winbindd" > > > CTDB_SERVICE_SMB="sernet-samba-smbd" > > > > > > I'm wondering if this is what's making the difference? > > > The above is not what I meant, apologies. In the prod cluster, these > lines: > > > > CTDB_SERVICE_WINBIND="sernet-samba-winbindd" > > CTDB_SERVICE_SMB="sernet-samba-smbd" > > > > are actually absent. The CTDB_MANAGES_... ones are the same on both > setups. > > I'm guessing that's it. Instead of running the Sernet initscripts (or > systemd thingies), some other initscript is being run and it is > probably not making smbd use the correct configuration, so smbd is > probably running without clustering configured... > > ... but that's obviously just speculation! I don't know anything about > the Sernet packages... > > Possibly time to talk to someone at Sernet? > > peace & happiness, > martin > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba
On 21/10/16 10:52, Ralph Böhme wrote:> On Fri, Oct 21, 2016 at 10:30:46AM +0100, Alex Crow via samba wrote: >> Interestingly I have a setup here for testing for rollout of S4 AD. The file >> servers are in an AD domain and are running Sernet 4.4.5, so one version >> older than production. > maybe it's related to bug 12005 that was fixed in 4.4.6? Can you test > with attached patch that reverts the change? > > Cheerio! > -slowI could test that but in production running from direct source builds is not permitted here. There must be a repo available or at least the ability to build RPMs. I've tried before rebuilding upstream Samba using RH spec files but I've never succeeded in getting all the packages to build correctly :-( That's why I use the Sernet repo. Another interesting point is that I've just upgraded the test cluster to 4.4.6 and it appears to be working, although that is only two hosts. The prod setup is 6 hosts, with two sub-clusters, so there could be a difference there. Cheers Alex -- This message is intended only for the addressee and may contain confidential information. Unless you are that person, you may not disclose its contents or use it in any way and are requested to delete the message along with any attachments and notify us immediately. This email is not intended to, nor should it be taken to, constitute advice. The information provided is correct to our knowledge & belief and must not be used as a substitute for obtaining tax, regulatory, investment, legal or any other appropriate advice. "Transact" is operated by Integrated Financial Arrangements Ltd. 29 Clement's Lane, London EC4N 7AE. Tel: (020) 7608 4900 Fax: (020) 7608 5300. (Registered office: as above; Registered in England and Wales under number: 3727592). Authorised and regulated by the Financial Conduct Authority (entered on the Financial Services Register; no. 190856).
On 21/10/16 10:52, Ralph Böhme wrote:> On Fri, Oct 21, 2016 at 10:30:46AM +0100, Alex Crow via samba wrote: >> Interestingly I have a setup here for testing for rollout of S4 AD. The file >> servers are in an AD domain and are running Sernet 4.4.5, so one version >> older than production. > maybe it's related to bug 12005 that was fixed in 4.4.6? Can you test > with attached patch that reverts the change? > > Cheerio! > -slowHi Ralph, Some more tests I've done indicate that locking is only working between 2 of my 6 VIPs (one per host). If I open a file on either of these two "working" hosts, it's locked on the other working one, but not on any others. Opening a file on any of the "non-working" hosts means the file is not locked anywhere else. On my test setup with only two nodes it seems to work normally with both 4.4.5 and 4.4.6. All hosts have the same smb.conf. Cheers Alex -- This message is intended only for the addressee and may contain confidential information. Unless you are that person, you may not disclose its contents or use it in any way and are requested to delete the message along with any attachments and notify us immediately. This email is not intended to, nor should it be taken to, constitute advice. The information provided is correct to our knowledge & belief and must not be used as a substitute for obtaining tax, regulatory, investment, legal or any other appropriate advice. "Transact" is operated by Integrated Financial Arrangements Ltd. 29 Clement's Lane, London EC4N 7AE. Tel: (020) 7608 4900 Fax: (020) 7608 5300. (Registered office: as above; Registered in England and Wales under number: 3727592). Authorised and regulated by the Financial Conduct Authority (entered on the Financial Services Register; no. 190856).