Hi all, after compiling samba-3.0.24 in Solaris 9 Generic_118558-28 with gcc version 3.4.2 using the following configure: ./configure --prefix=/opt/samba-3.0.24 --disable-cups --disable-iprint --with-ads --with-krb5=/opt/krb5-1.5.1 --with-acl-support --with-pam The global config stablish this machine as a domain member of an AD domain: workgroup = GRUPOGMV netbios name = GMVPROJECTS4 realm = GMV.ES security = ADS lm announce = True I get the following error when I run the smbd with -D flag: [2007/05/17 13:03:14, 5] auth/auth_util.c:debug_nt_user_token(448) NT user token: (NULL) [2007/05/17 13:03:14, 5] auth/auth_util.c:debug_unix_user_token(474) UNIX token of user 0 Primary group is 0 and contains 0 supplementary groups [2007/05/17 13:03:14, 0] lib/fault.c:fault_report(41) =============================================================== [2007/05/17 13:03:14, 0] lib/fault.c:fault_report(42) INTERNAL ERROR: Signal 11 in pid 12271 (3.0.24) Please read the Trouble-Shooting section of the Samba3-HOWTO [2007/05/17 13:03:14, 0] lib/fault.c:fault_report(44) From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf [2007/05/17 13:03:14, 0] lib/fault.c:fault_report(45) =============================================================== [2007/05/17 13:03:14, 0] lib/util.c:smb_panic(1599) The system is configured as an ldap client, in a NIS/LDAP domain, and the net join command created the machine account in our AD. Best regards and thanks in advance. Eduardo
Created attachment 2701 [details] The smb.conf file This is the smb.conf file we are using with the samb a server.
There's not really enough information to go on here. Can you get a backtrace ot at least a level 10 debug log from smbd surrounding the crash? Also, please include the output from `ldd smbd`. Thanks.
(In reply to comment #2) > There's not really enough information to go on here. > Can you get a backtrace ot at least a level 10 debug > log from smbd surrounding the crash? Also, please include the > output from `ldd smbd`. Thanks. > Here it is the ldd smbd output: ldd smbd libthread.so.1 => /usr/lib/libthread.so.1 libldap-2.3.so.0 => /opt/openldap-2.3.32/lib/libldap-2.3.so.0 liblber-2.3.so.0 => /opt/openldap-2.3.32/lib/liblber-2.3.so.0 libgssapi_krb5.so.2 => /opt/krb5-1.5.1/lib/libgssapi_krb5.so.2 libkrb5.so.3 => /opt/krb5-1.5.1/lib/libkrb5.so.3 libk5crypto.so.3 => /opt/krb5-1.5.1/lib/libk5crypto.so.3 libcom_err.so.3 => /opt/krb5-1.5.1/lib/libcom_err.so.3 libresolv.so.2 => /usr/lib/libresolv.so.2 libsocket.so.1 => /usr/lib/libsocket.so.1 libnsl.so.1 => /usr/lib/libnsl.so.1 libdl.so.1 => /usr/lib/libdl.so.1 libpam.so.1 => /usr/lib/libpam.so.1 libsec.so.1 => /usr/lib/libsec.so.1 libsendfile.so.1 => /usr/lib/libsendfile.so.1 libiconv.so.2 => /usr/local/lib/libiconv.so.2 libc.so.1 => /usr/lib/libc.so.1 librt.so.1 => /usr/lib/librt.so.1 libgen.so.1 => /usr/lib/libgen.so.1 libssl.so.0.9.7 => /usr/local/ssl/lib/libssl.so.0.9.7 libcrypto.so.0.9.7 => /usr/local/ssl/lib/libcrypto.so.0.9.7 libgcc_s.so.1 => /usr/local/lib/libgcc_s.so.1 libkrb5support.so.0 => /opt/krb5-1.5.1/lib/libkrb5support.so.0 libmp.so.2 => /usr/lib/libmp.so.2 libcmd.so.1 => /usr/lib/libcmd.so.1 libaio.so.1 => /usr/lib/libaio.so.1 libmd5.so.1 => /usr/lib/libmd5.so.1 /usr/platform/SUNW,Ultra-250/lib/libc_psr.so.1 /usr/platform/SUNW,Ultra-250/lib/libmd5_psr.so.1
Created attachment 2709 [details] A level 10 smbd log This is the log from smbd -D and log level = 10. Thanks.
Just a few educated guesses: Are you using Sun nss_ldap client ? If so this might just be a failure caused by mixing the Sun ldap libs and the openldap ones. One possible workaround might be to use nscd if you are not.
(In reply to comment #5) > Just a few educated guesses: > > Are you using Sun nss_ldap client ? If so this might just be a > failure caused by mixing the Sun ldap libs and the openldap ones. > One possible workaround might be to use nscd if you are not. > Hi Gerald, right, the system is configured to use the sun ldap client. The nscd is runnning in this system and I have been able to install samba 3.0.25 in solaris 8 and solaris 10 in the same way annd they are working fine. Could it be a SASL issue? is it necessary for the kind of config i want to set up? Thanks in advance and best regards.
Ok, if you're using SUN ldap then you have some mixup with the openldap libraries. See the ldd output, it does contain openldap. Please try compiling Samba so that it uses only one single set of libraries. Volker
Comment on attachment 2701 [details] The smb.conf file 123
The content of attachment 2701 [details] has been deleted by Björn Jacke <bj@sernet.de> who provided the following reason: deleted on submitter's request The token used to delete this attachment was generated at 2012-02-06 16:19:15 UTC.
The content of attachment 2709 [details] has been deleted by Björn Jacke <bj@sernet.de> who provided the following reason: deleted on submitter's request The token used to delete this attachment was generated at 2012-02-06 16:20:09 UTC.