problems after upgrade from 3.3.2 to 3.4.0
in [Samba]
|
Prev: Error joining domain "The specified account already exists"
Next: [Samba] Interdomain trust with different WINS servers
From: Christian PERRIER on 26 May 2010 04:50 Quoting Thomas Gutzler (thomas.gutzler(a)gmail.com): > Hi, > > After upgrading one of my samba servers from ubuntu jaunty (3.3.2) to > karmic (3.4.0) I cannot access the shares any more. The default for "passdb backend" changed between these versions (from "smbpasswd" to "tdbsam") and, as you don't explicitly set it in smb.conf, I'd gues this might be the reason for this. Try adding: passdb backend = smbpasswd -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
From: Thomas Gutzler on 26 May 2010 07:00 Hi Christian, On 26/05/2010 4:44 PM, Christian PERRIER wrote: > Quoting Thomas Gutzler (thomas.gutzler(a)gmail.com): >> Hi, >> >> After upgrading one of my samba servers from ubuntu jaunty (3.3.2) to >> karmic (3.4.0) I cannot access the shares any more. > > The default for "passdb backend" changed between these versions (from > "smbpasswd" to "tdbsam") and, as you don't explicitly set it in > smb.conf, I'd gues this might be the reason for this. > > Try adding: > > passdb backend = smbpasswd Thanks for your reply. I am aware of this change but thought I wasn't affected because both smb.conf (PDC and other samba server) had passdb backend = tdbsam already set. Yet another setting not listed by testparm. Out of curiosity I tried setting it to smbpasswd on fintlewoodlewix; didn't make a difference. Here is the full smb.conf: [global] workgroup = OBEL server string = %h file server dns proxy = no log file = /var/log/samba/log.%m max log size = 1000 syslog = 0 panic action = /usr/share/samba/panic-action %d security = domain password server = 130.95.136.177 encrypt passwords = true passdb backend = tdbsam invalid users = root unix password sync = no passwd program = /usr/bin/passwd %u passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* . map to guest = bad uid guest account = nobody socket options = TCP_NODELAY [data] comment = valuable not backed up research data writeable = yes path = /home/fintlewoodlewix/data create mode = 0644 force create mode = 0644 force directory mode = 0755 directory mode = 0755 guest ok = yes -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
From: Christian PERRIER on 26 May 2010 08:50 Quoting Thomas Gutzler (thomas.gutzler(a)gmail.com): > passdb backend = tdbsam > already set. Yet another setting not listed by testparm. Ah, because this is the default so it's trimmed by testparm. 3.3.2 testparm would probably have it shown. So, sorry for the wrong answer. Are you in position to upgrade your Ubuntu box again to "whatever funky name used by Ubuntu 10.04" so that you bump to samba 3.4.7? (sorry, there are too many codenames in Ubuntu and I can never remember all of them...this is why I like to see us, Debian, release every 2 year..:-)) -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
From: Harry Jede on 26 May 2010 16:30 On Mittwoch, 26. Mai 2010 wrote Thomas Gutzler: > Hi Christian, > > On 26/05/2010 4:44 PM, Christian PERRIER wrote: > > Quoting Thomas Gutzler (thomas.gutzler(a)gmail.com): > >> Hi, > >> > >> After upgrading one of my samba servers from ubuntu jaunty (3.3.2) > >> to karmic (3.4.0) I cannot access the shares any more. > > > > The default for "passdb backend" changed between these versions > > (from "smbpasswd" to "tdbsam") and, as you don't explicitly set it > > in smb.conf, I'd gues this might be the reason for this. > > > > Try adding: > > > > passdb backend = smbpasswd > > Thanks for your reply. I am aware of this change but thought I wasn't > affected because both smb.conf (PDC and other samba server) had > passdb backend = tdbsam > already set. Yet another setting not listed by testparm. Mmmh, testparm is not so bad ;-) Try this: # testparm -v -s /dev/null |grep passdb Or my favorite upgrade path: # testparm -v -s /dev/null > smb.conf.default-$(smbd -V|cut -f2 -d' ') Run this before and after upgrading samba To get a small host specific file without the services: # testparm -s --section-name=global > smb.conf.$HOSTNAME-$(smbd -V| cut -f2 -d' ') So you may end up with 4 files: # ls smb.conf.* smb.conf.myserver-3.0.22 smb.conf.myserver-3.4.7 smb.conf.default-3.0.22 smb.conf.default-3.4.7 Run a diff against the default files and you may see which config params has changed their default values. -- Regards Harry Jede -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
From: Thomas Gutzler on 26 May 2010 22:10
On 27/05/2010 4:19 AM, Harry Jede wrote: > On Mittwoch, 26. Mai 2010 wrote Thomas Gutzler: >> >> On 26/05/2010 4:44 PM, Christian PERRIER wrote: >>> Quoting Thomas Gutzler (thomas.gutzler(a)gmail.com): >>>> >>>> After upgrading one of my samba servers from ubuntu jaunty (3.3.2) >>>> to karmic (3.4.0) I cannot access the shares any more. >>> > > Or my favorite upgrade path: > # testparm -v -s /dev/null > smb.conf.default-$(smbd -V|cut -f2 -d' ') > Run this before and after upgrading samba > > To get a small host specific file without the services: > # testparm -s --section-name=global > smb.conf.$HOSTNAME-$(smbd -V| > cut -f2 -d' ') It's a bit late to run it before the upgrade now but I found another machine running jaunty (enjoy), so I installed samba and ran testparm with the smb.conf from the updated machine (fintlewoodlewix). Here's the diff between the two defaults (without the line numbers): # diff smb.conf.default-3.3.2 smb.conf.default-3.4.0 < netbios name = ENJOY > netbios name = FINTLEWOODLEWIX < server string = Samba 3.3.2 > server string = Samba 3.4.0 < config backend = file < passdb backend = smbpasswd > passdb backend = tdbsam < use kerberos keytab = No > dedicated keytab file = > kerberos method = default > map untrusted to domain = No < max open files = 10000 > max open files = 16384 < config file = < lock directory = > lock directory = /var/run/samba > state directory = /var/lib/samba > cache directory = /var/cache/samba > perfcount module = > access based share enum = No > browsable = Yes < include = And the host specific ones. The only thing I changed there was to get rid of the PAM stuff and change the password server from name to IP. # diff smb.conf.enjoy-3.3.2 smb.conf.fintlewoodlewix-3.4.0 < obey pam restrictions = Yes < password server = io > password server = 130.95.136.177 < passdb backend = tdbsam < pam password change = Yes I also deleted all .tdb files in /var/lib/samba, the machine account on the PDC and rejoined the domain but authentication still doesn't work. Neither does the mapping to guest for invalid users. While I had samba running on the jaunty machine, I joined it to the domain and tried if I could connect to it using the same machine and credentials as before; and I could. Even the guest account seems to work alright with no change in the configuration other than the path in the share. I might follow Christians suggestion and upgrade to 10.04 unless there are any other suggestions. Maybe a second upgrade fixes it. Tom -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba |