Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #207309 > unrolled thread

Debugging samba

Back to article view | Back to linux.debian.user

Contents

  Debugging samba Kevin DAGNEAUX <kevin.dagneaux@fiitelcom.fr> - 2019-04-11 15:50 +0200
    Re: Debugging samba Roberto C. Sánchez <roberto@debian.org> - 2019-04-11 16:30 +0200
      Re: Debugging samba Kevin DAGNEAUX <kevin.dagneaux@fiitelcom.fr> - 2019-04-11 17:00 +0200
        Re: Debugging samba Roberto C. Sánchez <roberto@debian.org> - 2019-04-11 17:00 +0200
        Re: Debugging samba deloptes <deloptes@gmail.com> - 2019-04-11 21:00 +0200
          Re: Debugging samba Kevin DAGNEAUX <kevin.dagneaux@fiitelcom.fr> - 2019-04-12 09:30 +0200
            Re: Debugging samba deloptes <deloptes@gmail.com> - 2019-04-12 10:30 +0200
              Re: Debugging samba Kevin DAGNEAUX <kevin.dagneaux@fiitelcom.fr> - 2019-04-12 10:50 +0200
                Re: Debugging samba deloptes <deloptes@gmail.com> - 2019-04-12 12:20 +0200
                  Re: Debugging samba deloptes <deloptes@gmail.com> - 2019-04-12 21:20 +0200

#207309 — Debugging samba

[Multipart message — attachments visible in raw view] — view raw

Hi,

I'm having crash problem with samba 2:4.5.16+dfsg-1+deb9u1 in debian 
9.8, i'm trying to debug it so i can't find the package samba-dbg.

Is there a way to debug samba without samba-dbg?

Kevin

[toc] | [next] | [standalone]

#207313

On Thu, Apr 11, 2019 at 03:46:11PM +0200, Kevin DAGNEAUX wrote:
> Hi,
> 
> I'm having crash problem with samba 2:4.5.16+dfsg-1+deb9u1 in debian 9.8,
> i'm trying to debug it so i can't find the package samba-dbg.
> 
> Is there a way to debug samba without samba-dbg?
> 
You might find this helpful:

https://wiki.debian.org/HowToGetABacktrace

Regards,

-Roberto

-- 
Roberto C. Sánchez

[toc] | [prev] | [next] | [standalone]

#207317

[Multipart message — attachments visible in raw view] — view raw

Le 11/04/2019 à 16:27, Roberto C. Sánchez a écrit :
> On Thu, Apr 11, 2019 at 03:46:11PM +0200, Kevin DAGNEAUX wrote:
>> Hi,
>>
>> I'm having crash problem with samba 2:4.5.16+dfsg-1+deb9u1 in debian 9.8,
>> i'm trying to debug it so i can't find the package samba-dbg.
>>
>> Is there a way to debug samba without samba-dbg?
>>
> You might find this helpful:
>
> https://wiki.debian.org/HowToGetABacktrace
>
> Regards,
>
> -Roberto

Yes it was helpful, thank you !

But now, i've a dependency problem, version of samba in debian-security 
repo and samba-dbgsym in debian-debug repo are not the sames :

Les paquets suivants contiennent des dépendances non satisfaites :
  samba-dbgsym : Dépend: samba (= 2:4.5.16+dfsg-1) mais 
2:4.5.16+dfsg-1+deb9u1 devra être installé

Kevin

[toc] | [prev] | [next] | [standalone]

#207318

On Thu, Apr 11, 2019 at 04:45:53PM +0200, Kevin DAGNEAUX wrote:
> Le 11/04/2019 à 16:27, Roberto C. Sánchez a écrit :
> > On Thu, Apr 11, 2019 at 03:46:11PM +0200, Kevin DAGNEAUX wrote:
> > > Hi,
> > > 
> > > I'm having crash problem with samba 2:4.5.16+dfsg-1+deb9u1 in debian 9.8,
> > > i'm trying to debug it so i can't find the package samba-dbg.
> > > 
> > > Is there a way to debug samba without samba-dbg?
> > > 
> > You might find this helpful:
> > 
> > https://wiki.debian.org/HowToGetABacktrace
> > 
> > Regards,
> > 
> > -Roberto
> 
> Yes it was helpful, thank you !
> 
> But now, i've a dependency problem, version of samba in debian-security repo
> and samba-dbgsym in debian-debug repo are not the sames :
> 
> Les paquets suivants contiennent des dépendances non satisfaites :
>  samba-dbgsym : Dépend: samba (= 2:4.5.16+dfsg-1) mais
> 2:4.5.16+dfsg-1+deb9u1 devra être installé
> 

