similar to: Upgrade from 4.9.8 to 4.10.3 on Centos using Sernet Packages

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

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 Cristian, Well, nothing to say about your steps, these looks good. And lmdb could be disable in the sernet packages, cant say, i dont know. And only one DC has these problems or all? If only one DC crashed. Which DC crashes. Last added? Oldest? Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Christian

Hello you all, I did some more tests used Samba 4.10.4 and still the same Problem. I also upgraded all the DCs and the problem is the same on all of them. Downgraded all of the an problem is gone. I went up to loglevel 5 an saw nothing that was related. How do I debug further? @rowland: I wrote to bugzilla-maintenance at samba.org to get an bugzilla account but haven't gotten any feedback.

> Am 20.05.2019 um 16:41 schrieb L.P.H. van Belle via samba <samba at lists.samba.org>: > > Hello Cristian, > > Well, nothing to say about your steps, these looks good. > And lmdb could be disable in the sernet packages, cant say, i dont know. > > And only one DC has these problems or all? If only one DC crashed. > Which DC crashes. Last added? Oldest? I

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

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

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

In addition to Rowland comment. if you still able to test it. Remove 1 setting at a time, restart and test it. Start with these, in this order. logging = syslog only prefork children = 8 I think if the logging line is removed your problem is solved. man smb.conf /logging should explain more. Because I cant/find the setting : logging = syslog only Greetz, Louis

Am 20.05.19 um 14:31 schrieb Rowland penny via samba: > Samba 4.10.0 was the first version that works with python3 and whilst > this may not have a bearing on your problem, is python3 installed. No python3 is installed. I would also saume that sernet would pull in python3 if needed (this did not happen). > > Of course this may not be a problem if the Sernet packages have been >

Am 20.05.19 um 15:34 schrieb Rowland penny via samba: > On 20/05/2019 14:02, Christian Naumer via samba wrote: >> Am 20.05.19 um 14:31 schrieb Rowland penny via samba: >>> Samba 4.10.0 was the first version that works with python3 and whilst >>> this may not have a bearing on your problem, is python3 installed. >> No python3 is installed. I would also saume that

Hai, A few more questions.. Is this a 32bit system or 64bit system? What is the used ldb version? ( should be 1.5.4 ) I dont know RH, so i want to see the installed packages, with this egrep. egrep "ldb|tdb|tevent|samba|winbind|talloc|lmdb|talloc|wrapper" A version running 4.9.8 and a 4.10.3 would be great to see for me. It could be related to lmdb, bre these DC's

Hi all, In attempting to build Samba 4.9.8 on CentOS 6 using mock, but using Kernel 4.19.46 as a base, Samba failed to compile spitting out the following error: [ 178/3886] Generating smbd/build_options.c [ 179/3886] Generating PKGCONFIG_netapi.pc [ 180/3886] Generating samba-passdb_empty_c [ 181/3886] Generating PKGCONFIG_smbclient.pc [ 182/3886] Generating vfs_empty_c [

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

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

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