samba - Nov 2022 - Migrate and Update (Samba 4.1 ADDC to Samba Latest Version on different Server).

Rowland I upgraded the server to Debian 11, samba still on 4.1.

The service is reporting some errors.

I'm ready to start to update samba 4.1 to 4.16.

# service samba4 status
? samba4.service - LSB: start Samba daemons
     Loaded: loaded (/etc/init.d/samba4; generated)
     Active: active (running) since Thu 2022-11-17 16:37:55 -03; 2s ago
       Docs: man:systemd-sysv-generator(8)
    Process: 2339 ExecStart=/etc/init.d/samba4 start (code=exited,
status=0/SUCCESS)
      Tasks: 17 (limit: 4555)
     Memory: 199.1M
        CPU: 799ms
     CGroup: /system.slice/samba4.service
             ??2343 /usr/local/samba/sbin/samba -D
             ??2344 /usr/local/samba/sbin/samba -D
             ??2345 /usr/local/samba/sbin/samba -D
             ??2346 /usr/local/samba/sbin/samba -D
             ??2347 /usr/local/samba/sbin/samba -D
             ??2348 /usr/local/samba/sbin/smbd -D --option=server role
check:inhibit=yes --foreground
             ??2349 /usr/local/samba/sbin/samba -D
             ??2350 /usr/local/samba/sbin/samba -D
             ??2351 /usr/local/samba/sbin/samba -D
             ??2352 /usr/local/samba/sbin/samba -D
             ??2353 /usr/local/samba/sbin/samba -D
             ??2354 /usr/local/samba/sbin/samba -D
             ??2355 /usr/local/samba/sbin/samba -D
             ??2356 /usr/local/samba/sbin/samba -D
             ??2357 /usr/local/samba/sbin/samba -D
             ??2365 /usr/local/samba/sbin/smbd -D --option=server role
check:inhibit=yes --foreground

Nov 17 16:37:55 titan samba[2342]:   samba version 4.1.0 started.
Nov 17 16:37:55 titan samba[2342]:   Copyright Andrew Tridgell and the
Samba Team 1992-2013
Nov 17 16:37:55 titan samba4[2339]: Starting Samba 4 daemon: samba.
Nov 17 16:37:55 titan systemd[1]: Started LSB: start Samba daemons.
Nov 17 16:37:55 titan samba[2343]: [2022/11/17 16:37:55.995835,  0]
../source4/smbd/server.c:492(binary_smbd_main)
Nov 17 16:37:55 titan samba[2343]:   samba: using 'standard' process
model
Nov 17 16:37:56 titan samba[2356]: [2022/11/17 16:37:56.145464,  0]
../lib/util/util_runcmd.c:317(samba_runcmd_io_handler)
Nov 17 16:37:56 titan samba[2356]:   /usr/local/samba/sbin/samba_spnupdate:
/usr/bin/env: ?python?: No such file or directory
Nov 17 16:37:56 titan samba[2356]: [2022/11/17 16:37:56.148865,  0]
../lib/util/util_runcmd.c:317(samba_runcmd_io_handler)
Nov 17 16:37:56 titan samba[2356]:   /usr/local/samba/sbin/samba_dnsupdate:
/usr/bin/env: ?python?: No such file or directory



El mi?, 16 nov 2022 a las 14:21, Juan Ignacio (<juan.ignacio.pazos at
gmail.com>)
escribi?:
> Thx for your fast reply Rowland.
>
> About, " I would normally suggest you keep upgrading the distro to
> Bullseye (11),
> but in your case, I would pause here.
> "
> Will try to update up to bullseye dont have nothing to lose right now.
>
> I'm going to inform you after the upgrade is complete so I can start to
do
> what you suggested.
>
> Thx in advance.
>
>
> El mi?, 16 nov 2022 a las 13:27, Rowland Penny via samba (<
> samba at lists.samba.org>) escribi?:
>
>>
>>
>> On 16/11/2022 14:21, Juan Ignacio wrote:
>> > Hi Rowland and Samba Team:
>> >
>> > I finally had time to clone the old server with Debian 7 and Samba
4.1
>> > to a VM on proxmox and updated the Debian distro to Debian 10.
>>
>> I would normally suggest you keep upgrading the distro to Bullseye
(11),
>> but in your case, I would pause here.
>>
>> >
>> > I think now its time to update the Samba installation, i have vm
>> backups
>> > so im secure right now.
>> >
>> > What is the best procedure to start the update to the latest
versi?n of
>> > Samba, the server is a AD Samba 4.1 with 2 Linux Member Servers
who
>> work
>> > like file servers.
>>
>> Forget the Unix domain members in the short term, they are the least of
>> your worries.
>>
>> I would upgrade the DC's by adding a new DC on your new VM, once
this
>> has been joined and is running correctly, I would then transfer all the
>> FSMO roles to the new DC.
>>
>> Now demote every other DC, just leaving your new DC.
>>
>> Create another VM, but this time use Bullseye and Samba from Debian
>> backports, this will get 4.16.6. Repeat the procedure above, until you
>> just have a DC running Samba 4.16.6 with all the FSMO roles.
>>
>> You can now add further DC's and test the Unix domain members, they
>> should still work.
>>
>> > Is using winbind and the all the needed packages, some webapps
login
>> the
>> > users using this server.
>>
>> You may have to alter how the webapps login, but then you may not.
>>
>> Rowland
>>
>> --
>> To unsubscribe from this list go to the following URL and read the
>> instructions:  https://lists.samba.org/mailman/options/samba
>>
>

On 17/11/2022 19:42, Juan Ignacio wrote:
> Rowland I upgraded the server to Debian 11, samba still on 4.1.
Why ?
I suggested creating a new computer running Debian Bullseye (11), which 
would get you 4.13.x .
You could then join this to to your domain as a new DC.

Once everything is working correctly, you could then upgrade to 4.16.6 
by adding another new Bullseye DC running Samba from backports, this 
will get you 4.16.6

I cannot recommend the method you appear to be trying, which appears to 
be upgrading the OS (and somehow keeping the existing version of Samba)

I feel your method is bound to fail, there is just too much difference 
between 4.1.x and 4.16.6

Rowland

17.11.2022 22:42, Juan Ignacio via samba wrote:
> Rowland I upgraded the server to Debian 11, samba still on 4.1.
> 
> The service is reporting some errors.
> 
> I'm ready to start to update samba 4.1 to 4.16.
> 
> # service samba4 status
> ? samba4.service - LSB: start Samba daemons
Upgrading debian packages across releases is not supported.
You either upgrade jessie->stretch->buster->.. (if I remember
the codenames right), or you install a new server and migrate,
as Rowland suggested.  Or you remove old samba completely
(purge) and install new after upgrading the server.

While samba itself can be upgraded right to current version,
but the packaging is not prepared for this. In particular,
"samba4" startup script has been there when debian moved from samba3
to samba4. It's been renamed to "samba"
a few releases ago, and that rename has been removed in subsequent
releases. So if you upgrade from debian samba 4.1 package to
debian samba 4.16 package, you'll have two startup scripts
which will conflict with each other.
>       Loaded: loaded (/etc/init.d/samba4; generated)
>       CGroup: /system.slice/samba4.service
>               ??2343 /usr/local/samba/sbin/samba -D
usr/local/ really?

This is not a debian package.

/mjt