Stringer Kenneth M NGA-PRTN USA CTR
2011-Jul-08 19:30 UTC
[Samba] Upgrading from 3.0.37 to 3.5.9
I am upgrading from 3.0.37 to 3.5.9 on the same server and need some advice. I am running Solaris 10 on a domain server that services 10 XP and Win 7 clients. The existing Samba directory structure is not standard. I believe the engineer who built the Solaris install transferred all Samba 2.0 directories from the old server to the current server and then created additional directories for the install and symbolically linked some of the old files to the new install. Anyway, Samba is installed in two different structures on the server: Samba and /etc/samba... and /etc/sfw.... We are using the "sfw" directories: The smb.conf file in /etc/samba is symbolically linked to the smb.conf file in /etc/sfw. So here are my questions: 1) How do I migrate the tdbsam database from 3.0.37 to 3.5.9? 2) Can I use the existing smb.conf file? 3) Can I just backup smb.conf and tdbsam files and reinstall to all the default directories and then copy the backup files to the appropriate Samba directories? 4) What else do I need to migrate? I'm sure if I just do a ./configure like the Samba web site says, my whole team will be down until I get it fixed. There seems to be nothing in the documentation, which is very old, to help w/ this issue. Any input to point me in the right direction would be greatly appreciated. Thanks. Ken
I upgraded a while ago. I believe with samba 3.0.x from sun that the
executables are in /usr/sfw and that configuration and account info is
in /etc/samba. You will also have database files in /var/samba
You should run "testparm -v " to see the location of configuration
files
and directories.
You MUST back these up!
I think 3.5.x will also look for smb.conf in /etc/samba by default.
You can explicitly define paths if need be. Once you upgrade you
should run "testparm -v" before starting samba to which which paths
have
changed.
I don't believe you will have any issue with TDB files. I am using an
LDAP backend so the user accounts weren't in TDB anyway. Other
databases (e.g. idmap caches) were, If you do have problems you could
probably use the old pdbedit to export to text, and the new pdbedit to
import back to TDB.
You may need to explicitly define a local unix "nobody" account to map
as the guest account
e.g.
useradd .... smbnobody
vi smb.conf
.....
guest account = smb_nobody
...
There may have been changes on how password policies function (e.g
maximum password age etc.)
On 07/08/2011 03:30 PM, Stringer Kenneth M NGA-PRTN USA CTR
wrote:> I am upgrading from 3.0.37 to 3.5.9 on the same server and need some
advice. I am running Solaris 10 on a domain server that services 10 XP and Win
7 clients. The existing Samba directory structure is not standard. I believe
the engineer who built the Solaris install transferred all Samba 2.0 directories
from the old server to the current server and then created additional
directories for the install and symbolically linked some of the old files to
the new install. Anyway, Samba is installed in two different structures on the
server: Samba and /etc/samba... and /etc/sfw.... We are using the
"sfw" directories:
>
>
>
> The smb.conf file in /etc/samba is symbolically linked to the smb.conf
file in /etc/sfw. So here are my questions:
>
> 1) How do I migrate the tdbsam database from 3.0.37 to 3.5.9?
>
> 2) Can I use the existing smb.conf file?
>
> 3) Can I just backup smb.conf and tdbsam files and reinstall to all
the default directories and then copy the backup files to the appropriate Samba
directories?
>
> 4) What else do I need to migrate?
>
>
>
> I'm sure if I just do a ./configure like the Samba web site says, my
whole team will be down until I get it fixed. There seems to be nothing in the
documentation, which is very old, to help w/ this issue. Any input to point me
in the right direction would be greatly appreciated.
>
>
>
> Thanks.
>
>
>
> Ken
>
>
>
Hello Ken and Samba Friends, On Fri, Jul 08, 2011 at 02:30:39PM -0500, Stringer Kenneth M NGA-PRTN USA CTR wrote:> I am upgrading from 3.0.37 to 3.5.9 on the same server and need some advice. I am running Solaris 10 on a domain server that services 10 XP and Win 7 clients. The existing Samba directory structure is not standard. I believe the engineer who built the Solaris install transferred all Samba 2.0 directories from the old server to the current server and then created additional directories for the install and symbolically linked some of the old files to the new install. Anyway, Samba is installed in two different structures on the server: Samba and /etc/samba... and /etc/sfw.... We are using the "sfw" directories: > > > > The smb.conf file in /etc/samba is symbolically linked to the smb.conf file in /etc/sfw. So here are my questions: > > 1) How do I migrate the tdbsam database from 3.0.37 to 3.5.9? > > 2) Can I use the existing smb.conf file? > > 3) Can I just backup smb.conf and tdbsam files and reinstall to all the default directories and then copy the backup files to the appropriate Samba directories? > > 4) What else do I need to migrate? > > > > I'm sure if I just do a ./configure like the Samba web site says, my whole team will be down until I get it fixed. There seems to be nothing in the documentation, which is very old, to help w/ this issue. Any input to point me in the right direction would be greatly appreciated. > > >When I tried to do a similar update I got (probably) stuck within an upgrade procedure of the tdbsam database. There is a file called group_mapping.tdb.upgraded although the file group_mapping.tdb is missing. Samba complains about the missing file and stops working upon smbclien -L localhost: protocol negotiation failed: NT_STATUS_PIPE_BROKEN.>From the log.smbd:<snip> [2011/07/12 11:03:16, 0] lib/util_tdb.c:tdb_log(664) tdb(/var/db/samba/group_mapping.tdb): tdb_reopen: open failed (No such file or directory) [2011/07/12 11:03:16, 0] lib/util.c:reinit_after_fork(3319) tdb_reopen_all failed. [2011/07/12 11:03:16, 0] smbd/server.c:open_sockets_smbd(570) reinit_after_fork failed. [2011/07/12 11:03:16, 0] lib/util.c:smb_panic(1633) PANIC (pid 80611): reinit_after_fork failed. [2011/07/12 11:03:16, 0] lib/util.c:log_stack_trace(1737) BACKTRACE: 4 stack frames: #0 0x122b9fd <smb_panic+93> at /usr/local/sbin/smbd #1 0x12ef709 <main+5945> at /usr/local/sbin/smbd #2 0x104abdb <_start+203> at /usr/local/sbin/smbd #3 0x104ab25 <_start+21> at /usr/local/sbin/smbd [2011/07/12 11:03:16, 0] lib/fault.c:dump_core(181) dumping core in /var/log/samba/cores/smbd </snip> Basically nobody can work with samba anylonger since then, and I do not have time to reinstall samba. I already asked for help on this list, but without any success so far. I wonder if you were succesful with the upgrade? -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, Willy ************************************* W.K. Offermans Home: +31 45 544 49 44 Mobile: +31 681 15 87 68 e-mail: Willy at Offermans.Rompen.nl
From: Thomas Harvey <tom.harvey at onefinestay.com> Date: Tue, 12 Jul 2011 13:41:24 +0100> When doing > windows administration tasks, installing software, changing > settings, I need to authenticate as an admin user. Currently, I need > to enter the local admin user and password. This is becoming a bit > of a bind, can I have a centrally stored (in the LDAP with everyone > else) admin user. I have tried the Domain Admin samba group to no > avail, I guess I want a Windows admin as opposed to a Domain admin." Domain Admins" global group automatically becomes a member of "Administrators" local group of each client if "Domain Admins" already exists. Is your "Domain Admins" global group joined to Administrators local group of each client? And is your "admin" user (a domain user) already joined to the "Domain Admins" global group? "Domain Admins" global group is enouch to your purpose, I think. Instead, you can join your "admin" user to Administrators local group of each client then "admin" user will do administration tasks. --- TAKAHASHI Motonobu <monyo at samba.gr.jp>