Bug 10434 - Samba panic at Outlook sync
Summary: Samba panic at Outlook sync
Alias: None
Product: Samba 4.0
Classification: Unclassified
Component: DCE-RPCs and pipes (show other bugs)
Version: 4.0.1
Hardware: x64 Linux
: P5 major (vote)
Target Milestone: ---
Assignee: Andrew Bartlett
QA Contact: Samba QA Contact
Depends on:
Reported: 2014-02-10 13:42 UTC by Marcin Kukiełka
Modified: 2022-08-19 05:44 UTC (History)
1 user (show)

See Also:

debug Samba log (20.31 KB, application/octet-stream)
2014-02-10 13:42 UTC, Marcin Kukiełka
no flags Details

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.
Comment 1 Douglas Bagnall 2022-08-19 05:44:39 UTC
I'm going to INVALID this, given this is not Samba code:

> No symbol table info available.
> #23 0x00007f89a5606df3 in emsmdbp_object_get_properties () from /usr/lib64/samba4/modules/dcerpc_mapiproxy_server/exchange_emsmdb.so
> No symbol table info available.
> #24 0x00007f89a5611111 in EcDoRpc_RopGetPropertiesSpecific () from /usr/lib64/samba4/modules/dcerpc_mapiproxy_server/exchange_emsmdb.so
> No symbol table info available.
> #25 0x00007f89a5602701 in ?? () from /usr/lib64/samba4/modules/dcerpc_mapiproxy_server/exchange_emsmdb.so
> No symbol table info available.
> #26 0x00007f89a5603334 in ?? () from /usr/lib64/samba4/modules/dcerpc_mapiproxy_server/exchange_emsmdb.so
> No symbol table info available.
> #27 0x00007f89a5603e8e in ?? () from /usr/lib64/samba4/modules/dcerpc_mapiproxy_server/exchange_emsmdb.so
> No symbol table info available.
> #28 0x00007f89a6968383 in mapiproxy_server_dispatch () from /usr/lib64/libmapiproxy.so.0
> No symbol table info available.
> #29 0x00007f89a6ba798c in ?? () from /usr/lib64/samba4/modules/dcerpc_server/dcesrv_mapiproxy.so
> No symbol table info available.
> #30 0x0000003ecac6cfe2 in dcesrv_request (dce_conn=<value optimized out>, pkt=<value optimized out>, blob=...) at ../source4/rpc_server/dcerpc_server.c:965
>        pull = 0x236dce0
>        status = <value optimized out>
>        context = 0x27c97e0

No-one has even mentioned mapiproxy on the lists since 2018, so I'm assuming it just keeps getting deader.

Reopen if I'm wrong, but I think raising it with SOGo would be the best idea, if it still matters.