[Samba] Upgrading from 3.0.37 to 3.5.9
gaiseric.vandal at gmail.com
Thu Jul 14 07:52:18 MDT 2011
On 07/14/2011 04:50 AM, Willy Offermans wrote:
> Hello Ken and Samba Friends,
> On Tue, Jul 12, 2011 at 08:32:31AM -0500, Stringer Kenneth M NGA-PRTN USA CTR wrote:
>> I have not yet attempted the upgrade so unfortunately I have no advice. I am thinking about doing a complete package removal of all previous versions and reinstalling 3.5.9. I only have 8 users, so it's no big deal for them to re-enter their passwords, as long as I back up smb.conf.
>> -----Original Message-----
>> From: Willy Offermans [mailto:Willy at Offermans.Rompen.nl]
>> Sent: Tuesday, July 12, 2011 4:08 AM
>> To: Stringer Kenneth M NGA-PRTN USA CTR
>> Cc: samba at lists.samba.org
>> Subject: Re: [Samba] Upgrading from 3.0.37 to 3.5.9
>> 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:
>> [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,
>> W.K. Offermans
>> Home: +31 45 544 49 44
>> Mobile: +31 681 15 87 68
>> e-mail: Willy at Offermans.Rompen.nl
> Yeah! I guess that it is the best solution to reinstall samba completely.
> However I will take the ``opportunity'' to move on to a LDAP+Samba
Are you sure the file is missing- or just not where samba was looking
It should be easy enough to manually recreate the group mappings -
net groupmap add ntgroup="Domain Admins" unixgroup=512 rid=512 type=domain
net groupmap add ntgroup="Domain Users" unixgroup=513 rid=513
net groupmap add ntgroup="Domain Guests" unixgroup=514 rid=514
net groupmap add ntgroup="Domain Computers" unixgroup=515 rid=515
net groupmap add ntgroup="Domain Controllers" unixgroup=516 rid=516
The ntgroups MUST use the well known RID's- it helps if the Unix groups
have the same number (or at least something that makes it easier to
match up- e.g. "....unixgroup=10512 rid=512...."
More information about the samba