Bug 10434 – Samba panic at Outlook sync

Bug 10434 - Samba panic at Outlook sync


Summary:	Samba panic at Outlook sync

Status:	NEW

Product:	Samba 4.0
Classification:	Unclassified
Component:	DCE-RPCs and pipes
Version:	4.0.1
Hardware:	x64 Linux

Importance:	P5 major
Target Milestone:	---
Assigned To:	Andrew Bartlett
QA Contact:	Samba QA Contact

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2014-02-10 13:42 UTC by Marcin Kukiełka
Modified:	2014-02-11 10:59 UTC (History)
CC List:	1 user (show)

See Also:

Attachments
debug Samba log (20.31 KB, application/octet-stream) 2014-02-10 13:42 UTC, Marcin Kukiełka	no flags	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Marcin Kukiełka 2014-02-10 13:42:57 UTC

Created attachment 9670 [details]
debug Samba log

I'm using Samba 4.0.1 and SOGo installed and configured  Samba is configured as domain controller using the official manual http://www.sogo.nu/files/docs/SOGo%20Native%20Microsoft%20Outlook%20Configuration.pdf
When I try to sync Outlook via 135 tcp port samba panics with error:

/usr/sbin/samba: Uncaught exception NSInvalidArgumentException, reason: Tried to add nil key to dictionary
[2014/02/10 12:45:59,  0] ../lib/util/fault.c:72(fault_report)
  ===============================================================
[2014/02/10 12:45:59,  0] ../lib/util/fault.c:73(fault_report)
  INTERNAL ERROR: Signal 6 in pid 12924 (4.0.1-4.centos6.1)
  Please read the Trouble-Shooting section of the Samba HOWTO
[2014/02/10 12:45:59,  0] ../lib/util/fault.c:75(fault_report)
  ===============================================================

After error port 135 is closed. Other domain controller services (DNS, LDAP) are ok.
Debug samba log in attachment.