similar to: samba-tool domain backup offline stalls

On Wed, July 22, 2020 14:48, Rowland penny wrote: > On 22/07/2020 19:40, James B. Byrne via samba wrote: >> >> On Wed, July 22, 2020 12:35, James B. Byrne wrote: >>> FreeBSD-12.1p7 jail running Samba-4.10.15 on ZFS. >>> >>> When I run 'samba-tool domain backup offline targetdir=/tmp' I see this: >>> >>> running backup on dirs:

On Wed, July 22, 2020 12:35, James B. Byrne wrote: > FreeBSD-12.1p7 jail running Samba-4.10.15 on ZFS. > > When I run 'samba-tool domain backup offline targetdir=/tmp' I see this: > > running backup on dirs: /var/db/samba4/private /var/db/samba4 /usr/local/etc > Starting transaction on /var/db/samba4/private/secrets > I tried the backup online option instead and

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>

Hey All, I don't know what's wrong, or what I may have done wrong, but I THOUGHT I followed all the correct steps to setup samba, and it's not working. Here's what I did: D/L latest samba code (4.13.1) & extract install dependencies ./configure --prefix=/usr/local --enable-fhs (enable-fhs was required to get configure to run through completely) make make install cp

On Wed, July 22, 2020 21:47, Andrew Bartlett wrote: > Are you using DLZ_BIND9? There is a bug where it doesn't know the locking rules for those files. No. I am using the internal dns service. > Otherwise, work out which commend it is waiting on (the child) and > what lock that is waiting on (lslocks on linux is what I used to > debug this stuff). There does not appear to be

Hi all, again, I ask for your help. I have a domain with 2DC's running samba 4.10.6. The disk on the DC holding the FSMO's failed. I recovered most of it from backups, and reinstalled samba hopping to rejoin it to the domain. However, when I try # kinit administrator #samba-tool domain join eurohidra.local DC -Uadministrator I get #Could not find machine account in secrets database: Failed

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

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

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

I just upgraded one of my DCs ununtu 20.04 -> 22.04 and samba 4.18 -> 4.19, but the Dc is not yet working again. systemctl status samba-ad-dc shows: Dec 05 12:48:39 cobra samba[749]: [2023/12/05 12:48:39.562920, 0] ../../source4/samba/service_task.c:36(task_server_terminate) Dec 05 12:48:39 cobra samba[749]: task_server_terminate: task_server_terminate: [winbindd child process

OS = Ubuntu 18.04 LXD container Samba version = 4.11.12 Repo = Louis' (many thanks) I recently upgraded from 4.10.14->4.10.17->4.11.12 Now the samba-ad-dc service fails with the following upon reboot: --- root at samba:~# systemctl status samba-ad-dc ? samba-ad-dc.service - Samba AD Daemon Loaded: loaded (/lib/systemd/system/samba-ad-dc.service; enabled; vendor preset: enabled)

On Sun, 20 Nov 2016 15:55:08 -0500 Adam Tauno Williams via samba <samba at lists.samba.org> wrote: > > And it looks like nobody is listening on port 135 - > > [root at larkin26 ~]# netstat --listen --inet --program --numeric > Active Internet connections (only servers) > Proto Recv-Q Send-Q Local Address Foreign > Address State PID/Program name

I want to use samba4 in a openldap multimaster enviroment, but my tests are going bad, this are the problems: - Provision is broken for openldap: NotImplementedError: <bound method OpenLDAPBackend.post_setup of <samba.provisionbackend.OpenLDAPBackend object at 0xb626194c> - When i try to run samba i get errors like this: samba -i -M single samba version 4.0.0alpha12-GIT-c75106f

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]

05.12.2023 17:21, Joachim Lindenberg via samba: > I just upgraded one of my DCs ununtu 20.04 -> 22.04 and samba 4.18 -> 4.19, but the Dc is not yet working again. > > systemctl status samba-ad-dc shows: > > Dec 05 12:48:39 cobra samba[749]: [2023/12/05 12:48:39.562920, 0] ../../source4/samba/service_task.c:36(task_server_terminate) > Dec 05 12:48:39 cobra samba[749]:

On Sun, 2016-11-20 at 16:50 -0500, Adam Tauno Williams via samba wrote: > On Sun, 2016-11-20 at 21:11 +0000, Rowland Penny via samba wrote: > > On Sun, 20 Nov 2016 15:55:08 -0500 > > Adam Tauno Williams via samba <samba at lists.samba.org> wrote: > > > And it looks like nobody is listening on port 135 - > > > [root at larkin26 ~]# netstat --listen --inet

OK I recompiled with --with-lockdir=/var/lib/samba/lock and it's now getting further... now I'm getting this when I try to start the samba daemon: Calling SPN name update script /opt/samba/sbin/winbindd: winbindd version 4.11.2 started. /opt/samba/sbin/winbindd: Copyright Andrew Tridgell and the Samba Team 1992-2019 /opt/samba/sbin/winbindd: Failed to create directory /var/run for pid

I've been using Samba4 on Debian/Jessie since it became "stable". After the last upgrade however, I got a massive failure. The first symptom I noticed was that I couldn't grab updates from the Debian servers. However when clients tried to log in, the real problem revealed itself. They could only log on using a temporary profile and couldn't connect to any of the shares

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