Recent Samba (4.18.0+) winbind configuration ?
Rowland Penny
rpenny at samba.org
Thu Apr 13 09:26:37 UTC 2023
On 13/04/2023 08:09, Andreas Schneider wrote:
> On Tuesday, 11 April 2023 19:47:45 CEST Rowland Penny via samba-technical
> wrote:
>> On 11/04/2023 18:15, Jeremy Allison via samba-technical wrote:
>>> On Tue, Apr 11, 2023 at 02:32:27PM +0200, Jiří Šašek - Solaris Prague
>>>
>>> via samba-technical wrote:
>>>> Story begins when Samba 4.14.0 changed its VFS so we decided to skip
>>>> 4.14.x and also 4.15.x releases to bundle it on Solaris but various
>>>> problems were also with later releases and we were only fixing issues
>>>> in 4.13.0 . Currently (4.18.0) the situation can called be critical so
>>>> I focused on recent release.
>>>>
>>>> winbindd is giving up and I think the key could be in log message:
>>>>
>>>> [2023/04/11 11:28:53.090661, 5, pid=1525, effective(0, 0), real(0,
>>>> 0), class=winbind] ../../source3/winbindd/wb_lookupname.c:
>>>> 52(wb_lookupname_send)
>>>> WB command lookupname start.
>>>> Search namespace 'smbsetup' and domain 'smbsetup' for name ''.
>>>>
>>>> ...where "smbsetup" is my domain ...and I have added core-dump here
>>>> to freeze the stack:
>>>>
>>>> [2023/04/11 11:28:53.090780, 0, pid=1525, effective(0, 0), real(0,
>>>> 0)] ../../source3/lib/dumpcore.c:315(dump_core)
>>>> dumping core in /var/samba/log/cores/winbindd
>>>
>>> Jiří, please open a bug and upload the full backtrace.
>>>
>>> Thanks,
>>>
>>> Jeremy.
>>
>> Damn, I missed that, focussed on how wrong chatGPT had got it wrong,
>> anyone heard of 'autorid_compat' ?
>>
>> I still think that Yura needs to post their smb.conf etc.
>
> Not the smb.conf but the output of "testparm -s"! Always ask for testparm
> output including the errors and warnings it prints ;-)
>
There are times when seeing what is on disk is helpful, you can see just
what, if anything, the OP has tried, I deemed that this was one of those
times.
Rowland
More information about the samba-technical
mailing list