[Samba] [samba4] crash of winbind after "ls -l /usr/local/samba/var/locks/sysvol"

[Rowland Penny]

On 14/04/13 07:30, Andrew Bartlett wrote:
> On Sun, 2013-04-14 at 02:08 +0200, François Lafont wrote:
>> Hi,
>>
>> I used Samba 4.0.5 in Wheezy. Here is that I have done:
>> But there is something curious with the /usr/local/samba/var/locks/sysvol/ directory:
>>
>> ---------------------------------------------------------------
>> # ls -n /usr/local/samba/var/locks/sysvol/
>> total 8
>> drwxrws---+ 4 0 3000000 4096 Apr 14 01:40 chezmoi.priv
>> ---------------------------------------------------------------
>>
>> Which group has the gid 3000000?
> The files are owned by the domain administrators group.  Winbind doesn't
> know how to make up a 'user' record for that group yet.

In that case, would you like to explain why, if I add a user to Domain 
Admins and then mount a share as the user from the S4 server via cifs, 
all the files get saved as user 3000000?

Rowland

>
>> ---------------------------------------------------------------
>> # wbinfo -g | tr '\n' '\0' | xargs -0 -n 1 wbinfo --group-info
>> CHEZMOI\Enterprise Read-Only Domain Controllers:*:3000018:
>> CHEZMOI\Domain Admins:*:3000008:
>> CHEZMOI\Domain Users:*:100:
>> CHEZMOI\Domain Guests:*:3000012:
>> CHEZMOI\Domain Computers:*:3000019:
>> CHEZMOI\Domain Controllers:*:3000020:
>> CHEZMOI\Schema Admins:*:3000007:
>> CHEZMOI\Enterprise Admins:*:3000006:
>> CHEZMOI\Group Policy Creator Owners:*:3000004:
>> CHEZMOI\Read-Only Domain Controllers:*:3000021:
>> CHEZMOI\DnsUpdateProxy:*:3000022:
>> ---------------------------------------------------------------
>>
>> There is no 3000000 gid. And, a bit more embarrassing, if I use "ls -l" to resolv the gid to a name, winbind is crashing:
> Can you please try to get a gdb backtrace, or better still run 'samba'
> under valgrind?  We would very much like to fix that.
>
> You could also file these details in a bug, if we don't sort it out
> quickly.
>
> Thanks,
>
> Andrew Bartlett
>


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.