#x27;
single_terminate: reason[wbsrv_call_loop: tstream_read_pdu_blob_recv() -
NT_STATUS_CONNECTION_DISCONNECTED]
===
INTERNAL ERROR: Signal 11 in pid 14988 (4.0.4-GIT-f77d5d6)
Please read the Trouble-Shooting section of the Samba HOWTO
=
Hi all,
just as info, i can reproduce this crash with debian wheezy with 4.0.5, by
just doing
wbinfo --uid-info 300
and only when the nssswitch.conf have "compat winbind"
i didn't have this crash with 4.0.4.
best regards
philippe
--
View this message in context:
http://samba.2283325.n4.
If you have the time to track this down, it might be worth doing a git
bisect. It will require compiling samba about 7 times and testing
each one.
Basically you clone the samba repository (as per the Samba 4 HOWTO on
the wiki) and then:
1.) $ git bisect start samba-4.0.5 samba-4.0.4
2.) Compile
Hi all,
just as info, i also have the same crash with debian wheezy and samba 4.0.5, by
just doing
wbinfo --uid-info 300 and also only when the nssswitch.conf have "compat
winbind"
but i didn't have this crash with 4.0.4, in this case NO problem.
best regards
philippe
--
To unsubscribe
Hi,
Le 26/04/2013 11:38, Andrew Bartlett a écrit :
> Can you try that again with:
>
> valgrind samba -i -M single > out 2>&1
>
> I'm not worried about memory leaks (they don't cause crashes), and
> missing the '-' in front of -M probably means you didn't get the crash
> in the log you gave.
On Fri, 2013-04-26 at 19:47 +0200, sa...@nisx.de wrote:
> Hi,
>
> same problem here:
We need to know where that free is coming from, can you add
--num-callers=64?
eg
valgrind --num-callers=64 samba -i -M single > out 2>&1
> root@leela:~# valgrind samba -i -M single > out 2>&1
> root@leela:~#
Hi,
same problem here:
root@leela:~# valgrind samba -i -M single > out 2>&1
root@leela:~# cat out
==4450== Memcheck, a memory error detector
==4450== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
==4450== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
==4450==
On Sun, 2013-04-21 at 14:07 +0200, François Lafont 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:
>
>
Nachricht-
Von: Volker Lendecke [mailto:volker.lende...@sernet.de]
Gesendet: Mittwoch, 24. April 2013 13:35
An: Thomas Nolte
Betreff: Re: [Samba] [samba4] crash of winbind after "ls -l
/usr/local/samba/var/locks/sysvol"
On Wed, Apr 24, 2013 at 12:51:51PM +0200, sa...@nisx.de wrote:
w Bartlett
Betreff: Re: [Samba] [samba4] crash of winbind after "ls -l
/usr/local/samba/var/locks/sysvol"
[Ooops, sorry Michael for my first message, I have made a mistake with the
recipients]
Hello,
Le 22/04/2013 13:29, Michael Wood a écrit :
> Did winbind also crash when you ran it
after "ls -l
/usr/local/samba/var/locks/sysvol"
[Ooops, sorry Michael for my first message, I have made a mistake with the
recipients]
Hello,
Le 22/04/2013 13:29, Michael Wood a écrit :
> Did winbind also crash when you ran it under valgrind?
Yes, I think so. I have done
[Ooops, sorry Michael for my first message, I have made a mistake with the
recipients]
Hello,
Le 22/04/2013 13:29, Michael Wood a écrit :
> Did winbind also crash when you ran it under valgrind?
Yes, I think so. I have done 2 tests with "valgrind --leak-check=full samba -i
M single > out 2>&1
Hi
On 21 April 2013 14:07, François Lafont 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:
>
>
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 insta
-
> Von: samba-boun...@lists.samba.org [mailto:samba-boun...@lists.samba.org] Im
> Auftrag von François Lafont
> Gesendet: Freitag, 19. April 2013 23:08
> An: samba@lists.samba.org
> Betreff: Re: [Samba] [samba4] crash of winbind after "ls -l
> /usr/local/samba/var/locks/sysvol&q
www.nisx.de
-Ursprüngliche Nachricht-
Von: samba-boun...@lists.samba.org [mailto:samba-boun...@lists.samba.org] Im
Auftrag von François Lafont
Gesendet: Freitag, 19. April 2013 23:08
An: samba@lists.samba.org
Betreff: Re: [Samba] [samba4] crash of winbind after "ls -l
/usr/local/samb
Hi,
I go back to this thread (the title is explicit) just to have news. I have seen
in other threads that other people have similar problems. Should we consider
this problem as a bug (in Samba 4.0.5) or is it a wrong installation from my
part? In the first case, are information that I have give
Le 14/04/2013 13:51, François Lafont a écrit :
>> I'm going to search, meanwhile, here is the ouput of the "samba -i -M single
>> -d 10" command during the "ls -l /usr/local/samba/var/locks/sysvol/" problem.
>
> Ooups! Sorry I have forgotten the url address:
> http://sisco.laf.free.fr/codes/sam
Le 14/04/2013 13:49, François Lafont a écrit :
> I'm going to search, meanwhile, here is the ouput of the "samba -i -M single
> -d 10" command during the "ls -l /usr/local/samba/var/locks/sysvol/" problem.
Ooups! Sorry I have forgotten the url address:
http://sisco.laf.free.fr/codes/samba4_gid_3
Le 14/04/2013 08:30, Andrew Bartlett a écrit :
>> ---
>> # ls -n /usr/local/samba/var/locks/sysvol/
>> total 8
>> drwxrws---+ 4 0 300 4096 Apr 14 01:40 chezmoi.priv
>> ---
>>
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:
---
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 /us
Hi,
I used Samba 4.0.5 in Wheezy. Here is that I have done:
---
samba-tool domain provision --realm=CHEZMOI.PRIV --domain=CHEZMOI \
--server-role=dc --dns-backend=SAMBA_INTERNAL --adminpass='+toto123'
echo "nameserver 192.168.0.21" >
23 matches
Mail list logo
