After updating to samba-3.4.2 my users suddenly couldn't log in any more. Furthermore, running smbpasswd reported that there was no entry for the named user. The configured smb passwd file however clearly listed the name in question. To work around this problem, I changed my config file like this: -smb passwd file = /some/path/and/file +passdb backend = smbpasswd:/some/path/and/file strace indicates that before this change, /var/lib/samba/private/passdb.tdb was used as the password database, at least by smbpasswd. There is no indication in the smb.conf(5) man page that smb passwd file were deprecated, so this comes as a real surprise to me. I would expect a revbumped ebuild of samba-server to do at least one of the following: 1. elog about this problem, so admins can adjust their config manually 2. automatically adjust the config file resp. merge an adjusted version 3. avoid the problem by restoring "smb passwd file", maybe by making smbpasswd (without explicitely named path) the default passdb backend, or by automatically setting the backend if the smb passwd file config option is given 4. declare smbpasswd deprecated and elog instructions about how to migrate to tdb
In a way INVALID (read the changes), but I don't use samba. Unless as an upstream doc bug. Though perhaps elog warning would be useful.
(In reply to comment #1) > Unless as an upstream doc bug. Not even sure there; they MIGHT intend the "smb passwd file" directive so that admins can specify the type of backend in one place using passdb backend, and the location for it in another place. Dunno. Some remark would still be useful, though. Sall I report this upstream? > Though perhaps elog warning would be useful. Definitely, and it's a solution I can live with.
OK, lets see, if this gets some response.
I guess this is the cause of the problem: http://www.samba.org/samba/history/samba-3.4.0.html > Major enhancements in Samba 3.4.0 include: > ------------------------------------------ > > Configuration changes: > o The default passdb backend has been changed to 'tdbsam'! HTH, Marcel
This change in backends should have at least warranted a news flash via eselect... I mean really...
Ran into same problem, why has this broken ebuild been unmasked and marked as stable, it is broken, smbusers can't access anymore... Cmon guys this really costs time I do not have... switched back to 3.0.37 ...
*** Bug 319337 has been marked as a duplicate of this bug. ***
I just hit this as well. One of the nice folks at #samba worked me through it. Basically you can upgrade your old smbpasswd file to the tdb database with pdbedit -i smbpasswd:/path/to/oldfile -e tdbsam:/path/to/newfile In my case the old file was in /etc/samba/smbpasswd, and the new one (the default where samba now looks on gentoo without extra config) is /var/lib/samba/private/passdb.tdb Hopefully this can make its way into a news, or ewarn in the ebuild for other people.
*** Bug 314817 has been marked as a duplicate of this bug. ***
we are all agree about the source of the problem after upgrading to samba 3.4, but probably a different bug regarding the task "document/warn the user" would be more helpful...
I've added an elog text to both samba 3.4 and 3.5, perhaps it's too late to fire a news item. Sorry for all the inconveniences
*** Bug 352869 has been marked as a duplicate of this bug. ***