You might need to add a stretch/updates-debug source as well.

Regards,

-Roberto
-- 
Roberto C. Sánchez

[toc] | [prev] | [next] | [standalone]

#207337

Kevin DAGNEAUX wrote:

> But now, i've a dependency problem, version of samba in debian-security
> repo and samba-dbgsym in debian-debug repo are not the sames :

may be a similar problem is the root cause for your crashes, because I am
running samba for years and my wife uses it from windows on daily bases and
I have some virtual machines with Win7 too, but never had a crash in the
past 10+ years.

Why don't you start with the log files - increase log level etc.?

regards

[toc] | [prev] | [next] | [standalone]

#207355

[Multipart message — attachments visible in raw view] — view raw

> Kevin DAGNEAUX wrote:
>
>> But now, i've a dependency problem, version of samba in debian-security
>> repo and samba-dbgsym in debian-debug repo are not the sames :
> may be a similar problem is the root cause for your crashes, because I am
> running samba for years and my wife uses it from windows on daily bases and
> I have some virtual machines with Win7 too, but never had a crash in the
> past 10+ years.
>
> Why don't you start with the log files - increase log level etc.?
>
> regards
>
I'm using samba for lot of years too, i'm having trouble only with the 
last version from debian repo.

When crashing, samba don't need to be restarted and windows client just 
see a small freeze.

Log file talk about a lock problem on a directory that have never 
existed, in log file i don't have any info about which IP trying to 
access to this directory, that why a i try a debug to see if i've more 
info about thoses access.

Maybe you don't have any problem because samba panic script can't send 
you a mail.

Kevin

[toc] | [prev] | [next] | [standalone]

#207360

Kevin DAGNEAUX wrote:

> I'm using samba for lot of years too, i'm having trouble only with the
> last version from debian repo.
> 

Which debian version and which samba version - perhaps I missed this.

> When crashing, samba don't need to be restarted and windows client just
> see a small freeze.
> 
> Log file talk about a lock problem on a directory that have never
> existed, in log file i don't have any info about which IP trying to
> access to this directory, that why a i try a debug to see if i've more
> info about thoses access.
> 

Then enable logging per machine ID.

> Maybe you don't have any problem because samba panic script can't send
> you a mail.

I definitely do not have any problem, but can you share the crash report -
perhaps I am wrong

I have installed
 cat /etc/debian_version
9.8
$ dpkg -l | grep samba
ii  python-samba                   2:4.5.16+dfsg-1                    amd64       
Python bindings for Samba
ii  samba                          2:4.5.16+dfsg-1                    amd64       
SMB/CIFS file, print, and login server for Unix
ii  samba-common                   2:4.5.16+dfsg-1                    all         
common files used by both the Samba server and client
ii  samba-common-bin               2:4.5.16+dfsg-1                    amd64       
Samba common files used by both the server and the client
ii  samba-dsdb-modules             2:4.5.16+dfsg-1                    amd64       
Samba Directory Services Database
ii  samba-libs:amd64               2:4.5.16+dfsg-1                    amd64       
Samba core libraries
ii  samba-vfs-modules              2:4.5.16+dfsg-1                    amd64       
Samba Virtual FileSystem plugins

[toc] | [prev] | [next] | [standalone]

#207362

[Multipart message — attachments visible in raw view] — view raw

