similar to: Samba4 won't start

Ok tomas. For a good removal of all samba packages. 1) for x in `dpkg -l | grep samba` ; do apt-get remove --purge $x ; done 2) apt-get remove --purge winbind That should clear all packages of samba. When thats done. Try the install again. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: Thomas Massip [mailto:thomas.massip at e-tera.com] > Verzonden: woensdag 27

Hi all, I try to install a samba4 AD DC, but when I try: samba-tool domain provision --use-rfc2307 --interactive I have this: Realm [DOMAINTEST.LAN]: Domain [DOMAINTEST]: Server Role (dc, member, standalone) [dc]: DNS backend (SAMBA_INTERNAL, BIND9_FLATFILE, BIND9_DLZ, NONE) [SAMBA_INTERNAL]: DNS forwarder IP address (write 'none' to disable forwarding) [127.0.1.1]:

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

Hi, after rebooting the AD DC i regularly get NT_STATUS_ADDRESS_NOT_ASSOCIATED and - as a consequence - task_server_terminate: [XXXd failed to setup interfaces] error messages in log.samba (I removed a couple of "samba: setproctitle not initialized, please either call setproctitle_init() or link against libbsd-ctor." lines for better readability): [2019/06/11 09:23:47.400171, 0]

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>

> > 1) > Aug 14 15:39:34 ceph1 dovecot: imap(account=domaintest.com): Error: > open(/var/run/dovecot/replication-notify-fifo) failed: Permission denied > > What is the correct perms for /var/run/dovecot/replication-notify-fifo ? > Currently: > # ll /var/run/dovecot/replication-notify-fifo > prw------- 1 root root 0 Aug 14 15:57 >

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:

Hi, I have a failover cluster for mail server with: Ubuntu12.04 + DRBD (for block replication) + Ext4 filesystem + Dovecot-2.0.19-2 with Mdbox It works fine with ~50k accounts. My cluster design: http://adminlinux.com.br/cluster_design.txt I plan to test Dovecot Replication with dsync to build an active/active cluster with load balancing. Can anyone direct me to some literature? A tutorial

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)

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 commands are timing out, netstat reveals that no process is listening on :53. Other than that, Samba is starting and working fine. I can list shares,

Hai Jonathan,? Only one question left then does it work now? ;-) if you added the ipv6 to hosts file? run hostname -I these ipnumers , add these in hosts and samba should always start.. Unless, your using dhcp.. that might be bit different.. greetz, ? Louis ? ? Van: Jonathan Kreider [mailto:jonathan.kreider at gmail.com] Verzonden: donderdag 17 september 2020 15:09 Aan: L.P.H. van

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>

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

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

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

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

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

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

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