[Samba] Unable to fetch value for secret BCKUPKEY_, are we an undetected RODC?

[Mark Foley]

Garming - thanks for your quick response.

That link you gave me has Samba 3.x patches. I didn't notice any links to 4.x patches. 

Official Distro Releases are often behind the current stable release, generally. In fact, when
I first installed Samba4 the Linux version was more recent than the Ubuntu version. This lag is
probably due to abundance of caution and/or lack of manpower.

I don't think users will notice any problem (though they haven't used the new version yet). I've
tested quite often this weekend and noticed nothing bad. If it's just a matter of a cluttered
log file I can live with that until the Slack-folk catch up to version 4.2. I'm cautious about
patching and wandering outside the official distro. Who knows what might happen at the next
distro upgrade - perhaps losing the patch, at best.

THX --Mark

-----Original Message-----
> To: Mark Foley <mfoley at ohprs.org>, samba at lists.samba.org
> From: Garming Sam <garming at catalyst.net.nz>
> Date: Mon, 4 Jul 2016 10:51:37 +1200
> Subject: Re: [Samba] Unable to fetch value for secret BCKUPKEY_,
>  are we an undetected RODC?
>
> If it is that bug that you're referencing, besides obviously upgrading,
> you could try to patch it yourself. Whether or not you need to patch
> this, probably depends on whether or not your users are actually seeing
> issues. All that seems to  happen is that it's entering a failure case
> when it hasn't actually failed.
>
> https://www.samba.org/samba/patches/
>
> Cheers,
>
> Garming
>
> On 04/07/16 07:06, Mark Foley wrote:
> > I upgraded from 4.1.23 to 4.2.12 and am now getting (lots of) messages:
> >
> > Unable to fetch value for secret BCKUPKEY_, are we an undetected RODC?
> >
> > I found an almost identical message (titled: "Update samba4 from 4.1.17 to 4.2.1 failed") on
> > the web from May 22, 2015 at:
> >
> > http://samba.2283325.n4.nabble.com/Update-samba4-from-4-1-17-to-4-2-1-failed-td4686215.html
> >
> > but saw no resolution other than suggestions by Rowland Penny to remove certain smb.conf
> > settings, none of which I have.
> >
> > That page references a bug report https://bugzilla.samba.org/show_bug.cgi?id=11416, with a
> > response on 2016-04-08 saying the problem is fixed in 4.3 and above.
> >
> > Seems like this is a problem going from 4.1 to 4.2, but not fixed until 4.3.
> >
> > Is there anything I can or should do about this?
> >
> > --Mark
> >
>