> Kevin DAGNEAUX wrote:
>
>> I'm using samba for lot of years too, i'm having trouble only with the
>> last version from debian repo.
>>
> Which debian version and which samba version - perhaps I missed this.
>
>> When crashing, samba don't need to be restarted and windows client just
>> see a small freeze.
>>
>> Log file talk about a lock problem on a directory that have never
>> existed, in log file i don't have any info about which IP trying to
>> access to this directory, that why a i try a debug to see if i've more
>> info about thoses access.
>>
> Then enable logging per machine ID.
>
>> Maybe you don't have any problem because samba panic script can't send
>> you a mail.
> I definitely do not have any problem, but can you share the crash report -
> perhaps I am wrong
>
> I have installed
>   cat /etc/debian_version
> 9.8
> $ dpkg -l | grep samba
> ii  python-samba                   2:4.5.16+dfsg-1                    amd64
> Python bindings for Samba
> ii  samba                          2:4.5.16+dfsg-1                    amd64
> SMB/CIFS file, print, and login server for Unix
> ii  samba-common                   2:4.5.16+dfsg-1                    all
> common files used by both the Samba server and client
> ii  samba-common-bin               2:4.5.16+dfsg-1                    amd64
> Samba common files used by both the server and the client
> ii  samba-dsdb-modules             2:4.5.16+dfsg-1                    amd64
> Samba Directory Services Database
> ii  samba-libs:amd64               2:4.5.16+dfsg-1                    amd64
> Samba core libraries
> ii  samba-vfs-modules              2:4.5.16+dfsg-1                    amd64
> Samba Virtual FileSystem plugins
>
>
>
$ cat /etc/debian_version
9.8

$ dpkg -l | grep samba
ii  python-samba 2:4.5.16+dfsg-1+deb9u1             amd64        Python 
bindings for Samba
ii  samba 2:4.5.16+dfsg-1+deb9u1             amd64        SMB/CIFS file, 
print, and login server for Unix
ii  samba-common 2:4.5.16+dfsg-1+deb9u1             all          common 
files used by both the Samba server and client
ii  samba-common-bin 2:4.5.16+dfsg-1+deb9u1             amd64        
Samba common files used by both the server and the client
ii  samba-dsdb-modules 2:4.5.16+dfsg-1+deb9u1             amd64        
Samba Directory Services Database
ii  samba-libs:amd64 2:4.5.16+dfsg-1+deb9u1             amd64        
Samba core libraries
ii  samba-vfs-modules 2:4.5.16+dfsg-1+deb9u1             amd64        
Samba Virtual FileSystem plugins

