LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Debian (http://www.linuxquestions.org/questions/debian-26/)
-   -   samba problem after debian upgrade (http://www.linuxquestions.org/questions/debian-26/samba-problem-after-debian-upgrade-727049/)

chesterman 05-19-2009 10:09 AM

samba problem after debian upgrade
 
after a debian etch->lenny upgrade, my samba+ldap setup is not workin' properly. ldap apears to be fine, 'cause my squid authentication is still working. however, my users cannot access their shared folders on the samba server.

setup: debian 5
Code:

fileserver-veltrac:~# smbd --version
Version 3.0.24
fileserver-veltrac:~# slapd -V
@(#) $OpenLDAP: slapd 2.3.30 (Oct  5 2008 22:08:58) $
        jmm@galadriel:/home/jmm/ldap/openldap2.3-2.3.30/debian/build/servers/slapd

fileserver-veltrac:~# uname -a
Linux fileserver-veltrac 2.6.18-6-686 #1 SMP Sat Dec 27 09:31:05 UTC 2008 i686 GNU/Linux

the net getlocalsid command returns me the following:

Code:

[2009/05/19 11:00:20, 0] lib/smbldap_util.c:smbldap_search_domain_info(267)
  smbldap_search_domain_info: Got too many (2) domain info entries for domain DOMINIO
SID for domain DOMINIO is: S-1-5-21-874179082-3571801642-3889913597

the smbd.log:

Code:

  ===============================================================
[2009/05/19 08:45:59, 0] lib/fault.c:fault_report(42)
  INTERNAL ERROR: Signal 11 in pid 6550 (3.0.24)
  Please read the Trouble-Shooting section of the Samba3-HOWTO
[2009/05/19 08:45:59, 0] lib/fault.c:fault_report(44)
 
  From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
[2009/05/19 08:45:59, 0] lib/fault.c:fault_report(45)
  ===============================================================
[2009/05/19 08:45:59, 0] lib/util.c:smb_panic(1599)
  PANIC (pid 6550): internal error
[2009/05/19 08:45:59, 0] lib/util.c:log_stack_trace(1706)
  BACKTRACE: 15 stack frames:
  #0 /usr/sbin/smbd(log_stack_trace+0x23) [0x822c3d3]
  #1 /usr/sbin/smbd(smb_panic+0x46) [0x822c4c6]
  #2 /usr/sbin/smbd [0x821a69a]
  #3 [0xb7eff420]
  #4 /usr/lib/liblber-2.4.so.2(ber_memfree_x+0x50) [0xb76ac300]
  #5 /usr/lib/libldap_r-2.4.so.2 [0xb76dc274]
  #6 /usr/lib/libldap_r-2.4.so.2 [0xb76bc6d8]
  #7 /usr/lib/libldap_r-2.4.so.2 [0xb76eb950]
  #8 /lib/ld-linux.so.2 [0xb7f0e453]
  #9 /lib/i686/cmov/libc.so.6(exit+0x89) [0xb7b23ab9]
  #10 /usr/sbin/smbd [0x82c23bc]
  #11 /usr/sbin/smbd [0x82c23e0]
  #12 /usr/sbin/smbd(main+0x10f0) [0x82c3860]
  #13 /lib/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7b0b455]
  #14 /usr/sbin/smbd [0x8082b11]
[2009/05/19 08:45:59, 0] lib/fault.c:dump_core(173)
  dumping core in /var/log/samba/cores/smbd
[2009/05/19 08:45:59, 0] lib/fault.c:fault_report(41)
  ===============================================================
[2009/05/19 08:45:59, 0] lib/fault.c:fault_report(42)
  INTERNAL ERROR: Signal 11 in pid 6556 (3.0.24)
  Please read the Trouble-Shooting section of the Samba3-HOWTO
[2009/05/19 08:45:59, 0] lib/fault.c:fault_report(44)
 
  From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
[2009/05/19 08:45:59, 0] lib/fault.c:fault_report(45)
  ===============================================================
[2009/05/19 08:45:59, 0] lib/util.c:smb_panic(1599)
  PANIC (pid 6556): internal error
[2009/05/19 08:45:59, 0] lib/util.c:log_stack_trace(1706)
  BACKTRACE: 16 stack frames:
  #0 /usr/sbin/smbd(log_stack_trace+0x23) [0x822c3d3]
  #1 /usr/sbin/smbd(smb_panic+0x46) [0x822c4c6]
  #2 /usr/sbin/smbd [0x821a69a]
  #3 [0xb7eff420]
  #4 /usr/lib/liblber-2.4.so.2(ber_memfree_x+0x50) [0xb76ac300]
  #5 /usr/lib/libldap_r-2.4.so.2 [0xb76dc274]
  #6 /usr/lib/libldap_r-2.4.so.2 [0xb76bc6d8]
  #7 /usr/lib/libldap_r-2.4.so.2 [0xb76eb950]
  #8 /lib/ld-linux.so.2 [0xb7f0e453]
  #9 /lib/i686/cmov/libc.so.6(exit+0x89) [0xb7b23ab9]
  #10 /usr/sbin/smbd [0x82c23bc]
  #11 /usr/sbin/smbd [0x82c23e0]
  #12 /usr/sbin/smbd(start_background_queue+0x25c) [0x824893c]
  #13 /usr/sbin/smbd(main+0x1344) [0x82c3ab4]
  #14 /lib/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7b0b455]
  #15 /usr/sbin/smbd [0x8082b11]
[2009/05/19 08:45:59, 0] lib/fault.c:dump_core(173)
  dumping core in /var/log/samba/cores/smbd

and the winbindd.log:

Code:

2009/05/19 10:04:44, 0] lib/smbldap.c:smb_ldap_setup_conn(638)
  ldap_initialize: Time limit exceeded
[2009/05/19 10:04:44, 1] lib/smbldap.c:another_ldap_try(1150)
  Connection to LDAP server failed for the 1 try!
[2009/05/19 10:04:45, 0] lib/smbldap.c:smb_ldap_setup_conn(638)
  ldap_initialize: Time limit exceeded
[2009/05/19 10:04:45, 1] lib/smbldap.c:another_ldap_try(1150)
  Connection to LDAP server failed for the 2 try!
[2009/05/19 10:04:46, 0] lib/smbldap.c:smb_ldap_setup_conn(638)
  ldap_initialize: Time limit exceeded
[2009/05/19 10:04:46, 1] lib/smbldap.c:another_ldap_try(1150)
  Connection to LDAP server failed for the 3 try!
...

searching the web i'd found tons of issues on upgrading samba, but none of them solved my problem.

i appreciate any help. forgive for my poor english.

chesterman 05-19-2009 01:36 PM

after many tries and upgrading my samba to 3.2.5, the sharing is working... kind of.
now everyone can access their exclusive folders on the server, also can acess the public folder (anyone can access this folder without authentication). when people try to access folders that they should not access (like a IT guy accessing the Sales folder), the server also forbid the access. But when someone try to access their group folder (like the Sales guy accessing the Sales folder), windows show a error message, telling me the folder is no accessible.

any help is welcome.

tks in advance.


All times are GMT -5. The time now is 05:35 AM.