Samba crashes wit "signal 11" error

Bug #1573181 reported by ^_Pepe_^ on 2016-04-21
This bug affects 3 people
Affects Status Importance Assigned to Milestone
samba (Ubuntu)

Bug Description

My Samba server (Ubuntu 14.04.4) has suddenly started to refuse Win or Linux connections with a "signal 11" error.

My server is pretty stable (home server for DLNA, and files) and all machines have now problems (Ubuntu, Mint, Windows).

I have R/W permissions for all shares and all users, including guests, and I have change nothing recently except regular updates.

Please let me know if someone needs more information

Best and thanks

tags: added: trusty
Changed in samba (Ubuntu):
importance: Undecided → High
milestone: ubuntu-14.04.4 → none
tags: added: regression-update

Currentlu updated to 16.04, no luck. Samba version still same.

Including interesting logs?field.comment=Including interesting logs

Launchpad Janitor (janitor) wrote :

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

Changed in samba (Ubuntu):
status: New → Confirmed
Jacob Becker (jacob-becker-h) wrote :

I've tried to purge the old (4.1.6) version and clean install of 4.3.8
no success

still got
[2016/04/21 14:34:21.966214, 0] ../lib/util/fault.c:79(fault_report)
  INTERNAL ERROR: Signal 11 in pid 25664 (4.3.8-Ubuntu)
  Please read the Trouble-Shooting section of the Samba HOWTO
[2016/04/21 14:34:21.966270, 0] ../lib/util/fault.c:81(fault_report)
[2016/04/21 14:34:21.966293, 0] ../source3/lib/util.c:789(smb_panic_s3)
  PANIC (pid 25664): internal error

Marc Deslauriers (mdeslaur) wrote :

Today's Samba update may contain the fix for this issue:

Could the original bug reporter please test the update and comment here? Thanks!

Jacob Becker (jacob-becker-h) wrote :

Sadly this fix doesn't work for me.
[2016/05/04 20:12:19.872964, 0] ../lib/util/fault.c:78(fault_report)
[2016/05/04 20:12:19.873006, 0] ../lib/util/fault.c:79(fault_report)
  INTERNAL ERROR: Signal 11 in pid 6369 (4.3.9-Ubuntu)
  Please read the Trouble-Shooting section of the Samba HOWTO
[2016/05/04 20:12:19.873032, 0] ../lib/util/fault.c:81(fault_report)
[2016/05/04 20:12:19.873051, 0] ../source3/lib/util.c:789(smb_panic_s3)
  PANIC (pid 6369): internal error

However, it looks like this issue is somehow connected to the usage of ldapsam as password backend.
It works with a fresh configuration, if i enable our passdb backend = ldapsam: "...."
the error comes up again.

The configuration works like a charm with samba 4.1.6 but not with 4.3.8 or 4.3.9

kind regards

Hi all.
I don't have ldapsam active.
I've updated today, deleted all in /var/log/samba and after several hours, all new client logs are zero bytes, which is good for me.

Video streaming is now as fast as usual, and VLC (Win, OSx and Mint) is not complaining about "bad file descriptor" as was during past three weeks.

I propose to wait for Jacob Becker's investigations to get further info.

Thanks to all.


Hi all.
After intesive use of Samba I can confirm that the signal 11 error is not present after last patch.

I'm marking fix released. Please @Jacob, feel free to open a different bug.


Changed in samba (Ubuntu):
status: Confirmed → Fix Released
Jacob Becker (jacob-becker-h) wrote :


found a solution for me as well
it turns out that the line

ldapsam:trusted = yes

is the key.
after turnig it into a comment, samba works again.

kind regards

Erlon R. Cruz (sombrafam) wrote :

I still have the same problem even after the update mentioned :/.

Andreas Hasenack (ahasenack) wrote :

@sombrafam, can you attach your smb.conf and the core file(s) from /var/log/samba/cores/smbd please?

Andreas Hasenack (ahasenack) wrote :

Actually, ignore that. Could you please file a new bug instead with that info? You can use "apport-bug samba" IIRC.

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

Other bug subscribers