Bug 4336 - INTERNAL ERROR when passdb backend is LDAP in Solaris 10
Summary: INTERNAL ERROR when passdb backend is LDAP in Solaris 10
Alias: None
Product: Samba 3.0
Classification: Unclassified
Component: smbldap-tools (show other bugs)
Version: 3.0.23d
Hardware: Sparc Solaris
: P3 major
Target Milestone: none
Assignee: Tournier Jerome
QA Contact: smbldap-tools team
Depends on:
Reported: 2007-01-11 11:09 UTC by Qing Chang
Modified: 2007-08-23 06:09 UTC (History)
1 user (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Qing Chang 2007-01-11 11:09:38 UTC
Samba 3.0.23d built on SunFire V880 with Solaris 10 with LDAP support. 
When LDAP is used for paaswd backend, samba panics with internal error. 
Samba works fine when LDAP is not used. Samba 3.0.14a works fine with
LDAP as passdb backend on the same machine.

Samba 3.0.23d also built on another SunFire V880 with Solaris 8 with
LDAP support, which works fine with LDAP as passdb backend.

Following is an excerpt of smbd log at log level 10:

====== begin =========
[2007/01/11 11:22:16, 5] passdb/pdb_interface.c:make_pdb_method_name(158)
  Attempting to find an passdb backend to match ldapsam:ldap://ldap.server.ca (ldapsam)
[2007/01/11 11:22:16, 5] passdb/pdb_interface.c:make_pdb_method_name(179)
  Found pdb backend ldapsam
[2007/01/11 11:22:16, 2] lib/smbldap_util.c:smbldap_search_domain_info(219)
  smbldap_search_domain_info: Searching for:[(&(objectClass=sambaDomain)(sambaDomainName=FILESERV))]
[2007/01/11 11:22:16, 5] lib/smbldap.c:smbldap_search_ext(1179)
  smbldap_search_ext: base => [dc=server,dc=ca], filter => [(&(objectClass=sambaDomain)(sambaDomainName=FILESERV))], scope => [2]
[2007/01/11 11:22:16, 5] lib/smbldap.c:smbldap_close(1080)
  The connection to the LDAP server was closed
[2007/01/11 11:22:16, 10] lib/smbldap.c:smb_ldap_setup_conn(632)
  smb_ldap_setup_connection: ldap://ldap.server.ca
[2007/01/11 11:22:16, 0] lib/fault.c:fault_report(41)
[2007/01/11 11:22:16, 0] lib/fault.c:fault_report(42)
  INTERNAL ERROR: Signal 11 in pid 11299 (3.0.23d)
  Please read the Trouble-Shooting section of the Samba3-HOWTO
[2007/01/11 11:22:16, 0] lib/fault.c:fault_report(44)

  From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
[2007/01/11 11:22:16, 0] lib/fault.c:fault_report(45)
[2007/01/11 11:22:16, 0] lib/util.c:smb_panic(1599)
  PANIC (pid 11299): internal error
[2007/01/11 11:22:16, 0] lib/util.c:log_stack_trace(1756)
  unable to produce a stack trace on this platform
[2007/01/11 11:22:16, 0] lib/fault.c:dump_core(173)
  dumping core in /usr/local/samba/var/cores/smbd
======= end ========
Comment 1 Qing Chang 2007-01-18 11:18:34 UTC
wondering if this is not a legitimate bug, or I have chosen a
wrong component. Please advise.

As mentioned originally, I have 2 identical SunFire V880 with 
different OS, Solaris 8 and Solaris 10. OpenLDAP 2.3.27 is 
installed on both, Solaris 8 have openssl -0.9.7g and Solaris 10
has openssl-0.9.8c. I'll try openssl -0.9.7g on Solaris 10
to see if that is the problem.
Comment 2 Björn Jacke 2007-08-23 06:09:24 UTC
Is Samba 3.0.23d maybe compiled against the system ldap libs? I suspect you compiled your old Samba 3.0.14 against openldap but at runtime the system ldap libs are tried to be used. Even if you link the openldap libs with rpath or equivalent option the namespace will be overwritten as soon as you also link against another library which is linked agains the system ldap library. You might have problems like this.

Anyhow - you say 3.0.23d works fine, so I'll close this bug for now. Please reopen if you have this problems with the latest Samba versions.