similar to: Replication failures

Hello, according to this: https://gitlab.com/samba-team/samba/merge_requests/26 samba should support DNS record scavenging is this only true for the internal DNS or also BIND? Should this work? I enabled it (dns zone scavenging = yes) to try it out and got this (didn't enable it from the DNS Manager tool as I got the error first): Jul 24 16:39:20 dc1 samba[29071]: [2019/07/24

>> >> I was able to get replication working again by deleting DNS records that were conflicting in LDAP. >> >> Used ldapcmp tool to find conflicts >> https://wiki.samba.org/index.php/Samba-tool_ldapcmp >> > > Ok, the problem seems to be back again. > > Ubuntu 16.04, samba 4.9.3 > > I’ve checked with: samba-tool ldapcmp > between dc1

Hai, Can you run this script on a good DC and the problem DC. https://raw.githubusercontent.com/thctlo/samba4/master/samba-collect-debug-info.sh Mail me both files. I'll have a quick check. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens M B via samba > Verzonden: woensdag 24 april 2019 14:48 > Aan: samba at

Hi All, I need so assistance please. Env. RHEL 7 # samba-tool -V 4.12.1-SerNet-RedHat-10.el7 bind-9.11.4-16.P2.el7_8.2.x86_64 I recently updated out Samba DC's from 4.11.7 -> 4.12.1. I then also ran # samba-tool domain schemaupgrade Updates went well without any issues, except for 1 DC it seems like. I have multiple core.* files that are created at / [root at DC3 /]# ll core.*

Hello all, some additional info: Samba version is 4.10.6 on Centos7 with sernet packages. I am using bind_dlz as dns. This happens on all DC regardless if scavening was enabled with the Windows DNS Manager. I enabled one new zone but this still happens. Replication is also not working then as the kcc seqfaults every view seconds. In the release notes it says: This support should however only be

Hi sambalist, I'm using sernet samba for several years. I found that there's error in the log.samba file like this: [2019/07/10 14:55:25.892988, 0] ../../lib/util/fault.c:79(fault_report) =============================================================== [2019/07/10 14:55:25.893187, 0] ../../lib/util/fault.c:80(fault_report) INTERNAL ERROR: Signal 11 in pid 9906

Reindl/Harald, What is your first name? Sorry for asking, but always wondered about it. I just wanted to note here that... 1) I have seen this also if samba is upgraded and not restarted. Or 2) if a packages is not upgrade because an extra package is also needed at install. And that should be tested/checked/tried out first and if that all fails, then its needed to contact sernet support.

Hi everybody, for some time now I have an issue with our samba/bind9-DLZ setup which became worse lately. I use the RSAT DNS tool to configure DNS records. In the past it sometimes happened, that DNS died when accessing the domain zone. This condition could only be resolved by restarting samba on the affected DC. Unfortunately the situation got worse and configuration/modification of entries

Hello Daniel, thank you for the fast reply. I am also using Windows 10. I'll setup a temporary Win7 VM to test if this will make any difference. Do you know if this a known issue with RSAT on Windows 10 ? Best regards Andreas Am 09.11.2018 um 11:23 schrieb Mueller: > I had this error when I did it from Windows 10. > I usede a Windows 7 PC and everything was fine again. > >

On Mon, 2020-11-09 at 14:43 +1030, O'Connor, Daniel wrote: > > Good idea. > First step is building Samba from source which is not a fun > experience on FreeBSD :( We do honestly want to make this easier. Now of course that doesn't help for a historical bisect, but we are open to and encourage up- streaming of patches from ports. (We also ask that patches we reject - this

Hi all, I am currently having some problems managing DNS on our Samba servers with bind9 backend. Whenever I try to access the AD domain zone from the MS DNS tool the DNS part crashes and services need to be restarted. After the crash DNS is not working anymore. I get the following in log.samba: [2019/09/20 09:39:10.681745,? 0]

Hi there. I'm running an AD DC in a KVM VM, a centos7 server. named is showing a very hight cpu usage, close to 100%. I just increased the number of CPUs to 2 to cope. This is a small company, with perhaps 20 workstations and another 20 linux servers. There shouldn't be that much happening. top - 17:27:48 up 2:29, 1 user, load average: 1.08, 1.13, 1.09 Tasks: 139 total, 1 running,

Hi everyone, In case anyone's interested, I've posted the rpm builds of samba 4.8.11 that I'm using on RHEL7.6. (I run these in VMs, serving as AD DCs for my SOHO). Comments most welcomed. http://nova.polymtl.ca/~coyote/dist/samba/samba-4.8.11 If you're on RHEL7/Centos7, you've got several repos to choose from: http://azzurro.ezplanet.net/el7

Hi, I'm testing samba4 alpha 12 on Ubuntu 10.04 Lucid Server I followed this HOWTO http://wiki.samba.org/index.php/Samba4/HOWTO All seems ok. Now, i want get the samba users, groups in my server with winbind I find this howto http://wiki.samba.org/index.php/Samba4/Winbind "The current installation process put the library libnss_winbind.so in <PATH_TO_SAMBA>/lib (ie.

Hi, I'm trying to create a samba4.0.1-package for ubuntu12.4. It seems as if I've succeeded to resolve the dependencies and everything is compiling and linking just fine until it switches to the source4 directory. There I always get these kerberos/heimdal-related linker-errors: default/source3/libads/kerberos_57.o: In function

We've been having issues with the samba process PANICing for some time now (approx 24 months, though the log files have rotated so I can't give an exact date). For most of this time it was an annoyance - it occurred perhaps once a fortnight and didn't cause great disruption. Around the end of 2019 the PANIC's became more frequent. When they occur machines attempting to authenticate

Hello you all, we have a 4 DC environment running on Centos7 with the Sernet-Packages. Version on all DCs is 4.9.8 (smb.conf below). We upgraded one of the DCs to 4.10.3. After a few minutes we see this in the logs: May 20 10:57:17 dc3 samba[15547]: [2019/05/20 10:57:17.200060, 0] ../../lib/util/fault.c:79(fault_report) May 20 10:57:17 dc3 samba[15547]:

Hi, I've just done a fresh install of ubuntu maverick, I added the PPA sources deb http://ppa.launchpad.net/samba-team/ppa/ubuntu maverick main deb-src http://ppa.launchpad.net/samba-team/ppa/ubuntu maverick main installed Samba4.... For some reason samba can't find libwbclient root at morannon:/etc/apt/sources.list.d# ldd -d -r /usr/sbin/samba linux-vdso.so.1 =>

On Sun, 2019-04-14 at 10:38 -0400, Nico Kadel-Garcia via samba wrote: > On Sat, Apr 13, 2019 at 11:43 PM Sérgio Basto <sergio at serjux.com> > wrote: > > > > On Sat, 2019-04-13 at 07:43 -0400, Nico Kadel-Garcia via samba > > wrote: > > > On Fri, Apr 12, 2019 at 7:20 AM Andreas Habel via samba > > > <samba at lists.samba.org> wrote: > >

Hi! Sorry my late answer. I did run the sysvolcheck/reset commands and everything seems fine. On my server I use the following rpm packages, installed from the tranquil.it repository. ldb-tools.x86_64 2.0.10-1.el7?????????????????? @samba_custom libldb.x86_64?????????????????????? 2.0.10-1.el7 @samba_custom libldb-devel.x86_64???????????????? 2.0.10-1.el7 @samba_custom