segfault on Samba v4.3.11-Ubuntu
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
samba (Ubuntu) |
Triaged
|
Medium
|
Andreas Hasenack |
Bug Description
Samba crash sometimes with this message :
I don't understand what is the event which make it crash.
The clients for Samba are on Windows 7 and 10.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_
0x00007fb966bc607a in __GI___waitpid (pid=4502, stat_loc=
#0 0x00007fb966bc607a in __GI___waitpid (pid=4502, stat_loc=
#1 0x00007fb966b3efbb in do_system (line=line@
#2 0x00007fb966b3f39a in __libc_system (line=line@
#3 0x00007fb9695ea8d1 in smb_panic_s3 (why=<optimized out>) at ../source3/
#4 0x00007fb96a35df1f in smb_panic (why=why@
#5 0x00007fb96a35e136 in fault_report (sig=<optimized out>) at ../lib/
#6 sig_fault (sig=<optimized out>) at ../lib/
#7 <signal handler called>
#8 smbXsrv_
#9 0x00007fb969eef643 in reply_sesssetup
#10 0x00007fb969f2be67 in switch_message (type=<optimized out>, req=req@
#11 0x00007fb969f2dbb3 in construct_reply (deferred_pcd=0x0, encrypted=false, seqnum=0, unread_bytes=0, size=76, inbuf=0x0, xconn=0x559a1fd
#12 process_smb (xconn=
#13 0x00007fb969f2f21c in smbd_server_
#14 0x00007fb96827d917 in run_events_poll (ev=0x559a1fddd120, pollrtn=<optimized out>, pfds=0x559a1fdf
#15 0x00007fb96827db77 in s3_event_loop_once (ev=0x559a1fddd120, location=<optimized out>) at ../source3/
#16 0x00007fb966ec7d3d in _tevent_loop_once () from /usr/lib/
#17 0x00007fb966ec7edb in tevent_
#18 0x00007fb969f30578 in smbd_process (ev_ctx=
#19 0x0000559a1ea83e12 in smbd_accept_
#20 0x00007fb96827d917 in run_events_poll (ev=0x559a1fddd120, pollrtn=<optimized out>, pfds=0x559a1fdf
#21 0x00007fb96827db77 in s3_event_loop_once (ev=0x559a1fddd120, location=<optimized out>) at ../source3/
#22 0x00007fb966ec7d3d in _tevent_loop_once () from /usr/lib/
#23 0x00007fb966ec7edb in tevent_
#24 0x0000559a1ea82099 in smbd_parent_loop (parent=
#25 main (argc=<optimized out>, argv=<optimized out>) at ../source3/
A debugging session is active.
Description: Ubuntu 16.04.6 LTS
Release: 16.04
syslog :
Mar 5 11:33:45 ServeurDev smbd[4501]: [2019/03/05 11:33:45.439809, 0] ../source3/
Mar 5 11:33:45 ServeurDev smbd[4501]: No protocol supported !
Mar 5 11:33:45 ServeurDev smbd[4501]: [2019/03/05 11:33:45.483363, 0] ../lib/
Mar 5 11:33:45 ServeurDev smbd[4501]: =======
Mar 5 11:33:45 ServeurDev smbd[4501]: [2019/03/05 11:33:45.483416, 0] ../lib/
Mar 5 11:33:45 ServeurDev smbd[4501]: INTERNAL ERROR: Signal 11 in pid 4501 (4.3.11-Ubuntu)
Mar 5 11:33:45 ServeurDev smbd[4501]: Please read the Trouble-Shooting section of the Samba HOWTO
Mar 5 11:33:45 ServeurDev smbd[4501]: [2019/03/05 11:33:45.483441, 0] ../lib/
Mar 5 11:33:45 ServeurDev smbd[4501]: =======
Mar 5 11:33:45 ServeurDev smbd[4501]: [2019/03/05 11:33:45.483458, 0] ../source3/
Mar 5 11:33:45 ServeurDev smbd[4501]: PANIC (pid 4501): internal error
Mar 5 11:33:45 ServeurDev smbd[4501]: [2019/03/05 11:33:45.484348, 0] ../source3/
Mar 5 11:33:45 ServeurDev smbd[4501]: BACKTRACE: 23 stack frames:
Mar 5 11:33:45 ServeurDev smbd[4501]: #0 /usr/lib/
Mar 5 11:33:45 ServeurDev smbd[4501]: #1 /usr/lib/
Mar 5 11:33:45 ServeurDev smbd[4501]: #2 /usr/lib/
Mar 5 11:33:45 ServeurDev smbd[4501]: #3 /usr/lib/
Mar 5 11:33:45 ServeurDev smbd[4501]: #4 /lib/x86_
Mar 5 11:33:45 ServeurDev smbd[4501]: #5 /usr/lib/
Mar 5 11:33:45 ServeurDev smbd[4501]: #6 /usr/lib/
Mar 5 11:33:45 ServeurDev smbd[4501]: #7 /usr/lib/
Mar 5 11:33:45 ServeurDev smbd[4501]: #8 /usr/lib/
Mar 5 11:33:45 ServeurDev smbd[4501]: #9 /usr/lib/
Mar 5 11:33:45 ServeurDev smbd[4501]: #10 /usr/lib/
Mar 5 11:33:45 ServeurDev smbd[4501]: #11 /usr/lib/
Mar 5 11:33:45 ServeurDev smbd[4501]: #12 /usr/lib/
Mar 5 11:33:45 ServeurDev smbd[4501]: #13 /usr/lib/
Mar 5 11:33:45 ServeurDev smbd[4501]: #14 /usr/lib/
Mar 5 11:33:45 ServeurDev smbd[4501]: #15 /usr/sbin/
Mar 5 11:33:45 ServeurDev smbd[4501]: #16 /usr/lib/
Mar 5 11:33:45 ServeurDev smbd[4501]: #17 /usr/lib/
Mar 5 11:33:45 ServeurDev smbd[4501]: #18 /usr/lib/
Mar 5 11:33:45 ServeurDev smbd[4501]: #19 /usr/lib/
Mar 5 11:33:45 ServeurDev smbd[4501]: #20 /usr/sbin/
Mar 5 11:33:45 ServeurDev smbd[4501]: #21 /lib/x86_
Mar 5 11:33:45 ServeurDev smbd[4501]: #22 /usr/sbin/
Mar 5 11:33:45 ServeurDev smbd[4501]: [2019/03/05 11:33:45.484530, 0] ../source3/
Mar 5 11:33:45 ServeurDev smbd[4501]: smb_panic(): calling panic action [/usr/share/
Mar 5 11:33:46 ServeurDev smbd[4501]: [2019/03/05 11:33:46.928620, 0] ../source3/
Mar 5 11:33:46 ServeurDev smbd[4501]: smb_panic(): action returned status 0
Mar 5 11:33:46 ServeurDev smbd[4501]: [2019/03/05 11:33:46.928743, 0] ../source3/
Mar 5 11:33:46 ServeurDev smbd[4501]: dumping core in /var/log/
Mar 5 11:33:46 ServeurDev smbd[4501]:
configuration :
obey pam restrictions = yes
unix password sync = yes
package :
Paquet : samba
État: installé
Automatiquement installé: non
Version : 2:4.3.11+
Priorité : optionnel
Section : net
Responsable : Ubuntu Developers <email address hidden>
Architecture : amd64
Taille décompressée : 11,5 M
Dépend: adduser, libpam-modules, libpam-runtime (>= 1.0.1-11), lsb-base (>= 4.1+Debian11ubu
libtdb1 (>= 1.2.7+git20101214), libtevent0 (>= 0.9.16), libwbclient0 (= 2:4.3.11+
Pré-dépend: dpkg (>= 1.15.6~)
Recommande: attr, logrotate, samba-dsdb-modules, samba-vfs-modules
Suggère: bind9 (>= 1:9.5.1), bind9utils, ctdb, ldb-tools, ntp, smbldap-tools, winbind, ufw
Est en conflit: libldb1 (< 1:1.1.15), libldb1:i386 (< 1:1.1.15), samba (< 2:3.3.0~rc2-5), samba:i386 (< 2:3.3.0~rc2-5), samba-ad-dc, samba-doc (< 2:4.0.5~), samba-tools, samba4 (< 4.0.0~alpha6-2), samba:i386
Casse: qtsmbstatus-server (< 2.2.1-3~), qtsmbstatus-
Remplace: libsamdb0 (< 4.0.0~alpha17~), python-samba (< 2:4.1.4+dfsg-3), python-samba:i386 (< 2:4.1.4+dfsg-3), samba-ad-dc, samba-common (<= 2.0.5a-2), samba-common:i386 (<= 2.0.5a-2), samba-doc (< 2:4.0.5~), samba-libs (<
Améliore: bind9, ntp
Changed in samba (Ubuntu): | |
status: | New → Triaged |
tags: | added: server-next |
Changed in samba (Ubuntu): | |
status: | Incomplete → New |
tags: | removed: server-next |
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?
This will help us to find and resolve the problem.