samba - Sep 2004 - Best way to update old Mdk box w/2.09 to 3.06??

Mates,

    I am at the point that I will have to update my trusty samba 2.0.9 to
3.0.6 or 2.2.11. (damn SP2)  Problem is that my production machine is still
running Mandrake 7.2 and, of course, there aren't any RPMs for the old
distro. So, I guess my option is to install from source. Do I need to rpm -e
the 2.0.9 before attempting to compile and install 2.2.11 or 3.0.6? My
server is a simple server that doesn't rely on ldap, kerbose, winbind, etc.
Does is make sense to go to 3.0.6 instead of 2.2.11? Any pointers or
gotchas??

    Installing from source, is there anything other than ./configure, make,
make install and rtfm for the new smb.conf entries??

--
David C. Rankin, J.D., P.E.
RANKIN * BERTIN, PLLC
510 Ochiltree Street
Nacogdoches, Texas 75961
(936) 715-9333
(936) 715-9339 fax
www.rankin-bertin.com
--

I previously reported a problem where I was seeing all sorts of Interrupted
system call errors for the /etc/samba/smbpasswd file.  This caused some
significant temporary problems at our site in user validations.

Seems upon analysis of the various log material, and coding.....that the
Interrupted system call is legit.  It is simply indicating a timeout for the
lock request on the /etc/samba/smbpasswd file which really should not happen
but it does.

OK, in checking the system further, we find one system basically constantly
holding open / or using the passwd file for authentication for some reason
thus causing the other clients to become basically locked out.

This client has the following log entries:

[2004/09/07 18:32:52, 2] smbd/server.c:exit_server(568)
  Closing connections
[2004/09/07 18:45:32, 2] smbd/sesssetup.c:setup_new_vc_session(602)
  setup_new_vc_session: New VC == 0, if NT4.x compatible we would close all
old resources.
[2004/09/07 18:45:32, 2] smbd/sesssetup.c:setup_new_vc_session(602)
  setup_new_vc_session: New VC == 0, if NT4.x compatible we would close all
old resources.
[2004/09/07 18:45:32, 2] lib/access.c:check_access(324)
  Allowed connection from  (141.248.152.163)
[2004/09/07 18:45:32, 2] lib/access.c:check_access(324)
  Allowed connection from  (141.248.152.163)
[2004/09/07 18:45:32, 0] passdb/pdb_smbpasswd.c:mod_smbfilepwd_entry(899)
  mod_smbfilepwd_entry:  Using old smbpasswd format.  This is no longer
supported.!
[2004/09/07 18:45:32, 0] passdb/pdb_smbpasswd.c:mod_smbfilepwd_entry(900)
  mod_smbfilepwd_entry:  No changes made, failing.!
[2004/09/07 18:45:32, 0]
passdb/pdb_smbpasswd.c:smbpasswd_update_sam_account(1436)
  smbpasswd_update_sam_account: mod_smbfilepwd_entry failed!
[2004/09/07 18:45:32, 0] passdb/pdb_smbpasswd.c:mod_smbfilepwd_entry(899)
  mod_smbfilepwd_entry:  Using old smbpasswd format.  This is no longer
supported.!
[2004/09/07 18:45:32, 0] passdb/pdb_smbpasswd.c:mod_smbfilepwd_entry(900)
  mod_smbfilepwd_entry:  No changes made, failing.!
[2004/09/07 18:45:32, 0]
passdb/pdb_smbpasswd.c:smbpasswd_update_sam_account(1436)
  smbpasswd_update_sam_account: mod_smbfilepwd_entry failed!
[2004/09/07 18:47:40, 2] smbd/process.c:timeout_processing(1138)
  Closing idle connection
[2004/09/07 18:47:40, 2] smbd/server.c:exit_server(568)
  Closing connections

===================
NOTE: Both the machine and client smbpasswd entries are of the "NEW"
type as
noted by the number of fields in each entry:

client$:753:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:BDCCBA58CAE2136EE5F68206ADC748E
A:[W         ]:LCT-40F2BF93:

username:962:A8AD058EA120084B1486235A2333E4D2:11D4C351D6C291170C2D6192EB8E99
FC:[U          ]:LCT-41360DED:

Further entries in the /etc/passwd and /etc/shadow file track correctly to
the information in the samba passwd file.
I'm not sure any changes are being made here as our site (by directive
unfortunately) so I do not understand what would be changing either.

What problem are we seeing?  Any ideas what to do to fix this?




=========================================
M. D. Parker
Systems Administrator
General Atomics / Electromagnetic Systems
+1 858 455 2877
mike.parker@ga.com

David Rankin wrote:
>Mates,
>
>    I am at the point that I will have to update my trusty samba 2.0.9 to
>3.0.6 or 2.2.11. (damn SP2)  Problem is that my production machine is still
>running Mandrake 7.2 and, of course, there aren't any RPMs for the old
>distro. So, I guess my option is to install from source. Do I need to rpm -e
>the 2.0.9 before attempting to compile and install 2.2.11 or 3.0.6? My
>server is a simple server that doesn't rely on ldap, kerbose, winbind,
etc.
>Does is make sense to go to 3.0.6 instead of 2.2.11? Any pointers or
>gotchas??
>  
>
I don't know what is the best way, but one can have two
versions on the same machine if one follows certain rules.

Configure a unique --prefix=<path> and install everything
in there.
Right now I have a RH9 with the rpm samba and a reperately
compiled samba svn 3.0 prefix'd to /usr/local/samba3.

Copy the init.d or rc scripts to start/stop the installed samba
to a different name and modify it to point to the devel samba3.
export LD_LIBRARY_PATH=/usr/local/samba3 to point to the
dynamic libraries.  The loader will look there before using
/etc/ld.so.cache (which points to the old samba).
Change the PATH so the samba3 binaries come first.
Same is true for interactive sessions used to test.

On the weekends, nighttime, stop the production samba and fire up the
test samba.  Use a different netbios name to test.
export the new LD_LIBRARY_PATH and PATH on interactive sessions.
Test away.  Uncover any migration issues.  Like the format of
smbpasswd changed.
Shutdown the new samba3, restart the old samba.  Start a workday.

Can't help with the migration issues.
Someone else will have to help.

When you finally make the migration change and you don't need to go
back, rpm -e the old samba.

One note, it is critical to have current Kerberos and ldap libraries
or the AD integration either won't configure in or won't have
all the functionality to net ads join and successully interoperate
in native AD mode, so it's good you don't need it.

Regards, Doug