similar to: samba-tool domain backup offline stalls

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

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

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 At which point samba-tool enters a permanent wait state. 86064 root 1 52 0 131M 78M wait 3 0:01 0.00%

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

On Sun, 17 Feb 2019 18:26:21 +0100 Andrea Venturoli via samba <samba at lists.samba.org> wrote: > 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

Hello. I'm running a few sites where the AD DC is a FreeBSD jail. Due to the recent CVEs, I upgraded one of them from 4.3.11 to 4.3.13 and suddenly I run into problems. I don't know whether this matters, but the upgrade involved replacing openldap-client with openldap-sasl-client. Anyway, after the new binaries were in place, Samba would not start. Relevant part of the logs (I can

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>

Rowland Penny rpenny at samba.org Fri Aug 9 15:25:00 UTC 2024 On Fri, 9 Aug 2024 10:40:18 -0400 "James B. Byrne via samba" <samba at lists.samba.org> wrote: >> I am testing samba-4.19 on FreeBSd-14.1 and am getting this error in >> the log.wb-<DOMAIN> file: >> >> ../../source3/winbindd/winbindd_dual.c:1965(winbindd_sig_term_handler) >> >>

I decided to restart the provisioning process. I stopped the samba_server, deleted /usr/local/etc/smb4.conf and /var/db/samba4. I then decided to do an interactive provisioning and this is the result: [root at smb4-1 ~ (master)]# ll /var/samba4 ; ll /usr/local/etc/smb4.conf ls: /var/samba4: No such file or directory ls: /usr/local/etc/smb4.conf: No such file or directory [root at smb4-1 ~

On FreeBSD-12.1p7 running Samba-4.10.15 I have a working test AD domain. While samba_server is confirmed stopped the 'samba-tool domain backup offline' command gives the following error: [root at smb4-1c-testfmso ~ (master)]# hostname smb4-1.brockley.harte-lyne.ca [root at smb4-1c-testfmso ~ (master)]# samba-tool domain backup offline --targetdir=/tmp ERROR(<class

On 23/07/2020 18:12, James B. Byrne via samba wrote: > > On Thu, July 23, 2020 16:16:30, Mani Wieser wrote: > >>>> ../../source4/nbt_server/interfaces.c:228(nbtd_add_socket) >>>> Failed to bind to 127.0.162.1:137 - NT_STATUS_ADDRESS_ALREADY_ASSOCIATED >> check where has port 137 occupied > There is nothing listening on 137 > > [root at smb4-2 ~

I am testing samba-4.19 on FreeBSd-14.1 and am getting this error in the log.wb-<DOMAIN> file: ../../source3/winbindd/winbindd_dual.c:1965(winbindd_sig_term_handler) I suspect that this may caused by an ip4 address assignment clash as I am using the configuration and data structures copied from our running Samba-4.13 DC. When I run winbindd interactively I see this: #

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

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 deployed has crashed again, this is the third time since > 12/17/2015 that this

On 23/07/2020 18:36, Jeremy Allison wrote: > On Thu, Jul 23, 2020 at 06:31:09PM +0100, Rowland penny via samba wrote: >> On 23/07/2020 18:12, James B. Byrne via samba wrote: >>> On Thu, July 23, 2020 16:16:30, Mani Wieser wrote: >>> >>>>>> ../../source4/nbt_server/interfaces.c:228(nbtd_add_socket) >>>>>> Failed to bind to

I built this machine, and while it isn't the most robust box in the world it has been stable otherwise. The RAID array is configured RAID1, I can't see how that could cause corruption issues and I haven't experienced any other data corruption issues apart from SAMBA collapsing. I did start seeing samba failures about two weeks ago, restarting the machine brought the domain up in

On Mon, July 13, 2020 10:23, Andrea Venturoli wrote: > On 2020-07-13 15:06, James B. Byrne wrote: > >>> Just out of curiosity, are you also using vfs_zfsacl? >> >> Yes. > > But only on DC1, AFAICT! > I see no mention of it on DC2's smb.conf. > That could be the reason why you have two different behaviour. > > bye > av. > That appears to

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

Hi, I installed Samba 4.0.13 from ports and ran.. sudo mv /usr/local/etc/samba /usr/local/etc/samba.3 sudo mv /usr/local/etc/smb.conf /usr/local/etc/smb.conf.3 sudo vi /usr/local/etc/smb.conf.3 # Add realm entry sudo mv /var/db/samba /var/db/samba.3 sudo samba-tool domain classicupgrade --dbdir=/usr/local/etc/samba.3 --use-ntvfs /usr/local/etc/smb.conf.3 When I try and start I get.. sudo samba

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]