similar to: samba 4.7->4.8 in place upgrade

On Wed, 2018-03-14 at 16:55 -0400, Justin Foreman wrote: > Note that I turned up to -d5 but the relevant output didn't seem to change. I just cleaned up my obfuscation for clarity (all referenced DNs were identical): > > DRS replication add DN of aca72580-587e-4dab-adee-07a5f8027dfa is CN=foo,OU=bar,DC=baz > Failed to apply records: Failed to locally apply remote add of

After performing the update of samba version 4.7.3 to version 4.8.0, an error occurred while starting the service. The samba seems to have trouble finding its way through the db: Unable to determine the DomainSID, can not enforce uniqueness constraint on local domainSIDs Searching for dsServiceName in rootDSE failed: operations error at ../source4/dsdb/samdb/ldb_modules/rootdse.c:516 Failed to

same problem. Never pass the 4.8 version. samba-tool dbcheck --cross-ncs --fix Unable to determine the DomainSID, can not enforce uniqueness constraint on local domainSIDs Searching for dsServiceName in rootDSE failed: operations error at ../source4/dsdb/samdb/ldb_modules/rootdse.c:516 Failed to find our own NTDS Settings DN in the ldb! Searching for dsServiceName in rootDSE failed: operations

On Thu, August 20, 2020 16:14, Rowland penny wrote: > On 20/08/2020 20:40, James B. Byrne via samba wrote: >> FreeBSd-12.1p8 >> Samba-4.10.15 >> >> >> I have this problem: >> >> samba-tool dbcheck --cross-ncs >> Searching for dsServiceName in rootDSE failed: operations error at >> ../../source4/dsdb/samdb/ldb_modules/rootdse.c:518 >>

On 3/16/2018 10:07 AM, barış tombul via samba wrote: > same problem. > Never pass the 4.8 version. > > samba-tool dbcheck --cross-ncs --fix > Unable to determine the DomainSID, can not enforce uniqueness constraint on > local domainSIDs > > Searching for dsServiceName in rootDSE failed: operations error at > ../source4/dsdb/samdb/ldb_modules/rootdse.c:516 > Failed

As guidance, we look forward to Samba 4.8.1 for upgrade. However, the same bug remains in version 4.8.0 Again I will go back to the previous version (4.7.5) Does anyone else share this problem? samba4.service - LSB: start and stop samba4 Loaded: loaded (/etc/rc.d/init.d/samba4; bad; vendor preset: disabled) Active: active (running) since Thu 2018-04-26 16:32:31 -04; 6 minutes ago

Then I don't know what caused it. I had no problems prior to the upgrade, and the upgrade was done without errors.. Unfortunately, no, I don't have backups. 'sam.ldb' is still there, though, and so are the databases unter 'sam.ldb.d'. Yes, I tried restarting Samba, even rebooted the server but to no avail. Here are the results from running samba in the shell: lpcfg_load:

Oh, that doesn't sound good... Arch Linux. I did a regular system upgrade using pacman -Syu which automatically upgrades all packages to their latest version. I have another, practically identical system and I didn't have this issue there. Though I might have had a smaller jump between versions. On Sat, 22 Dec 2018 at 22:21, Rowland Penny via samba <samba at lists.samba.org>

Can anyone tell me in which likely version will fix this problem. If this bug will really be fixed? I noticed that it does not appear in the list of known defects of samba 4.8.0 and 4.8.1. Thank you for your help; *Atte.* *Rafael d'Ávila.* *"O único lugar onde o sucesso vem antes do trabalho é no dicionário."* Em qui, 26 de abr de 2018 às 16:55, Rowland Penny via samba <

On my primary Samba AD DC server all work ok when doing online backup, but on my secudary server I have error: ERROR(<type 'exceptions.IndexError'>): uncaught exception - list index out of range ? File "/usr/lib/python2.7/dist-packages/samba/netcmd/__init__.py", line 177, in _run ??? return self.run(*args, **kwargs) ? File

FreeBSd-12.1p8 Samba-4.10.15 I have this problem: samba-tool dbcheck --cross-ncs Searching for dsServiceName in rootDSE failed: operations error at ../../source4/dsdb/samdb/ldb_modules/rootdse.c:518 Failed to find our own NTDS Settings DN in the ldb! Searching for dsServiceName in rootDSE failed: operations error at ../../source4/dsdb/samdb/ldb_modules/rootdse.c:518 Failed to find our own NTDS

Dear all. I currently have a Centos7 box running Samba 4.6.5. I would like to increase functional level to latest one. For this reason I created another box (Ubuntu 22.04) with 4.18.9. The plan was to define Ubuntu box as an additional AD server. Once have replica of the AD, move FSMO from Centos to Ubuntu, demote the Centos server and finally increase functional level. On Ubuntu, checked

Hi: I tried to use samba 4.8.1/4.8.2 to join windows domain as DC. and saw warning message like "Unable to determine the DomainSID, can not enforce uniqueness constraint on local domainSIDs" I didn't get that message when using samba 4.7.7. is the message safe to ignore? the complete join message below: [root at samba-dc ~]# /usr/local/samba/bin/samba-tool domain join

Hello, we want to backup the AD-database with the samba-tool backup-option. We use Sernet-packages 4.9.4 we have two DCs if I do the backup on the same DC I got the following messages: ----------------- root at dc-ste-01:~# samba-tool domain backup online --server=dc-ste-01 --targetdir=. -U administrator Password for [LF\administrator]: .... Committing SAM database Setting isSynchronized and

On Wed, 12 Dec 2018 16:01:52 +0100 "peter.grotz--- via samba" <samba at lists.samba.org> wrote: > Thanks Rowland for your answer. > > these are sernet-packages from their subscription. > > There are 4 DCs (all with last sernet-rpms) 2 are demoted with probs > (dc-01 and dc-02 both centos6) and 2 are running (dc-10 and dc-11 on > centos 7) > >

On Wed, 12 Dec 2018 15:43:09 +0100 peter grotz via samba <samba at lists.samba.org> wrote: > I forgot: this is samba 4.9.3 on centos 7 Where did you get Samba 4.9.3 from ? > > Thanks > > > Hello, > > I got a problem with adding an new dc to a domain. when I try to join > I get the following: What are the other DC(s) ? Rowland

Hi, Just to reiterate an important point, the 'domain backup' command is there to backup your domain information, not your DC. If you still have a working domain, then you can recover any DC by simply rejoining it to the domain. Do not use backup/restore to recover an individual DC. If you want to recover your entire domain (i.e. power off all your DCs and start again from scratch),

On Wed, 27 Mar 2019 09:45:18 +0100 "L.P.H. van Belle via samba" <samba at lists.samba.org> wrote: > Hai, > > > I dont think one noticed this.. > > ldbsearch -H ldap://dc4 -UAdministrator > ldbsearch -H ldap://dc1 -U Administrator > > So whats the difference when you see this responce of the command: > Invalid option -U: unknown ... >

Hello, Today I tried to upgrade to samba 4.8.0, the upgrade seems to have failed, and I can't seem to fix it or back out. The issue seems to be I've lost the some KRB tickets. Here's and example of the errors i get: samba-tool domain exportkeytab /tmp/test2 samba_kdc_fetch: could not find own KRBTGT in DB: dsdb_search at ../source4/dsdb/common/util.c:4641 ERROR(runtime): uncaught

this is semi-off topic but still related to ror. i had a problem with testing my depot program (which i follow the tutorial in agile web development book). it took me many hours to solved the problem. all the while i thought i was using spaces inside the test/fixtures/products.yml programmer_book: id: 1 title: Pragmatic Programmer description: Best book