Displaying 20 results from an estimated 5000 matches similar to: "classic upgrade issue from samba 4.20"
2025 Jan 03
1
classic upgrade issue from samba 4.20
Hi Rowland
Le 03/01/2025 ? 11:30, Rowland Penny via samba a ?crit?:
> On Thu, 2 Jan 2025 16:58:09 +0100
> Arnaud FLORENT via samba <samba at lists.samba.org> wrote:
>
>> Hi and happy new year everyone
>>
>>
>> i am testing classic upgrade with recent samba versions
>>
>> everything is ok until version 4.19
>>
>>
>> but for samba
2025 Jan 03
1
classic upgrade issue from samba 4.20
On Fri, 3 Jan 2025 11:45:36 +0100
Arnaud FLORENT via samba <samba at lists.samba.org> wrote:
> Hi Rowland
>
> Le 03/01/2025 ? 11:30, Rowland Penny via samba a ?crit?:
> > On Thu, 2 Jan 2025 16:58:09 +0100
> > Arnaud FLORENT via samba <samba at lists.samba.org> wrote:
> >
> >> Hi and happy new year everyone
> >>
> >>
> >>
2025 Jan 03
1
classic upgrade issue from samba 4.20
On Thu, 2 Jan 2025 16:58:09 +0100
Arnaud FLORENT via samba <samba at lists.samba.org> wrote:
> Hi and happy new year everyone
>
>
> i am testing classic upgrade with recent samba versions
>
> everything is ok until version 4.19
>
>
> but for samba version 4.20 (4.20.6+dfsg-1~~mjt+ubt22 amd64) and 4.21,
> it fails with this message
>
>
> Failed
2013 Jul 04
1
samba-tool classic upgrade - Next rid problem
Hi there,
I am trying to upgrade my old Samba3 (with LDAP backend) to Samba 4.
I am doing this on a test VM for now as a proof of concept.
When running this command:
/usr/local/samba/bin/samba-tool domain classicupgrade
--dbdir=/home/administrator/samba3/ --use-xattrs=yes
--realm=internal.com /home/administrator/samba3/smb.conf
I get this:
Reading smb.conf
Provisioning
Exporting account
2024 Jun 27
1
Online AD Backup fails with "no auth" in 4.20?
On Thu, 27 Jun 2024 17:12:38 +0100
Luis Peromarta via samba <samba at lists.samba.org> wrote:
> I can confirm that, in order to do backups from a member server, you
> need to install samba-ad-dc in the member server running > 4.20.
>
Whilst I do have samba-ad-dc installed on my Unix domain member, I fail
to see why it would be required for 'samba-tool domain backup
2018 Jul 03
1
Classicup
Command:
samba-tool domain classicupgrade --dbdir=/etc/samba.PDC/ --realm=nemuh.cz --
dns-backend=BIND9_DLZ /etc/samba.PDC/smb.PDC.conf
...a lot of lines... and:
Following names are both user names and group names:
radix
lekarna
vema
dss
vydejzp
nagios
doprava
audio
ERROR(<class 'samba.provision.ProvisioningError'>): uncaught exception -
ProvisioningError:
2012 Dec 20
1
Changing administrator password after Samba4 classic upgrade
I used to upgrade samba3 to samba4 with almost successful with one problem,
administrator can't access. As administrator, by default it is the only
user account that is given full control over the system.
My query is how to change the administrator password? we have one account
which can join to the samba 4 AD based on the migrated data but the problem
can't change the administrator or
2013 Aug 19
1
samba-tool classicupgrade throws uncaught exception
I have a new server running CentOS 6.4 x64, which will serve as our new
Samba4 server. It is set up in a test environment, and I've copied over the
tdb files and the smb.conf file from our samba3 server (Same OS and
version).
I'm trying to do an in-place upgrade on the copied files, but keep hitting
an assert / uncaught exception during the upgrade:
# /usr/local/samba/bin/samba-tool
2013 Apr 17
1
user both missing and present
I'm trying the classicupgrade, and it is crashing out:
ERROR(<class 'samba.provision.ProvisioningError'>): uncaught exception -
ProvisioningError: Could not add member 'S-1-5-21-305843216-174882882-
1673945419-42545' to group 'S-1-5-21-305843216-174882882-1673945419-
1231' as either group or user record doesn't exist: Unable to find GUID
for DN
File
2020 May 19
2
sysvolcheck and sysvolreset errors
I have a samba DC based on Debian Buster running samba 4.12.2 from Louis' repo. A second DC on Raspbian buster is running samba
4.12.0. I have sysvol replication working using rsync/unison as per the WiKi. I wasn't having any issues until I tried to edit
a GPO and found that all the acl settings had disappeared. This may have happened when I upgraded the DCs from 4.11.x to 4.12.x
2016 Dec 09
2
Samba on Debian 8; NT4 domain, win10
On Fri, 9 Dec 2016 11:11:56 +0100
"Stefan G. Weichinger via samba" <samba at lists.samba.org> wrote:
> From: "Stefan G. Weichinger via samba" <samba at lists.samba.org>
> To: samba at lists.samba.org
> Subject: Re: [Samba] Samba on Debian 8; NT4 domain, win10
> Date: Fri, 9 Dec 2016 11:11:56 +0100
> Reply-To: "Stefan G. Weichinger"
2024 Aug 06
3
Upgrade from 4.13 to 4.20 failed
On Tue, 6 Aug 2024 20:41:51 +0200
Anders ?stling via samba <samba at lists.samba.org> wrote:
> Hello
> I have an older Debian 11 with Samba 4.13 as domain member serving som
> industrial systems with files.
> Today I decided to upgrade both Debian (to 12) and Samba (to 4.17 and
> then 4.20). The upgrade using the backport repo worked after some
> extra steps. Som
2016 Mar 19
3
classicupgrade migration issues
On Fri, Mar 18, 2016 at 4:04 PM, Andrew Bartlett <abartlet at samba.org> wrote:
> The upgrade code assumes you run on the same host. I realise now that
> folks doing an upgrade use that an an opportunity to upgrade hardware,
> and keep old systems as fallbacks, so the assumptions cause trouble.
>
> Make the new host identical in terms of the data needed to upgrade
>
2023 Mar 30
2
clients not connecting to samba shares
On 2023-03-29 15:50, Rowland Penny via samba wrote:
>
>
> On 29/03/2023 20:06, Gary Dale via samba wrote:
>>>
>> Following the advice of
>> https://wiki.samba.org/index.php/Distribution-specific_Package_Installation,
>> below the installation report after I did a more thorough purging of
>> Samba-related stuff. I took the further advice and changed the
2019 Sep 25
1
classicupgrade fails in sernet-samba 4.11 on CentOS 8, Python 3 bug?
Hi,
we might have encountered a possible python 3 bug in samba 4.11. We are
using the sernet-samba packages.
While the classicupgrade works on centos6 (using python 2) it fails on
centos8 (using python3) with a classic python3 bug message:
# samba-tool domain classicupgrade --dbdir=pdc-files/ --realm=ad.xxx.de
--dns-backend=SAMBA_INTERNAL pdc-files/smb.conf
INFO 2019-09-25 06:15:34,366 pid:12017
2019 Dec 20
4
Upgrading from Debian Stretch to Buster, Van Belle package
Ah, ok,
apt-get remove libldb1 ldb-tools
Then try again : apt install samba winbind acl
The replacement of libldb1 to libldb2 is missing something.
I'll have a look at that.
Greetz,
Louis
> -----Oorspronkelijk bericht-----
> Van: Lmloge [mailto:lmloge at orange.fr]
> Verzonden: vrijdag 20 december 2019 13:15
> Aan: L.P.H. van Belle
> CC: samba at lists.samba.org
2016 Dec 09
3
Samba on Debian 8; NT4 domain, win10
Am 2016-12-09 um 11:11 schrieb Stefan G. Weichinger via samba:
> Could not add group name=Domain Admins ((68, "samldb: Account name
> (sAMAccountName) 'Domain Admins' already in use!"))
I think this is my problem (on the old host/pdc):
# net groupmap list
Domain Admins (S-1-5-21-2777655458-4002997014-749295002-1006) -> root
Domain Guests
2024 Aug 19
1
Can't join new samba dc to existing dc
On Mon, 19 Aug 2024 15:40:15 +0700
fransnicho via samba <samba at lists.samba.org> wrote:
> Hi Rowland,
> Thanks for your response ?
>
> If I succesfully upgrade DC4 (the karoshi samba package) to samba
> 4.20, is there any posibilities that i can join the new samba machine
> (DC6) to the DC4 ?
Possibly, try it.
> If I rebuild new machine, what data will be lost
2016 Mar 18
3
classicupgrade migration issues
On Fri, Mar 18, 2016 at 2:39 PM, Andrew Bartlett <abartlet at samba.org> wrote:
> Exactly. Think about it a little - how can it determine the group
> membership, if the users/groups do not exist locally on the host doing
> the migration?
To clarify then:
Do I need both the users and groups on the new host as they are on the
old host, or just the groups? Is there any constraint
2015 Jun 04
1
error when samba-tool domain classicupgrade
When you try to upgrade on a test stand, an error occurs.
I do not understand that you need to add ldap, or improve migration script?
Before that I tried to version 4.1.7, but the error was the sam
root at dc1:~/smb_old# samba --version
Version 4.2.2-SerNet-Ubuntu-7.trusty
I also modified the file
--- ./upgrade.py 2014-10-01 00:00:00.000000000 +0600
+++