similar to: Replication failures

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

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

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

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

I’m getting errors with replication Samba 4.9.3 on Ubuntu 16.04 6 Samba DC’s at 3 sites I recently joined a Win2k8 R2 server to the domain and promoted it to domain controller. The replication was working before that, and not working after. I didn’t realize the problems and tried to join a Win2012 R2 server and promote to DC as well. That also failed with an error about replication failures.

Sorry.. Centos.. yum update I dont know the Centos version of apt dist-upgrade. But check if ldb tdb tevent are upgrade. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > L.P.H. van Belle via samba > Verzonden: woensdag 10 juli 2019 10:12 > Aan: samba at lists.samba.org > Onderwerp: Re: [Samba] error in

Am 10.07.19 um 14:39 schrieb L.P.H. van Belle via samba: > Reindl/Harald, > > What is your first name? Sorry for asking, but always wondered about it. > I just wanted to note here that... Harald > 1) I have seen this also if samba is upgraded and not restarted. won't happen on original CentOS packages, they have restart triggers in the spec files > 2) if a packages is

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

I would suggest, downgrade to a "release" samba version. Check if it happens again.. 4.10.9-GIT-e3f51924971 < 4.10.9 is not released yet. If is also craches with 4.10.8, then submit a bug in bugzilla. (note: > ? Please read the Trouble-Shooting section of the Samba HOWTO ) ;-) Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

I had this error when I did it from Windows 10. I usede a Windows 7 PC and everything was fine again. Daniel Müller -----Ursprüngliche Nachricht----- Von: Andreas Oster via samba [mailto:samba at lists.samba.org] Gesendet: Freitag, 9. November 2018 11:16 An: samba at lists.samba.org Betreff: [Samba] Samba panic when accessing DNS domain entry with RSAT DNS tool Hi everybody, for some

I do not know. But after I did it one time from a windos 10 machine with RSAT my whole dns was broken. The only thing could cure that was to open RSAT on my windows 7 admin PC and delete the entries I added on Windows 10 and save the changes. Daniel Müller -----Ursprüngliche Nachricht----- Von: Andreas Oster [mailto:aoster at novanetwork.de] Gesendet: Freitag, 9. November 2018 11:52 An:

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]

On Mon, 18 Dec 2017 17:31:42 +0000 Kristján Valur Jónsson via samba <samba at lists.samba.org> wrote: > 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.

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

Ok, I'm following the bug https://bugzilla.samba.org/show_bug.cgi?id=13191 If there is a bug release planned I'll sit this out until then. On 18 December 2017 at 17:46, Rowland Penny via samba <samba at lists.samba.org > wrote: > On Mon, 18 Dec 2017 17:31:42 +0000 > Kristján Valur Jónsson via samba <samba at lists.samba.org> wrote: > > > Hi there. > >

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