Comment 8 for bug 1573181

Revision history for this message
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