Per machin log file is enabled (using the default setting "log file = 
/var/log/samba/log.%m"), so log file that contain error is /var/log/log. 
(machin seems not identified by samba).

Here is the content of log file :


[2019/04/12 10:31:57.105329,  0] 
../source3/locking/posix.c:455(decrement_lock_ref_count)
   PANIC: assert failed at ../source3/locking/posix.c(455): 
lock_ref_count >= 0
[2019/04/12 10:31:57.105373,  0] ../source3/lib/util.c:791(smb_panic_s3)
   PANIC (pid 2206): assert failed: lock_ref_count >= 0
[2019/04/12 10:31:57.106329,  0] ../source3/lib/util.c:902(log_stack_trace)
   BACKTRACE: 29 stack frames:
    #0 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(log_stack_trace+0x1c) 
[0x7f9e6a6a6c0c]
    #1 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(smb_panic_s3+0x20) 
[0x7f9e6a6a6ce0]
    #2 /usr/lib/x86_64-linux-gnu/libsamba-util.so.0(smb_panic+0x2f) 
[0x7f9e6cbc319f]
    #3 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0(+0x194740) 
[0x7f9e6c7f8740]
    #4 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0(+0x19493f) 
[0x7f9e6c7f893f]
    #5 
/usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0(release_posix_lock_posix_flavour+0x1fc) 
[0x7f9e6c7faadc]
    #6 
/usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0(brl_unlock+0x566) 
[0x7f9e6c7f6bb6]
    #7 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0(do_unlock+0xce) 
[0x7f9e6c7f29ce]
    #8 
/usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0(smbd_do_setfilepathinfo+0x1b60) 
[0x7f9e6c75b2a0]
    #9 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0(+0xf8dbb) 
[0x7f9e6c75cdbb]
    #10 
/usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0(reply_trans2+0x645) 
[0x7f9e6c75f695]
    #11 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0(+0x123086) 
[0x7f9e6c787086]
    #12 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0(+0x1254ba) 
[0x7f9e6c7894ba]
    #13 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0(+0x1264ac) 
[0x7f9e6c78a4ac]
    #14 /usr/lib/x86_64-linux-gnu/libtevent.so.0(+0xaea3) [0x7f9e692e7ea3]
    #15 /usr/lib/x86_64-linux-gnu/libtevent.so.0(+0x9277) [0x7f9e692e6277]
    #16 /usr/lib/x86_64-linux-gnu/libtevent.so.0(_tevent_loop_once+0x9d) 
[0x7f9e692e204d]
    #17 
/usr/lib/x86_64-linux-gnu/libtevent.so.0(tevent_common_loop_wait+0x1b) 
[0x7f9e692e227b]
    #18 /usr/lib/x86_64-linux-gnu/libtevent.so.0(+0x9217) [0x7f9e692e6217]
    #19 
/usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0(smbd_process+0x6c9) 
[0x7f9e6c78b7d9]
    #20 /usr/sbin/smbd(+0xa7b4) [0x5583043b67b4]
    #21 /usr/lib/x86_64-linux-gnu/libtevent.so.0(+0xaea3) [0x7f9e692e7ea3]
    #22 /usr/lib/x86_64-linux-gnu/libtevent.so.0(+0x9277) [0x7f9e692e6277]
    #23 /usr/lib/x86_64-linux-gnu/libtevent.so.0(_tevent_loop_once+0x9d) 
[0x7f9e692e204d]
    #24 
/usr/lib/x86_64-linux-gnu/libtevent.so.0(tevent_common_loop_wait+0x1b) 
[0x7f9e692e227b]
    #25 /usr/lib/x86_64-linux-gnu/libtevent.so.0(+0x9217) [0x7f9e692e6217]
    #26 /usr/sbin/smbd(main+0x1784) [0x5583043b34f4]
    #27 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1) 
[0x7f9e68f5e2e1]
    #28 /usr/sbin/smbd(_start+0x2a) [0x5583043b35fa]
[2019/04/12 10:31:57.106501,  0] ../source3/lib/util.c:803(smb_panic_s3)
   smb_panic(): calling panic action [/usr/share/samba/panic-action 2206]
ptrace: Opération non permise.
/home/shares/Partages/Nextcloud/2206: Aucun fichier ou dossier de ce type.
/etc/samba/gdbcommands:1: Error in sourced command file:
No stack.
[2019/04/12 10:31:57.246124,  0] ../source3/lib/util.c:811(smb_panic_s3)
   smb_panic(): action returned status 0
[2019/04/12 10:31:57.246236,  0] ../source3/lib/dumpcore.c:303(dump_core)
   dumping core in /var/log/samba/cores/smbd

[toc] | [prev] | [next] | [standalone]

#207367

Kevin DAGNEAUX wrote:

> [2019/04/12 10:31:57.105329,  0]
> ../source3/locking/posix.c:455(decrement_lock_ref_count)
> PANIC: assert failed at ../source3/locking/posix.c(455):
> lock_ref_count >= 0
> [2019/04/12 10:31:57.105373,  0] ../source3/lib/util.c:791(smb_panic_s3)
> PANIC (pid 2206): assert failed: lock_ref_count >= 0
> [2019/04/12 10:31:57.106329,  0]
> [../source3/lib/util.c:902(log_stack_trace)
> BACKTRACE: 29 stack frames:
> #0 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(log_stack_trace+0x1c)
> [0x7f9e6a6a6c0c]

google tells me many similar issues

https://bugzilla.samba.org/show_bug.cgi?id=13650
https://bugzilla.samba.org/show_bug.cgi?id=13558
https://bugzilla.samba.org/show_bug.cgi?id=13443
https://bugzilla.samba.org/show_bug.cgi?id=13439
https://www.ixsystems.com/community/threads/samba-panic-assert-failed-lock_ref_count-0.55140/

which kernel do you have?

[toc] | [prev] | [next] | [standalone]

#207397

Kevin DAGNEAUX wrote:

> The bug id 13439 give me an interesting info (about kernel / glibc).
> I'll follow this thread to see if a solution will be added.
> 
> I'm running kernel 4.9.144-3.1 (from debian repo)

I always optimize and use a newer version of the kernel, which I build for
the machine in question, which means I am far away from 4.9 for at least
two years now. Which seems consistant, because I saw there was coredump
from 2017 laying around - don't know if it is related or not though.
ATM I am on 4.19.25 which is LTS and I think I'll stick to it for a while as
everything is working so well, that I do not see a reason to change.

But on the other hand it is showing pthread as a problem and they were
discussing about some race condition - might be I never hit this condition
and you do more often.

Good luck

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web