samba - Dec 2021 - samba-ad-dc.service: Got notification message from PID 27448, but reception only permitted for main PID 27410

On 04 September 2021 16:18 Alexander Bokovoy wrote:
> On pe, 03 syys 2021, Roy Eastwood wrote:
> > On 03 September 2021 15:43 L.P.H. van Belle wrote:
> > [snip]
> > > >
> > > > This one means we've got sd_notify() from a process that
is not a
> > > > correct one. Do you know what process is that? E.g. is it
'samba' or
> > > > 'smbd' or 'winbindd'? or something else?
> >
> > The two processes were as follows:
> > root at rpi3-dc:~# ps ax | egrep '27416 | 27448'
> >   27416 ?        Ss     0:01 /usr/sbin/smbd -D --option=server role
check:inhibit=yes --foreground
> >   27448 ?        Ss     0:01 /usr/sbin/winbindd -D --option=server
role check:inhibit=yes --foreground
> >   28130 pts/0    S+     0:00 grep -E 27416 | 27448
> 
> So 'server role check:inhibit=yes' should prevent both winbindd and
smbd
> from sending SD notifications but somehow that doesn't happen in a
right
> way:
> 
>         if (lp_server_role() == ROLE_ACTIVE_DIRECTORY_DC) {
>                 if (!lp_parm_bool(-1, "server role check",
"inhibit", false)) {
>                         DBG_ERR("server role = 'active directory
domain controller' not compatible with running smbd standalone. \n");
>                         DEBUGADD(0, ("You should start 'samba'
instead, and it will control starting smbd if required\n"));
>                         exit(1);
>                 }
>                 /* Main 'samba' daemon will notify */
>                 daemon_sd_notifications(false);
>         }
> 
> I need to look into this with more details next week..
> 
> --
> / Alexander Bokovoy
What's the latest advice on this please?   I am getting messages as well now
on a member server running smbd, so have edited smbd.service to add
NotifyAccess=all to the [Service] section.     Is that still the correct advice
to suppress these log messages?

kind regards,

Roy