Panic or segfault in Samba

Bug #1955588 reported by René Líma
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
samba
Unknown
Unknown
samba (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

The Samba 'panic action' script, /usr/share/samba/panic-action,
was called for PID 61029 (/usr/sbin/smbd).

This means there was a problem with the program, such as a segfault.
Below is a backtrace for this process generated with gdb, which shows
the state of the program at the time the error occurred. The Samba log
files may contain additional information about the problem.

If the problem persists, you are encouraged to first install the
samba-dbgsym package, which contains the debugging symbols for the Samba
binaries. Then submit the provided information as a bug report to
Ubuntu by visiting this link:
https://launchpad.net/ubuntu/+source/samba/+filebug

[New LWP 61068]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x00007fb54466edff in __GI___wait4 (pid=61070, stat_loc=stat_loc@entry=0x7fffc61e90f8, options=options@entry=0, usage=usage@entry=0x0) at ../sysdeps/unix/sysv/linux/wait4.c:27
#0 0x00007fb54466edff in __GI___wait4 (pid=61070, stat_loc=stat_loc@entry=0x7fffc61e90f8, options=options@entry=0, usage=usage@entry=0x0) at ../sysdeps/unix/sysv/linux/wait4.c:27
#1 0x00007fb54466ed7b in __GI___waitpid (pid=<optimized out>, stat_loc=stat_loc@entry=0x7fffc61e90f8, options=options@entry=0) at waitpid.c:38
#2 0x00007fb5445de0e7 in do_system (line=<optimized out>) at ../sysdeps/posix/system.c:172
#3 0x00007fb544aaed3f in smb_panic_s3 () from /lib/x86_64-linux-gnu/libsmbconf.so.0
#4 0x00007fb544e8d09b in smb_panic () from /lib/x86_64-linux-gnu/libsamba-util.so.0
#5 0x00007fb544e8d2a5 in ?? () from /lib/x86_64-linux-gnu/libsamba-util.so.0
#6 <signal handler called>
#7 0x00007fb543e1bc7c in dbwrap_record_delete () from /usr/lib/x86_64-linux-gnu/samba/libdbwrap.so.0
#8 0x00007fb544ce3924 in smbXsrv_session_logoff () from /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0
#9 0x00007fb544cca2a7 in ?? () from /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0
#10 0x00007fb544784c4a in tevent_common_invoke_immediate_handler () from /lib/x86_64-linux-gnu/libtevent.so.0
#11 0x00007fb544784c6e in tevent_common_loop_immediate () from /lib/x86_64-linux-gnu/libtevent.so.0
#12 0x00007fb54478aab0 in ?? () from /lib/x86_64-linux-gnu/libtevent.so.0
#13 0x00007fb544788e3b in ?? () from /lib/x86_64-linux-gnu/libtevent.so.0
#14 0x00007fb544783ec8 in _tevent_loop_once () from /lib/x86_64-linux-gnu/libtevent.so.0
#15 0x00007fb54478416b in tevent_common_loop_wait () from /lib/x86_64-linux-gnu/libtevent.so.0
#16 0x00007fb544788dcb in ?? () from /lib/x86_64-linux-gnu/libtevent.so.0
#17 0x00007fb544cb53a8 in smbd_process () from /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0
#18 0x0000558c0b1bf8bd in ?? ()
#19 0x00007fb544784801 in tevent_common_invoke_fd_handler () from /lib/x86_64-linux-gnu/libtevent.so.0
#20 0x00007fb54478acd7 in ?? () from /lib/x86_64-linux-gnu/libtevent.so.0
#21 0x00007fb544788e3b in ?? () from /lib/x86_64-linux-gnu/libtevent.so.0
#22 0x00007fb544783ec8 in _tevent_loop_once () from /lib/x86_64-linux-gnu/libtevent.so.0
#23 0x00007fb54478416b in tevent_common_loop_wait () from /lib/x86_64-linux-gnu/libtevent.so.0
#24 0x00007fb544788dcb in ?? () from /lib/x86_64-linux-gnu/libtevent.so.0
#25 0x0000558c0b1bcbc7 in main ()
A debugging session is active.

 Inferior 1 [process 61029] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]
[Inferior 1 (process 61029) detached]

Revision history for this message
Chris Guiver (guiverc) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:

apport-collect 1955588

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

(this detail will provide release details, package details etc.)

Revision history for this message
Stefan Metzmacher (metze) wrote :
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

That would then be part of 4.15.3
Thanks Stefan, linking the upstream bug ...

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in samba (Ubuntu):
status: New → Confirmed
Revision history for this message
Bryce Harrington (bryce) wrote :

The upstream bug report has a patch associated with it, that should be reviewed for consideration to include in ubuntu's package.

Changed in samba (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Triaged
Revision history for this message
Bryce Harrington (bryce) wrote :

René or araemo, could you describe the steps leading up to the crash? For instance, does it occur when you try to connect using MacOS 10.15.4?

Also, are you running Ubuntu 20.04, or a different release?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.