similar to: [BUG] Fail update Samba 4.8.0

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

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 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

On Thu, 26 Apr 2018 16:43:13 -0400 Rafael Oliveira d'Ávila <davilatr at gmail.com> wrote: > 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

Hi, I'm testing the in-place upgrade from 4.7.5 samba to 4.8 and unfortunately it breaks. After the upgrade samba seems to have trouble to find his way through the db: ------------------ #ldbsearch -V Version 4.8.0 #ldbsearch -H private/sam.ldb Unable to determine the DomainSID, can not enforce uniqueness constraint on local domainSIDs search error - No such Base DN: DC=example,DC=com

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 >>

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 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

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

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

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>

Hello! After upgrade Samba, dont work more. Dns is ok(I Use bind). I have Two Severs, i  updated the second(dont having fsmo). Any Help ? Regards; Information; samba -V Version 4.6.3 ----- SO: lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:    Ubuntu 14.04.2 LTS Release:        14.04 Codename:       trusty ----- Samba option: ./configure    

Hi, i have the same problem. Inplace upgrade and i get the following error. Mar 23 13:46:50 orion2 systemd[1]: Started Session 30346 of user root. Mar 23 13:46:50 orion2 systemd-logind[1316]: Removed session 30346. Mar 23 13:46:50 orion2 sernet-samba-ad[7358]: Shutting down SAMBA AD services : ..done Mar 23 13:46:50 orion2 systemd[1]: Stopped LSB: initscript for the SAMBA AD services. Mar 23

Hello guys. When checking the Samba status, an error is displayed. This error was displayed after upgrading from version 4.7.5 to version 4.7.7 I've reviewed everything and found nothing wrong. Anyone have any idea what it is? *Mai 14 08:54:47 XXXXXX.XXXXXX.COM <http://XXXXXX.XXXXXX.COM> samba[14480]: [2018/05/14 08:54:47.676288, 0]

Hi guys, My samba4 PDC (we have only one in our LAN) has crashed. I did a backup yesterday, following the instructions described here https://wiki.samba.org/index.php/Backup_and_Recovery. Now, I'm trying to restore the backup to a new server. I've performed the restore procedures but I'm getting the following errors when I try to start samba4 on the new server: Calling DNS name

Hello，I'm using samba ad dc about a year. I have 2 DCs, One is DC1 with FSMO role. And another is DC2. there's a error in DC1 when i use dbcheck tool. And samba-tool dbcheck --cross-ncs--fix can't fix that. And I made a big mistake ! In DC2 I use "tdbbackup -s .bak /var/lib/samba/private/sam.ldb" create a bak file. and using that bak file replace the sam.ldb

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

Hi Rowland, I just realized that I actually do have backups of everything in /var/lib/samba (which is the main folder for Samba on Arch). I'd still be interested how to recover from this situation without a backup but priority is to get the AD back up and running again. How would you suggest I proceed? On Sat, 22 Dec 2018 at 23:01, Viktor Trojanovic <viktor at troja.ch> wrote: >

On Tue, 24 Apr 2018 09:22:48 -0400 Rafael Oliveira d'Ávila via samba <samba at lists.samba.org> wrote: > After performing the update of samba version 4.7.3 to version 4.8.0, > an error occurred while starting the service. > > > Can someone help me? Did you solve this problem? > > I did the donwgrade for the service to work. > That is how you solve this