similar to: 4th Submission to Samba List -- No Response Yet

I have samba 3.0.28 installed on several servers and winbind dies every couple of days on all of them. The deaths appear to correlate with the following log messages: [2009/01/25 04:02:09, 0] lib/util.c:smb_panic(1655) PANIC (pid 13395): internal error [2009/01/25 04:02:09, 0] lib/util.c:log_stack_trace(1759) BACKTRACE: 14 stack frames: #0 winbindd(log_stack_trace+0x2d) [0x800ccc10] #1

I have samba 3.0.28 installed on several servers and winbind dies every couple of days on all of them. The deaths appear to correlate with the following log messages: [2009/01/25 04:02:09, 0] lib/util.c:smb_panic(1655) PANIC (pid 13395): internal error [2009/01/25 04:02:09, 0] lib/util.c:log_stack_trace(1759) BACKTRACE: 14 stack frames: #0 winbindd(log_stack_trace+0x2d) [0x800ccc10] #1

Okay, so I've just put the sernet repo file in my yum.repos.d directory and a yum update will elevate my samba server to the latest version. Is there any pitfall that is out there that I can avoid before yum updating. Centos 5.3 samba3-3.0.34-37 & related packages openldap-2.3.43-3.el5 & related packages I still have my samba3-3.0.34 packages squirreled away so I can force downgrade

I was using Samba-3.0.14a perfectly fine. Now, I'm trying to use Samba-3.0.34. I can do an "ADS" join fine with Samba-3.0.34, but I cannot do my old non-ADS join anymore. Winbindd starts and stays running fine, but when I run net to do the non-ADS join I'm running into a strange "interfaces" issue. It now wants an "interfaces" line in the smb.conf file when

Hi. Today I upgraded samba from 3.0.34 to 3.4.4 without changing anything in smb.conf but with changing local and domain sid: old samba 1) net getdomainsid and getlocalsid new samba 2) net setdomainsid and setlocalsid to ones (both the same) from 1) after restarting samba I can't log into domain: XP says : domain controller unavailable ... I tried to rejoin domain - and I can ;) however

Hi I am trying install Samba-Vscan. When run *make* show this message [root at LinuxDefault samba-vscan]# make --debug GNU Make 3.81 Copyright (C) 2006 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. *This program built for i686-redhat-linux-gnu* *Reading

I'm trying to select a subset of a dataframe while dropping some factors. While the dataset gets smaller all Factor levels remain and I need to get rid of them. Strangely enough, I am almost certain that the same code on the same data worked OK earlier today - and it is not the first time that I'm not able to replicate earlier results with this command (I know, I might just be going

With samba 3.0.34 I have the issue described here http://webui.sourcelabs.com/samba/issues/5535 That is "smbpasswd -a joe" gives RID=2*UID+1000 while "net rpc user add joe" gives the value of the sambaNextRid attribute of the sambaDomainName LDAP entry. Also "smbpasswd -am machine" gives RID=2*UID+1000 while directly joining the domain gives RID=sambaNextRid This is

I have two CentOS servers running samba3-3.0.34-37. When I connect to a samba share from my Windows 2003 R2 servers, and then try to copy a file to it, I often get the message "target filesystem does not support long filenames." Sometimes it works and sometimes it doesn't. I've been fighting this problem for 2 years. I've replaced my Windows servers, changed my Windows

Hello, I am using samba server as members of windows AD domain , with "security = ADS", the logins unix and windows are aligned. Since the version 3.0.34 , I have strange behaviour on shares where we use "valid users" with unix groups it does'nt work. Nok: Valid users = @group1 Valid users = +group1 Still work : Valid users = Domain\user Valid users = user The bad

Hello, can anyone give me some tips why the file size of various samba executables has been increased dramatically from 3.0.34 to 3.3.3 (e.g. smbd 3.5MB -> ~7MB) The reason is that it is necessary for our project to keep the size as small as possible. You can have a look into the makefile here:

Hi, we had this setup working for quite some time but after upgrading the samba package things look different: we now have the following samba/ldap setup: samba-3.0.34p1-cups-ldap openldap-server-2.3.43 the samba-ldap configuration is: doing parameter ldap suffix = dc=foo,dc=ch doing parameter ldap machine suffix = ou=Computers,ou=Samba,ou=system doing parameter ldap user suffix =

I have a problem with large files (>2 Gb) in a Debian sarge based system. I install samba 3.0.34 with this configuration: ./configure --with-smbwrapper --with-ldap --with-automount --with-smbmount --with-pam --with-pam_smbpass --with-ldapsam --with-syslog --without-profiling-data --with-quotas --with-sys-quotas --with-libsmbclient --with-acl-support --with-utmp --with-vfs --with-winbind

Hello, I'm upgrading my samba installation from 3.0.34 (FreeBSD 6.4) to 3.4.x (CentOS 5.5) from SerNet. I have LDAP based samba domain (PDC and BDC) and a homes/Profiles member server. I first upgraded my DCs to 3.4.9 with no problem. I have recently installed a new file server (samba 3.4.11 on CentOS 5.5). I have issues connecting to this server with old versions of smbclient which

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 =============================================================== "Minds are like parachutes. They only function when they are open." Sir James Dewar =============================================================== Release Announcements ===================== This is a bug fix release of the Samba 3.0 series.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 =============================================================== "Minds are like parachutes. They only function when they are open." Sir James Dewar =============================================================== Release Announcements ===================== This is a bug fix release of the Samba 3.0 series.

Hello, I plan to update my samba-3.0.22/openldap-2.3.24 to samba-3.0.34/openldap-2.4.15 and I'm currently testing it. This is on FreeBSD. My idea is : 1) slapcat the openldap server and save the various tdb files. 2) deinstall samba and openldap and wipe out the bdb files 3) install the newer versions 4) slapadd to the new openldap server This seems to work in my test lab. During my tests I

Hello Somebody have idea which user account is responsible of guest info ? There is any box linux with openldap and samba integrated ? Thanks .. . [2009/10/14 18:38:11, 0] smbd/server.c:main(942) smbd version 3.0.34 started. Copyright Andrew Tridgell and the Samba Team 1992-2009 [2009/10/14 18:38:11, 0] param/loadparm.c:set_server_role(4293) Server's Role (logon server) conflicts

Hi. After an upgrade from 3.0.34 to 3.4.x or 3.5.x (I run samba on FreeBSD, and, ufortunately, 3.0.x branch was just removed from FreeBSD ports) I notices that I got a new domain PROBE, not referenced in any of my configs. Previously it was only a BUILTIN domain, now there are two of them. As the number of predefined domains continues to grow - I want to ask, if there is any possibility to

Release Announcements ===================== This is a security release in order to address CVE-2009-1888. o CVE-2009-1888: In Samba 3.0.31 to 3.3.5 (inclusive), an uninitialized read of a data value can potentially affect access control when "dos filemode" is set to "yes". ###################################################################### Changes