similar to: After upgrade to 4.9.4, internal DNS no longer working

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>

Hi there. I'm trying to upgrad from 4.7.7 to 4.9.4. I built from source, running on centos 7.6 on a Raspberry Pi. When testing on a secondary DC, my "samba-tool drs showrepl" errors out with: ERROR(<class 'samba.drs_utils.drsException'>): DRS connection to dc02.rvx.is > failed - drsException: DRS connection to dc02.rvx.is failed: (8, >

so the DC with FSMO is not done first?     Van: Kristján Valur Jónsson [mailto:kristjan at rvx.is] Verzonden: vrijdag 28 december 2018 17:08 Aan: L.P.H. van Belle Onderwerp: Re: [Samba] replication failing for 4.9.4 dc01 is still running 4.7.7.  No need to restart it.  There is also still a DC03 running 4.7.7.  the only one I've upgraded is DC02.  resolv.conf on DC02 is configured with

On Sat, 22 Dec 2018 21:23:31 +0100 Viktor Trojanovic via samba <samba at lists.samba.org> wrote: > Hi list, > > I just upgraded my Samba AD DC to v4.9.4. Unfortunately, I can't > recall which version I had before that, I believe it must have been > something between 4.6 and 4.8. > > Anyway, now that the upgrade is done, it looks like DNS is gone. Host >

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 to the samba users list again. I've got an emergency here, a Samba AD DC I've got deployed has crashed again, this is the third time since 12/17/2015 that this domain has failed completely. No power outages or unexpected shutdowns, samba simply fails to start, it appears my database is yet again corrupt: [2016/03/02 11:27:17.025235, 0]

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 Wed, 26 Dec 2018 14:40:10 +0100 Viktor Trojanovic <viktor at troja.ch> wrote: > Hi Rowland, > > Thanks for taking an interest. > > On Wed, 26 Dec 2018 at 14:27, Rowland Penny via samba > <samba at lists.samba.org> wrote: > > > On Wed, 26 Dec 2018 11:43:37 +0100 > > Viktor Trojanovic <viktor at troja.ch> wrote: > > > > > I

On 02/03/16 20:46, IT Admin wrote: > Any further information required? Any troubleshooting steps? I need to > get this domain functional ASAP. > > Please advise. > > JS > On Mar 2, 2016 11:39 AM, "IT Admin" <it at cliffbells.com> wrote: > >> Hello to the samba users list again. I've got an emergency here, a Samba >> AD DC I've got

Hai, DC1, did you reboot it or just restarted services, i advice a reboot. Then on DC2. Samba internal DNS by accident? If so, stop samba, set log level = 10 Start it wait 30 sec, stop it. Now change the resolv.conf so DC1 is the first contacted. and start it again. Test again. Now im out the office in 15 min, but try this. Keep these logs, a samba dev may ask for it. Greetz,

The two systems I'm referring to are on different domains, different locations. No connection whatsoever except me being the one administering both. According to oEMInformation the server was provisioned by 4.3.3. I just checked the Samba log file and it seems that version 4.7.4 was running before the update. I'm now looking at the logs right before the upgrade and indeed, there have

Ok, you have found something, and i've seen a bit more. First, this. /usr/bin/samba_kcc: ImportError: /usr/lib/samba/libreplace-samba4.so: version `SAMBA_4.7.4' not found (required by /usr/lib/libsamba-util.so.0) [2018/12/22 19:13:45.004497, 0] There are left overs from a previous install. You are on Arch Linux as i did read. With what i've seen. Stop samba and all related

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:

I touched the two missing files /var/db/samba4/private/dns_update_list /var/db/samba4/private/spn_update_list And restarted the Samba44 service. This is what I see now: [2017/02/09 15:48:47.507874, 0] ../source4/smbd/server.c:372(binary_smbd_main) samba version 4.4.8 started. Copyright Andrew Tridgell and the Samba Team 1992-2016 [2017/02/09 15:48:47.922389, 0]

On 3/23/2018 8:50 AM, Sven Vogel via samba wrote: > 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

I am working on a FreeBSD jail (12.1p4) using samba410. I have joined this service to our existing Samab DC DOMAIN using samba-tool domain join. This worked as far as I can tell. I have these entries in smb4.conf # BOF # Global parameters [global] netbios name = SAMBA-02 realm = BROCKLEY-2016.HARTE-LYNE.CA server role = active directory domain controller workgroup = BROCKLEY-2016

I was too quick to send my previous email. It can't really be a problem of the package since I have, as mentioned, another system with the exact same setup and the exact same package versions and it all works there... On Sun, 23 Dec 2018 at 11:18, Viktor Trojanovic <viktor at troja.ch> wrote: > Yes, I tried running dbcheck (see first email), it showed 0 errors from > the start, I

Hello. On several FreeBSD 11.2/amd64 servers, I've got a jail dedicated to running Samba as an AD DC. Some days ago I upgraded one of them from 4.8.7 to 4.8.9 and suddenly everything stopped working. Since it was a production box, I immediately restored the whole jail from a backup, with no chance to better investigate. Today, with more time, I tried on another server and again I run

Hi there I have migrated from an older version of Samba DC to Samba 4.9.4 AD. Running Centos 7. One server with everything on...  (AD and file server) Bind 9.9.4 Built from source. Followed directions in the wiki. All seems to go fine, but when I startup samba-ad-dc it shows a few errors.    ([kdc failed to setup interfaces]) The initial tests (in the directions in wiki) go fine until I get to 

On Wed, July 8, 2020 04:23, Rowland penny wrote: > On 08/07/2020 08:50, Mani Wieser via samba wrote: >> >> On 07.07.2020 22:14, Mani Wieser via samba wrote: >> Found it (while having my morning walk with the dog): same as with >> SOA: this is a zone/domain thing and not record >> >> Usage: samba-tool dns delete <server> <zone> <name>