Re: Debugging samba
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
begin:vcard
fn:Kevin DAGNEAUX
n:DAGNEAUX;Kevin
org:Fiitelcom
adr;quoted-printable:;;12 rue du Pr=C3=A9 Drou=C3=A9;Chavelot;;88150;France
email;internet:kevin.dagneaux@fiitelcom.fr
title:Informaticien
tel;work:03 29 36 88 85
x-mozilla-html:TRUE
url:https://www.fiitelcom.fr
version:2.1
end:vcard
Reply to: