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

[Michael Wood]

Hi

On 21 April 2013 14:07, François Lafont <flafdivers at free.fr> wrote:
> Hello,
>
> Le 20/04/2013 20:00, Michael Wood a écrit :
>
>> As Andrew suggested it would be good if you could run it under
>> valgrind and reproduce the crash.
>
> I don't know valgrind sorry. In spite of all, I have tried this:
>
> ---------------------------------------------------------------
> apt-get install valgrind
>
> ./configure --enable-debug  #<--- I add the --enable-debug
> make
> make install
>
> samba-tool domain provision --realm=CHEZMOI.PRIV --domain=CHEZMOI --server-role=dc --dns-backend=SAMBA_INTERNAL --adminpass='+toto123'
> echo "nameserver 192.168.0.21" > /etc/resolv.conf
> samba
>
> ln -s /usr/local/samba/lib/libnss_winbind.so /lib/libnss_winbind.so
> ln -s /lib/libnss_winbind.so /lib/libnss_winbind.so.2
>
> # I put "winbind" in the nsswitch.conf file.
> sed -i -r -e 's/^(passwd:.*)$/\1 winbind/g' -e 's/^(group:.*)$/\1 winbind/g' /etc/nsswitch.conf
>
> valgrind --leak-check=full samba -i M single > out 2>&1
> ---------------------------------------------------------------
>
> Here is the output during the "ls -l /usr/local/samba/var/locks/sysvol/" problem:
>
> http://sisco.laf.free.fr/codes/samba4_gid_3000000_valgrind.log
>
> Will that be enough?
>
>> Also, you should probably log a bug in bugzilla.
>
> It's done: https://bugzilla.samba.org/show_bug.cgi?id=9820

Did winbind also crash when you ran it under valgrind?

Perhaps you should attach the two logs directly to the bug instead of
just linking to them.

One of the Samba developers will have to let you know if the
information you have provided is enough.

Regards,
Michael

-- 
Michael Wood <esiotrot at gmail.com>